Summary

  • RFC 801 set 1 January 1983 as the end of a migration that each host organization had to implement, with dual-protocol relays bridging selected services in between.
  • The 1985 retrospective confirms the cutover date but records mail-relay dependence, host-table problems and service-host performance work afterward.

Analysis

A “flag day” sounds like one coordinated software update. The ARPANET’s NCP-to-TCP migration was closer to a deadline imposed on many separate operators. In November 1981, RFC 801 asked each host organization to implement IP/TCP and the principal services—Telnet, file transfer and mail—on its own systems. The task was supposed to begin by January 1982; the complete switch from NCP was targeted for 1 January 1983.

The transition plan assumed systems would not move together. Some hosts would speak TCP while others still used the Network Control Protocol (NCP). RFC 801 therefore set out relay hosts that could run both environments and carry Telnet, FTP or mail between them. A user transferring a file across the boundary might log in to a relay, fetch the file from an NCP host, then retrieve it over TCP. Compatibility was an operating service, not an abstract promise.

Mail had its own earlier planning. RFC 773, from October 1980, explored forwarding between old and new mail systems and listed unfinished questions, including how to designate forwarders and distribute host-name and capability information. This was not just about changing packet formats: names had to resolve, users needed a route to other mailboxes, and service operators had to keep a working bridge available.

RFC 801’s schedule forecast that most hosts would use TCP by July 1982, the final NCP-only host would complete conversion by November, and “full Internet service” would follow in January 1983, when NCP and the relays were removed. Those milestones were targets in a plan. A later account supplies the execution evidence: RFC 942, published in 1985, refers to the ARPANET cutover on 1 January 1983 after years of parallel use and a final six-month run-up that added TCP-only hosts.

The retrospective complicates the clean ending. Terminal access controllers and service hosts needed dual-protocol support before user machines began converting. Relays proved useful chiefly for mail, not as a general path for all traffic. The Network Information Center was not ready for the new protocols, which disrupted distribution of the host-name table. And once the new system faced sustained user load, service hosts needed performance analysis and parameter tuning.

So the transition succeeded at one level: NCP service ended on schedule and ARPANET switched to TCP/IP. It was not a claim that every support function had been proven under load or that all users experienced a seamless day. RFC 820, also issued in January 1983, noted that the change involved other protocols as well. The “Internet” arrived through a protocol suite, its applications and the people responsible for operating them.

Sources