Internet Protocol Handbook: Table of contents
A draft contents list for a planned binder of the main Internet protocol documents.
Postel, J., "Internet Protocol Handbook: Table of contents", RFC 774, DOI 10.17487/RFC0774, October 1980, <https://www.rfc-editor.org/info/rfc774>.
@misc{rfc774,
series = {Request for Comments},
number = 774,
howpublished = {RFC 774},
publisher = {RFC Editor},
doi = {10.17487/RFC0774},
url = {https://www.rfc-editor.org/info/rfc774},
author = {J. Postel},
title = {{Internet Protocol Handbook: Table of contents}},
pagetotal = 3,
year = 1980,
month = oct,
} RFC text
Contents
Network Working Group J. Postel
Request for Comments: 774 ISI
October 1980
Obsoletes: RFCs 766
Obsoletes: IENs, 118
Internet Protocol Handbook
Table of Contents
The internet family of protocols is replacing the old ARPANET protocols.
To this end an Internet Protocol Handbook will be prepared by the
Network Information Center. This Handbook is tentatively planned to be
available at the end of 1980. This Internet Protocol Handbook will
closely parallel the old ARPANET Protocol Handbook, and will primarily
be a collection of existing RFCs and IENs.
Attached is the current draft table of contents for the Internet
Protocol Handbook. Any suggestions for additions should be sent to Jon
Postel (Postel@ISIF).
RFCs and IENs are public access document files and may be copied from
the Network Information Center online Library at SRI-KL via FTP using
the FTP user name ANONYMOUS and password GUEST. The IENs have pathnames
of the form "<NETINFO>IEN-nnn.TXT", and the RFCs have pathnames of the
form "<NETINFO>RFCnnn.TXT", where "nnn" is replaced by the document
number. [Note the inconsistency: IENs have a hyphen in the pathname,
RFCs don't.]
RFC 774
Internet Protocol Handbook
Table of Contents
Overview
The Catenet Model for Internetworking IEN-48
Gateway Level
Internet Protocol IEN-128 RFC760
Gateway Routing: An Implementation Specification IEN-30
How to Build a Gateway IEN-109
Gateway Monitoring Protocol IEN-131
CMCC Performance Measurement Message Formats IEN-157
Host Level
User Datagram Protocol RFC768
Transmission Control Protocol IEN-129 RFC761
Multiplexing Protocol IEN-90
Application Level
Time Server Protocol IEN-142
Name Server Protocol IEN-116
Trivial File Transfer Protocol IEN-133
Telnet Protocol IEN-148 RFC764
File Transfer Protocol IEN-149 RFC765
Mail Transfer Protocol RFC772
Internet Message Protocol IEN-113 RFC759
RFC 774
Internet Protocol Handbook
Appendices
Assigned Numbers RFC770
Address Mappings IEN-115
Document File Format Standards RFC678
Mail Header Format Standards RFC733
AI ELI5
On this page
§1The Planned Handbook
RFC 774 says the internet family of protocols was replacing the old ARPANET protocols. To support that, the Network Information Center was to prepare an Internet Protocol Handbook, tentatively planned to be available at the end of 1980.
The Handbook would closely parallel the old ARPANET Protocol Handbook and would mostly be a collection of existing RFCs and IENs. Suggestions for additions were to be sent to Jon Postel.
Before the internet rules were scattered everywhere, someone planned to gather the important ones into one binder.
§2How the Contents Are Organized
The draft table of contents has five groups. Overview holds the catenet model for internetworking (IEN-48). Gateway Level starts with the Internet Protocol (IEN-128, RFC 760) and also lists gateway routing, building a gateway, gateway monitoring and performance measurement message formats.
Host Level lists the User Datagram Protocol (RFC 768), the Transmission Control Protocol (IEN-129, RFC 761) and the Multiplexing Protocol (IEN-90). Application Level covers the time server, name server and trivial file transfer protocols, Telnet, File Transfer Protocol, Mail Transfer Protocol and the Internet Message Protocol.
The Appendices list Assigned Numbers (RFC 770), Address Mappings (IEN-115), Document File Format Standards (RFC 678) and Mail Header Format Standards (RFC 733).
The binder is sorted like a building: big picture first, then the parts that move packets between networks, then the parts computers use to talk, then the programs people use, then reference tables at the back.
§3Finding the Documents
The memo notes that RFCs and IENs are public access files that can be copied from the Network Information Center online Library at SRI-KL using FTP with the user name ANONYMOUS and password GUEST.
IEN pathnames look like <NETINFO>IEN-nnn.TXT and RFC pathnames look like <NETINFO>RFCnnn.TXT, where nnn is the document number. The memo points out an inconsistency: IENs have a hyphen in the pathname and RFCs do not.
The memo also tells you where to download each paper and warns that two kinds of file names are spelled slightly differently.