Request for comment
Request 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 Internet Engineering Task Force (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.
Here is the list of the most important RFCs:
RFC 0822 RFC 0823 RFC 0824 RFC 0825
RFC 0983, RFC 0985, RFC 0987
RFC 1006, RFC 1009, RFC 1066
RFC 1123, RFC 1149, RFC 1156
RFC 1495
RFC 1521
RFC 1632
RFC 1718,
RFC 1776, RFC 1789, RFC 1792
RFC 1809, RFC 1812, RFC 1876, RFC 1889
RFC 1918, RFC 1969
RFC 2026, RFC 2045, RFC 2046, RFC 2047, RFC 2048, RFC 2049, RFC 2083
RFC 2116, RFC 2126, RFC 2156, RFC 2181, RFC 2183, RFC 2184
RFC 2223, RFC 2231
RFC 2326, RFC 2327
RFC 2401, RFC 2419, RFC 2420, RFC 2421
RFC 2525, RFC 2535, RFC 2543, RFC 2549
RFC 2644, RFC 2645, RFC 2646
RFC 2747, RFC 2748, RFC 2749
RFC 2822
RFC 3008, RFC 3023, RFC 3066, RFC 3094, RFC 3097, RFC 3098
RFC 3106, RFC 3114, RFC 3115
RFC 3261
Generic RFC's
* RFC 0825, Request for comments on Requests For Comments. Jon Postel.
Nov-01-1982. (Format: TXT=4255 bytes) (Obsoleted by RFC 1111, RFC 1543,
RFC 2223) (Status: UNKNOWN)
* RFC 2223, Instructions to RFC Authors. Jon Postel, Joyce K. Reynolds.
October 1997. (Format: TXT=37948 bytes) (Obsoletes RFC 1543, RFC 1111,
RFC 0825) (Status: INFORMATIONAL)
* RFC 1718, The Tao of IETF - A Guide for New Attendees of the Internet
Engineering Task Force. The IETF Secretariat, G. Malkin. November 1994.
(Format: TXT=50477 bytes) (Obsoletes RFC 1539) (Also FYI0017) (Status:
INFORMATIONAL)
* RFC 2026, The Internet Standards Process -- Revision 3. Scott O.
Bradner. October 1996. (Format: TXT=86731 bytes) (Obsoletes RFC 1602)
(Also BCP0009) (Status: BEST CURRENT PRACTICE)
Link-Level RFC's
* RFC 1969, The PPP DES Encryption Protocol (DESE). K. Sklower, G. Meyer.
June 1996. (Format: TXT=20383 bytes) (Obsoleted by RFC 2419) (Status:
INFORMATIONAL)
* RFC 2419, The PPP DES Encryption Protocol, Version 2 (DESE-bis). K.
Sklower, G. Meyer. September 1998. (Format: TXT=24414 bytes) (Obsoletes
RFC 1969) (Status: PROPOSED STANDARD
Internetwork-Level RFC's
* RFC 791, Internet Protocol. J. Postel. Sep-01-1981. (Format: TXT=97779
bytes) (Obsoletes RFC0760) (Also STD0005) (Status: STANDARD)
* RFC 3115, Mobile IP Vendor/Organization-Specific Extensions. G.
Dommety, K. Leung. April 2001. (Format: TXT=16363 bytes) (Obsoletes RFC
3025) (Status: PROPOSED STANDARD)
* RFC 1809, Using the Flow Label Field in IPv6. C. Partridge. June 1995.
(Format: TXT=13591 bytes) (Status: INFORMATIONAL)
This is about using the flow label field in IPv6. This document is
merely a suggestion and does not contain any standards in it. The
current standard for flow labels in IPv6 is described in RFC 3595 here.
* RFC 2644, Changing the Default for Directed Broadcasts in Routers. D.
Senie. August 1999. (Format: TXT=6820 bytes) (Updates RFC 1812) (Also
BCP0034) (Status: BEST CURRENT PRACTICE)
Host/Router Requirements RFC's
* RFC 0985, Requirements for Internet gateways - draft. National Science
Foundation, Network Technical Advisory Group. May-01-1986. (Format:
TXT=59221 bytes) (Obsoleted by RFC 1009) (Status: UNKNOWN)
* RFC 1009, Requirements for Internet gateways. R.T. Braden, Jon Postel.
Jun-01-1987. (Format: TXT=128173 bytes) (Obsoletes RFC 0985) (Obsoleted
by RFC 1812) (Status: HISTORIC)
* RFC 1122, Requirements for Internet Hosts - Communication Layers.
Robert Braden (editor). October 1989. (Format: TXT=295992 bytes) (Also
STD0003) (Status: STANDARD)
* RFC 1123, Requirements for Internet Hosts - Application and Support.
Robert Braden (editor). October 1989. (Format: TXT=245503 bytes)
(Updates RFC 0822) (Updated by RFC 2181) (Also STD0003) (Status:
STANDARD)
* RFC 1812, Requirements for IP Version 4 Routers. F. Baker. June 1995.
(Format: TXT=415740 bytes) (Obsoletes RFC 1716, RFC 1009) (Updated by
RFC 2644) (Status: PROPOSED STANDARD)
ISO Interoperation RFC's
* RFC 983, ISO transport arrives on top of the TCP. D.E. Cass, Marshall
T. Rose. Apr-01-1986. (Format: TXT=59819 bytes) (Obsoleted by RFC 1006)
(Status: UNKNOWN)
* RFC 1006, ISO transport services on top of the TCP: Version 3. M.T.
Rose, D.E. Cass. May-01-1987. (Format: TXT=31935 bytes) (Obsoletes RFC
0983) (Updated by RFC 2126) (Also STD0035) (Status: STANDARD)
* RFC 2126, ISO Transport Service on top of TCP (ITOT). Y. Pouffary, A.
Young. March 1997. (Format: TXT=51032 bytes) (Updates RFC 1006)
(Status: PROPOSED STANDARD)
Domain Name System RFC's
* RFC 1876, A Means for Expressing Location Information in the Domain
Name System. C. Davis, Paul Vixie, T. Goodwin, I. Dickinson. January
1996. (Format: TXT=29631 bytes) (Updates RFC 1034, RFC 1035) (Status:
EXPERIMENTAL)
* RFC 2181, Clarifications to the DNS Specification. Robert Elz, Randy
Bush. July 1997. (Format: TXT=36989 bytes) (Updates RFC 1034, RFC 1035,
RFC 1123) (Updated by RFC 2535) (Status: PROPOSED STANDARD)
This covers the operation of secondary domain name servers.
* RFC 2535, Domain Name System Security Extensions. Donald E. Eastlake
3rd. March 1999. (Format: TXT=110958 bytes) (Obsoletes RFC 2065)
(Updates RFC 2181, RFC 1035, RFC 1034) (Updated by RFC 2931, RFC 3007,
RFC 3008) (Status: PROPOSED STANDARD)
* RFC 3008, Domain Name System Security (DNSSEC) Signing Authority. B.
Wellington. November 2000. (Format: TXT=13484 bytes) (Updates RFC 2535)
(Status: PROPOSED STANDARD)
X.500 RFC's
* RFC 1632, A Revised Catalog of Available X.500 Implementations. A.
Getchell, S. Sataluri, Editors. May 1994. (Format: TXT=124111 bytes)
(Obsoletes RFC 1292) (Obsoleted by RFC 2116) (Status: INFORMATIONAL)
* RFC-2116, X.500 Implementations Catalog-96. C. Apple, K. Rossen. April
1997. (Format: TXT=243994 bytes) (Obsoletes RFC 1632) (Also FYI0011)
(Status: NFORMATIONAL)
Network Management RFC's
* RFC 1066, Management Information Base for network management of
TCP/IP-based internets. K. McCloghrie, Marshall T. Rose. Aug-01-1988.
(Format: TXT=135177 bytes) (Obsoleted by RFC 1156) (Status: UNKNOWN)
* RFC 1156, Management Information Base for network management of
TCP/IP-based internets. K. McCloghrie, Marshall T. Rose. May-01-1990.
(Format: TXT=138781 bytes) (Obsoletes RFC 1066) (Status: HISTORIC)
* RFC 1792, TCP/IPX Connection Mib Specification. T. Sung. April 1995.
(Format: TXT=16389 bytes) (Status: EXPERIMENTAL)
E-Mail RFC's
* RFC 0822, Standard for the format of ARPA Internet text messages. David
H. Crocker. Aug-13-1982. (Format: TXT=109200 bytes) (Obsoletes RFC
0733) (Obsoleted by RFC 2822) (Updated by RFC 1123, RFC 1138, RFC 1148,
RFC 1327, RFC 2156) (Status: HISTORIC)
This is an important early RFC from the IETF that specified the format
of e-mail messages exchanged between computers on the Internet. Many
additions have been made to it, but it remained a standard for many
years until obsoleted by RFC 2822 (the number is not a coincidence: it
was reserved for this use).
* RFC 2822, Internet Message Format. Peter W. Resnick, Editor. April
2001. (Format: TXT=110695 bytes) (Obsoletes RFC 0822) (Status: PROPOSED
STANDARD)
This standard specifies a syntax for text messages that are sent
between computer users, within the framework of electronic mail
messages. This standard is about text-only messages. The syntax for
sending other types of messages, such as binary or structured data, is
specified as an extension of this standard by the MIME document series:
RFC 2045, RFC 2046, RFC 2049.
* RFC 3098, How to Advertise Responsibly Using E-Mail and Newsgroups or -
how NOT to $$$$$ MAKE ENEMIES FAST! $$$$$. E. Gavin, D. Eastlake 3rd,
S. Hambridge. April 2001. (Format: TXT=64687 bytes) (Also FYI0038)
(Status: INFORMATIONAL)
X.400 E-Mail RFC's
* RFC 0987, Mapping between X.400 and RFC 822. S.E. Kille. Jun-01-1986.
(Format: TXT=127540 bytes) (Obsoleted by RFC 1327, RFC 2156) (Updated
by RFC 1026, RFC 1138, RFC 1148) (Status: UNKNOWN)
* RFC 1495 Mapping between X.400 and RFC-822 Message Bodies. Harald Tveit
Alvestrand, Steve Kille, R. Miles, Marshall T. Rose, S. Thompson.
August 1993. (Format: TXT=20071 bytes) (Obsoleted by RFC 2156) (Updates
RFC 1327) (Status: PROPOSED STANDARD)
* RFC 2156, MIXER (Mime Internet X.400 Enhanced Relay): Mapping between
X.400 and RFC 822/MIME. Steve Kille. January 1998. (Format: TXT=280385
bytes) (Obsoletes RFC 0987, RFC 1026, RFC 1138, RFC 1148, RFC 1327, RFC
1495) (Updates RFC 0822) (Status: PROPOSED STANDARD)
MIME RFC's
* RFC 1521, MIME (Multipurpose Internet Mail Extensions) Part One:
Mechanisms for Specifying and Describing the Format of Internet Message
Bodies. N. Borenstein, N. Freed. September 1993. (Format: TXT=187424,
PS=393670, PDF=205091 bytes) (Obsoletes RFC 1341) (Obsoleted by RFC
2045, RFC 2046, RFC 2047, RFC 2048, RFC 2049) (Updated by RFC 1590)
(Status: DRAFT STANDARD)
* RFC 2045, Multipurpose Internet Mail Extensions (MIME) Part One: Format
of Internet Message Bodies. N. Freed, N. Borenstein. November 1996.
(Format: TXT=72932 bytes) (Obsoletes RFC 1521, RFC 1522, RFC 1590)
(Updated by RFC 2184, RFC 2231) (Status: DRAFT STANDARD)
* RFC 2046, Multipurpose Internet Mail Extensions (MIME) Part Two: Media
Types. N. Freed, N. Borenstein. November 1996. (Format: TXT=105854
bytes) (Obsoletes RFC 1521, RFC 1522, RFC 1590) (Updated by RFC 2646)
(Status: DRAFT STANDARD)
* RFC 2047, MIME (Multipurpose Internet Mail Extensions) Part Three:
Message Header Extensions for Non-ASCII Text. K. Moore. November 1996.
(Format: TXT=33262 bytes) (Obsoletes RFC 1521, RFC 1522, RFC 1590)
(Updated by RFC 2184, RFC 2231) (Status: DRAFT STANDARD)
RFC 2047 specifies a standard way of encoding non US-ASCII characters
into a string that identifies both the character set to use and the
actual characters. The result of the encoding will be US-ASCII, and can
be transmitted in Internet mail and decoded appropriately on the
receiving end. This encoding is necessary in the first place because
many characters in non-English languages can not be represented in
7-bit ASCII.
There are some mail clients that are not RFC 2047 Compliant, if you are
using one of this clients you are strongly encuraged to change your
mail client or to update it to a compliant version:
Eudora 4: Double quote characters are encoded with a Windows codpage
and are eight-bit characters. Eudora's MIME headers indicate the MIME
type but not 8-bit encoding. Suggest enabling "quoted printable"
encoding.
* RFC 2048, Multipurpose Internet Mail Extensions (MIME) Part Four:
Registration Procedures. N. Freed, J. Klensin, Jon Postel. November
1996. (Format: TXT=45033 bytes) (Obsoletes RFC 1521, RFC 1522, RFC
1590) (Updated by RFC 3023) (Also BCP0013) (Status: BEST CURRENT
PRACTICE)
* RFC 2049, Multipurpose Internet Mail Extensions (MIME) Part Five:
Conformance Criteria and Examples. N. Freed, N. Borenstein. November
1996. (Format: TXT=51207 bytes) (Obsoletes RFC 1521, RFC 1522, RFC
1590) (Status: DRAFT STANDARD)
* RFC 2183, Communicating Presentation Information in Internet Messages:
The Content-Disposition Header Field. R. Troost, S. Dorner, K. Moore.
August 1997. (Format: TXT=23150 bytes) (Updates RFC 1806) (Updated by
RFC 2184, RFC 2231) (Status: PROPOSED STANDARD)
* RFC 2184, MIME Parameter Value and Encoded Word Extensions: Character
Sets, Languages, and Continuations. N. Freed, K. Moore. August 1997.
(Format: TXT=17635 bytes) (Obsoleted by RFC 2231) (Updates RFC 2045,
RFC 2047, RFC 2183) (Status: PROPOSED STANDARD)
* RFC 2231, MIME Parameter Value and Encoded Word Extensions: Character
Sets, Languages, and Continuations. N. Freed, K. Moore. November 1997.
(Format: TXT=19280 bytes) (Obsoletes RFC 2184) (Updates RFC 2045, RFC
2047, RFC 2183) (Status: PROPOSED STANDARD)
* RFC 2646, The Text/Plain Format Parameter. R. Gellens. August 1999.
(Format: TXT=29175 bytes) (Updates RFC 2046) (Status: PROPOSED
STANDARD)
April 1st RFC's
* RFC 1776 The Address is the Message. Steve Crocker. Apr-01-1995.
(Format: TXT=2051 bytes) (Status: INFORMATIONAL)
* RFC 2549, IP over Avian Carriers with Quality of Service, D. Waitzman.
Apr-01-1999. (Format: TXT=9519 bytes) (Updates RFC1149) (Status:
INFORMATIONAL)
This is a humorous RFC by the IETF. It was written by D. Waitzman and
released on April Fool's Day 1999; it is an April 1st RFC. It updates
Waitzman's earlier RFC 1149 about the transmission of IP traffic via
carrier pigeons.
Random Support RFC's
* RFC 3023, XML Media Types. M. Murata, S. St.Laurent, D. Kohn. January
2001. (Format: TXT=86011 bytes) (Obsoletes RFC 2376) (Updates RFC 2048)
(Status: PROPOSED STANDARD)
* RFC 3097, RSVP Cryptographic Authentication -- Updated Message Type
Value. R. Braden, L. Zhang. April 2001. (Format: TXT=6320 bytes)
(Updates RFC 2747) (Status: PROPOSED STANDARD)
* RFC 2747, RSVP Cryptographic Authentication. F. Baker, B. Lindell, M.
Talwar. January 2000. (Format: TXT=49477 bytes) (Updated by RFC 3097)
(Status: PROPOSED STANDARD)
Random Application RFC's
* RFC 1789, INETPhone: Telephone Services and Servers on Internet. C.
Yang. April 1995. (Format: TXT=14186 bytes) (Status: INFORMATIONAL)
* RFC 3066, Tags for the Identification of Languages. H. Alvestrand.
January 2001. (Format: TXT=26522 bytes) (Obsoletes RFC1766) (Also
BCP0047) (Status: BEST CURRENT PRACTICE)
This provides a way to register extensions of codes for language names
in ISO 639. The current reviewer of new tags and maintainer of the
registry is Michael Everson. An alternative for language codes is the
Ethnologue.
See also Registry
* RFC 3106, ECML v1.1: Field Specifications for E-Commerce. D. Eastlake,
T. Goldstein. April 2001. (Format: TXT=40715 bytes) (Obsoletes RFC
2706) (Status: INFORMATIONAL)
Random RFC's
* RFC 0823 DARPA Internet gateway. R.M. Hinden, A. Sheltzer. Sep-01-1982.
(Format: TXT=62620 bytes) (Updates IEN 109, IEN 30) (Status: HISTORIC)
This is a memo and status report of the DARPA Internet Gateway. It
deals with two areas: gateway procedures and message formats. Topics
include information on the forwarding of internet datagrams, various
protocols supported by the gateway, and specific gateway software.
Unlike many other RFCs, it does not list any implementation specifics.
* RFC 0824 CRONUS Virtual Local Network. W.I. MacGregor, D.C. Tappan.
Aug-25-1982. (Format: TXT=58732 bytes) (Status: UNKNOWN) Full text of
RFC 0824
* RFC 3094, Tekelec's Transport Adapter Layer Interface. D. Sprague, R.
Benedyk, D. Brendes, J. Keller. April 2001. (Format: TXT=265099 bytes)
(Status: INFORMATIONAL)
This content from Wikipedia is licensed under the GNU Free Documentation License.
|
