RFCs are sequentially numbered, starting with RFC 1 published in 1969 (the RFC series predates the IETF). Today, there are more than 9000 documents in the series. The RFC series has two subseries, STDs and BCPs, with each numbered STD and BCP comprising one or more RFCs.

../bcp/ 12-Mar-2025 22:53 - beta/ 23-Jul-2019 05:54 - fyi/ 15-May-2019 21:34 - ien/ 15-May-2019 21:36 - inline-errata/ 08-Mar-2025 06:20 - pending-errata/ 08-Sep-2008 19:25 - prerelease/ 14-Mar-2025 23:19 - rerendered/ 19-Dec-2024 22:50 - std/ 14-Dec-2022 17:59 - 1id-guidelines.txt.pdf 27-Mar-2002 ...

Over this time, a number of changes have been made to TCP as it was specified in RFC 793, though these have only been documented in a piecemeal fashion. This document collects and brings those changes together with the protocol specification from RFC 793.

The canonical place to find RFCs is the RFC Editor Web Site. However, as we’ll see below, some key information is missing there, so most people use tools.ietf.org. Even finding the right RFC can be difficult since there are so many (currently, nearly 9,000!).

The RFC Production Center (RPC) works with authors and others to ensure documents are clear and follow the RFC Style Manual. Once an RFC is ready for publication, authors undertake a final review for errors, editorial and otherwise.

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", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. Note that the force of these words is modified ...

2023年1月1日 · RFC 9334 Remote ATtestation procedureS (RATS) Architecture Abstract. In network protocol exchanges, it is often useful for one end of a communication to know whether the other end is in an intended operating state.

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:

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 policies on an ongoing and operational basis. This includes raising support or concerns for proposed policy updates and initiating proposed policy changes ...

RFC 7636 OAUTH PKCE September 2015 This specification adds additional parameters to the OAuth 2.0 Authorization and Access Token Requests, shown in abstract form in Figure 2. A. The client creates and records a secret named the "code_verifier" and derives a transformed version "t(code_verifier)" (referred to as the "code_challenge"), which is sent in the OAuth 2.0 …