Which RFCs do you think most developers should read?

Question

Some RFCs are complex and esoteric, and some are approachable educational, and rewarding even for generalists or non-experts.As an example I felt that RFC 1034 ("DOMAIN NAMES - CONCEPTS AND FACILITIES") [0] was well worth reading.Which RFCs do you think most developers would benefit from reading through in their entirety (or close to)?[0] https://www.rfc-editor.org/rfc/rfc1034

L81132 · Accepted Answer

Easy question -- everyone MUST read https://www.rfc-editor.org/rfc/rfc2119.Seriously, once you get clarity and precision around these words, sloppy writing will make you cringe.

drpixie · Answer

Probably none.RFCs are about implementation specifics and details. Developers should be aware they exist, but don't waste your time until you need to implement or use something specific.Better to spend your time getting a good general understanding of machine-code and assembler, compilers, network protocols, database mechanisms, etc. Then you'll be able to make sense of, and maybe implement, RFCs.

zgs · Answer

RFC 1149 is worthwhile. It's followup, RFC 2549, rather less so.I've read lots of RFCs over the years and had too implement (too) many.

Which RFCs do you think most developers should read?

Easy question -- everyone MUST read https://www.rfc-editor.org/rfc/rfc2119.
Seriously, once you get clarity and precision around these words, sloppy writing will make you cringe.

RFC 1149 is worthwhile. It's followup, RFC 2549, rather less so.
I've read lots of RFCs over the years and had too implement (too) many.