TCP/IP Stack Tutorial

Hello Sorin

Yes, this is Cisco’s attempt to promote this new TCP/IP model in their curriculum, and to be honest, it’s not a bad idea. When we talk about networking, we usually use the OSI model layer names and numbers. We talk about a L2 or L3 switch, or L2 functionality as switching and L3 functionality as routing, and L4 operation as TCP sessions and UDP datagrams. The problem is that all of these technologies are not actually modeled around the OSI model but around the TCP/IP model. So according to the TCP/IP model, switching is L1, routing is L2 and TCP sessions are L3. However, we never refer to the layers of the TCP/IP model with numbers so that we don’t get confused with those of the OSI model.

Now Cisco is attempting to normalize the TCP/IP model with the OSI model by splitting the Link layer into the Data Link and Physical layers and renaming the Internet layer as the Network layer as shown below.

In my opinion this is a good idea because it clarifies the role of the various parts of Ethernet and IP communications by using the actual model after which they have been standardized, which is the TCP/IP model. And this clarifies its relationship with the OSI model as well.

Now this has not generally been adopted by the telecom industry at large nor has it been defined in any RFC, but for the time being it is restricted to Cisco courses and documentation. I’m hoping that it will overflow into the more widespread conscience of the networking world as a whole. For the exams however, not to worry as any indication of layers of models will make it quite clear as to what they are asking for, whether it’s the updated TCP/IP model, the original or the OSI.

I hope this has been helpful!

Laz

3 Likes