RFC Request for Comments
See also IETF, Standards, Standard bodies, Security Glossary
Request for Comments (RFC) comes from the Internet Engineering Task Force
- Snippet from Wikipedia: Request for Comments
A Request for Comments (RFC) is a publication in a series from the principal technical development and standards-setting bodies for the Internet, most prominently the Internet Engineering Task Force (IETF). An RFC is authored by individuals or groups of engineers and computer scientists in the form of a memorandum describing methods, behaviors, research, or innovations applicable to the working of the Internet and Internet-connected systems. It is submitted either for peer review or to convey new concepts, information, or, occasionally, engineering humor.
The IETF adopts some of the proposals published as RFCs as Internet Standards. However, many RFCs are informational or experimental in nature and are not standards. The RFC system was invented by Steve Crocker in 1969 to help record unofficial notes on the development of ARPANET. RFCs have since become official documents of Internet specifications, communications protocols, procedures, and events. According to Crocker, the documents "shape the Internet's inner workings and have played a significant role in its success," but are not widely known outside the community.
Outside of the Internet community, other documents also called requests for comments have been published, as in U.S. Federal government work, such as the National Highway Traffic Safety Administration.
This is a partial list of RFCs (Request for Comments memoranda). A Request for Comments (RFC) is a publication in a series from the principal technical development and standards-setting bodies for the Internet, most prominently the Internet Engineering Task Force (IETF).
While there are over 9,150 RFCs as of February 2022, this list consists of RFCs that have related articles. A complete list is available from the IETF website.[1]
Numerical list For the Wikipedia process, see Wikipedia:Requests for comment. This is a partial list of RFCs (Request for Comments memoranda). A Request for Comments (RFC) is a publication in a series from the principal technical development and standards-setting bodies for the Internet, most prominently the Internet Engineering Task Force (IETF).
While there are over 9,150 RFCs as of February 2022, this list consists of RFCs that have related articles. A complete list is available from the IETF website.[2]
- RFC 1055 - A Non-Standard for Transmission of IP Datagrams Over Serial Lines: SLIP - June 1988 - SLIP
- RFC 1118 - The Hitchhikers Guide to the Internet - September 1989 - The Hitchhikers Guide to the Internet
- RFC 1119 - Network Time Protocol (version 2) specification and implementation - September 1989 - NTP v 2
- RFC 1149 - A Standard for the Transmission of IP Datagrams on Avian Carriers - April 1, 1990 - IP over Avian Carriers
- RFC 1305 - Network Time Protocol (Version 3) Specification, Implementation and Analysis - March 1992 - NTP v 3 - RFC 5905 - Obsoletes RFC 1119, RFC 1059, RFC 958
- RFC 2253 - Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names
- RFC 2427 - Multiprotocol Interconnect over Frame Relay - September 1998 - Frame Relay - 1294, 1490 -
- RFC 3401 - Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS - October 2002 - DDDS
- RFC 3403 - Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database
- RFC 3404 - Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI) Resolution Application
- RFC 3492 - Punycode: A Bootstring encoding of Unicode for Internationalized Domain Names in Applications (IDNA) - March 2003 - Punycode
- RFC 4353 - A Framework for Conferencing with the Session Initiation Protocol (SIP) - February 2006 - Conference call
- RFC 4575 - A Session Initiation Protocol (SIP) Event Package for Conference State - August 2006 - Conference call
- RFC 4655 - A Path Computation Element (PCE)-Based Architecture - August 2008 - Path computation element
- RFC 4787 - Network Address Translation (NAT) Behavioral Requirements for Unicast UDP - January 2007 - NAT
- RFC 5533 - Shim6: Level 3 Multihoming Shim Protocol for IPv6 - June 2009 - Site Multihoming by IPv6 Intermediation
- RFC 5969 - IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) - January 2010 - IPv6 rapid deployment
- RFC 6409 - Message submission for mail - November 2011 - message submission agentreplaces 2476, 4409
- RFC 6805 - The Application of the Path Computation Element Architecture to the Determination of a Sequence of Domains in MPLS and GMPLS - November 2012 - Path computation element
- RFC 7232 - Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests - June 2014 - HTTP v1.1Obsoletes 2616
- RFC 7235 - Hypertext Transfer Protocol (HTTP/1.1): Authentication - June 2014 - HTTP v1.1 - - Obsoletes 2616
- RFC 7252 - Constrained Application Protocol (CoAP) - June 2014 - Constrained Application Protocol - -
- RFC 7567 - IETF Recommendations Regarding Active Queue Management - July 2015 - Active Queue Management - -
Topical list Obsolete RFCs are indicated with struck-through text.
- Lightweight Directory Access Protocol: RFC 1487, RFC 1777, RFC 2251, RFC 2252, RFC 2253, RFC 2254, RFC 2255, RFC 2256, RFC 4510, RFC 4511, RFC 4512, RFC 4513, RFC 4514, RFC 4515, RFC 4516, RFC 4517, RFC 4518, RFC 4519, RFC 4520, RFC 4521, RFC 4522, RFC 4523, RFC 4524, RFC 4525, RFC 4526, RFC 4527, RFC 4528, RFC 4529, RFC 4530, RFC 4531, RFC 4532, RFC 4533, RFC 4534
- RFC Bibliographic Listing - Listing of bibliographic entries for all RFCs. Also notes when an RFC has been made obsolete.
© 1994 - 2024 Cloud Monk Losang Jinpa or Fair Use. Disclaimers
SYI LU SENG E MU CHYWE YE. NAN. WEI LA YE. WEI LA YE. SA WA HE.