Difference between revisions of "Network Control Program"

From Computer History Wiki
Jump to: navigation, search
(Add some detail on sockets, links, etc)
(addnl details)
Line 5: Line 5:
 
==Details==
 
==Details==
  
NCP provides [[reliable byte stream]]s, called 'connections', used by [[application]]s to talk to each other. It runs over the [[Host-to-IMP Protocol]], and consists of two semi-separate protocols:
+
NCP provides uni-directional [[reliable byte stream]]s, called 'connections', used by [[application]]s to talk to each other (usually a pair of connections, one in each direction). It runs over the [[Host-to-IMP Protocol]], and consists of two semi-separate protocols:
  
 
* Initial Connection Protocol (ICP)
 
* Initial Connection Protocol (ICP)
 
* ARPANET Host-to-Host Protocol (AHHP)
 
* ARPANET Host-to-Host Protocol (AHHP)
  
The connection was identified by a 'socket' at each end, along with the [[Host-to-IMP Protocol#Host addresses|addresses]] of the two hosts; socket numbers were 32 bits long. However, these did not appear in [[packet]]s; instead, 'link's were used. In the [[Host-to-IMP Protocol#Packet formats|original 32-bit leader]], there was an 8-bit link field; in the later 96-bit leader, there was a 12-bit field called the 'message ID', and the link field was the high 8 bits of this.
+
The connection was identified by a 'socket' at each end, along with the [[Host-to-IMP Protocol#Host addresses|addresses]] of the two hosts; socket numbers were 32 bits long. Only one connection was permitted to each socket at any host.
  
When a connection was set up, between one host/socket to another, it used a particular link, and no other connection could use that link until the connection was closed. Links were like [[virtual circuit]]s in their properties, in that packets sent on one were received reliably (although there was an error message when that didn't happen) and in order at the other end of the link, but they had no open/close - a host just started using a link.
+
However, sockets did not appear in [[packet]]s; instead, 'link's were used. In the [[Host-to-IMP Protocol#Packet formats|original 32-bit leader]], there was an 8-bit link field; in the later 96-bit leader, there was a 12-bit field called the 'message ID', and the link field was the high 8 bits of this; the low 4 bits were set to zero.
 +
 
 +
When a connection was set up, between one host/socket to another, it used a particular link, specified by the receiver, and no other connection could use that link until the connection was closed. Links were like [[virtual circuit]]s in their properties, in that packets sent on one were received reliably (although there was an error message when that didn't happen) and in order at the other end of the link, but they had no open/close - a host just started using a link.
  
 
One link, 0, was special - it was the 'control link'. All messages involved in opening and closing a connection were sent over the control link - only data messages belonging to a connection went over a connection's link.
 
One link, 0, was special - it was the 'control link'. All messages involved in opening and closing a connection were sent over the control link - only data messages belonging to a connection went over a connection's link.

Revision as of 23:14, 16 February 2019

The Network Control Program, canonically abbreviated to NCP (which people often, but incorrectly, think stands for 'Network Control Protocol'), is the transport protocol run between hosts connected to the ARPANET, prior to the introduction of TCP/IP.

Since then, many other networking software systems were also called NCP; the modern equivalent would be network stack.

Details

NCP provides uni-directional reliable byte streams, called 'connections', used by applications to talk to each other (usually a pair of connections, one in each direction). It runs over the Host-to-IMP Protocol, and consists of two semi-separate protocols:

  • Initial Connection Protocol (ICP)
  • ARPANET Host-to-Host Protocol (AHHP)

The connection was identified by a 'socket' at each end, along with the addresses of the two hosts; socket numbers were 32 bits long. Only one connection was permitted to each socket at any host.

However, sockets did not appear in packets; instead, 'link's were used. In the original 32-bit leader, there was an 8-bit link field; in the later 96-bit leader, there was a 12-bit field called the 'message ID', and the link field was the high 8 bits of this; the low 4 bits were set to zero.

When a connection was set up, between one host/socket to another, it used a particular link, specified by the receiver, and no other connection could use that link until the connection was closed. Links were like virtual circuits in their properties, in that packets sent on one were received reliably (although there was an error message when that didn't happen) and in order at the other end of the link, but they had no open/close - a host just started using a link.

One link, 0, was special - it was the 'control link'. All messages involved in opening and closing a connection were sent over the control link - only data messages belonging to a connection went over a connection's link.

Further reading

  • Jon Postel, "Official Initial Connection Protocol", June 1971, NIC #7101, UCLA-NMC (this does not seem to be online, but an early version, which is almost identical to the final version, can be found here)
  • Alex McKenzie; Jon Postel "Host-to-Host Protocol for the ARPANET", October 1977, NIC #8246, Network Information Center

External links