TCP/IP and the 1983 Flag Day: The Switch That Created the Internet

If one date deserves to be called the birthday of the internet, 1 January 1983 is a strong candidate. On that day, every host on ARPANET was required to switch from the old Network Control Protocol (NCP) to a new pair of protocols: the Transmission Control Protocol and the Internet Protocol, together known as TCP/IP. The event was nicknamed "flag day", because there was no gradual transition. After the switch, machines that had not changed simply could not talk to the network.

The problem TCP/IP was designed to solve

By the early 1970s there was more than one packet network. ARPANET existed, but so did packet radio networks and satellite networks, all with different characteristics. Researchers wanted a way for them to exchange data, a network of networks. That is where the word "internet" comes from: an inter-network.

Vint Cerf, then at Stanford, and Bob Kahn, at ARPA, worked on this problem. They published their design in a 1974 paper called "A Protocol for Packet Network Intercommunication". The paper described a single protocol that handled both addressing and reliable delivery.

Splitting one protocol into two

During the late 1970s, the design was refined and divided. The reason was practical: some applications, such as voice, needed speed more than perfect delivery, while others, such as file transfer, needed every byte to arrive correctly. The work was split into two layers:

• IP (Internet Protocol) moves packets from one address to another on a best-effort basis. It does not guarantee delivery.
• TCP (Transmission Control Protocol) sits on top of IP and gives applications a reliable stream: it numbers the data, detects losses and asks for retransmission.

A third protocol, UDP, was added for applications that want to use IP without TCP's reliability machinery. Jon Postel, who edited many of the early protocol documents, played a major role in writing these specifications down. They were published as the RFC series, short numbered documents that are still the way internet standards are recorded.

The decision to switch

The United States Department of Defense declared TCP/IP the standard for its networks in 1982, and set 1 January 1983 as the date on which ARPANET would stop supporting NCP. People involved had been warning for months and had even held a trial period in which NCP was disabled for short times, to find the hosts that had not yet prepared. On the day, many sites had done the work in advance, and the switchover is generally remembered as having gone more smoothly than feared, although it took a lot of effort from the system administrators at each site.

Why the choice of design mattered

TCP/IP had several traits that helped it spread:

1. It is simple at the centre. The network only moves packets. The intelligence lives at the edges, in the computers at each end. New applications could be built without changing the network.
2. It is open. The specifications were free to read and implement. Anyone could write a TCP/IP stack.
3. It was included in Unix. The University of California, Berkeley released a TCP/IP implementation in its BSD Unix, which spread through universities.
4. It works over anything. TCP/IP runs over cables, Wi-Fi, mobile networks and satellite links, because it only assumes that packets can be sent somehow.

What happened next

With a standard in place, other networks could join. The National Science Foundation built NSFNET in the mid-1980s to connect university supercomputing centres, and regional networks attached to it. Commercial networks followed in the early 1990s. Today every device on the internet, from a phone to a web server, still speaks IP.

The protocol has had to evolve. Version 4 of IP, used since the flag day, has 32-bit addresses, which turned out to be too few. IPv6 was designed to replace it, a story we cover in our article on IPv4 exhaustion.

TCP and IP in everyday terms

You do not need to know the packet formats to benefit from the model. Think of IP as the postal address on an envelope, and TCP as a courier service that checks every envelope arrives, in the right order, and resends anything that goes missing. Each web page you open begins with a TCP connection to the server, then HTTP requests travel inside that connection. When a connection is encrypted with TLS, as it is on any site with an SSL certificate, the encryption is added on top of TCP rather than replacing it.

This layering is why the internet has been able to change so much without being rebuilt. The web, email, streaming and online games all use the same lower layers, while the application protocols above them differ. New versions of HTTP, for example, have been introduced without altering IP itself.

What site owners can learn from a flag day

Large technical migrations are possible, but they succeed through preparation: testing, announcements, rollback plans and a clear date. The same applies when you move a website to a new host. Moving the files is the easy part. The planning is what keeps a site online. Our free migration service follows that approach, with the team moving your site, databases and email so you do not have to manage the switch alone.