{"id":63,"date":"2011-11-22T19:55:08","date_gmt":"2011-11-22T19:55:08","guid":{"rendered":"http:\/\/microsoftgeek.com\/?p=63"},"modified":"2011-11-22T19:55:51","modified_gmt":"2011-11-22T19:55:51","slug":"how-encapsulation-works-within-the-tcpip-model","status":"publish","type":"post","link":"https:\/\/microsoftgeek.com\/?p=63","title":{"rendered":"How Encapsulation works within the TCP\/IP Model"},"content":{"rendered":"

In the previous section we reviewed the TCP\/IP and OSI model. For the sake of clarity, we will be using the TCP\/IP model to demonstrate encapsulation, as compared to the OSI model. If you are still struggling with grasping concepts of the TCP\/IP model you may wish to view the previous section once more. Otherwise, onward to the encapsulation process!<\/p>\n

The TCP\/IP Model<\/h3>\n

As we learned in the previous section, the TCP\/IP model has four layers. You can view a diagram of the model below.<\/p>\n

\"tcp<\/p>\n

Keep in mind that we divide the stack into four separate layers because they each perform a certain role or task. As data is being sent from one computer, it will pass from the top layer to the bottom. On the receiving end, the data will then be rebuilt from the bottom layer to the top. You can view an example of this process below.<\/p>\n

\"tcp<\/p>\n

Each layer a packet of information travels through adds what is called a header. Think of it in terms of a Russian doll. You\u2019re probably familiar with them: each doll has another smaller doll inside of it. Just like the dolls, each layer a sending packet passes through gains another header (or doll). When the packet is being rebuilt on the receiving end, each header is unpackaged the same way. You can see an example of a sending packet gaining header information below.<\/p>\n

\"tcp<\/p>\n

Note that at the receiving end, we would have the reverse process (Headers would be taken away at each layer, until the receiving packet is by itself.)<\/p>\n

Since each layer of the TCP\/IP model does a unique task separate of the other layers, we refer to the data package at each layer with different names. For instance, the data package at the Application Layer is called a message, while the same data package at the Internet Layer is called a datagram. Review the diagram below for the complete list of names.<\/p>\n

\"datagram<\/p>\n

Notice that the Transport Layer may have one of two names- a segment or a datagram. If the TCP protocol is being used, it is called a segment. If the UDP protocol is being used, it is called a Datagram.<\/p>\n

The data then passes through the Internet Layer onto the Network Access Layer, where a frame is created. Once the data packet leaves this level it is converted into a bitstream of electrical pulses, commonly referred to as 1\u2019s and 0\u2019s.<\/p>\n

Finally, you should note that Cisco demands CCNA students to know specific information on the Data Link Layer and encapsulation. As you can see, we haven\u2019t used the OSI model, but the TCP\/IP model (so we use the Network Access Layer as opposed to the Data Link and Physical Layer). Specifically, Cisco demands that students know that packets are packaged into frames at the Data Link Layer. And, like other layers, a header and trailer are added to the information at the Data Link Layer. You can see the encapsulation process with the OSI model below.<\/p>\n

\"osi<\/p>\n

We know what you\u2019re thinking- where\u2019s a good pneumonic when you need it? The easiest one we could find was \u201cDirty Sick People Feel Bad,\u201d whereas each letter of each word corresponds to Data, Segments, Packets, Frames, and Bits.<\/p>\n

Putting it All Together<\/h3>\n

Now that we have the basics down, we can finally review the entire process of data encapsulation. Refer to the below list to see a real-life example of encapsulation. If needed, you can view the above diagrams if you get lost.<\/p>\n

The Data Encapsulation Process<\/strong><\/p>\n