The RFC series has two subseries, STDs and BCPs, with each numbered STD and BCP comprising one or more RFCs. STDs are 'Internet Standard' RFCs, and BCPs are RFCs that describe 'Best …

Search the IETF email archive Much of the daily work of the IETF is conducted on electronic mailing lists. A new mail archive tool realizing the requirements developed in RFC 6778 is now in use:

RFC 5681 and RFC 6298 describe the basic algorithms on the IETF Standards Track that are broadly applicable. Multiple other suitable algorithms exist and have been widely used.

It’s no secret that plain text RFCs are difficult to read bordering on ugly, but things are about to improve; the RFC Editor is wrapping up a new RFC format, with much more pleasing presentation and the …

The RFC Series Consulting Editor (RSCE) is a senior technical publishing professional that provides expert advice to the RFC Production Center (RPC) and RSAB on how to implement established …

Authors who follow these guidelines should incorporate this phrase near the beginning of their document: The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", …

RFC 1542 [2] details the interactions between BOOTP and DHCP clients and servers [9]. There are some new, optional transactions that optimize the interaction between DHCP clients and servers that …

This document describes them and introduces some updates to reflect current usage and requirements of RFC publication. In particular, this updated structure is intended to communicate clearly the …

RFC 2616 HTTP/1.1 June 1999 When a client or server wishes to time-out it SHOULD issue a graceful close on the transport connection. Clients and servers SHOULD both constantly watch for the other …

RFC 7636 OAUTH PKCE September 2015 Because of this, "plain" SHOULD NOT be used and exists only for compatibility with deployed implementations where the request path is already protected. …