Request for Comments: Difference between revisions

From Citizendium
Jump to navigation Jump to search
imported>J. Noel Chiappa
m (Request For Comment moved to Request for Comments over redirect: Correct case/number (according to RFC Editor))
imported>J. Noel Chiappa
(Improve accuracy)
Line 1: Line 1:
{{subpages}}
{{subpages}}


'''Request for comment''', in short '''RFC''', is a series of notes about the [[Internet]], started in 1969 (when the [[Internet]] was still the [[ARPANET]]). An Internet Document can be submitted to the [[IETF]] by anyone, but the [[IETF]] decides if the document becomes an RFC. Eventually, if it gains enough interest, it may evolve into an [[Internet standard]].
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).


Each RFC is designated by an RFC number. Once published, an RFC never changes. Modifications to an original RFC are assigned a new RFC number.
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 :
Some examples :


*SMTP ["Simple Mail Transfer Protocol". Was RFC 821 (STANDARD), Obsoleted by RFC 2821 (PROPOSED STANDARD)]
*SMTP ["Simple Mail Transfer Protocol". Was RFC 821 (STANDARD), Obsoleted by RFC 2821 (PROPOSED STANDARD)]
*HTTP ["Hypertext Transfer Protocol" -- HTTP/1.1 RFC 2616]
*HTTP ["Hypertext Transfer Protocol" -- HTTP/1.1 RFC 2616]
*BGP-4 ["A Border Gateway Protocol 4" (BGP-4) RFC 4271]
*BGP-4 ["A Border Gateway Protocol 4" (BGP-4) RFC 4271]
 


External Links
==External Links==


[http://www.ietf.org/ IETF Home Page]
* [http://www.rfc-editor.org/ RFC Editor Home Page]
** [http://www.rfc-editor.org/rfcfaq.html RFC Editor FAQs]
** [http://www.rfc-editor.org/errata.php RFC Editor Errata]
* [http://www.ietf.org/ IETF Home Page]

Revision as of 07:07, 28 May 2008

This article is a stub and thus not approved.
Main Article
Discussion
Related Articles  [?]
Bibliography  [?]
External Links  [?]
Citable Version  [?]
 
This editable Main Article is under development and subject to a disclaimer.

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

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