25 years of TCP/IP

Opinion
Jan 22, 20082 mins

* Reminiscing 25 years of TCP/IP

Some of us have been around long enough to remember when there was no Internet. Also, we were around before there was TCP/IP. This year we are hearing quite a bit – even in the popular press – about 2008 being the 25th anniversary of the Internet and TCP/IP. For instance, NPR has a great interview with Vinton Cerf, who, along with Robert Kahn, “invented” the protocol. Cerf discussed the original scope of the project as defined for Defense Advanced Research Projects Agency (DARPA), and, in particular, gives a great explanation for the layperson what distinguished TCP (Transmission Control Protocol) from IP (Internet Protocol). With this in mind, it seems appropriate to take a look back to reminisce – for those who remember – and to educate – for those who don’t – concerning this evolution.

The first point is that TCP/IP was far from being the first packet switching protocol in existence. At the inception of TCP/IP, X.25 networks were already widely used, especially outside the United States. The major change, and one that would continue to be an issue for the next several years, is the fact that IP is a connectionless protocol while X.25 (and, later, frame relay and ATM) are connection-oriented. As a connectionless protocol, the delivery of data is not guaranteed at the IP layer; hence, the addition of TCP to ensure that all of the packets are delivered – and that they are delivered in the proper order. (It’s also worth pointing out that the equivalent of IP was available in X.25 in the form of single-packet “datagrams.”)

Nevertheless, we need to cognizant that even though TCP/IP is now a de-facto standard for most communications – corporate and otherwise – it was not an instant “slam-dunk” success that was the obvious choice for all networks.

Next time, we look at where TCP/IP is now and why it requires a whole new generation of WAN firewalls.

Jim has a broad background in the IT industry. This includes serving as a software engineer, an engineering manager for high-speed data services for a major network service provider, a product manager for network hardware, a network manager at two Fortune 500 companies, and the principal of a consulting organization. In addition, Jim has created software tools for designing customer networks for a major network service provider and directed and performed market research at a major industry analyst firm. Jim’s current interests include both cloud networking and application and service delivery. Jim has a Ph.D. in Mathematics from Boston University.

More from this author