Tweet This is a modified version of the Internet RFC suitable for machine-translating. Original version is available here: RFC694
Ad
UNKNOWN
Network Working Group J. Postel
NWG / Request for Comments: 694 SRI-ARC
June 18, 1975
Protocol Information
Introduction
This file contains information on the various protocols in the ARPA Network. An effort will be made to keep the information current, but his depends on the cooperation of the users of this file to convey any information about protocol developments, or corrections to this information to Jon Postel at SRI-ARC.
Online address is POSTEL@BBNB; Phone is (415) 326-6200 x 3718; U.S. Mail address is Stanford Research Institute, Augmentation Research Center, 222 Ravenswood, Menlo park, California 94025.
This is a compendium of all the protocol related activity and most of this activity and most of this activity is with experimental protocols, for those protocols, which are official standards the designation "[Official]" will be appended to the name.
Much of the documentation of protocols appears as Requests for Comments (RFCs) and many of these are available online. When a document is accessible online a pointer to that source will be given. Also note that recent RFCs are online at Office-1 in directory <NETINFO> with names of the form RFCnnn.TXT where nnn is replaced by the RFC number. There is also an index of recent RFCs as an online file:
There are two files that list the addresses of the Network Liaisons, one file lists the online message address, and the other the US Mail address and phone number. A network liaison is a person designated by a host organization as the contact and coordinator for network technical information fro that organization.
These files are prepared by Jake Feinler of the Network Information Center (NIC). Indeed the NIC has been very helpful in providing the online file space for the recent Request for Comments, and other protocol related files. The NIC also maintains the hardcopy reference library of all RFCs.
The NIC has assembled and filed with the National Technical information Service the collection of documents known as "ARPA Network Current Network Protocols". This collection represents the more or less "official" protocols as of 1-December-74. The accession number is ADA003890.
IMP-IMP
surface
Contact:
Alex McKenzie (MCKENZIE@BBN)
Documents:
Heart, F. et. al. "the Interface Message Processor for the ARPA Computer Network," AFIPS Conference Proceedings, 36:551-567, SJCC 1970.
McQuillan, J.M. et. al. "Improvements in the Design and Performance of the ARPA Network," AFIPs Conference Proceedings, 41:741-754 RFCC, 1972.
McQuillan, J.M. "Throughput in the ARPA network - Analysis and Measurement," BBN Report 2491, the text is also contained in BBN Quarterly Technical Report 16, available from the National Technical Information Service [NTIS] accession number AD7544441.
The "link number" field has been extended from 8 to 12 bits and renamed the "message identification" field. Message type 6 now is used to indicate a reason for at type 7 (destination dead) message. (See BBN1822).
There has been some recent changes to the Ready line interpretation by the IMP for deciding the alive/dead status of a host.
Important changes to the IMP and IMP/HOST Interface announced in RFC 660 23-Oct-74.
(31-DEC-74) The change to allow up to eight messages to be in transit between a source host and destination host should be made very soon. This should not effect the hosts at all except to provide better thruput and fewer inter-message delays.
(6-JAN-75) BBN Report 1822 updated.
Sections 1, 2, 4, and 5, and Appendix C now include data on the Pluribus IMP. The Pluribus IMP is based on a modular mutliprocessor hardware design; it should be capable of much higher bandwidth and greater reliability than other IMP models.
Section 3.1 contains additional information, which may be helpful to Host programmers.
Section 3.3 and 3.4 add a new type of Host to Host data message, the uncontrolled packet. Section 3.7 has been added to describe the use of this new message type.
Section 3.4 describes changes to the sub-types of IMP to host message types 6 and 7.
Appendix A has been updated. Appendix B has been expanded to provide specific recommendations for Host implementation of the Host/IMP Interface.
Minor clarifications have been made in Appendix F. (No changes have been made to Figure F - (or F-9.)
Recent developments:
(18-June-75) Very important changes to the Host to IMP and IMP to Host interface protocol are proposed (specified?) in a recent note. The areas changed include: expanded leader size, expanded address field, new message length field, expanded handling type field, source host control of packets per message, change in the handling of unordered messages (current type 3 messages), change in the addressing of fake hosts, including an address field in the IMP/Host hop message, (best of all) backward compatibility, and a possible change in the maximum message length.
Walden, D. "IMP/Host and Host/IMP Protocol Change," RFC 687, NIC 32654, 2-Jun-75.
McKenzie, A. "host/Host Protocol for the ARPA Network," NIC 8246, NTIS: AD757680, Jan 1972.
Postel, J. "Assigned link Numbers," RFC 604, NIC 21186, 26-Dec-73.
Burchfiel, et. al. "Tip-Tenex Reliability Improvements" RFC 636 NIC 30490 June 1974.
People:
Jon Postel (POSTEL@BBNB)
Alex McKenzie (MCKENZIE@BBN)
Jerry Burchfiel (BURCHFIEL@BBN)
Dave Walden (WALDEN@BBN)
Schedule:
Comments:
The BBN TIP and TENEX groups have specified and are implementing additional protocol commands with the intention of providing better reliability and survivability over system malfunctions. The additional protocol commands are for cleaning up partly closed connections and resynchronizing the allocation values on open connections (see RFC 636).
Walden, D. "A System for Interprocess Communication in a Resource Sharing Computer Network, " RFC 62, NIC 4962, 3-Aug- 70. Also published in Communications of the ACM volume 15, number 4, April 1972.
Bressler, B. "A Proposed Experiment with a Message Switching Protocol, " RFC 333, NIC 9926, 15-May-72.
People:
Dave Walden (WALDEN@BBN)
Bob Bressler (BRESSLER@BBN)
Schedule:
Comments:
Recent developments:
tcp - Transmission Control Protocol
Contact:
Vint Cert (CERF@ISI)
Documents:
Cert, V. and R,. Kahn. "A Protocol for Packet Network Intercommunication," IEEE Transactions on Communication Vol COM- 22 No 5, May 1974.
Mader, E. "A Protocol Experiment," RFC 700, NIC 31020.
Some experiments now running. Implementation of full protocol to begin by 1-Jan-75.
Comments:
Specification completed August 4th, but some work still in progress on handling of single message conversations. A new sequencing scheme (proposed by Tomlinson) may be utilized. The addressing field is now used as 4 bit format, 4 bit network, 16 bit TCP, and 24 bit process&port.
Crocker has suggested a 64 bit path address to be parsed and reformatted by the gateways along the route. There is reluctance to experiment with too many things at once though.
(28-Oct-74) A file indicating some of the changes in the specifications since the 4-Aug-74 document is now available as [ISI] <CRF> TCP- CHANGES. The areas of change are "Initial Sequence Number", "Socket definition", "Additional User System Calls", "Packet Format", and "Discussion of opening and closing (SYN, REL)".
(23-NOV-74) Specifications for test implementation are now said to be ready on 1-DEC-74, and an implementation completed by 1- FEB-74.
(31-DEC-74) New specification document available:
Cerf, V. Y. Dalal, and C. Sunshine. "Specification of Internet Transmission Control Program," RFC 675, INWG 72, NIC 31505, December 1974 Revision.
Status of TCP development. The BBN version is running at BBN-TENEXA, but simulates a lot of JSYS calls which will be cast into the tenex operating system during the summer. The SU-DSL version for the PDP-11/20 is in the debugging stage. The UCL (London) version for a PDP-9 is in the coding stage. We are continuing with the "three-way handshake" version which is highly reliable in environments which permit packets to be delivered on the order of hours later than they were injected into the connected networks. A simple TCP is being designed for the packet radio network and does not use three-way handshake since waiting a second or so to clear out old packets in not serious.
A test plan for packet radio net, arpanet, and atlantic satellite networks is in preparation (delivery date 1 August 1975).
Recent international agreements indicate that a form of TCP with a simpler header (144 bits instead of 256 bits) and no three-way handshake is the most likely international standard. An IFIP WG 6.1 Recommendation to CCITT stated that the maximum packet delay through all concatenated networks should not exceed 30 seconds.
nvp - Network Voice Protocol
Contact:
Danny Cohen (COHEN@ISIB)
Documents:
"Specifications for the Network Voice Protocol (NVP)" NSC Note
43.
People:
Schedule:
Comments:
Specification document available (10-Oct-74). (20-JAN-75) An initial version of NVP was implemented for real-time voice experiments between ISI and Lincoln Laboratory in August 1974. An expanded version has been in operation since December 1974 for real-time voice communication between Lincoln and CHI. NVP uses both type 0 and type 3 IMP-Host messages, and allows increased bandwidth and decreased delays at the cost of reliability.
All Hosts were to have been running the new Telnet (both user and server) by 1 January 1974.
Comments:
Note: the server program is to be available on socket 23 decimal (27 octal).
The Status Option has been revised to take advantage of the subcommand feature and to reduce the amount of data transmitted to report the option status.
Seven new options have been defined to allow control of the format effectors Carriage Return, Line Feed, Form Feed, Horizontal Tab, and Vertical Tab.
(31-DEC-74) Rick Schantz has made some suggestions regarding the Reconnection Option in:
Schantz, R. "A Note on Reconnection Protocol," RFC 671, NIC 31439, 6-Dec-74.
(31-DEC-74) Kanodia has published an RFC on performance measurements of FTP at Multics, which shows the important effect of Host buffering in constraining thruput.
Kanodia, R. "Performance Improvement in ARPANET File Transfers From Multics," RFC662, NIC 31386, 26-Nov-74.
(15-May-75) The Tenex FTP implementation has been extended to transfer paged files as described in: Clements, R. "FTPSRV - Extensions for Tenex Pages Files," RFC 683, NIC 32251, 3-April-75.
(18-Jun-75) Brian Harvey has suggested that old FTP is good enough, that it is in wide use, so lets just fix the bugs instead of implementing new FTP. His suggested bug fixes are also included in his RFC:
Harvey, B. "One More Try on the FTP," RFC 691, NIC 32700, 6- Jun-75.
Anderson, B. "Status Report on Proposed Data Reconfiguration Service," RFC 138, NIC 6715, 28-April-71.
Feah, "Data Reconfiguration Service at UCSB," RFC 437, NIC 13701, 30- June-74.
People:
Schedule:
Comments:
Recent developments:
RSEXEC - The Resource Sharing Executive
Contact:
Robert Thomas (THOMAS@BBN)
Documents:
Thomas, R. "A Resource Sharing Executive For the ARPANET," AFIPS Conference Proceedings, 42;155-163, NCC, 1973.
People:
Robert Thomas (THOMAS@BBN)
Schedule:
Comments:
The TIPs and some RSEXEC servers now are cooperating to perform TIP user authentication and accounting functions.
Recent developments:
Line Processor Protocol
Contact:
Don Andrews (ANDREWS@BBNB)
Documents:
[BBNB] <LP>MCS4.NLS Andrews, D. "Line Processor - A Device for Amplification of Display Terminal Capabilities for Text Manipulation," AFIPS Conference Proceedings, 43:257-265, NCC, 1974.
The national Software Works (NSW) is developing a set of protocols for its use of the ARPA Network, other uses of these protocols is encouraged.
The Distributed Programming System (DPS) is intended to facilitate the sharing of resources in the network at the subroutine level. The Distributed Programming System will be used to split NLS into a front end and back end components. Distributed Programming system is also to be used in the NSW and the basis for communication between the Works Manager, the Tool Bearing Hosts, and Front End procedure packages.
The documents cited below give a view of the Distributed Programming System and its use.
The documents cited here represent the state of the protocol in January-75, much as changed since that time that has not been adequately documented, therefore, these documents should be viewed as generally descriptive not specifically definitive.
Each is available online in two forms: as an NLS file and as a formatted text file. The Journal number (e.g., 24459) refers to the former, of course and the pathname (e.g., [BBNB] <NLS>PCP.TXT) to the latter, accessible via FTP using username=ANONYMOUS and password=GUEST (no account required).
In addition, these documents are available from Jon Postel in hardcopy.
PCP (24459,) "The Procedure Call Protocol"
This document describes the virtual programming environment provided by PCP, and the inter-process exchanges that implement it.
This document describes a package that runs in the setting provided by PCP and that serves as procedure-call-level interface to PCP proper. It includes procedures for calling, resuming, interrupting, and aborting remote procedures.
This document describes a package that runs in the setting provided by PCP and that augments PCP proper, largely in the area of data store manipulation. It includes procedures for obtaining access to groups of remote procedures and data stores, manipulating remote data stores, and creating temporary ones.
This document describes a package that runs in the setting provided by PCP and that provides the necessary tools for interconnecting two or more processes to form a multi- process system (e.g., NSW). It includes procedures for creating, deleting, logically and physically interconnecting processes, and for allocating and releasing processors.
This document defines an implementation, appropriate for mediating communication between processes on different hosts within the ARPANET, of the IPC primitives required by PCP.
PCPTNXINT (24792,) "Tenex PCP Process internal Structure"
This document defines the internal structure of a PCP process implemented to run on Tenex, and as such serves as a process implementer's guide. It describes the process' fork structure, the role and composition of each fork, and the manner in which the various forks interact with one another; indicates which components are supplied with PCP and which are the responsibility of the process implementer; and describes the manner in which the components are assembled at load time.
This document describes the host level protocol used in the NSW. The protocol is a slightly constrained version of the standard ARPANET host to host protocol. The constraints affect the allocation, RFNM wait, and retransmission policies.
This document describes a package that runs in the setting provided by PCP. It includes procedures and data stores for user identification, accounting, and usage information.
This document describes a package that runs in the setting provided by PCP. It includes procedures and data stores for opening, closing, and listing directories, for creating, deleting, and renaming files, and for transferring the files and file elements between processes.
This appendix contains some comments on implementation strategy. The thrust is to argue that the file package as specified is near minimal and that the conversion between the PCP format and the internal storage format can be encapsulated into a few subroutines.
This document describes a package that urns in the setting provided by PCP. It includes procedures for creating and deleting batch jobs, obtaining the status of a batch job, and communicating with the operator of a batch processing host. This package is implemented at the host that provides the batch processing facility.
This document describes a package that runs in the setting provided by PCP. It includes procedures for a remote process to debug at the assembly-language level, any processes known to the local process. The package contains procedures for manipulating and searching the process' address space, for manipulating and searching its symbol tables, and for setting and removing breakpoints from its address space. Its data stores hold process characteristics and state information, and the contents of program symbol tables.
RJE-MODEL (24655,) "The NSW Remote Job Entry Model"
This document discusses the process of utilizing a batch processing facility to complete a programming task in the NSW environment. This same activity in another environment might utilize a remote job entry system.
NVTP (24827,) "The Network Virtual Terminal Package"
The Network Virtual Terminal Package (package name = NVTP) contains the procedures interfacing PCP procedure calls to terminal oriented input and output character streams as defined by the ARPANET Telnet protocol.
(15-May-75) Significant changes in design and initial scope have altered the implementation of the Distributed Programming System from the design presented in these documents, the documents still serve to give the flavor of the intended system, but no longer are a reliable guide to the details of the actual implementation.
(18-Jun-75) The L10 source code of the Tenex implementation is available online as:
0-63 0-77 Network Wide Standard Function
64-127 100-177 Hosts Specific Functions
128-223 200-337 Reserved for Future Use
224-255 340-377 Any Experimental Function
Specific Assignments:
Decimal Octal Use 1 1 Old Telnet 3 3 Old File Transfer 5 5 Remote Job Entry 7 7 Echo 9 11 Discard 11 13 Who is on or SYSTAT 13 15 Date and Time 15 17 Who is up or NETSTAT 17 21 Short Text Message 19 23 Character generator TTYTST 21 25 New File Transfer 23 27 New Telnet 25 31 Distributed Programming System 65 101 Speech Data Base at LL-TX-2 67 103 Datacomputer at CCA 69 105 CPYTNET 71 107 NETRJS (EBCDIC) at UCLA-CCN 73 111 NETRJS (ASCII) at UCLA-CCN 75 113 NETRJS (TTY) at UCLA-CCN 77 115 any private RJE server 232-237 350-355 Authorized Mailer at BBN 239 357 Graphics 241 361 NCP Measurement 243 363 Survey Measurement 245 365 LINK 247 367 TIPSRV 249-255 371-377 RSEXEC
(31-DEC-74) Socket 25 (31 octal) assigned to Distributed Programming System.
Recent developments:
Postel [Page 36]
Ad
Translate documents to 日本語, svenska, Nederlands, Deutsch, français, русский, italiano, español, Tiếng Việt, polski, português, 中文, українська, català, norsk, فارسی, suomi, Bahasa Indonesia, العربية, čeština, 한국어, Bahasa Melayu, magyar, română, српски and other languages.
