Movatterモバイル変換
[0]ホーム
[RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Info page]
UNKNOWN
Network Working Group Ole Jacobsen (SRI)Request for Comments: 980 Jon Postel (ISI) March 1986Protocol Document Order InformationSTATUS OF THIS MEMO This RFC indicates how to obtain various protocol documents used in the DARPA research community. Included is an overview of the new 1985 DDN Protocol Handbook and available sources for obtaining related documents (such as, DoD, ISO, and CCITT). Distribution of this memo is unlimited.DOD INTERNET PROTOCOL DOCUMENTS: How to get the Requests for Comments (RFCs): RFCs are the working memos of the DARPA research community. The subjects may include protocol specifications, interface definitions, program descriptions, policy statements, trouble reports, algorithms, announcements, and humor. These may range from wild ideas and crazy suggestions, to firm specifications. The normal method for distribution of RFCs is for interested parties to copy the documents from the DDN Network Information Center's (NIC) online library using FTP. Public access files may be copied from the RFC directory on the SRI-NIC.ARPA host computer via FTP with username ANONYMOUS and password GUEST. The pathname of RFC nnn is RFC:RFCnnn.TXT. Requests for special distribution should be addressed to either the author of the RFC in question or to NIC@SRI-NIC.ARPA. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. For hardcopy distribution from the NIC there is a charge of $5 for each RFC that is less than 100 pages, and $10 for each RFC that is 100 pages or more to cover the cost of postage and handling (check, money order, or purchase order accepted). Order From: SRI International (SRI-NIC) DDN Network Information Center Room EJ291 333 Ravenswood Avenue Menlo Park, CA 94025 Phone: 1-415-859-3695 1-800-235-3155Jacobsen & Postel [Page 1]
RFC 980 March 1986Protocol Document Order Information How to get the Protocol Handbook - 1985: It has been about 5 years since the release of the Internet Protocol Transition Workbook (IPTW) and the related documents which were issued as a document set for implementors of TCP/IP and related application protocols. These were issued to assist the NCP-to-TCP transition which took place in early 1983. Since that time the network has undergone many changes, the most noteable being the creation of the Defense Data Network (DDN) and the ARPANET/MILNET split, leaving the ARPANET as a research and development network, and MILNET as an operational military network. An updated and much expanded version of the IPTW is needed to reflect these changes, and the 1985 DDN Protocol Handbook is a response to this need. The cost is $110 domestic, and $130 foreign, including 4th class postage (check, money order, or purchase order accepted). The 1985 DDN Protocol Handbook is divided into three volumes: 1. The first volume includes Military Standard (MIL STD) protocols as well as administrative guidelines pertaining to the MILNET portion of the DDN. 2. The second volume includes the DARPA Internet protocols as well as administrative guidelines pertaining to the ARPANET portion of the DDN. Most of these protocols have also been issued as RFCs. 3. The third volume contains several background articles, implementation guidelines, and additional protocol specifications. This volume is relevant to both portions of the network, and should be used in conjunction with the other two volumes. The Table of Contents of the three volumes is given inAppendix A.Jacobsen & Postel [Page 2]
RFC 980 March 1986Protocol Document Order Information Order From: SRI International (SRI-NIC) DDN Network Information Center Room EJ291 333 Ravenswood Avenue Menlo Park, CA 94025 Phone: 1-415-859-3695 1-800-235-3155 How to get the Old Protocol Workbook - 1982: The 1982 edition of the Protocol Handbook is a five volume set. These documents were distributed in hardcopy by the NIC, but are now out of print. Many of the protocols are also RFCs which are available online or in hardcopy from the NIC. The complete documents may be obtained from the National Technical Information Service (NTIS), or the Defense Technical Information Service (DTIC). The documents and their NTIS order numbers are: Internet Protocol Transition Workbook (IPTW) ADA153607 Internet Protocol Implementation Guide (IPIG) ADA153624 Internet Mail Protocol ADA153625 Internet Telnet Protocol and Options not deposited Miscellaneous Protocol not deposited Order From: National Technical Information Service (NTIS) 5285 Port Royal Road Springfield, VA 22161 Phone: 1-703-487-4650 (order desk) Or Defense Technical Information Center (DTIC) Cameron Station, Bldg. 5 Alexandria, VA 22314 Phone: 1-703-274-7633Jacobsen & Postel [Page 3]
RFC 980 March 1986Protocol Document Order Information How to get the MIL STD Internet Protocol Documents: Several of the Internet protocol documents have been issued as military standards (MIL-STDs). The MIL-STDs listed below are the official DoD versions of these commmunication protocols and should be consulted for any implementations. These documents are available from the Naval Publications and Forms Center. Requests can be initiated by telephone, telegraph, or mail; however, it is preferred that private industry use form DD1425, if possible. These five documents are included in the 1985 DDN Protocol Handbook. Internet Protocol (IP) MIL-STD-1777 Transmission Control Protocol (TCP) MIL-STD-1778 File Transfer Protocol (FTP) MIL-STD-1780 Simple Mail Transfer Protocol (SMTP) MIL-STD-1781 Telnet Protocol and Options (TELNET) MIL-STD-1782 Order From: Naval Publications and Forms Center, Code 3015 5801 Tabor Ave Philadelphia, PA 19120 Phone: 1-215-697-3321 (order tape) 1-215-697-4834 (conversation) There may also be brokers in your area that will handle orders for MIL-STDs. One such vendor for MIL-STD documents is Global Engineering. Relationship between the RFC versions and the MIL STD versions: The ARPA community specifications for IP (RFC-791) and TCP (RFC-793) and the DoD specifications above are intended to describe exactly the same protocols. Any difference in the protocols specified by these sets of documents should be reported to DCA and to DARPA. The RFCs and the MIL-STDs for IP and TCP differ in style and level of detail. It is strongly advised that the two sets of documents be used together. The ARPA and the DoD specifications for the FTP, SMTP, and Telnet protocols are essentially the same documents (RFCs 765, 821, 854). Note that the current ARPA specification for FTP isRFC-959. The MIL-STD versions have been edited slightly. Implementers should also check the "Official Protocols" memo for comments on protocol status or pending changes (RFC-961). DDN implementators shouldJacobsen & Postel [Page 4]
RFC 980 March 1986Protocol Document Order Information watch for DDN Management Bulletins (available from the NIC) which may announce policy changes with respect to the status of protocols on the DDN.OTHER PROTOCOL DOCUMENTS ISO Protocol Documents: Approved ISO standards, and ISO draft standards at either the DP or DIS level, are available from the American National Standards Institute (ANSI) in New York. Order From: American National Standards Institute 1430 Broadway New York, NY 10018 Phone: 1-212-642-4900 There may also be brokers in your area that will handle orders for ISO documents. One such vendor of ISO documents is OMNICOM. CCITT Protocol Documents: The approved CCITT Recommendations are published by the International Telecommunications Union (ITU) in Geneva. Order From: United Nations Bookstore Room GA 32B New York, NY 10017 Most of the Red book (1984) is available, including all but one of the X series. The useful volumes are: VIII.1 V Series $43.20 VIII.2 X.1 - X.15 8.60 VIII.3 X.20 - X.32 44.30 VIII.4 X.40 - X.181 46.40 VIII.5 X.200 - X.250 50.80 VIII.6 X.300 - X.353 10.80 VIII.7 X.400 - X.430 not available yet No shipping charge for over 5 books via UPS. First Class $1.00 per book. Check with order only.Jacobsen & Postel [Page 5]
RFC 980 March 1986Protocol Document Order Information All the ISO protocols are in the X.200 to X.430 area. There may also be brokers in your area that will handle orders for ISO documents. One such vendor of CCITT documents is OMNICOM. NRC Report The National Research Council's Report to the Department of Defense and the National Bureau of Standards entitled "Transport Protocols for Department of Defense Data Networks". This was originally published by the National Academy Press, February 1985. The Executive Summary isRFC-939. The complete report isRFC-942.DOCUMENT BROKERS We list here some document brokers as a convenience. There may be other brokers that should be listed, if so please let us know and they will be listed in future editions. Global Engineering: Global Engineering Documents 2625 Hickory Street Santa Ana, CA 92707 Phone: 1-800-854-7179 OMNICOM: OMNICOM, Inc. 501 Church Street, NE Suite 206 Vienna, VA 22180 Phone: 1-703-281-1135Jacobsen & Postel [Page 6]
RFC 980 March 1986Protocol Document Order Information APPENDIX A DDN PROTOCOL HANDBOOK 1985 -- TABLE OF CONTENTS VOLUME ONEACKNOWLEDGEMENTSSECTION 1: INTRODUCTION TO VOLUME ONESECTION 2: OVERVIEW 2.1 Purpose of the DDN Protocol Handbook 2.2 What the Handbook Contains 2.3 Role of DCA in Protocol Standardization 2.4 Protocol Review and Acceptance in the DoD 2.5 Position of DoD on Use of National and International StandardsSECTION 3: BACKGROUND 3.1 Brief History of the DDN 3.2 DoD Architectural ModelSECTION 4: DDN PROTOCOL CONFIGURATION MANAGEMENT 4.1 The DDN Program Management Office (DDN PMO) 4.2 The DDN Configuration Management 4.2.1 The DDN Configuration Control Group (CCG) 4.2.2 Blacker Front End Interface Control Document 4.2.3 OSD Directives 4.3 Protocol Testing and Validation (IVV&T) 4.4 Announcement Procedures 4.4.1 Requests for Comments (RFCs) 4.4.2 DCA Circulars 4.4.3 DDN Management Bulletins and Newsletters 4.4.4 The TACNEWS ServiceSECTION 5: OBTAINING PROTOCOL INFORMATION 5.1 Military Standards 5.2 The DDN Protocol Handbook 5.3 Requests for Comments (RFCs) 5.4 DDN Management Bulletins 5.5 NIC Services 5.6 Other Information SourcesJacobsen & Postel [Page 7]
RFC 980 March 1986Protocol Document Order InformationSECTION 6: DOD MILITARY STANDARD PROTOCOLS 6.1 Internet Protocol (IP) MIL-STD 1777 6.2 Transmission Control Protocol (TCP) MIL-STD 1778 6.3 File Transfer Protocol (FTP) MIL-STD 1780 6.4 Simple Mail Transfer Protocol (SMTP) MIL-STD 1781 6.5 Telnet Protocol and Options MIL-STD 1782 6.6 X.25 (Levels 1-3) (Undergoing Review Process) 6.7 Host Front End Protocol [RFC929] (Undergoing Review Process) 6.8 Internet Control Message Protocol (ICMP) (Undergoing Review Process)SECTION 7: REFERENCES VOLUME TWOACKNOWLEDGEMENTSSECTION 1: INTRODUCTION TO VOLUME TWOSECTION 2: BACKGROUND 2.1 A Brief History of the ARPANET 2.2 Management of the ARPANET 2.2.1 DARPA/IPTO 2.3 The Catenet Model for Internetworking [IEN 48] 2.4 The DARPA Internet Protocol Suite [RS-85-153]SECTION 3: PROTOCOL REVIEW AND ACCEPTANCE FOR THE DARPA INTERNET 3.1 Request for Comments (RFCs)3.2 Special Interest Group Discussions 3.3 The Internet Advisory BoardSECTION 4: OBTAINING PROTOCOL INFORMATION 4.1 Military Standards 4.2 The DDN Protocol Handbook 4.3 Requests for Comments (RFCs) 4.4 DDN Management Bulletins and Newsletters 4.5 NIC Services 4.6 Other Protocol Information SourcesJacobsen & Postel [Page 8]
RFC 980 March 1986Protocol Document Order InformationSECTION 5: CURRENT OFFICIAL ARPANET PROTOCOLS 5.1 Summary of All Current Official Protocols[RFC 961]SECTION 6: NETWORK LEVEL PROTOCOLS 6.1 Internet Protocol (IP) [RFC 791] 6.2 Internet Control Message Protocol (ICMP)[RFC 792]SECTION 7: HOST LEVEL PROTOCOLS 7.1 Major Host Protocols 7.1.1 User Datagram Protocol (UDP) [RFC 768] 7.1.2 Transmission Control Protocol (TCP) [RFC 793] 7.2 Minor Host Protocols 7.2.1 Host Monitoring Protocol (HMP) [RFC 869] 7.2.2 Cross Net Debugger (XNET) [IEN 158] 7.2.3 Multiplexing Protocol (MUX) [IEN 90] 7.2.4 Stream Protocol (ST) [IEN 119] 7.2.5 Network Voice Protocol (NVP-II) [RFC 741] 7.2.6 Reliable Data Protocol (RDP) [RFC 908] 7.3 Gateway Protocols 7.3.1 "Stub" Exterior Gateway Protocol (EGP) [RFC 904] 7.3.2 Gateway-Gateway Protocol (GGP)[RFC 823]SECTION 8: APPLICATION LEVEL PROTOCOLS 8.1.1 Telnet Protocol (TELNET) [RFC 854] 8.1.2 Telnet Options (TLNT-OPS) [RFC 855] 8.1.2.0 Binary Transmission [RFC 856] 8.1.2.1 Echo [RFC 857] 8.1.2.2 Reconnection [NIC 15391] 8.1.2.3 Suppress Go Ahead [RFC 858] 8.1.2.4 Approx Message Size Negotiation [NIC 15393] 8.1.2.5 Status [RFC 859] 8.1.2.6 Timing Mark [RFC 860] 8.1.2.7 Remote Controlled Trans and Echo [RFC 726] 8.1.2.8 Output Line Width [NIC 20196] 8.1.2.9 Output Page Size [NIC 20197] 8.1.2.10 Output Carriage-Return Disposition [RFC 652] 8.1.2.11 Output Horizontal Tabstops [RFC 653] 8.1.2.12 Output Horizontal Tab Disposition [RFC 654] 8.1.2.13 Output Formfeed Disposition [RFC 655] 8.1.2.14 Output Vertical Tabstops [RFC 656] 8.1.2.15 Output Vertical Tab Disposition [RFC 657]Jacobsen & Postel [Page 9]
RFC 980 March 1986Protocol Document Order Information 8.1.2.16 Output Linefeed Disposition [RFC 658] 8.1.2.17 Extended ASCII [RFC 698] 8.1.2.18 Logout [RFC 727] 8.1.2.19 Byte Macro [RFC 735] 8.1.2.20 Data Entry Terminal [RFC 732] 8.1.2.21 SUPDUP [RFC 736] 8.1.2.22 SUPDUP Output [RFC 749] 8.1.2.23 Send Location [RFC 779] 8.1.2.24 Terminal Type [RFC 930] 8.1.2.25 End of Record [RFC 885] 8.1.2.26 TACACS User Identification [RFC 927] 8.1.2.27 Output Marking [RFC 933] 8.1.2.28 Extended-Options-List [RFC 861] 8.1.3 File Transfer Protocol (FTP) [RFC 959] 8.1.4 Simple Mail Transfer Protocol (SMTP) [RFC 821] 8.1.5 Domain Name Protocol (DOMAIN) [RFC 883] 8.1.6 HOSTNAME Protocol (HOSTNAME) [RFC 953] 8.2 Minor Applications (Implemented by many hosts) 8.2.1 Trivial File Transfer Protocol (TFTP) [IEN 133] 8.2.2 Simple File Transfer Protocol (SFTP) [RFC 913] 8.2.3 Echo Protocol (ECHO) [RFC 862] 8.2.4 Discard Protocol (DISCARD) [RFC 863] 8.2.5 Daytime Protocol (DAYTIME) [RFC 867] 8.2.6 Time Server Protocol (TIME) [RFC 868] 8.2.7 Character Generator Protocol (CHARGEN) [RFC 864] 8.2.8 Quote of the Day Protocol (QUOTE) [RFC 865] 8.2.9 Active Users Protocol (USERS) [RFC 866] 8.2.10 Finger Protocol (FINGER) [RFC 742] 8.2.11 WHOIS Protocol (NICNAME) [RFC 954] 8.2.12 Network Standard Text Editor (NETED) [RFC 569] 8.3 Miscellaneous Applications (Implemented by few hosts) 8.3.1 Resource Location Protocol (RLP) [RFC 887] 8.3.2 Remote Job Entry (RJE) [RFC 407] 8.3.3 Remote Job Service (NETRJS) [RFC 740] 8.3.4 Remote Telnet Service (RTELNET) [RFC 818] 8.3.5 Graphics Protocol (GRAPHICS) [RFC 493] 8.3.6 Authentication Service (AUTH) [RFC 931] 8.3.7 DCNET Time Server Protocol (CLOCK) [RFC 778] 8.3.8 SUPDUP Protocol (SUPDUP) [RFC 734]Jacobsen & Postel [Page 10]
RFC 980 March 1986Protocol Document Order Information VOLUME THREEACKNOWLEDGEMENTSSECTION 1: INTRODUCTION TO VOLUME THREESECTION 2: PROTOCOL IMPLEMENTATION GUIDELINES 2.1 Window and Acknowledgment Strategy in TCP [RFC 813] 2.2 Names, Addresses, Ports, and Routes [RFC 814] 2.3 IP Datagram Reassembly Algorithms [RFC 815] 2.4 Fault Isolation and Recovery [RFC 816] 2.5 Modularity and Efficiency in Protocol Implementation [RFC 817] 2.6 A Protocol for Packet Network Intercommunication 2.7 Issues in Packet Network Interconnection 2.8 Protocols in a Computer Internetworking Environment 2.9 Internetwork Protocol Approaches 2.10 The ARPA Internet Protocol 2.11 Internetworking for the Military Environment 2.12 Connecting Different Types of Networks with GatewaysSECTION 3: APPENDICES 3.1 Assigned Numbers [RFC 960] 3.2 Pre-emption [RFC 794] 3.3 Service Mappings [RFC 795] 3.4 Address Mappings [RFC 796] 3.5 DoD Internet Host Table Specification [RFC 952] 3.6 Document Formats [RFC 678] 3.6.1 Instructions for Authors of RFCs 3.7 Bitmap Formats [RFC 797] 3.8 Facsimile Formats [RFC 769] 3.9 Character Set Definition (ASCII) 3.10 Interface Message Processor (BBN-1822) 3.11 ARPANET 1822L Host Access Protocol [RFC 878] 3.12 Internet Protocol on X.25 Networks [RFC 877] 3.13 Internet Protocol on Distributed Computer Networks [RFC 891] 3.14 Transmission of IP Datagrams over IEEE 802.3 Networks [RFC 948] 3.15 Internet Protocol on Ethernet Networks [RFC 894] 3.16 Internet Protocol on Experimental Ethernets [RFC 895] 3.17 Address Resolution Protocol (ARP) [RFC 826] 3.18 Reverse Address Resolution Protocol (RARP) [RFC 903] 3.19 Host Access Protocol (HAP) [RFC 907] 3.20 Loader Debugger Protocol (LDP) [RFC 909]Jacobsen & Postel [Page 11]
RFC 980 March 1986Protocol Document Order Information 3.21 CSNET Mailbox Name Server Protocol (CSNET-NS) [CS-DN-2] 3.22 Internet Name Server Protocol (NAMSRVR) [IEN 116] 3.23 Internet Message Protocol (MPM) [RFC 759] 3.24 Post Office Protocol (POP) [RFC 937]Jacobsen & Postel [Page 12]
[8]ページ先頭