Editing ARPANET (section)

== Networking evolution ==
{{more citations needed section|date=October 2022}}

=== IMP functionality ===

Because it was never a goal for the ARPANET to support IMPs from vendors other than BBN, the IMP-to-IMP protocol and message format were not standardized. However, the IMPs did nonetheless communicate amongst themselves to perform [[link-state routing]], to do reliable forwarding of messages, and to provide remote monitoring and management functions to ARPANET's Network Control Center. Initially, each IMP had a 6-bit identifier and supported up to 4 hosts, which were identified with a 2-bit index. An ARPANET host address, therefore, consisted of both the port index on its IMP and the identifier of the IMP, which was written with either <code>port/IMP</code> notation or as a single byte; for example, the address of MIT-DMG (notable for hosting development of [[Zork]]) could be written as either <code>1/6</code> or <code>70</code>. An upgrade in early 1976 extended the host and IMP numbering to 8-bit and 16-bit, respectively.{{citation needed|date=October 2022}}

In addition to primary routing and forwarding responsibilities, the IMP ran several background programs, titled TTY, DEBUG, PARAMETER-CHANGE, DISCARD, TRACE, and STATISTICS. These were given host numbers in order to be addressed directly and provided functions independently of any connected host. For example, "TTY" allowed an on-site operator to send ARPANET packets manually via the [[teletype]] connected directly to the IMP.{{citation needed|date=October 2022}}

=== 1822 protocol ===

The starting point for host-to-host communication on the ARPANET in 1969 was the [[1822 protocol]], which defined the transmission of messages to an IMP.<ref>{{cite tech report |url=http://www.bitsavers.org/pdf/bbn/imp/BBN1822_Jan1976.pdf |title=Interface Message Processor: Specifications for the Interconnection of a Host and an IMP |id=Report No. 1822 |publisher=Bolt Beranek and Newman, Inc. (BBN)}}</ref> The message format was designed to work unambiguously with a broad range of computer architectures. An 1822 message essentially consisted of a message type, a numeric host address, and a data field. To send a data message to another host, the transmitting host formatted a data message containing the destination host's address and the data message being sent, and then transmitted the message through the 1822 hardware interface. The IMP then delivered the message to its destination address, either by delivering it to a locally connected host, or by delivering it to another IMP. When the message was ultimately delivered to the destination host, the receiving IMP would transmit a ''Ready for Next Message'' (RFNM) acknowledgment to the sending, host IMP.{{citation needed|date=October 2022}}

=== Network Control Protocol ===

Unlike modern Internet datagrams, the ARPANET was designed to reliably transmit 1822 messages, and to inform the host computer when it loses a message; the contemporary [[Internet Protocol#Reliability|IP]] is unreliable, whereas the [[Transmission Control Protocol|TCP]] is reliable. Nonetheless, the 1822 protocol proved inadequate for handling multiple connections among different applications residing in a host computer. This problem was addressed with the [[Network Control Protocol (ARPANET)|Network Control Protocol]] (NCP), which provided a standard method to establish reliable, flow-controlled, bidirectional communications links among different processes in different host computers. The NCP interface allowed [[application software]] to connect across the ARPANET by implementing higher-level [[communication protocols]], an early example of the ''protocol layering'' concept later incorporated in the [[OSI model]].<ref name="LINCP"/>

NCP was developed under the leadership of [[Steve Crocker]], then a graduate student at UCLA. Crocker created and led the Network Working Group (NWG) which was made up of a collection of graduate students at universities and research laboratories, including [[Jon Postel]] and [[Vint Cerf]] at UCLA. They were sponsored by ARPA to carry out the development of the ARPANET and the software for the host computers that supported applications.

=== TCP/IP ===

[[Stephen J. Lukasik]] directed DARPA to focus on internetworking research in the early 1970s. Bob Kahn moved from BBN to DARPA in 1972, first as program manager for the ARPANET, under Larry Roberts, then as director of the IPTO when Roberts left to found [[Telenet]]. Kahn worked on both satellite packet networks and ground-based radio packet networks, and recognized the value of being able to communicate across both. Steve Crocker, now at DARPA, and the leaders of British and French network projects founded the [[International Network Working Group]] in 1972 and, on Crocker's recommendation, [[Vint Cerf]], now on the faculty at [[Stanford University]], became its Chair.<ref name="Pelkey8.3">{{cite book |last=Pelkey |first=James |title=Entrepreneurial Capitalism and Innovation: A History of Computer Communications 1968–1988 |chapter=8.3 CYCLADES Network and Louis Pouzin 1971–1972 |chapter-url=https://historyofcomputercommunications.info/section/8.3/CYCLADES-Network-and-Louis-Pouzin-1971-1972/}}</ref><ref name="Hafnerp222">{{harvnb|Hafner|Lyon|1996|p=[https://archive.org/details/wherewizardsstay00haf_vgj/page/222/mode/2up 222]}}</ref><ref name=":02">{{Cite journal|last=McKenzie |first=Alexander|date=2011 |title=INWG and the Conception of the Internet: An Eyewitness Account |journal=IEEE Annals of the History of Computing|volume=33|issue=1|pages=66–71|doi=10.1109/MAHC.2011.9 |s2cid=206443072|issn=1934-1547}}</ref> This group considered how to interconnect packet switching networks with different specifications, that is, [[internetworking]]. Research led by Kahn and Cerf resulted in the formulation of the [[Transmission Control Program]],<ref name=":1" /> which incorporated concepts from the French [[CYCLADES]] project directed by [[Louis Pouzin]].<ref name=":7">{{Cite news|url=https://www.economist.com/news/technology-quarterly/21590765-louis-pouzin-helped-create-internet-now-he-campaigning-ensure-its|title=The internet's fifth man|date=2013-11-30|newspaper=The Economist|access-date=2020-04-22|issn=0013-0613|quote=In the early 1970s Mr Pouzin created an innovative data network that linked locations in France, Italy and Britain. Its simplicity and efficiency pointed the way to a network that could connect not just dozens of machines, but millions of them. It captured the imagination of Dr Cerf and Dr Kahn, who included aspects of its design in the protocols that now power the internet.}}</ref> Its specification was written by Cerf with [[Yogen Dalal]] and Carl Sunshine at Stanford in December 1974 ({{IETF RFC|675}}). The following year, testing began through concurrent implementations at Stanford, BBN and [[University College London]].<ref name=":3">{{cite web|title=How the Internet Came to Be|url=http://elk.informatik.hs-augsburg.de/tmp/cdrom-oss/CerfHowInternetCame2B.html|author1=by Vinton Cerf, as told to Bernard Aboba|date=1993|access-date=25 September 2017|quote=We began doing concurrent implementations at Stanford, BBN, and University College London. So effort at developing the Internet protocols was international from the beginning. ... Mar '82 - Norway leaves the ARPANET and become an Internet connection via TCP/IP over SATNET. Nov '82 - UCL leaves the ARPANET and becomes an Internet connection.|url-status=dead|archive-date=26 September 2017|archive-url=https://web.archive.org/web/20170926042220/http://elk.informatik.hs-augsburg.de/tmp/cdrom-oss/CerfHowInternetCame2B.html}}</ref> At first a monolithic design, the software was redesigned as a modular protocol stack in version 3 in 1978. [[IPv4|Version 4]] was installed in the ARPANET for production use in January 1983, replacing NCP. The development of the complete [[Internet protocol suite]] by 1989, as outlined in {{IETF RFC|1122}} and {{IETF RFC|1123}}, and [[Internet protocol suite#Adoption|partnerships with the telecommunication and computer industry]] laid the foundation for the adoption of TCP/IP as a comprehensive protocol suite as the core component of the emerging [[Internet]].<ref name="LITCPIP" />