Network Control Protocol (ARPANET)

The Network Control Protocol (NCP) was a communication protocol for a computer network in the 1970s and early 1980s. It provided the transport layer of the protocol stack running on host computers of the ARPANET, the predecessor to the modern Internet.

NCP preceded the Transmission Control Protocol (TCP) as a transport layer protocol used during the early ARPANET. NCP was a simplex protocol that utilized two port numbers, establishing two connections, for two-way communications. An odd and an even port were reserved for each application layer application or protocol. The standardization of TCP and UDP reduced the need for the use of two simplex ports for each application down to one duplex port.^[1]^: 15

There is some confusion over the name, even among the engineers who worked with the ARPANET.^[2] Originally, there was no need for a name for the protocol stack as a whole, so none existed. When the development of TCP started, a name was required for its predecessor, and the pre-existing acronym 'NCP' (which originally referred to Network Control Program, the software which implemented this stack) was organically adopted for that use.^[3]^[4] Eventually, it was realized that the original expansion of that acronym was inappropriate for its new meaning, so a new quasi-backronym was created, 'Network Control Protocol' - again, organically, not via a formal decision.^[5]^[6]

^ Stevens, W. Richard (1994). TCP/IP Illustrated Volume I. Vol. 1. Reading, Massachusetts, USA: Addison-Wesley Publishing Company. ISBN 0-201-63346-9.
^ Crocker, Stephen (27 June 2022). "Separation of TCP and IP". elists.isoc.org. Retrieved 5 August 2022.
^ "Internetting or Beyond NCP" (PDF). Retrieved 4 August 2022.
^ Proposed Revisions to the TCP (PDF). IEN 18. Retrieved 4 August 2022.
^ Reynolds, J.; Postel, J. (1987). The Request For Comments Reference Guide. doi:10.17487/RFC1000. RFC 1000. Over the next few months we designed a symmetric host-host protocol, and we defined an abstract implementation of the protocol known as the Network Control Program. ("NCP" later came to be used as the name for the protocol, but it originally meant the program within the operating system that managed connections. The protocol itself was known blandly only as the host-host protocol.)
^ Mail Transfer Protocol. doi:10.17487/RFC0772. RFC 772. Retrieved 5 August 2022.

[stevens1994v1-1] Stevens, W. Richard (1994). TCP/IP Illustrated Volume I. Vol. 1. Reading, Massachusetts, USA: Addison-Wesley Publishing Company. ISBN 0-201-63346-9.

[2] Crocker, Stephen (27 June 2022). "Separation of TCP and IP". elists.isoc.org. Retrieved 5 August 2022.

[NCPReuse1-3] "Internetting or Beyond NCP" (PDF). Retrieved 4 August 2022.

[NCPReuse2-4] Proposed Revisions to the TCP (PDF). IEN 18. Retrieved 4 August 2022.

[rfc1000-5] Reynolds, J.; Postel, J. (1987). The Request For Comments Reference Guide. doi:10.17487/RFC1000. RFC 1000. Over the next few months we designed a symmetric host-host protocol, and we defined an abstract implementation of the protocol known as the Network Control Program. ("NCP" later came to be used as the name for the protocol, but it originally meant the program within the operating system that managed connections. The protocol itself was known blandly only as the host-host protocol.)

[NCPReDefinition-6] Mail Transfer Protocol. doi:10.17487/RFC0772. RFC 772. Retrieved 5 August 2022.

[1]

[2]

[3]

[4]

[5]

[6]