HomeVideos

OSI and TCP IP Models - Best Explanation

Now Playing

OSI and TCP IP Models - Best Explanation

Transcript

479 segments

0:00

so

0:02

like I was telling you guys the OSI

0:04

model is more of a reference a guideline

0:07

to help us delegate responsibilities to

0:10

help us understand what the

0:11

communication process entails and so I

0:14

had you guys just list them out from top

0:16

to bottom but remember the communication

0:19

process entails both directions

0:22

going down the stack is what we call

0:25

encapsulating and going up the stack we

0:29

call decapsulation

0:31

and today I hope to explain why the

0:35

encapsulation process is very critical

0:37

to the communication

0:39

that is to get the message from the

0:41

sender to the receiver

0:47

layer six sorry layer seven layer six

0:50

and layer 5 can be grouped in in fact

0:52

the sole responsibly for the three of

0:54

these is to produce what for the

0:56

transport layer

0:58

yeah so by the time we get down to the

1:01

transport layer

1:04

the pdu

1:06

to look something like this it should be

1:08

in a binary format so these three layers

1:12

produce a pdu

1:15

that we will call data

1:18

pdu is short for what protocol data unit

1:23

depending on the application all the

1:26

encryptions in the compressions

1:28

these zeros and ones are going to be

1:29

something that's really trivial I mean

1:33

that's what network people see all the

1:35

time or just zeros and ones they don't

1:36

know if it's an email or it's a voice

1:38

communication or whether it's a video

1:41

stream in fact that's what we call the

1:43

converging Network right the digital

1:45

converging Network this is why Time

1:47

Warner and all the other companies can

1:48

offer you phone internet TV all in the

1:51

same line it's all zeros and ones once

1:54

you get into zeros and ones you need to

1:57

identify that typically on the

1:59

application layer we identify zeros and

2:02

ones

2:03

by a file extension

2:05

a DOT EXE

2:08

represents zeros and ones used to

2:11

execute instructions a DOT jpeg jpg

2:16

represents those zeros and once to

2:17

display a picture

2:22

likewise we have identifications used in

2:24

networking sometimes we call these

2:27

addresses

2:28

to identify the application of the

2:30

service

2:31

that's the first thing that the

2:34

transport layer is going to do

2:36

the transport layer is going to identify

2:37

what applications make in the request

2:40

and what app sorry what service is going

2:42

to receive this

2:44

applications make requests

2:46

Services receive them

2:50

all right

2:51

so the way we identify them is to report

2:55

addresses

3:03

it's going to be a source

3:06

and there's going to be a destination

3:11

we stamp each and every one

3:15

of the pdu for the transport layer with

3:17

the source and destination what is the

3:19

pdu call of the transport layer

3:25

segment

3:27

and why is it called a segment because

3:29

what is the second thing or I should say

3:31

technically this would be the first

3:33

thing

3:34

yeah it takes the date and breaks up

3:36

into pieces hence we call those pieces

3:37

segments right so the pdu for the

3:40

transport layer

3:42

it's called a segment

3:46

why do we segment our data

3:49

security performance

3:52

and we can also allow multiple

3:54

Communications to occur relatively at

3:56

the same time which we call multiplexing

3:58

right

3:59

what was the one of the protocols

4:03

that defined

4:06

the segment because remember protocol

4:08

data unit right so if we're producing a

4:12

pdu there's got to be a protocol that

4:14

told me how to produce that pdu correct

4:17

so what was one of the protocols

4:20

TCP was one of them absolutely

4:24

and TCP we said time's irrelevant I'm

4:27

going to sacrifice time over reliability

4:32

okay this is why those big fat Cadillacs

4:35

I've launched a bunch of luxury items in

4:36

there that add weight to the car but a

4:38

sports car which is going to cost more

4:40

than a Cadillac I mean if you're getting

4:41

like a high-end sports car probably

4:43

going to trim all that fat because they

4:46

want speed correct

4:49

so what was the other protocol designed

4:52

UDP

4:55

TCP is the most popular one

5:00

all right we passed that segment down to

5:03

the network layer

5:05

and what is that Network layer going to

5:07

produce what are we going to take that

5:08

segment and make it into

5:11

packet

5:14

and what is one of the most popular

5:15

protocols on this layer that tells the

5:19

operating system how to take a segment

5:20

and make it into a packet

5:22

IP

5:23

and with IP

5:25

we have a source

5:27

and a destination address

5:34

much much bigger than Port addresses but

5:37

nevertheless same principle

5:39

but what's the difference between these

5:42

addresses what does the transport layer

5:44

use addresses for

5:47

they're both logical but which one does

5:49

the Tran what does the transport layer

5:51

use addresses for to identify what

5:54

they're called Port addresses but what

5:55

do they use to identify

5:57

services or applications

5:59

because look above the transport layer

6:02

the transport layer is looking up and

6:03

says okay who's getting this data who's

6:06

getting that data the way they know that

6:08

is through Port addresses okay so what

6:11

are the addresses used at the network

6:12

layer what do they use to identify

6:15

the key is Network what is the

6:17

definition of a network

6:19

to where more devices connected together

6:20

so they got to identify the devices on

6:22

the network

6:25

so the sender

6:27

and the receiver's IP address goes here

6:30

into the packet

6:32

all right so the packet gets passed down

6:36

and that becomes what

6:39

so we're in a data link layer

6:43

and we're going to produce what we call

6:45

a frame

6:49

remember the frame is the only time we

6:51

add a header and a trailer

6:54

and that frame

6:56

uses well we could use all kinds of

6:58

different protocols

7:00

I always like to talk to data link layer

7:02

with the physical layer because its idea

7:04

is to connect all that logical stuff

7:07

now the way I explained in my last class

7:09

and I got a kick out of it but I think

7:11

it clicked can you guys tell me what

7:13

Internet Explorer smells like

7:16

I know you guys are gonna say it smells

7:18

like because it's a piece of

7:19

but what about Firefox what about Chrome

7:23

what do they smell like what do they

7:25

feel like when you guys touch Internet

7:26

Explorer what does it feel like

7:30

felt a little heavy squishy

7:35

it doesn't have

7:37

smell

7:38

it doesn't have texture because it's all

7:42

virtual

7:43

it's abstract right

7:46

if I tell you what a nine if I ask you

7:48

what a nine volt battery feels like you

7:49

guys can tell me right

7:53

that's down here the physical stuff is

7:56

what we touch what we work with so this

7:58

layer is to take that abstract stuff and

8:01

make it into something real

8:04

and we need standards

8:06

we need standards that tell me okay I

8:09

can work with all that logical stuff

8:11

give me all those zeros and ones and I'm

8:13

going to convert into something that

8:15

people can touch taste hear feel it's

8:18

see

8:20

all depends on your interface card

8:23

now I say here because if you could hear

8:25

like my dog or Beyond

8:27

you can hear the Wi-Fi network sending

8:30

messages

8:31

and they operate a 2.4 gigahertz

8:33

Spectrum that's well beyond our hearing

8:36

and you guys are going to be glad for

8:37

that

8:39

I mean the way we listen to FM radios

8:41

which are in the megahertz is you need a

8:43

tuner to tune into that frequency and

8:45

then to

8:46

tone it down to a range that you can

8:49

hear correct

8:51

networks we call them modems

8:53

but nevertheless those signals are all

8:56

over us they're in this classroom all

8:58

time I'm sending one from this

8:59

microphone to my phone

9:01

drive me nuts if you guys heard or saw

9:03

all those things

9:05

but they do exist

9:07

the question is

9:08

how do I know that the interface card

9:10

that I bought

9:12

is going to work

9:14

with my other devices on my network

9:17

there's got to be standards like when

9:19

you go shopping for a hard drive it says

9:20

USB or a flash drive it says USB you

9:23

know you have a USB port and you expect

9:25

it to work

9:26

so when you guys go shopping for

9:28

interface cards or network devices what

9:31

are you looking for when you guys go

9:32

shopping for wireless cards or wireless

9:34

routers what do you look for

9:37

says Wi-Fi maybe but more importantly it

9:39

says 802.11

9:41

followed by a letter

9:44

so where the latest one is 802.11 AC

9:49

in order to use all that bandwidth to

9:52

use that wireless router to its full

9:54

potential what kind of interface card

9:56

are you going to need

9:57

an 802.11 AC interface card

10:02

so don't stop halfway and buy just a

10:04

wireless router

10:07

go the extra mile and buy the interface

10:09

card that uses the full potential out of

10:11

that wireless router

10:13

clear about that if I was setting up a

10:16

wired Network like we've been doing in

10:17

Packet Tracer you click on the computer

10:19

it says what for the interface card

10:22

fast

10:24

ether and that is a protocol or a

10:26

standard

10:29

that happens

10:31

right here the data link

10:37

ethernet has source

10:40

and destination addresses

10:43

but they're physical

10:46

that means the company that made that

10:48

interface card

10:49

burned an address into that card that

10:52

you cannot change

10:56

we'll get more into the difference

10:57

between physical and logical

10:59

right physical just takes those bits

11:04

and produces a signal

11:06

they carry them

11:09

that's it

11:10

now I tell my students

11:13

there are other models that explain the

11:16

same process

11:18

some are less elaborate as this

11:22

one of the most popular models

11:25

that we used as a substitute

11:28

to the OSI model is called the TCP slash

11:31

IP model and if you want to take a guess

11:33

why it's called TCP slash IP

11:41

because the persons that develop the

11:43

internet

11:44

focused on two protocols and only two

11:46

protocols TCP slash IP

11:50

they need to make sure data is reliable

11:51

because went back when it was called

11:53

arpanet

11:55

everything was very sensitive

11:57

with all this research

11:58

there wasn't any like voice or video or

12:01

any of that kind of crap

12:03

in fact the reason why the Internet was

12:05

developed was because a cold war

12:06

situation that we've connected are

12:07

missile silos so when Washington DC was

12:10

attacked we could still give the launch

12:12

codes over in Alaska

12:13

or turkey or wherever so we had

12:16

developed a very reliable Network so if

12:18

pathway gets disconnected we have

12:20

another way to get there another route

12:22

and that's what IP

12:24

says

12:25

so they said you know what

12:27

we developed this thing

12:29

let's create a model

12:31

that shows a grand overview of how this

12:34

behaves

12:36

and they said in order to use our

12:37

network if you want to send a web page

12:38

you need a web browser

12:41

and so they said

12:43

the first three layers are going to be

12:45

accomplished

12:47

under the application layer

12:51

so I just grouped the first three in

12:52

fact we've looked at layer 7 6 and 5

12:55

didn't I say that's all software stuff

12:57

OSI models a little bit more thorough

13:00

and said you know what I don't want a

13:03

cartographer writing the user interface

13:05

for my web browser

13:07

and thank God for that because if the

13:09

cryptographer did do that they would

13:11

hide the OK button it's a secret

13:16

likewise I wouldn't want a programmer

13:18

Who develops user interfaces

13:21

to write the cryptography program

13:22

because they would say oh it's real easy

13:25

passwords password

13:28

because their job is to make the

13:30

application user friendly

13:33

the cryptographer's job is to make it

13:35

very unfriendly

13:38

so that when you see it it doesn't make

13:39

any sense

13:42

very thorough and so what I like to see

13:44

is does that happen over here absolutely

13:46

because so there's like a division and

13:49

probably in that division there are

13:51

these departments because they need to

13:53

be accomplished

13:55

we do need session stuff we do need

13:57

presentation stuff but TCP was like yeah

14:00

that's all in the software

14:02

and that's we're going to do and it too

14:04

will produce data

14:07

and it too is interconnected and it's

14:10

going to connect to

14:13

the transport layer

14:16

and it two would produce segments

14:21

because I don't care

14:23

how you communicate but eventually in

14:26

your communication process you're going

14:28

to need to identify

14:30

what you're talking about the subject

14:32

right

14:34

have you ever talk to somebody then out

14:35

of the blue they bring something up and

14:37

you're like we were just talking about

14:38

uh Hell on Wheels why are you talking

14:41

about the weather next week what did it

14:43

have anything to do with the topic right

14:45

so in there you're gonna need some way

14:47

to identify what application or what

14:49

service you're talking with

14:52

so transport layer transport layer all

14:55

the same

14:57

remember these are the people that

14:58

developed the Internet

15:01

so their layer isn't going to be called

15:03

the network layer or rather they're

15:05

going to call it the inner Network layer

15:08

and what does inner mean anyway enter

15:13

it's just abbreviated from

15:14

interconnected

15:19

so just a bunch of networks connected

15:21

together

15:23

networks are networks whether they're

15:25

dropped together or not they all need to

15:26

behave the same way and it too is going

15:29

to produce

15:30

a packet

15:36

all right this is a very simple model so

15:39

it's going to take the last two

15:40

and group them together

15:43

and they're going to call this the

15:45

network access layer and oh hell does

15:49

that cause problems so far I have a 99

15:53

failure rate on my exam

15:56

when I give a multiple choice question

15:58

and I say

16:00

uh which

16:04

layer on the OSI model

16:07

is the same as the network access layer

16:12

and I will only give you one it'll be

16:14

like Network layer Network transport and

16:16

session something like that and students

16:18

want to say this one

16:20

network network it's got to be the same

16:22

thing

16:23

and it's not

16:26

the key here is access

16:28

going on to the network we're talking

16:30

about the physical stuff

16:32

so it takes both the data link and the

16:35

physical stuff in here

16:37

and it too

16:39

cause it's pdu a frame now let me give

16:42

you an example away from networks into

16:45

Hardware because I'm a hardware guy I

16:47

love reading Hardware magazines I love

16:49

staying on latest edge with CPUs gpus

16:52

and all that stuff especially the stuff

16:54

with the phones like iPhone just

16:55

released a new processor they're called

16:57

their motion processor and I'm just like

16:59

oh wow just another processor great what

17:01

does it do and so I'm looking at this

17:03

and I remember back in the 90s you know

17:06

we get into little geek fights and say

17:08

oh Nvidia is better than ATI or some

17:10

crap like that and then somebody would

17:12

say well no ATI has gotten great

17:14

processors and their gpus are excellent

17:16

they have more transistors and they have

17:18

more shaders and everything and I'm like

17:20

oh yeah whippy do and just like you guys

17:23

might be getting a pissing contest with

17:25

about Xbox 360 versus the PlayStation 3.

17:28

oh yeah PlayStation 3 has a lot of

17:30

muscle

17:31

compared to the Xbox

17:32

but what drives us to

17:34

these game consoles

17:39

content

17:41

likewise

17:42

I was so discouraged with ATI because

17:45

they had shitty Developers

17:47

the people at the valve drivers

17:50

didn't know what they were doing because

17:51

ATI needed to save money so they said

17:53

you know what you're an engineer you're

17:54

also going to develop the driver

17:56

what is a software driver it acts as a

17:58

translator between the hardware and the

18:00

operating system right

18:02

if you're a translator isn't doing a

18:04

good job translating you could find

18:07

yourself in prison right

18:09

likewise if your driver isn't using the

18:12

hardware to its full potential

18:14

you wasted all your money on all that

18:17

muscle and what you have is a dumb jock

18:19

I can't read and so you've paid a

18:21

millions of dollars to play football

18:22

well you guys understand a game plan and

18:25

so now he's running to the opposite

18:27

field goal or running to the opposite

18:29

end zone and you're like well you're big

18:31

and strong well you're pretty stupid

18:35

so I'm gonna get rid of you don't bring

18:38

out any teams I kept it Loose likewise

18:42

so what happened is over here Nvidia

18:45

decided to follow a model like this and

18:47

said we'll pay for engineers

18:49

and we'll also pay for software

18:52

developers that do nothing but developed

18:54

drivers

18:56

you need them

18:58

but they just have more levels

19:01

which might cost them more but hopefully

19:04

they produce a better product

19:05

over here the same process has to be

19:08

done the communication process has to

19:10

happen

19:12

however

19:14

how we group them and organize or

19:16

delegate responsibility is our business

19:18

model

Interactive Summary

The video explains the OSI model as a reference for understanding communication processes, detailing the concepts of encapsulation and decapsulation. It breaks down how data is processed through different layers, from the application layer down to the physical layer. Key aspects covered include the Protocol Data Units (PDUs) at each layer (Data, Segment, Packet, Frame), the role of addresses (Port, IP, MAC), and the functions of protocols like TCP and IP. The video also introduces the TCP/IP model as an alternative, highlighting its simpler structure by grouping layers. Finally, it draws parallels between network communication layers and hardware components, emphasizing the importance of standards and software drivers for optimal performance.

Suggested questions

11 ready-made prompts