Request for Comments: Difference between revisions
imported>Pat Palmer (adding a paragraph about importance) |
imported>Pat Palmer (reworking the "importance" paragraph a little) |
||
| Line 3: | Line 3: | ||
A '''Request for Comments''', or '''RFC''' for short, is one of a series of documents about the [[Internet]], mostly technical, but some about policy issues. Some - but not all - are formal [[Internet standard]]s, which set the engineering specifications for the internals of the Internet. The series was started in 1969 (before the Internet existed, when its predecessor, the [[ARPANET]], was just being started). | A '''Request for Comments''', or '''RFC''' for short, is one of a series of documents about the [[Internet]], mostly technical, but some about policy issues. Some - but not all - are formal [[Internet standard]]s, which set the engineering specifications for the internals of the Internet. The series was started in 1969 (before the Internet existed, when its predecessor, the [[ARPANET]], was just being started). | ||
The first written standards for the [[Internet]], as well as the [[ARPANET]], [[NSFNET]], and other research arose from the [[Internet Engineering Task Force]] (IETF)<ref name="IETF">{{cite web|url=http://www.garykessler.net/library/ietf_hx.html|title="IETF: History, Background, and Role in Today's Internet"|publisher=Gary C. Kessler|year=1996|accessdate=2007-04-23}}</ref> | The first written standards for the [[Internet]], as well as the [[ARPANET]], [[NSFNET]], and other research arose from the [[Internet Engineering Task Force]] (IETF)<ref name="IETF">{{cite web|url=http://www.garykessler.net/library/ietf_hx.html|title="IETF: History, Background, and Role in Today's Internet"|publisher=Gary C. Kessler|year=1996|accessdate=2007-04-23}}</ref> RFC process. IETF was born in the late 1960s as a result of the U. S. Advanced Research ([[ARPA]]) initiative, and leading eventually to the development of the [[Internet]]. The open nature of the IETF standards-seeking process, in which any person could submit, or comment upon, a [[Request for Comments]], or ''RFC'') was remarkable, and the IETF proved to be about as effective as formally endorsed standards bodies at creating usable and widely adopted standards. The non-proprietary nature of the RFC process also foreshadowed the later development, in the 1980's, of the [[open source software]] movement. Some standards also resulted from a deliberate sharing of specifications by industry participants, notably the open specifications leading to the industry-wide [[IBM compatible PC]] beginning in the early 1980's. | ||
Most RFCs, including all formal Internet standards, are produced by the [[IETF]]. A document can also be submitted to the [[RFC Editor]] by anyone (after being published as an [[ Internet Draft]]), but it is up to the RFC editor (who usually checks with the IETF) whether or not to accept it. Eventually, if it gains enough interest, it may evolve into an Internet standard. | Most RFCs, including all formal Internet standards, are produced by the [[IETF]]. A document can also be submitted to the [[RFC Editor]] by anyone (after being published as an [[ Internet Draft]]), but it is up to the RFC editor (who usually checks with the IETF) whether or not to accept it. Eventually, if it gains enough interest, it may evolve into an Internet standard. | ||
Revision as of 20:24, 8 October 2008
A Request for Comments, or RFC for short, is one of a series of documents about the Internet, mostly technical, but some about policy issues. Some - but not all - are formal Internet standards, which set the engineering specifications for the internals of the Internet. The series was started in 1969 (before the Internet existed, when its predecessor, the ARPANET, was just being started).
The first written standards for the Internet, as well as the ARPANET, NSFNET, and other research arose from the Internet Engineering Task Force (IETF)[1] RFC process. IETF was born in the late 1960s as a result of the U. S. Advanced Research (ARPA) initiative, and leading eventually to the development of the Internet. The open nature of the IETF standards-seeking process, in which any person could submit, or comment upon, a Request for Comments, or RFC) was remarkable, and the IETF proved to be about as effective as formally endorsed standards bodies at creating usable and widely adopted standards. The non-proprietary nature of the RFC process also foreshadowed the later development, in the 1980's, of the open source software movement. Some standards also resulted from a deliberate sharing of specifications by industry participants, notably the open specifications leading to the industry-wide IBM compatible PC beginning in the early 1980's.
Most RFCs, including all formal Internet standards, are produced by the IETF. A document can also be submitted to the RFC Editor by anyone (after being published as an Internet Draft), but it is up to the RFC editor (who usually checks with the IETF) whether or not to accept it. Eventually, if it gains enough interest, it may evolve into an Internet standard.
Each RFC is designated by an RFC number. Once published, an RFC never changes (although there are now errata sheets for them). Modifications to an original RFC are assigned a new RFC number.
Some examples :
- SMTP ["Simple Mail Transfer Protocol". Was RFC 821 (STANDARD), Obsoleted by RFC 2821 (PROPOSED STANDARD)]
- HTTP ["Hypertext Transfer Protocol" -- HTTP/1.1 RFC 2616]
- BGP-4 ["A Border Gateway Protocol 4" (BGP-4) RFC 4271]
External Links
- ↑ "IETF: History, Background, and Role in Today's Internet". Gary C. Kessler (1996). Retrieved on 2007-04-23.