Network Working Group RFC Editor
Request for Comments: 5000 USC/ISI
STD: 1 May 2008
Obsoletes: 3700
Category: Informational
Internet Official Protocol Standards
Status of This Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
IESG Note
This document obsoletes RFC 3700. It also reclassifies RFCs that
were previously published as STD 1 as Historic. More specifically,
this RFC moves RFCs 3000, 3300, 3600, and 3700 to Historic status.
Abstract
This document is published by the RFC Editor to provide a summary of
the current standards protocols (as of 18 February 2008). It lists
those official protocol standards, Best Current Practice, and
Experimental RFCs that have not been obsoleted; it is not a complete
index to the RFC series. Newly published RFCs and RFCs whose status
has changed are starred.
For an up-to-date list, see http://www.rfc-editor.org/rfcxx00.html,
which is updated daily.
Table of Contents
1. Overview ........................................................22. RFC Resources and Retrieval .....................................23. Current Technical Specifications ................................33.1. Standard Protocols Ordered by STD ..........................33.2. Standard Protocols Ordered by RFC ..........................63.3. Draft Standard Protocols ...................................83.4. Proposed Standard Protocols ...............................113.5. Best Current Practice Ordered by BCP ......................573.6. Best Current Practice Ordered by RFC ......................623.7. Experimental Protocols ....................................674. Security Considerations ........................................74RFC Editor Informational [Page 1]

RFC 5000 Internet Official Protocol Standards May 20081. Overview
This memo contains a snapshot of the state of standardization of
protocols used in the Internet, as determined by the Internet
Engineering Task Force (IETF). It is a 18 February 2008 snapshot of
the current official protocol standards list and the Best Current
Practice list, which is updated daily and is available from the RFC
Editor Web site.
The RFC Editor publishes Request for Comments (RFC) documents that
are the output of 4 streams: IAB, IETF, IRTF, and Independent
Submission via the RFC Editor.
This memo is published by the RFC Editor for the IESG and IAB, in
which the categorizations are in accordance with Section 2.1 of "The
Internet Standards Process -- Revision 3", RFC 2026, which specifies
the rules and procedures by which all Internet standards are set.
Sections 3.1 - 3.7 of this memo contain the lists of protocols in
each stage of standardization - Standard, Draft Standard, Proposed
Standard, Experimental, as well as Best Current Practice documents.
Protocols that are new to this document or have been moved from one
protocol level to another, or that differ from the previous edition
of this document are marked with an asterisk. Informational and
Historic RFCs are not included. This list is not a complete index to
RFCs.
2. RFC Resources and Retrieval
This list is a live document that is updated daily on the RFC Editor
site at:
http://www.rfc-editor.org/rfcxx00.html
RFCs are available online via http and ftp as:
http://www.rfc-editor.org/rfc/rfcXXXX.txtftp://ftp.rfc-editor.org/in-notes/rfcXXXX.txt
where XXXX represents the corresponding RFC number.
The RFC Editor maintains the official repository of all RFCs and
indexes to them. The site also provides additional information about
the history of the RFC Editor, current submission and review
procedures, and editorial and publication procedures. Please see the
RFC Editor site for all other RFC related information:
http://www.rfc-editor.orgRFC Editor Informational [Page 2]

RFC 5000 Internet Official Protocol Standards May 2008
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78 and at http://www.rfc-editor.org/copyright.html,
and except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
RFC Editor Informational [Page 75]