Internet Official Protocol Standards
RFC 2600

Document Type RFC - Historic (March 2000; No errata)
Obsoleted by RFC 2700
Obsoletes RFC 2500
Last updated 2013-03-02
Stream Legacy
Formats plain text pdf html bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 2600 (Historic)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                    Internet Engineering Task Force
Request for Comments: 2600                                   J. Reynolds
Obsoletes: 2500, 2400, 2300, 2200, 2000, 1920,                 R. Braden
1880, 1800, 1780, 1720, 1610, 1600, 1540, 1500,                  Editors
1410, 1360, 1280, 1250, 1200, 1140, 1130, 1100,               March 2000
1083
STD: 1
Category: Standards Track

                  Internet Official Protocol Standards

Status of this Memo

   This memo describes the state of standardization of protocols used in
   the Internet as determined by the Internet Engineering Task Force
   (IETF).  This memo is an Internet Standard.  Distribution of this
   memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2000).  All Rights Reserved.

Overview

   This memo is published by the RFC Editor 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.  This memo is prepared by the RFC Editor for the
   IESG and IAB.  Please see http://www.rfc-editor.org for later updates
   to this document.

IETF                        Standards Track                     [Page 1]
RFC 2600                   Internet Standards                 March 2000

Table of Contents

   1.  Contacts . . . . . . . . . . . . . . . . . . . . . . . . .   2
   1.1.  IAB, IETF, and IRTF Contacts . . . . . . . . . . . . . .   2
   1.2.  Internet Assigned Numbers Authority (IANA) Contact . . .   2
   1.3.  Request for Comments Editor (RFC Editor) Contact . . . .   2
   1.4.  Requests for Comments Distribution Contact . . . . . . .   3
   1.5.  Sources for Requests for Comments  . . . . . . . . . . .   3
   2.  Current Technical Specifications . . . . . . . . . . . . .   4
   2.1.  Standard Protocols Ordered by STD  . . . . . . . . . . .   4
   2.2.  Standard Protocols Ordered by RFC  . . . . . . . . . . .   7
   2.3.  Draft Standard Protocols . . . . . . . . . . . . . . . .   9
   2.4.  Proposed Standard Protocols  . . . . . . . . . . . . . .  11
   2.5.  Experimental Protocols . . . . . . . . . . . . . . . . .  24
   2.6.  Historic Protocols . . . . . . . . . . . . . . . . . . .  28
   3.  Security Considerations  . . . . . . . . . . . . . . . . .  30
   4.  Editors' Addresses . . . . . . . . . . . . . . . . . . . .  30
   5.  Full Copyright Statement . . . . . . . . . . . . . . . . .  31

1.  Contacts

   This section contains important contact information, for reference.

1.1.  IAB, IETF, and IRTF Contacts

   Internet Architecture Board (IAB) Contact: www.iab.org

   Internet Engineering Task Force (IETF) Contact: www.ietf.org

   Internet Research Task Force (IRTF) Contact: www.irtf.org

1.2.  Internet Assigned Numbers Authority (IANA) Contact

   See: www.iana.org

1.3.  Request for Comments Editor (RFC Editor) Contact

   See: www.rfc-editor.org

   The RFC Editor publishes documents that are the output of the IETF
   process or are submitted individually via electronic mail.  Further
   information about the RFC series is contained in section 2.1, RFC
   2026 and at http://www.rfc-editor.org.

IETF                        Standards Track                     [Page 2]
RFC 2600                   Internet Standards                 March 2000

   How to obtain the most recent edition of this "Internet Official
   Protocol Standards" memo:

      The file "in-notes/std/std1.txt" may be copied via FTP from the
      FTP.ISI.EDU computer using the FTP username "anonymous" and FTP
      password "guest".

1.4.  Requests for Comments Distribution Contact

   RFCs can be obtained via FTP from FTP.ISI.EDU, with the pathname in-
   notes/rfcnnnn.txt (where "nnnn" refers to the number of the RFC).
   Login with FTP username "anonymous" and password "name@host.domain".

   RFCs can also be obtained via electronic mail from ISI.EDU by using
   the RFC-INFO service.  Address the request to "rfc-info@isi.edu" with
   a message body of:

           Retrieve: RFC
              Doc-ID: RFCnnnn

   (Where "nnnn" refers to the number of the RFC (always use 4 digits -
   the DOC-ID of RFC 822 is "RFC0822")).  The RFC-INFO@ISI.EDU server
   provides other ways of selecting RFCs based on keywords and such; for
   more information send a message to "rfc-info@isi.edu" with the
   message body "help: help".

   contact: RFC-Manager@ISI.EDU

1.5.  Sources for Requests for Comments

   Details on many sources of RFCs via FTP or EMAIL may be obtained by
   sending an EMAIL message to "rfc-info@ISI.EDU" with the message body
   "help: ways_to_get_rfcs".  For example:

           To: rfc-info@ISI.EDU
           Subject: getting rfcs

           help: ways_to_get_rfcs

IETF                        Standards Track                     [Page 3]
RFC 2600                   Internet Standards                 March 2000

2.  Current Technical Specifications
Show full document text