Hacker News new | ask | show | jobs
by marcosdumay 4292 days ago
Use the Kitchen Sink[1] record type. It's more appropriated than TXT.

[1] https://tools.ietf.org/html/draft-ietf-dnsind-kitchen-sink-0...
2 comments
0x0 4292 days ago
I saw "ASN.1" in the draft and immediately thought "over-engineered".
link
jbert 4292 days ago
When bytes count (and they often don't, but in this case they probably do), what would be your preferred system? And what do you see as your favoured approach's main advantage(s) over ASN.1/BER?
link
dbrower 4292 days ago
ASN.1/BER is a pain in the ass. I'd rather gzip json. Or poke chopsticks in my eyes.

(creds: http://tools.ietf.org/html/rfc1697)

link
0x0 4292 days ago
^ What that guy said. ASN.1 parsers are super complicated and have been the cause of remote exploits more than once.
link
sitkack 4291 days ago
I'd say that is by design.
link
lionet 4290 days ago
MIBs are not ASN.1, actually.
link
ryan-c 4292 days ago
Not even an April fools' RFC. Wow.
link