3 ms·
Ask HN: What is your favorite RFC?
- Something1234 8y agoI'm working on writing a paper for a class on the DNS system. I really like rfc1035 [1]. It describes the goals, and terms involved. Also it goes into details on their design tradeoffs, and how they made it distributed. [1]: https://tools.ietf.org/html/rfc1035 https://tools.ietf.org/html/rfc1035
- ocdtrekkie 8y agoRFC1178. I take my PC naming seriously.
- jamieweb 8y agoRFC2142 - I like it when organisations use standardised email addresses such as support@ and security@ for different business units. Unfortunately many orgs either don't have these mailboxes set up, or they aren't actively monitored.
- mpweiher 8y agoA Standard for the Transmission of IP Datagrams on Avian Carriers https://www.ietf.org/rfc/rfc1149.txt https://www.ietf.org/rfc/rfc1149.txt "There is persistent delivery retry, until the carrier drops."
- DanBC 8y agoRFC 2468. https://tools.ietf.org/html/rfc2468 https://tools.ietf.org/html/rfc2468
- LinuxBender 8y agoRFC-6919 [1] The key words "MUST (BUT WE KNOW YOU WON'T)", "SHOULD CONSIDER", "REALLY SHOULD NOT", "OUGHT TO", "WOULD PROBABLY", "MAY WISH TO", "COULD", "POSSIBLE", and "MIGHT" in this document are to be interpreted as described in RFC 6919. [1] - https://tools.ietf.org/html/rfc6919 https://tools.ietf.org/html/rfc6919
- wglb 8y agoRFC 4042 which details UTF 9 in good detail.
- avianauthor 8y agoTo LinuxBender: RFC2549 also clarified the key words: MUST Usually. MUST NOT Usually not. SHOULD Only when Marketing insists. MAY Only if it doesn't cost extra.