RFC 980
Protocol document order information
Network Working Group 💖
RFC 980 ✨ is titled Protocol Document Order Information 🎀. It was written by Ole Jacobsen (SRI) and Jon Postel (ISI) 👑 and dated March 1986 🌸. The header doesn't give a category, and it doesn't say what it obsoletes or updates 🙈.
Status of This Memo 🦋
Okay so this memo is basically a guide to getting your hands on the protocol docs the DARPA research community uses 📚. It gives you an overview of the new 1985 DDN Protocol Handbook 🌈 and tells you where to find related docs from 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 💜. They can cover protocol specs, interface definitions, program descriptions, policy statements, trouble reports, algorithms, announcements, and humor 😭. Some are wild ideas and crazy suggestions, and some are firm specifications 🔥. It's giving variety, bestie.
The usual way to get RFCs is to copy them from the DDN Network Information Center's (NIC) online library using FTP 💻. Public access files can be copied from the RFC directory on the SRI-NIC.ARPA host with username ANONYMOUS and password GUEST 🔑. The pathname for RFC nnn is RFC:RFCnnn.TXT 🗂️.
If you want special distribution, send your request either to the author of the RFC in question or to NIC@SRI-NIC.ARPA 📨. Unless the RFC itself says otherwise, all RFCs are for unlimited distribution 🌸.
For hardcopies from the NIC, there's a charge of $5 for each RFC under 100 pages, and $10 for each RFC that is 100 pages or more 🍓. That covers postage and handling. They take check, money order, or purchase order 💅.
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-3155How to get the Protocol Handbook - 1985 📖
About 5 years have passed since the Internet Protocol Transition Workbook (IPTW) came out 🦋. That set of documents was made for TCP/IP implementors and related application protocols, to help with the NCP-to-TCP transition in early 1983 🌈. A lot has changed since then. The biggest things were the creation of the Defense Data Network (DDN) and the ARPANET/MILNET split 💥. After the split, the ARPANET became a research and development network, and MILNET became an operational military network 🫶.
The IPTW needed a big update to reflect all that 🔥. The 1985 DDN Protocol Handbook is that update 💖. It costs $110 domestic and $130 foreign, including 4th class postage. They take check, money order, or purchase order ✨.
The 1985 DDN Protocol Handbook is split into three volumes 📚:
- Volume one has the Military Standard (MIL STD) protocols and administrative guidelines for the MILNET part of the DDN 🎖️.
- Volume two has the DARPA Internet protocols and administrative guidelines for the ARPANET part of the DDN 🛰️. Most of these have also been issued as RFCs 🫶.
- Volume three has background articles, implementation guidelines, and extra protocol specs 🧠. It matters for both parts of the network, so use it alongside the other two volumes 💜.
The Table of Contents for all three volumes is in Appendix A 👑.
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-3155How to get the Old Protocol Workbook - 1982 🕰️
The 1982 Protocol Handbook is a five-volume set 📦. The NIC used to send these out in hardcopy, but they're out of print now 😭. A lot of the protocols are also RFCs, which you can get online or in hardcopy from the NIC 🌸. The complete documents are available from the National Technical Information Service (NTIS) or the Defense Technical Information Service (DTIC) 💅. Here are the documents and their NTIS order numbers 🍓:
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 depositedOrder 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-7633How to get the MIL STD Internet Protocol Documents 🎖️
A few of the Internet protocol docs were issued as military standards (MIL-STDs) 🫡. The MIL-STDs below are the official DoD versions of these communication protocols, so they're the ones to check for any implementation 🔥. You can get them from the Naval Publications and Forms Center 📮. You can request them by phone, telegraph, or mail, but private industry is encouraged to use form DD1425 if possible 📝. All five docs are 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-1782Order 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 near you that handle MIL-STD orders 🧚. One vendor for MIL-STD docs is Global Engineering 💜.
Relationship between the RFC versions and the MIL STD versions 🧩
The ARPA community specs for IP (RFC-791) and TCP (RFC-793) and the DoD specs above are meant to describe exactly the same protocols 🫶. If the protocols differ between these sets of docs, report it to DCA and DARPA 🚨. The RFCs and the MIL-STDs for IP and TCP differ in style and level of detail, so it's strongly advised to use the two sets together 💅.
The ARPA and DoD specs for FTP, SMTP, and Telnet are basically the same documents (RFCs 765, 821, 854) 🌈. The current ARPA spec for FTP is RFC-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 implementors should watch for DDN Management Bulletins, which you can get from the NIC, since they may announce policy changes about 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-4900There may also be brokers near you that handle ISO orders 💜. One vendor of ISO docs 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 10017Most of the Red book (1984) is available, including all but one of the X series 📕. These are the useful volumes 💖:
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 yetThere's no shipping charge for orders over 5 books via UPS 📦. First Class is $1.00 per book 💅. They take check with order only ✨.
All the ISO protocols are in the X.200 to X.430 area 🧠.
There may also be brokers near you that handle CCITT orders 🧚. One vendor of CCITT docs is OMNICOM 💜.
NRC Report 📑
This is the National Research Council's Report to the Department of Defense and the National Bureau of Standards, called "Transport Protocols for Department of Defense Data Networks" 🫶. It was first published by the National Academy Press in February 1985 🌸. The Executive Summary is RFC-939 and the complete report is RFC-942 📚.
Document Brokers 🛍️
Here are some document brokers, just as a convenience 💖. There may be other brokers that should be listed. If you know of one, let them know, and they'll be listed in future editions 🫶.
Global Engineering:
Global Engineering Documents
2625 Hickory Street
Santa Ana, CA 92707
Phone: 1-800-854-7179OMNICOM:
OMNICOM, Inc.
501 Church Street, NE
Suite 206
Vienna, VA 22180
Phone: 1-703-281-1135SECTION 6: DOD MILITARY STANDARD PROTOCOLS ✨
okay bestie, this is the DoD military standards list 🫡 each protocol gets its own MIL-STD number (or an RFC, or a note that it's still in review) 💅
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 📚
nothing is listed under this one in this copy, so there's no reading homework here 🙈
VOLUME TWO 🦋
ACKNOWLEDGEMENTS 🫶
SECTION 1: INTRODUCTION TO VOLUME TWO 🌈
nothing else sits under this heading, so onward we go ✨
SECTION 2: BACKGROUND 🍓
this section is basically the family tree of everything 🌳 history, management, the catenet idea, and the DARPA Internet Protocol Suite, all in one neat list
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 🎀
this is how protocols got reviewed and accepted, through RFCs, special interest group chats, and the Internet Advisory Board 🧚
3.1 Request for Comments (RFCs)
3.2 Special Interest Group Discussions
3.3 The Internet Advisory BoardSECTION 4: OBTAINING PROTOCOL INFORMATION 🔥
where to actually find the info you need 👀 military standards, the DDN Protocol Handbook, RFCs, DDN bulletins and newsletters, NIC services, and other sources
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 SourcesSECTION 5: CURRENT OFFICIAL ARPANET PROTOCOLS 👑
the official ARPANET protocols, summed up in one place (look at that reference, [RFC 961] is doing a lot here 💖)
5.1 Summary of All Current Official Protocols [RFC 961]SECTION 6: NETWORK LEVEL PROTOCOLS 🌸
the network layer crew: IP and ICMP, each with its own RFC 💅
6.1 Internet Protocol (IP) [RFC 791]
6.2 Internet Control Message Protocol (ICMP) [RFC 792]SECTION 7: HOST LEVEL PROTOCOLS 💜
okay the host level is where it gets spicy 🌶️ major host protocols first (UDP and TCP, obviously iconic), then a whole crowd of minor ones, then the gateway 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 🦋
this is the big one 🥹 the app layer. TELNET comes with a whole pile of options (8.1.2.0 through 8.1.2.28, slay), then FTP, SMTP, DOMAIN and HOSTNAME, then the minor and miscellaneous apps that the crowd of hosts either uses a lot or barely touches 🧚
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]
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]VOLUME THREE 🌈
ACKNOWLEDGEMENTS 🫶
SECTION 1: INTRODUCTION TO VOLUME THREE 💖
same deal as before, nothing else lives under this heading, so on to the good stuff ✨
SECTION 2: PROTOCOL IMPLEMENTATION GUIDELINES 🛠️
this is where the implementation advice lives 🫡 TCP windows and acks, names and routes, reassembly, fault recovery, and a whole bunch of internetworking topics, some of which have RFC numbers and some of which don't
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 🧁
the appendices are a whole buffet 🍰 assigned numbers, address mappings, document formats, and a bunch of network-specific protocols for ARPANET, X.25, Ethernet, ARP and RARP, plus POP and mail stuff at the end
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]
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]📦 where this page comes from
- ietf: rfc980 1986-03
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms