📄 rfc2800.txt
字号:
Network Working Group Internet Engineering Task ForceRequest for Comments: 2800 J. ReynoldsObsoletes: 2700 R. BradenSTD: 1 S. GinozaCategory: Standards Track Editors May 2001 Internet Official Protocol StandardsStatus of this Memo This memo is an Internet Standard. Distribution of this memo is unlimited.Copyright Notice Copyright (C) The Internet Society (2001). All Rights Reserved.Abstract This memo contains a snapshot of the state of standardization of protocols used in the Internet as of April 17, 2001. It lists only official protocol standards RFCs; it is not a complete index to the RFC series. The latest version of this memo is designated STD 1.Table of Contents 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Contacts . . . . . . . . . . . . . . . . . . . . . . . . . 2 2.1. Internet-Related Organizations . . . . . . . . . . . . . 2 2.2. Request for Comments Editor (RFC Editor) Web Pages . . . 2 2.3 Retrieval using FTP . . . . . . . . . . . . . . . . . . 3 2.4 Search and Retrieval Using Email . . . . . . . . . . . . 4 3. Current Technical Specifications . . . . . . . . . . . . . 5 3.1. Standard Protocols Ordered by STD . . . . . . . . . . . 5 3.2. Standard Protocols Ordered by RFC . . . . . . . . . . . 8 3.3. Draft Standard Protocols . . . . . . . . . . . . . . . . 10 3.4. Proposed Standard Protocols . . . . . . . . . . . . . . 13 3.5. Experimental Protocols . . . . . . . . . . . . . . . . . 30 3.6. Historic Protocols . . . . . . . . . . . . . . . . . . . 35 4. Security Considerations . . . . . . . . . . . . . . . . . 37 5. Editors' Addresses . . . . . . . . . . . . . . . . . . . . 37 6. Full Copyright Statement . . . . . . . . . . . . . . . . . 38IETF Standards Track [Page 1]RFC 2800 Internet Standards May 20011. 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 an April 17, 2001 snapshot of the current official protocol standards 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 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. This memo is published by the RFC Editor for the IESG and IAB 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.6 of this memo contain the lists of protocols in each stage of standardization - Standard, Draft Standard, Proposed Standard, Experimental and Historic. 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 RFCs are not included. This memo lists the current standards track, Experimental, and Historic protocols; it is not a complete index to RFCs.2. Resources This section contains important contact information, for reference.2.1. Internet-Related Organizations 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 Internet Assigned Numbers Authority (IANA) Contact: www.iana.org2.2. Request for Comments Editor (RFC Editor) Web Pages The RFC Editor maintains the official repository of all RFCs and indexes to them. The RFC Editor web site is: http://www.rfc-editor.org.IETF Standards Track [Page 2]RFC 2800 Internet Standards May 2001 At this URL, a user can: (a) Obtain the current "Internet Official Protocol Standards" list. See: http://www.rfc-editor.org/rfcxx00.html This hyper-linked listing is updated daily. (b) Retrieve the latest version of this STD 1 memo. See: http://www.rfc-editor.org/go.html, and select STD and "1". (c) Retrieve text of any RFC. See: http://www.rfc-editor.org/go.html (d) Search for RFCs by category. See: http://www.rfc-editor.org/category.html (e) Search the RFC index for document number, author, title, and/or keywords, and retrieve the text of any matching documents. See: http://www.rfc-editor.org/rfcsearch.html RFC information can also be retrieved using FTP or email.2.3 Retrieval using FTP RFC-related files may be copied via FTP from the FTP.RFC-EDITOR.ORG computer using the FTP username "anonymous" and password "name@host.domain". An FTP user can: (a) Retrieve the latest version of this STD 1 memo. File: "in-notes/std/std1.txt" (b) Retrieve text of any RFC. File: "in-notes/rfcnnnn.txt" will retrieve the ASCII version. Some RFCs also have secondary Postscript and/or PDF versions, available from File: "in-notes/rfcnnnn.ps" and/or "in-notes/rfcnnnn.pdf", respectively. Here "nnnn" is a 1-4 digit RFC number, with no leading zeros.IETF Standards Track [Page 3]RFC 2800 Internet Standards May 20012.4 Search and Retrieval Using Email To use the RFC Editor's email-based RFC-INFO service, send a request to: RFC-INFO@RFC-EDITOR.ORG In the message body, include your information request. For example, the following message bodies may be used. (a) To retrieve the latest version of this STD 1 memo: Retrieve: STD Doc-ID: STD0001 (b) To retrieve ASCII text of any RFC: Retrieve: RFC Doc-ID: RFCnnnn Here "nnnn" must be filled with leading zeros to 4 digits. (c) The RFC-INFO@RFC-EDITOR.ORG server provides other capabilities, e.g., search and retrieval based on author, title, and/or keyword. For more information, send the following message body to the server: help: help The server will email back the results.IETF Standards Track [Page 4]RFC 2800 Internet Standards May 20013. Current Technical Specifications3.1. Standard Protocols Ordered by STDMnemonic Title RFC# STD#------------------------------------------------------------------------------ Internet Official Protocol Standards 2800 1*-------- Assigned Numbers 1700 2-------- Requirements for Internet Hosts - Communication 1122 3 Layers-------- Requirements for Internet Hosts - Application 1123 3 and Support-------- [Reserved for Router Requirements. See RFC 1812] 4*IP Internet Protocol 791 5ICMP Internet Control Message Protocol 792 5-------- Broadcasting Internet Datagrams 919 5-------- Broadcasting Internet datagrams in the presence 922 5 of subnets-------- Internet Standard Subnetting Procedure 950 5IGMP Host extensions for IP multicasting 1112 5UDP User Datagram Protocol 768 6TCP Transmission Control Protocol 793 7TELNET Telnet Protocol Specification 854 8TELNET Telnet Option Specifications 855 8FTP File Transfer Protocol 959 9SMTP [Reserved for Simple Mail Transfer Protocol (SMTP). 10* See RFC 2821.]SMTP-SIZE SMTP Service Extension for Message Size Declaration 1870 10MAIL [Reserved for Internet Message Format. See RFC 11* 2822.]NTP [Reserved for Network Time Protocol (NTP). See 12* RFC 1305.]DOMAIN Domain names - concepts and facilities 1034 13DOMAIN Domain names - implementation and specification 1035 13DNS-MX [Was Mail Routing and the Domain System (RFC974). 14* Now Historic.]SNMP Simple Network Management Protocol (SNMP) 1157 15SMI Structure and identification of management 1155 16 information for TCP/IP-based internetsConcise-MI Concise MIB definitions 1212 16MIB-II Management Information Base for Network Management 1213 17
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -