IETF | RFCs 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 Current Practices' for the Internet, some of which are administrative processes for the IETF
Index of rfc - Internet Engineering Task Force Explore the comprehensive index of RFCs, managed by the Internet Engineering Task Force, for insights into internet standards and protocols
Publishing and accessing RFCs - IETF 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
RFC 9334: Remote ATtestation procedureS (RATS) Architecture Not all documents approved by the IESG are candidates for any level of Internet Standard; see Section 2 of RFC 7841 ¶ Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https: www rfc-editor org info rfc9334 ¶
IETF | Internet Engineering Task Force The 2024 IETF Annual Report provides a summary of Internet Engineering Task Force (IETF), Internet Architecture Board (IAB), Internet Research Task Force (IRTF), and RFC Editor community activities from last year
How to Read an RFC - IETF If an RFC doesn’t answer your question, or you’re not sure about the intent of its text, the best thing to do is to find the most relevant Working Group and ask a question on their mailing list
RFC 2119 - Key words for use in RFCs to Indicate Requirement Levels 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
RFC Editor - IETF 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
IETF | Internet Engineering Task Force Network Working Group T Berners-Lee Request for Comments: 1738 CERN Category: Standards Track L Masinter Xerox Corporation M McCahill University of Minnesota Editors December 1994 Uniform Resource Locators (URL) Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements Please refer