The Network Control Program (sometimes the abbreviation NCP is mistakenly expanded to Network Control Protocol, but this term is not found in the contemporary documentation) was the original protocol suite of the ARPANET.
In NCP, the physical layer, the data link layer, and the network layer were all specified by the Host/IMP Protocol. The transport layer was the Host-to-Host Protocol, together with the Initial Connection Protocol. Layers above that were all joined in with the application (e.g. FTP, SMTP, etc).
On January 1, 1983, parts of NCP were rendered obsolete when the ARPANET changed its core networking protocols from NCP to the more flexible and powerful TCP/IP protocol suite, marking the start of the Internet as we know it today.
Further reading
Feinler, E.; Postel, Jon B. ARPANET Protocol Handbook (Network Information Center, Menlo Park, 1978)
The NetworkControlProgram (sometimes the abbreviation NCP is mistakenly expanded to NetworkControl Protocol, but this term is not found in the contemporary documentation) was the original protocol suite of the ARPANET.
The NCPtransport layer was the Host-to-Host Protocol, together with the Initial Connection Protocol.
On January 1, 1983, parts of NCP were rendered obsolete when the ARPANET changed its core networking protocols from NCP to the more flexible and powerful TCP/IPprotocol suite, marking the start of the Internet as we know it today.
A control command is directed to a particular NCP by being sent to its HOST as a message over link number 1 (designated as the control link), which is reserved for that purpose.
Network Test Command ECO <48 bit code> An NCP may test the quality of communications between it and a foreign NCP by directing to it an ECO command with an arbitrary <48 bit code> (of the same length as a socket identifier) and 'on'.
NCP A uses this link number in deciding who the intended recipient is, and stores the message in a buffer for the recipient process.
Feeds |
Contact