A brief history of the RFC format (2021)(apnic.net) Geoff Huston recently discussed the processes behind putting together an RFC, and the history of why they came to be, so today we’re going to explore another aspect of what makes RFCs the way they are — their plain text format.
31 points by rdpintqogeogsaa 116 days ago | 23 comments
The “simple” 38 step journey to getting an RFC(benjojo.co.uk) The Internet is built on the mutual understanding of network protocols and practices, and most of those protocols are defined using Request For Comments (RFC) or Best Common Practices (BCP) documents.
The FIPS Compliance of HKDF(filippo.io) HKDF is an HMAC-based key-derivation function specified in RFC 5869. It’s nice and we generally like using it. FIPS (Federal Information Processing Standards) is used generally as a moniker for the set of standards, recommendations, and guidance published by the U.S. National Institute of Standards and Technology, and more specifically for FIPS 140, the standard concerning the validation of cryptographic modules.
Evil Bit(wikipedia.org) The evil bit is a fictional IPv4 packet header field proposed in a humorous April Fools' Day RFC from 2003,[1] authored by Steve Bellovin. The Request for Comments recommended that the last remaining unused bit, the "Reserved Bit"[2] in the IPv4 packet header, be used to indicate whether a packet had been sent with malicious intent, thus making computer security engineering an easy problem – simply ignore any messages with the evil bit set and trust the rest.