28.06.2014 Views

Learning by Doing: CISCO Certified Network ... - SCN Research

Learning by Doing: CISCO Certified Network ... - SCN Research

Learning by Doing: CISCO Certified Network ... - SCN Research

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Encapsulation<br />

As we move down the OSI model a process called encapsulation takes place. At<br />

the session layer the information is called "data." At the transport layer the data is<br />

converted into "segments." At the network layer the segments are encapsulated into<br />

"packets." At the data link layer the packets are now encapsulated into "frames."<br />

Finally, at the physical layer the frames are converted into "bits."<br />

A good way to remember this is “Don’t Send People Free Beer.” Beer is on the<br />

physical layer because its macho. If you want to remember it from the bottom up (which<br />

might confuse you with the OSI model direction) you can remember “Been free people<br />

since democracy.”<br />

Pay close attention to when the information headers and footers are added. This<br />

can be somewhat confusing. Let’s take a look at a make believe situation between two<br />

users communicating over the Internet. Suppose Joe wants to send an email to Casey.<br />

His message is 50,000 <strong>by</strong>tes in size at the application layer. This email is passed down to<br />

the presentation layer where it is compressed, encrypted, and formatted down to a<br />

message of 30,000 <strong>by</strong>tes in size (ok…so it really won’t be this neat but cut me a break it<br />

is easier to explain this way). Then the 30,000 <strong>by</strong>te compressed, formatted, and<br />

encrypted data is sent to the session layer. Here Joe’s computer establishes a session with<br />

Casey’s computer…<br />

Session layer communication:<br />

Joe: Hey Casey…can I hook up with you (no pun intended)<br />

Casey: I acknowledge that you are requesting a hook up<br />

Joe: I received your acknowledgement of my request for a hookup.<br />

Casey: I received your acknowledgement of my acknowledgment of your request<br />

for a hookup.<br />

Then the data is passed to the transport layer for numbering. Here the 30,000 <strong>by</strong>te data is<br />

broken down into 6 segments and numbered: 1 of 6, 2 of 6, 3 of 6, 4 of 6, 5 of 6 and 6 of<br />

6. Handshaking and windowing takes place to finish the establishment of the session.<br />

Transport layer communication:<br />

Joe: I want to send information so how quickly can I send it?<br />

Casey: I acknowledge that you are requesting to send information.<br />

Joe: I received your acknowledgement of my request to send information.<br />

Casey: I received your acknowledgement of my acknowledgment of your request<br />

to send information.<br />

Casey: I am not busy so you can transmit at 22300 bps.<br />

Joe: I acknowledge that you can transmit at 22300 bps.<br />

Casey: I received your acknowledgement of my request to transmit at 22300 bps.<br />

Joe: I received your acknowledgement of my acknowledgment of your ability<br />

to receive information at 22300 bps.<br />

Then the transport layer segment is passed to the network layer. The network layer adds<br />

the source and destination ip addresses (logical addresses) plus some other stuff (we will<br />

look at later). Then the new “packet” is sent to the data link layer. There the data link<br />

66

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!