SLP is described in RFC 2608 and RFC 3224 and implementations are available for both Solaris and Linux.

* RFC 2608, Service Location Protocol, version 2

It has been defined in RFC 2608 and RFC 3224 as Standards Track document.

According to the definitions given in the RFC 2608 specification, a location is a topologically specific and named entity on a local network of any extension, and that is not any geographic or otherwise topographic or geometric location.

* SBLIM CIM Client for Java-includes an RFC 2614 compliant SLP implementation in Java.

The Common Gateway Interface ( CGI ) is a standard ( see RFC 3875: CGI Version 1. 1 ) method for web server software to delegate the generation of web content to executable files.

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 HTTP / 1. 1 standard as defined in RFC 2068 was officially released in January 1997.

Improvements and updates to the HTTP / 1. 1 standard were released under RFC 2616 in June 1999.

* RFC 3282 Content Language Headers ( draft standard )

If an RFC is part of a proposal that is on the Standard Track, then at the first stage, the standard is proposed and subsequently organizations decide whether to implement this Proposed Standard.

A given Internet Standard, STD n, may be RFCs x and y at a given time, but later the same standard may be updated to be RFC z instead.

There exists an Internet standard, RFC 1042, for encapsulating IP version 4 traffic in IEEE 802. 2 frames with LLC / SNAP headers.

It is described in Internet standard document RFC 2460, published in December 1998.

PGP and similar products follow the OpenPGP standard ( RFC 4880 ) for encrypting and decrypting data.

A given Internet Standard, STD n, may be RFCs x and y at a given time, but later the same standard may be updated to be RFC z instead.

RFC 4098 standard defines the types of BGP-protocol routers according to the routers ' functions:

The following RFC publications by the IETF " secsh " working group document SSH-2 as a proposed Internet standard.

In RFC 1866, the initial HTML 2. 0 standard, the document character set was defined as ISO-8859-1.

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

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

Several vendors ( Cisco, Juniper, Alcatel-Lucent, Huawei, Quagga ), now implement the below two extensions to stub and NSSA area and although not covered by RFC they are considered by many to be standard features in OSPF implementations.

RFC 2616 ( Hypertext Transfer Protocol — HTTP / 1. 1 ) offers standard definitions:

This protocol-based DNS update method was documented and standardized in IETF publication RFC 2136 in 1997 and has become a standard part of the DNS protocol ( see also nsupdate program ).

* RFC 1055, which documents the SLIP " standard "

, the current reference implementation is version 4 ( NTPv4 ), which is a proposed standard as documented in RFC 5905.

The standard, officially reserved, domain name for these addresses is localhost ( RFC 2606 ).

For example, Microsoft documents their standard format to store M-JPEG in AVI files, Apple documents how M-JPEG is stored in QuickTime files, RFC 2435 describes how M-JPEG is implemented in an RTP stream, and an M-JPEG CodecID is planned for the Matroska file format.

This extension has become a proposed standard and has been assigned the number RFC 5746.

; D: The Tango standard library includes a module to create UUIDs ( v3, v4, and v5 ) according to RFC 4122.

The definitive descriptions of the rules for forming domain names appear in RFC 1035, RFC 1123, and RFC 2181.

RFC 1912 conveys basic rules for determining appropriate TTL values.

RFC 3633 added a DHCPv6 mechanism for prefix delegation.

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

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

Many clients accept both RFC 1951 and RFC 1950-formatted data for the " deflate " compressed method, but a server has no way to detect whether a client will correctly handle RFC 1950 format.

USB 3G / GPRS modems use a terminal-like interface over USB 1. 1, 2. 0 and later, data formats V. 42bis, and RFC 1144 and some models have connector for external antenna.

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.

* RFC 5226 ( BCP 26 ) Guidelines for Writing an IANA Considerations Section in RFCs

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

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

The Request for Comments RFC 1392 amplifies this meaning as " person who delights in having an intimate understanding of the internal workings of a system, computers and computer networks in particular.

The final attempt of the Hoover Administration to rescue the economy occurred in 1932 with the passage of the Emergency Relief and Construction Act, which authorized funds for public works programs and the creation of the Reconstruction Finance Corporation ( RFC ).

An Internet Standard is a special Request for Comments ( RFC ) or set of RFCs.