Version early phases of the design work, R. Metcalfe, A. McKenzie, H. Zimmerman, G. LeLann, and M. Elie were most helpful in explicating the various issues to be resolved. Of course, we remain responsible for the remaining errors and misstatements which no doubt lurk in the nooks and crannies of the text. Processes are viewed as the active elements of all HOST computers in a network. Even terminals and files or other I/O media are viewed as communicating through the use of processes. Thus, all network communication is viewed as inter-process communication. Since a process may need to distinguish among several communication streams between itself and another process [or processes], we imagine that each process may have a number of PORTs through which it communicates with the ports of other processes. Since port names are selected independently by each operating system, TCP, or user, they may not be unique. To provide for unique names at each TCP, we concatenate a NETWORK identifier, and a TCP identifier with a port name to create a SOCKET name which will be unique throughout all networks connected together.

serves as Vice-chairman (United States) of IFIP Working Group 6.4 on Local Computer Networks.

No abstract

No abstract

Introductio nAs plans for network interconnection develop, the problems o f internet routing and addressing become increasingly important . In on e popular model of internet addressing, a hierarchical form of network an d local (within network) address is used, with the source providing onl y the destination address while the intermediate network(s) and/or Gateway s between networks take care of routing packets to that destination b y various paths . This and related techniques requiring some form o f routing table and knowledge at intermediate nodes are more full y discussed in [1,2,3] .