The Official Protocol of the Internet
TCP/IP was born approximately 20 years ago. Its precise genesis is hard to pin down because of the way it emerged. Unlike Kazaa or Doom or even Windows 2000, a date when it was first made available to the public just can't be nailed down. For that matter, it isn't possible to identify TCP/IP's creator. It simply wasn't developed by a software development company. Instead, it emerged piecemeal, over time, thanks to the individual efforts and contributions of people who weren't trying to revolutionize the way the world communicated. Their intent was far more humble: They were merely trying to make their own jobs better.That might sound a little strange. Today, everyone is so spoiled by sophisticated and powerful software that it is difficult imagining what it was like to try and use a computer 20 years ago. Around that same time, 20 years ago, is when TCP/IP and the Internet began their symbiotic lives. Over time, they would jointly revolutionize the way the world communicates. That revolution can be summed up in just one word: interoperability.
|
Groups of Functions
After learning a little about how TCP/IP emerged, you might be wondering just how schizophrenic and ill behaved a piece of software it is. It's well behaved, but it does look a bit like a Swiss army knifean attachment for everything. Its internal pieces do everything from taking data from applications to preparing it for the network, managing to act like a whole bunch of applications that make networks useful.The net effect is a powerful suite of communications protocols that work so well and seamlessly, that it's easy to forget that TCP/IP is there at all. It achieves this remarkable feat by playing sort of a zone defense. It organizes related or similar functions into layers and carefully delineates each layer's role and responsibilities. The passing of data between layers also is carefully orchestrated.Chapter 3, "The Quest for Freedom of Choice."The three main groups of functions can be categorized as follows:Tools for usersTools for applicationsTools for the network
Figure 4-1 shows you these categories in a layered reference model. This isn't the real TCP/IP reference model, but it helps keep things in perspective as you walk through more of the details. Besides, these layer names make a lot more sense than the official names!
Figure 4-1. TCP/IP's Functional Layers
