Where is IPv1, 2, 3,and 5?

While researching IPv6, I decided it would be a good exercise to tell the short, but interesting story about IPv5. Now the Internet Protocol (IP) was not originally designed as a method of managing addresses on networks; it was intended as a technology to split the original network stack with Transmission Control Protocol (TCP) at layer four and IP at layer three. At the time, the design for TCP was struggling to solve two problems at the same time: how do we package data, and how do we send that data some place? That’s how we got to IPv4.

The History of TCP TCP version 1 was designed in 1973. This was documented through RFC 675. TCP version 2 was documented in March 1977. In August 1977, Jon Postel realized they were going the wrong direction with the protocol. “We are screwing up in our design of internet protocols by violating the principle of layering. Specifically we are trying to use TCP to do two things: serve as a host level end to end protocol, and to serve as an internet packaging and routing protocol. These two things should be provided in a layered and modular way. I suggest that a new distinct internetwork protocol is needed, and that TCP be used strictly as a host level end to end protocol.”

At this point, TCP and IP were split, with both being versioned number 3 in the spring of 1978. Stability was added in the fourth revision and that is how we got to IPv4. What happened to IPv5? It was a failed attempt to expand and solve some of IPv4’s problems. IPv4 was built to support efficient delivery of streams of packets to either single or multiple destinations, requiring guaranteed data rates and controlled delay. In other words, it was attempting to solve quality–of-service issues from the original Internet Protocol. With IPv5, computer scientists were trying to find a way to transmit voice over packet-switching networks. Originally, IP was not designed in a time before routers were required to maintain state information. As the idea of streaming video and other new media become a reality, RFC 1190 was submitted for a formal implementation of IPv5. Apple, Sun, IBM and a few others attempted to implement IPv5, but ultimately, general improvements in bandwidth, applications and compression allowed the modern network to grow around IPv4’s problems.

About the Author

Stephen Coty - Chief Security Evangelist at Alert Logic

Stephen Coty

Stephen Coty originally joined Alert Logic as the head of the Threat Research team, where he led the effort to build threat content and deliver threat intelligence. He later became the Chief Security Evangelist for the company. Prior to joining Alert Logic, Coty was the Manager of Cyber Security for Rackspace Hosting, and has held IT positions at multiple companies, including Wells Fargo Bank, Applied Materials, Stanford Medical Center and The Netigy Corporation. He has been in the Information Technology field since 1993. Research has been his primary focus since 2007.

@StephenCoty | Articles: 14