| word looked up : | home / archive |
Request for comment : RFCRequest for comment. One of a series, begun in 1969, of numbered Internet informational documents and standards widely followed by commercial software and freeware in the Internet and Unix communities. Few RFCs are standards but all Internet standards are recorded in RFCs. Perhaps the single most influential RFC has been RFC 822, the Internet electronic mail (email) format standard.The RFCs issued by the IETF and its predecessors are the most well-known series known as 'RFC', and is almost always what is meant by RFC without further qualification; however, other organizations have in the past also issued series called 'RFCs'. The RFCs are unusual in that they are floated by technical experts acting on their own initiative and reviewed by the Internet at large, rather than formally promulgated through an institution such as ANSI. For this reason, they remain known as RFCs even once adopted as standards. The RFC tradition of pragmatic, experience-driven, after-the-fact standard writing done by individuals or small working groups has important advantages over the more formal, committee-driven process typical of ANSI or ISO. Emblematic of some of these advantages is the existence of a flourishing tradition of "joke" RFCs. Usually at least one a year is published, usually on April Fool's Day. The RFCs are most remarkable for how well they work - they manage to have neither the ambiguities that are usually rife in informal specifications, nor the committee-perpetrated misfeatures that often haunt formal standards, and they define a network that has grown to truly worldwide proportions. RFC 1, entitled "Host Software", was issued on April 7, 1969 by Steve Crocker. For more details about RFCs and the RFC process, see RFC 2026, "The Internet Standards Process, Revision 3" A complete RFC index in text format (http://www.ietf.org/iesg/1rfc_index.txt) is available from the IETF website, but because of its length, it is impractical to include it in the Wikipedia. The text of any particular RFC can be found by entering its number at http://www.ietf.org/rfc.html (http://www.ietf.org/rfc.html). Here is the list of the most important RFCs: 2026, 2045, 2046, 2047, 2048, 2049, 2083 2116, 2126, 2156, 2181, 2183, 2184 3008, 3023, 3066, 3094, 3097, 3098 See also: FYI, Internet standard, BCP partially based on FOLDOC
External links
copy. If you received it electronically, such person may.html">may.html">may
receive it electronically.
THIS ETEXT IS OTHERWISE PROVIDED TO YOU "AS-IS". NO OTHER
TO THE ETEXT OR ANY MEDIUM IT MAY BE ON, INCLUDING BUT NOT
PARTICULAR PURPOSE.
Some states do not allow disclaimers of implied warranties or
above disclaimers and exclusions may not apply to you, and you
You will indemnify and hold the Project, its directors,
and expense, including legal fees, that arise directly or
[1] distribution of this etext, [2] alteration, modification,
You may distribute copies of this etext electronically, or by
"Small Print!" and all other references to Project Gutenberg,
requires that you do not remove, alter or modify the
if you wish, distribute this etext in machine readable
including any form.html">form.html">form resulting from conversion by word pro-
*EITHER*:
[*] The etext, when displayed, is clearly readable, and
intended by the author of the work, although tilde
be used to convey punctuation intended by the
indicate hypertext links; OR
[*] The etext may be readily converted by the reader at
form by the program that displays the etext (as is
OR
[*] You provide, or agree to also provide on request at
etext in its original plain ASCII form (or in EBCDIC
"Small Print!" statement.
[3] Pay a trademark license fee to the Project of 20% of the
already use to calculate your applicable taxes. If you
payable to "Project Gutenberg Association/Carnegie-Mellon
. All is still licensed under the GNU FDL.
|
|
|||||