Network Control Protocol

Network Control Protocol. It was the foundational transport-layer protocol suite for the early ARPANET, enabling reliable communication between host computers across the packet-switched network. Developed by the Network Working Group, including key figures like Steve Crocker and Vint Cerf, it managed the establishment and termination of logical connections. NCP's operation was intrinsically linked to the underlying Interface Message Processor and the 1822 protocol, forming a complete host-to-host service layer.

Overview and Purpose

The primary purpose was to provide a standardized method for ARPANET host computers to establish and manage bidirectional communication streams, known as connections. It abstracted the complexities of the underlying network, allowing application programs on diverse systems like the IBM System/360, DEC PDP-10, and Xerox Sigma 7 to exchange data. This protocol suite was essential for enabling early network applications, including remote login via the Telnet protocol and file transfer, which later evolved into the File Transfer Protocol. Its development was a critical step in moving the ARPANET from a hardware-centric experiment to a usable software-driven resource-sharing network.

Technical Design and Operation

Technically, it operated by exchanging specific control messages to open and close connections between software processes on different hosts. A connection was established using an initial connection protocol, which involved a handshake to synchronize initial sequence numbers and negotiate parameters. Data flow was managed using a sliding window mechanism for reliability and flow control, with acknowledgments and retransmissions handled within the protocol. Control commands and data were encapsulated in messages transmitted over the 1822 protocol to the local Interface Message Processor. The design assumed a reliable network layer, as the ARPANET itself provided guaranteed delivery of packets between IMPs, which simplified its error-correction duties compared to later internet protocols.

Protocol Stack and Implementation

Within the early ARPANET protocol stack, it resided above the host-to-IMP 1822 protocol and below the nascent application protocols. Its implementation was part of the Network Control Program, a software package each host site installed to interface with the network. This suite included not only the core connection management logic but also preliminary versions of application protocols. The first official specification was published in RFC 33, with subsequent refinements documented in numerous other Request for Comments documents. Implementations varied by host operating system, such as the TOPS-10 for DEC machines, but adhered to the common standard to ensure interoperability across the heterogeneous ARPANET.

Historical Context and Evolution

Its development began in 1969, following the physical deployment of the first IMPs connecting UCLA, SRI, UCSB, and the University of Utah. It became the standard ARPANET host protocol in 1970, following the publication of its specification. For nearly a decade, it facilitated groundbreaking network experimentation and collaboration, supporting work at institutions like BBN, MIT, and Carnegie Mellon University. The protocol's limitations in supporting interconnected networks, a concept advanced by Robert Kahn and Vint Cerf, led to the design of the Transmission Control Protocol. A scheduled transition on January 1, 1983, known as the flag day, permanently replaced it with the Internet protocol suite, marking the birth of the modern Internet.

Comparison with Successor Protocols

Unlike its successor, the connection-oriented Transmission Control Protocol, it lacked an end-to-end host-based error recovery mechanism, relying instead on the reliability of the ARPANET interior. Furthermore, it was designed for a single, homogeneous network architecture and could not route data between disparate networks, a fundamental capability of the subsequent Internet Protocol. The Transmission Control Protocol integrated host-to-host communication with robust error handling, while the Internet Protocol handled the internetwork routing and addressing, a separation of concerns absent in the earlier suite. This comparison highlights the evolutionary leap from a network-specific utility to a universal internetworking framework, as envisioned in the seminal paper by Cerf and Kahn.

Category:ARPANET Category:Network protocols Category:History of the Internet