Networking

Internet Protocol History

IPv4 and TCP were published in September 1981 (RFC 791 and 793), DNS in 1983, IPv6 in 1995, HTTP/1.0 in 1996, TLS 1.3 in 2018 and HTTP/3 in 2022: a dated timeline sourced to the RFCs.

The core internet protocols were written down as RFCs: IPv4 in RFC 791 and TCP in RFC 793 (both September 1981), DNS in RFC 882/883 (November 1983, today RFC 1034/1035 from 1987), IPv6 in RFC 1883 (December 1995, now RFC 8200 from 2017), HTTP/1.0 in RFC 1945 (May 1996), TLS 1.0 in RFC 2246 (January 1999), TLS 1.3 in RFC 8446 (August 2018), QUIC in RFC 9000 (May 2021) and HTTP/3 in RFC 9114 (June 2022). The free pool of IPv4 addresses at IANA ran out on 3 February 2011. Every date below is the publication month the RFC Editor records for that document, or the date in the announcing organisation's own press release. To see how the 32-bit and 128-bit address formats relate, try the IPv4 to IPv6 Converter.

Timeline

DateMilestoneDocument
April 1969"Host Software" by Steve Crocker: the first Request for Comments.RFC 1
December 1974Specification of Internet Transmission Control Program (Cerf, Dalal, Sunshine): the first TCP specification.RFC 675
January 1980DoD standard Internet Protocol (Postel).RFC 760
August 1980User Datagram Protocol (UDP).RFC 768
September 1981Internet Protocol (IPv4), with 32-bit addresses; ICMP; Transmission Control Protocol (TCP). All three by Jon Postel.RFC 791, RFC 792, RFC 793
November 1981NCP/TCP transition plan: goal of a complete switch from NCP to IP/TCP by 1 January 1983.RFC 801
August 1982Simple Mail Transfer Protocol (SMTP).RFC 821
November 1983Domain names: concepts and implementation (Mockapetris), the first DNS specification.RFC 882, RFC 883
November 1987DNS rewritten as RFC 1034 and 1035, still the DNS Internet Standard.RFC 1034, RFC 1035
March 1989Tim Berners-Lee's "Information Management: A Proposal" at CERN, the start of the World Wide Web (he chose the name "World Wide Web" while writing the code in 1990).W3C archive
October 1989Requirements for Internet Hosts: the four-layer model (link, internet, transport, application).RFC 1122
1991The original HTTP, later called HTTP/0.9: the request is one line, the word GET and a document address; no client information is sent.W3C, "The HTTP Protocol As Implemented In W3"
September 1993Classless Inter-Domain Routing (CIDR) replaces class A/B/C allocation (now RFC 4632, 2006).RFC 1519
March 1995BGP-4, the inter-domain routing protocol (now RFC 4271, 2006).RFC 1771
December 1995First IPv6 specification, with 128-bit addresses.RFC 1883
February 1996Private address ranges 10/8, 172.16/12 and 192.168/16.RFC 1918
May 1996HTTP/1.0 (Informational).RFC 1945
January 1997First HTTP/1.1 specification.RFC 2068
March 1997Dynamic Host Configuration Protocol (DHCP).RFC 2131
December 1998IPv6 specification revised (Draft Standard).RFC 2460
January 1999TLS 1.0, the IETF successor to SSL.RFC 2246
June 1999HTTP/1.1 revised (Draft Standard); it stayed the HTTP/1.1 specification until June 2014.RFC 2616
May 2000HTTP over TLS (HTTPS).RFC 2818
January 2001Traditional Network Address Translation (NAT).RFC 3022
March 2005DNS Security Extensions (DNSSEC) in their current form.RFC 4033, RFC 4034
April 2006TLS 1.1.RFC 4346
August 2008TLS 1.2.RFC 5246
3 February 2011IANA's free pool of IPv4 addresses is depleted: the last five /8 blocks go one each to the five regional registries, triggered when APNIC received two blocks on 31 January.NRO announcement
March 2011SSL 2.0 prohibited.RFC 6176
8 June 2011World IPv6 Day, a one-day IPv6 event organised by the Internet Society.Internet Society
August 2011SSL 3.0 published for the record as a Historic document.RFC 6101
December 2011The WebSocket Protocol.RFC 6455
April 2012Shared address space 100.64.0.0/10 reserved for carrier-grade NAT.RFC 6598
6 June 2012World IPv6 Launch: ISPs, router makers and websites enable IPv6 permanently.Internet Society
June 2014HTTP/1.1 split into six RFCs (7230–7235), replacing RFC 2616.RFC 7230
May 2015HTTP/2: many requests multiplexed over one TCP connection.RFC 7540
June 2015SSL 3.0 deprecated: "SSLv3 MUST NOT be used".RFC 7568
24 September 2015ARIN (US, Canada, parts of the Caribbean) issues the last IPv4 addresses in its free pool.ARIN announcement
May 2016DNS over TLS (DoT).RFC 7858
July 2017IPv6 becomes an Internet Standard.RFC 8200
August 2018TLS 1.3: legacy ciphers removed, all key exchange gives forward secrecy, 0-RTT mode added.RFC 8446
October 2018DNS queries over HTTPS (DoH).RFC 8484
March 2021TLS 1.0 and TLS 1.1 deprecated: both "MUST NOT be used".RFC 8996
May 2021QUIC: a UDP-based, multiplexed, encrypted transport (with RFC 8999, 9001, 9002).RFC 9000
May 2022DNS over dedicated QUIC connections (DoQ).RFC 9250
June 2022HTTP rewritten: HTTP Semantics and HTTP/1.1 become Internet Standards; HTTP/2 revised; HTTP/3 over QUIC.RFC 9110, RFC 9112, RFC 9113, RFC 9114
August 2022TCP specification consolidated, replacing RFC 793 after 41 years.RFC 9293
May 2023QUIC version 2.RFC 9369
July 2026TLS 1.3 revised; obsoletes RFC 8446 and RFC 5246 (TLS 1.2) and sets new requirements for TLS 1.2 implementations.RFC 9846

Where each protocol stands today

ProtocolFirst specificationCurrent specificationCurrent status (RFC Editor)
IPv4RFC 760 (Jan 1980)RFC 791 (Sep 1981)Internet Standard
IPv6RFC 1883 (Dec 1995)RFC 8200 (Jul 2017)Internet Standard
TCPRFC 675 (Dec 1974); RFC 793 (Sep 1981)RFC 9293 (Aug 2022)Internet Standard
UDPRFC 768 (Aug 1980)RFC 768 (Aug 1980)Internet Standard
DNSRFC 882/883 (Nov 1983)RFC 1034, RFC 1035 (Nov 1987)Internet Standard
SMTPRFC 821 (Aug 1982)RFC 5321 (Oct 2008)Draft Standard
HTTP/1.1RFC 2068 (Jan 1997)RFC 9112 with RFC 9110 (Jun 2022)Internet Standard
HTTP/2RFC 7540 (May 2015)RFC 9113 (Jun 2022)Proposed Standard
HTTP/3RFC 9114 (Jun 2022)RFC 9114 (Jun 2022)Proposed Standard
QUICRFC 9000 (May 2021)RFC 9000; version 2 in RFC 9369Proposed Standard
TLS 1.3RFC 8446 (Aug 2018)RFC 9846 (Jul 2026)Proposed Standard
TLS 1.2RFC 5246 (Aug 2008)Obsoleted by RFC 8446 and RFC 9846Obsolete; still allowed
TLS 1.0 / 1.1RFC 2246 (Jan 1999) / RFC 4346 (Apr 2006)Deprecated by RFC 8996 (Mar 2021)Historic
SSL 2.0 / 3.0not IETF documents (SSL 3.0 recorded in RFC 6101, Aug 2011)Prohibited by RFC 6176 (Mar 2011) / RFC 7568 (Jun 2015)Prohibited (RFC 6101 is Historic)
DNSSECRFC 2535 (Mar 1999)RFC 4033–4035 (Mar 2005)Proposed Standard

The four layers of RFC 1122

Layer (RFC 1122)What it doesProtocols on this page
ApplicationUser-facing servicesHTTP/1.1, HTTP/2, HTTP/3, DNS, SMTP, TLS (between application and transport)
TransportEnd-to-end delivery between programsTCP, UDP, QUIC (runs over UDP)
InternetAddressing and routing packets between networksIPv4, IPv6, ICMP
LinkDelivery across one physical networkEthernet, Wi-Fi (IEEE 802.3, 802.11)

Reading the timeline

  • Dates are publication months. The RFC Editor records only the month and year for most RFCs, so that is what is shown. The few exact days come from announcements (NRO, ARIN, Internet Society).
  • Status words matter. "Internet Standard" is the IETF's highest maturity level; "Proposed Standard" is a full standard that has not been elevated, and much of the modern web (HTTP/2, HTTP/3, QUIC, TLS 1.3) is at that level. "Historic" marks a document kept only for the record. HTTP/1.0 (RFC 1945) was never a standard at all: it was published as Informational.
  • Obsoleted is not the same as dead. RFC 793 was obsoleted by RFC 9293 in 2022, but TCP was not replaced: the new RFC "collects and brings those changes together with the protocol specification from RFC 793", 41 years of piecemeal updates in one document. Likewise RFC 9846 (2026) obsoletes RFC 5246, yet TLS 1.2 is still allowed; RFC 9846 adds requirements for TLS 1.2 implementations rather than banning them.
  • HTTP/2 vs HTTP/3. HTTP/2 multiplexes requests over one TCP connection, and RFC 9113 itself notes that "TCP head-of-line blocking is not addressed by this protocol". QUIC (RFC 9000) avoids that: "when a packet loss occurs, only streams with data in that packet are blocked".
  • Address sizes. IPv4 addresses are fixed at four octets, 32 bits (RFC 791); IPv6 "increases the IP address size from 32 bits to 128 bits" (RFC 8200). The NRO notes IPv6 address space has been available from the registries since 1999.
  • Not every milestone is an RFC. The World Wide Web proposal (1989) and the original HTTP (1991) are CERN/W3C documents; the IPv4 exhaustion dates are registry announcements.

Sources

  • RFC Editor, RFC Index (rfc-index.xml, downloaded 6 October 2026, rfc-editor.org/rfc-index.xml): publication month, title, authors, current status and obsoletes / obsoleted-by links for every RFC on this page. Each RFC number links to its text at rfc-editor.org.
  • RFC texts quoted: RFC 791 (32-bit addresses), RFC 801 (1 January 1983 transition goal), RFC 1122 (four layers), RFC 1918 (private ranges), RFC 6598 (100.64.0.0/10), RFC 7568 and RFC 8996 ("MUST NOT be used"), RFC 8200 (32 to 128 bits), RFC 8446 §1.2 (differences from TLS 1.2), RFC 9000 (head-of-line blocking across streams), RFC 9113 §1 (TCP head-of-line blocking not addressed by HTTP/2), RFC 9293 (abstract), RFC 9846 (abstract: obsoletes RFC 8446 and RFC 5246).
  • Number Resource Organization, Free Pool of IPv4 Address Space Depleted, press release, Montevideo, 3 February 2011 (nro.net/ipv4-free-pool-depleted).
  • ARIN, ARIN IPv4 Free Pool Reaches Zero, announcement of 24 September 2015 (arin.net/vault/announcements/20150924).
  • Internet Society, World IPv6 Launch (worldipv6launch.org): World IPv6 Day 8 June 2011; World IPv6 Launch 6 June 2012.
  • W3C, Information Management: A Proposal, Tim Berners-Lee, CERN, March 1989 / May 1990 (w3.org/History/1989/proposal.html); The Original HTTP as defined in 1991 (w3.org/Protocols/HTTP/AsImplemented.html).

Frequently asked questions

When was IPv4 created?

IPv4 was specified in RFC 791, "Internet Protocol", by Jon Postel in September 1981, replacing the January 1980 DoD standard of RFC 760. It is still the current IPv4 specification and an Internet Standard. Its addresses are 32 bits long.

When did the internet switch to TCP/IP?

RFC 801, the NCP/TCP transition plan published in November 1981, set the goal of a complete switch from the ARPANET's NCP to IP/TCP by 1 January 1983. TCP itself had been specified in RFC 793 in September 1981; that RFC was replaced by RFC 9293 in August 2022.

When did the world run out of IPv4 addresses?

The central pool ran out on 3 February 2011, when IANA handed the last five /8 blocks equally to the five regional internet registries, as announced by the Number Resource Organization. ARIN, the registry for the US and Canada, issued the last addresses in its free pool on 24 September 2015.

What RFC defines TLS 1.3?

TLS 1.3 was first published as RFC 8446 in August 2018. In July 2026 the IETF published RFC 9846, a revised TLS 1.3 specification that obsoletes RFC 8446 and also RFC 5246 (TLS 1.2). TLS 1.0 and 1.1 were deprecated by RFC 8996 in March 2021.

What is the difference between HTTP/2 and HTTP/3?

HTTP/2 (RFC 7540, May 2015; now RFC 9113) multiplexes many requests over one TCP connection. HTTP/3 (RFC 9114, June 2022) carries HTTP over QUIC (RFC 9000, May 2021), which runs over UDP, so a lost packet only holds up the streams whose data it carried rather than every stream on the connection.

Was this article helpful?