DHCP was first defined as a standards track protocol in RFC 1531 in October 1993, as an extension to the Bootstrap Protocol ( BOOTP ).

Many worked to clarify the protocol as it gained popularity, and in 1997 RFC 2131 was released, and remains the standard for IPv4 networks.

The BOOTP protocol itself was first defined in RFC 951 as a replacement for the Reverse Address Resolution Protocol RARP.

The interim protocol was quickly replaced by the Interactive Mail Access Protocol ( IMAP2 ), defined in RFC 1064 ( in 1988 ) and later updated by RFC 1176 ( in 1990 ).

Version numbers 6 through 9 were proposed for various protocol models designed to replace IPv4: SIPP ( Simple Internet Protocol Plus, known now as IPv6 ), TP / IX ( RFC 1475 ), PIP ( RFC 1621 ) and TUBA ( TCP and UDP with Bigger Addresses, RFC 1347 ).

Postel was the RFC Editor from 1969 until his death, and wrote and edited many important RFCs, including RFC 791, RFC 792 and RFC 793, which define the basic protocols of the Internet protocol suite, and RFC 2223, Instructions to RFC Authors.

RFC 1460 introduced APOP into the core protocol.

A historic RFC is one that has been made obsolete by a newer version, documents a protocol that is not considered interesting in the current Internet, or has been removed from the standards track for other reasons.

Some of these RFCs would not be published at all today ; an early RFC was often just that: a simple request for comments, not intended to specify a protocol, administrative procedure, or anything else for which the RFC series is used today.

SMTP was first defined by RFC 821 ( 1982, eventually declared STD 10 ), and last updated by RFC 5321 ( 2008 ) which includes the extended SMTP ( ESMTP ) additions, and is the protocol in widespread use today.

The SSH-2 protocol has an internal architecture ( defined in RFC 4251 ) with well-separated layers.

The protocol was designed by David P. Reed in 1980 and formally defined in RFC 768.

UDP is a minimal message-oriented Transport Layer protocol that is documented in IETF RFC 768.

Though originally an ISO standard, the IETF republished the protocol as an Internet Standard in RFC 1142.

This version of the IS-IS < em > routing </ em > protocol was then called < em > Integrated IS-IS </ em > ( RFC 1195 ).

The specification for HTTP / 1. 1 ( RFC 2616 ) specifies three compression methods: " gzip " ( RFC 1952 ; the content wrapped in a gzip stream ), " deflate " ( RFC 1950 ; the content wrapped in a zlib-formatted stream ), and " compress " ( explained in RFC 2616 section 3. 5 as ' The encoding format produced by the common UNIX file compression program " compress ".

* RFC 1952 – GZIP file format specification version 4. 3

A request line containing only the path name is accepted by servers to maintain compatibility with HTTP clients before the HTTP / 1. 0 specification in RFC 1945.

The original specification of POP3 is RFC 1081 ( 1988 ).

Its current specification is RFC 1939, updated with an extension mechanism, RFC 2449 and an authentication mechanism in RFC 1734.

The current specification is RFC 4880 ( November 2007 ), the successor to RFC 2440.

The latest version of the specification is RFC 3261 from the IETF Network Working Group published in June 2002.

The IETF published the original specification as an IETF Proposed Standard in April 1998, and subsequently published a revised specification as an IETF Proposed Standard as RFC 4566 in July 2006.

A new version of the specification was published as RFC 4632 in 2006.

GnuPG is compliant with RFC 4880, which is the current IETF standards track specification of OpenPGP.

DATR was developed in the late 1980s by Roger Evans and Gerald Gazdar, and used extensively in the 1990s ; the standard specification is contained in the Evans and Gazdar RFC, available on the Sussex website ( below ).

The original specification of RIP, defined in RFC 1058, uses classful routing.

New methods have been standardized in RFC 5389 ( October 2008 ) and the STUN acronym now represents the new title of the specification: Session Traversal Utilities for NAT.

* The extra headers are called ' pseudoheaders ' because they do not appear in the RFC 822 headers specification for email.

TIFF has not had a major update since 1992, though several Aldus / Adobe technical notes have been published with minor extensions to the format, and several specifications, including TIFF / EP ( ISO 12234-2 ), TIFF / IT ( ISO 12639 ), TIFF-F ( RFC 2306 ) and TIFF-FX ( RFC 3949 ) have been based on the TIFF 6. 0 specification.

The new addressing architecture was introduced by RFC 791 in 1981 as a part of the specification of the Internet Protocol.

* IETF: RFC 3339

* IETF RFC 5013

The etymology of foo is explored in the Internet Engineering Task Force ( IETF ) RFC 3092, which notes usage of foo in 1930s cartoons including The Daffy Doc ( with Daffy Duck ) and comic strips, especially Smokey Stover and Pogo.

; November 24, 1995: HTML 2. 0 was published as IETF RFC 1866.

The standards development of HTTP was coordinated by the Internet Engineering Task Force ( IETF ) and the World Wide Web Consortium ( W3C ), culminating in the publication of a series of Requests for Comments ( RFCs ), most notably RFC 2616 ( June 1999 ), which defines HTTP / 1. 1, the version of HTTP in common use.

* RFC 2277 ( BCP 18 ) IETF Policy on Character Sets and Languages

* RFC 2438 ( BCP 27 ) Advancement of MIB specifications on the IETF Standards Track

* RFC 3935 ( BCP 95 ) A Mission Statement for the IETF

This is remedied by a set of extensions defined by the IETF LEMONADE Working Group for mobile devices: URLAUTH ( RFC 4467 ) and CATENATE ( RFC 4469 ) in IMAP and BURL ( RFC 4468 ) in SMTP-SUBMISSION.

The IETF is overseen by the Internet Architecture Board ( IAB ), which oversees its external relationships, and relations with the RFC Editor.

The IETF Chairperson is selected by the NOMCOM process specified in RFC 3777 for a 2-year term, renewable.

IPv4 is described in IETF publication RFC 791 ( September 1981 ), replacing an earlier definition ( RFC 760, January 1980 ).

Since the inception of RFC 4875 there has been tremendous surge in interest and deployment of MPLS multicast and this has led to several new developments both in the IETF and in shipping products.

MPLS is currently ( as of March 2012 ) in use in IP-only networks and is standardized by the IETF in RFC 3031.

The main QoS-related IETF Request For Comments ( RFC ) s are Definition of the Differentiated Services Field ( DS Field ) in the IPv4 and IPv6 Headers ( RFC 2474 ), and Resource ReSerVation Protocol ( RSVP ) ( RFC 2205 ); both these are discussed above.

The IETF has also published two RFCs giving background on QoS: RFC 2990: Next Steps for the IP QoS Architecture, and RFC 3714: IAB Concerns Regarding Congestion Control for Voice Traffic in the Internet.

In computer network engineering, a Request for Comments ( RFC ) is a memorandum published by the Internet Engineering Task Force ( IETF ) describing methods, behaviors, research, or innovations applicable to the working of the Internet and Internet-connected systems.

The RFC series contains three sub-series for IETF RFCs:

; FYI: For Your Information ; informational RFCs promoted by the IETF as specified in RFC 1150 ( FYI 1 ).