: the term " uniform resource name " ( URN ) has been used historically to refer to both URIs under the " urn " scheme ( RFC 2141 ), which are required to remain globally unique and persistent even when the resource ceases to exist or becomes unavailable, and to any other URI with the properties of a name.

So URNs and URLs are often complementary ; for example, you might discuss an RFC using both concepts: " you can find urn: ietf: rfc: 3187 ( URN ) over at < nowiki > http :// tools. ietf. org / html / rfc3187. html </ nowiki > ( URL ).

< dt > urn: ietf: rfc: 2648 </ dt >< dd > The URN for the IETF's RFC 2648 .</ dd >

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.

DHCPv6 was further extended to provide configuration information to clients configured using stateless address autoconfiguration in RFC 3736.

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

; 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.

The HTTP WG planned to publish new standards in December 1995 and the support for pre-standard HTTP / 1. 1 based on the then developing RFC 2068 ( called HTTP-NG ) was rapidly adopted by the major browser developers in early 1996.

The HTTP / 1. 1 standard as defined in RFC 2068 was officially released in January 1997.

* RFC 1766 + RFC 3066 Tags for the Identification of Languages ( was BCP 47 )

As SSL evolved into Transport Layer Security ( TLS ), the current version of HTTPS was formally specified by RFC 2818 in May 2000.

The RFC had minimal impact at the time, but was adopted by President Franklin D. Roosevelt and greatly expanded as part of his New Deal.

For example, in 2007 RFC 3700 was an Internet Standard — STD 1 — and in May 2008 it was replaced with RFC 5000, so RFC 3700 changed to Historic status, and STD 1 is RFC 5000.

IMAP was previously known as Internet Mail Access Protocol, Interactive Mail Access Protocol ( RFC 1064 ), and Interim Mail Access Protocol.

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 ).

It was published as RFC 1203 in 1991.

It was written specifically as a counter proposal to RFC 1176, which itself proposed modifications to IMAP2.

RFC 2132 describes the available DHCP options defined by Internet Assigned Numbers Authority ( IANA )-DHCP and BOOTP PARAMETERS.

Collectively, these stages are known as the Standards Track, and are defined in RFC 2026 and RFC 6410.

The Internet Standards Process is defined in several " Best Current Practice " documents, notably BCP 9 ( RFC 2026 and RFC 6410 ).

The current version, IMAP version 4 revision 1 ( IMAP4rev1 ), is defined by RFC 3501.

IMAP2bis did not have an extension mechanism, and POP now has one defined by RFC 2449.

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 Internet Control Message Protocol is part of the Internet Protocol Suite, as defined in RFC 792.

For stateless address autoconfiguration ( SLAAC ) to work, subnets require a / 64 address block, as defined in RFC 4291 section 2. 5. 1.

This scheme is defined in RFC 3596.

The MIME media type for JPEG is image / jpeg ( defined in RFC 1341 ), except in Internet Explorer, which provides a MIME type of image / pjpeg when uploading JPEG images.

For example as defined in RFC 4515.

The basic format of Internet email is defined in RFC 5322, which is an updated version of RFC 2822 and RFC 822.

The following example is taken from RFC 2183, where the header is defined

The filename may be encoded as defined by RFC 2231.

* RFC 4516-LDAP: Uniform Resource Locator ( Obsoletes RFC 2255 )

* RFC 3986 Uniform Resource Identifier ( URI ): Generic Syntax ( ASCII version )

* RFC 3617 – Uniform Resource Identifier ( URI ) Scheme and Applicability Statement for the Trivial File Transfer Protocol ( TFTP ), E. Lear, October 2003.

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 Resource Reservation Protocol ( RSVP ) is described in RFC 2205.

This URI will be used for looking-up and fetching the NAPTR record obtaining the called party wishes about how the call should be forwarded or terminated ( either on IP or on PSTN terminations ) – the so-called access information – which the registrant ( the called party ) has specified by writing his / her choice at the NAPTR record (" Naming Authority Pointer Resource Records " as defined in RFC 3403 ), such as e-mail addresses, a fax number, a personal website, a VoIP number, mobile telephone numbers, voice mail systems, IP-telephony addresses, web pages, GPS coordinates, call diversions or instant messaging.

* RFC 3473, " Generalized Multi-Protocol Label Switching ( GMPLS ) Signaling Resource ReserVation Protocol-Traffic Engineering ( RSVP-TE ) Extensions " ( January 2003 ).

* RFC 3936, " Procedures for Modifying the Resource reSerVation Protocol ( RSVP )" ( October 2004 ), describes current best practices and specifies procedures for modifying RSVP.

* RFC 4495, " A Resource Reservation Protocol ( RSVP ) Extension for the Reduction of Bandwidth of a Reservation Flow " ( May 2006 ), extends RSVP to enable the bandwidth of an existing reservation to be reduced instead of tearing down the reservation.

* RFC 4558, " Node-ID Based Resource Reservation Protocol ( RSVP ) Hello: A Clarification Statement " ( June 2006 ).

* RFC 4463, A Media Resource Control Protocol ( MRCP )

RFC 6494 updates SEND to use the Resource Public Key Infrastructure ( RPKI ).