* RFC 2148 — Deployment of the Internet White Pages Service

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

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

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

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

* RFC 3932 ( BCP 92 ) The IESG and RFC Editor Documents: Procedures

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

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

* RFC 4520 ( also BCP 64 )-Internet Assigned Numbers Authority ( IANA ) Considerations for the Lightweight Directory Access Protocol ( LDAP ) ( replaced RFC 3383 )

* RFC 4521 ( also BCP 118 )-Considerations for Lightweight Directory Access Protocol ( LDAP ) Extensions

; STD: Standard ; this used to be the third and highest maturity level of the IETF standards track specified in RFC 2026 ( BCP 9 ).

In 2011 RFC 6410 ( a new part of BCP 9 ) reduced the standards track to two maturity levels.

Best Current Practices work in a similar fashion ; BCP n refers to a certain RFC or set of RFCs, but which RFC or RFCs may change over time.

The BCP series also covers technical recommendations for how to practice Internet standards ; for instance the recommendation to use source filtering to make DoS attacks more difficult ( RFC 2827: " Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing ") is BCP 38.

Address assignments from within this range are specified in RFC 5771, an Internet Engineering Task Force ( IETF ) Best Current Practice document ( BCP 51 ).

* RFC 2014 ( BCP 8 ) describes more fully the guidelines and procedures of the IRTF Research Groups.

RFC 2026 belongs to a set of RFCs collectively known as BCP 9 ( Best Common Practice, an IETF policy ).

RFC 2026 was later updated by BCP 78 and 79 ( among others ).

As of 2011 BCP 78 is RFC 5378 ( Rights Contributors Provide to the IETF Trust ), and BCP 79 consists of RFC 3979 ( Intellectual Property Rights in IETF Technology ) and a clarification in RFC 4879.

Stephen D. Crocker ( born October 15, 1944 in Pasadena, California ) is the inventor of the Request for Comments series, authoring the very first RFC and many more.

Telnet was developed in 1969 beginning with RFC 15, extended in RFC 854, and standardized as Internet Engineering Task Force ( IETF ) Internet Standard STD 8, one of the first Internet standards.

The required media access control is taken from IEEE 802. 15. 4, a radio standard, and the required link layer is based on the mesh network standard AODV, formalized as RFC 3561.

Posted to France with just 15 hours solo, he first flew in combat in September 1916 with 169 Squadron, RFC, ( commanded by Major Paynter ).

The first game held at the stadium was Llanelli RFC versus Cardiff RFC held on 15 November 2008.

Unstoppable in the league, Gloucester RFC reached the inaugural Championship final 15 points clear of their nearest rival, however under the new league system Gloucester RFC were ' rewarded ' with a 3 week lay-off, while Wasps played regular rugby during the 3 weeks as a result Gloucester RFC lost their momentum and were crushed emphatically by Wasps at Twickenham.

Grove RFC has a large Youth section, across twelve Mini ( mixed, Under-7 to Under-12 ) and Junior groups ( Under-13 to Under-18 ; including two Girls ' -- Under 15 and Under 18 ), consistently has among the best Colts sides in the area, and has long had a policy of bringing through players from the Colts to the senior sides.

Educated at Bryn Celynnog Comprehensive school in Beddau, Jenkins first played rugby union aged 13 at Beddau RFC based in Pontypridd, starting out as a flanker but was pushed forward into the front row at age 15.

** 15 February-The Joint War Air Committee is established to co-ordinate the activities of the RFC and RNAS.

Between 1945 and June 1947, the RFC, War Assets Corporation and the War Assets Administration ( disposal function of the RFC was transferred to WAC on January 15, 1946, and to the WAA in March 1946 ) processed approximately 61, 600 World War II aircraft, of which 34, 700 were sold for flyable purposes and 26, 900, primarily combat types, were sold for scrapping.

Due to widespread and persistent ignorance of HTTP < tt > charset =</ tt > over the Internet ( at its server side ), WWW Consortium disappointed in HTTP / 1. 1 ’ s strict approach and encourages browser developers to use some fixes in violation of RFC 2616.

The original specifications were published by the Internet Engineering Task Force in RFC 882 and RFC 883, which were superseded in November 1987 by RFC 1034 and RFC 1035.

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

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.

Notably, Internet Explorer versions 6, 7, and 8 report deflate support but do not actually accept RFC 1950 format, making actual use of deflate highly unusual.

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.

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

An RFC that is to become a Standard or part of a Standard begins as an Internet Draft, and is later ( usually after several revisions ) accepted and published by the RFC Editor as a RFC and labeled a Proposed Standard.

Later, an RFC can be labeled Internet Standard.

), the RFC can advance to Internet Standard.

In October 2011 RFC 6410 in essence merged this second and the third Internet Standard maturity level for future Internet Standards.

If an RFC becomes an Internet Standard ( STD ), it is assigned an STD number but retains its RFC number.

When an Internet Standard is updated, its number stays the same and it simply refers to a different RFC or set of RFCs.

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.

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.