HomeVideos

OSI Reference Model - Best Explanation

Now Playing

OSI Reference Model - Best Explanation

Transcript

1194 segments

0:00

all right I got a couple questions for

0:02

you guys uh when we last met we're

0:05

talking about the OSI model can anybody

0:08

tell me

0:10

what organization is responsible for

0:13

developing this model

0:15

is that you are you guys want to start

0:17

easier questions Monday morning what's

0:19

that ISO yes yes ISL

0:24

now what's nice about that is the

0:26

letters are still in the OSI right

0:27

they're just flipped over so it's nice

0:30

way to remember that and why would the

0:32

international standards organization

0:34

develop this model I mean they create

0:36

other models they cut other standards

0:38

for us to follow why would they develop

0:40

the OSI model

0:47

yeah the idea is that we can foster

0:50

competition but yet still keep

0:52

compatibility

0:53

so we have the difference between

0:54

proprietary protocols and open protocols

0:57

correct

0:58

and so you can still have proprietary

1:00

protocols but what that means is that

1:03

the corporation owns them and they're

1:05

only ones allowed to change them and if

1:06

you want to use them you have to license

1:07

them

1:10

but open protocols is

1:12

we're going to create the standard

1:14

you're allowed to look at them

1:16

you can modify them but you have to

1:18

create a variation of it like the

1:20

802.11n or the 80211 B

1:23

they're still using the core standard

1:25

right

1:25

but then somebody has enhanced it so

1:28

they went to end

1:29

so Fosters competition but more

1:31

importantly allows me to know when I go

1:33

shopping

1:34

what to look for to make sure they're

1:36

compliant like when I buy a USB hard

1:39

drive I should expect on my home

1:41

computer that there is a port

1:44

that accepts that USB hard drive

1:46

back in the day it was always a

1:49

nightmare because we had different ports

1:50

on the back of our computer and it was

1:52

like okay this one plugged and this one

1:53

this goes to that one and somebody said

1:55

this is just stupid why don't we have

1:56

one universal Port that accepts

1:58

everything

2:00

and once again where that's starting to

2:01

grow again we got Thunderbolt we have

2:03

firewire we have USB so it's like why

2:05

can't we just have one that rules them

2:07

all

2:08

so standards allow me to know that when

2:10

I go shopping the devices I buy are

2:12

going to be compliant

2:14

right I threw out the 802.11

2:18

that's an example of another standard

2:21

but it's a wireless standard yes but

2:24

what organizations responsible for that

2:29

they're also responsible for this one

2:37

now it's always interchangeable because

2:39

you guys know this 802.11 as

2:44

Wi-Fi right

2:47

and you know this one as

2:56

probably faster than that's what I

2:57

should put in there what's that

3:00

IEEE

3:05

for some reason

3:07

Cisco in this curriculum is all gung-ho

3:10

about you guys knowing these

3:11

organizations

3:13

I don't understand why other than when

3:16

you become a network engineer

3:19

now you're getting down to nitty-gritty

3:21

you might be developing new interface

3:22

cards

3:23

that you'll have to look at what we call

3:25

rfcs

3:27

anybody tell me what RFC is short for

3:30

yes request for comments and it's not

3:33

read the you know you guys rfc's request

3:36

for comments and what how does that

3:39

system work

3:41

remember we're talking about open

3:43

platform right

3:44

so you guys can go to the IEEE site

3:48

read over the 802

3:50

3 or the 802.11

3:53

and start publishing your own

3:55

variation

3:57

or maybe fix a bug

4:00

and add your post from the rfcs and so

4:02

you're looking at the rfcs as ways to

4:05

see what's going on in Industry so I

4:09

guess that's the only kind of BS excuse

4:11

I can give you why Cisco is jamming down

4:13

into organizations down your throat

4:15

what's the other one that sort of

4:17

Fosters the open platform for the

4:20

internet

4:22

it's more of a society thing give you a

4:25

hint

4:27

eye soccer eye social the internet

4:29

Society

4:31

and their old big deal is to try to keep

4:33

things open and keep the internet

4:36

growing and people sharing

4:39

and

4:40

so we have the OSI model that's

4:43

developed by the iso and what is the

4:45

whole purpose of this well we said it's

4:47

too Foster competition but it also helps

4:49

delegate responsibilities

4:52

and it also can be used to understand

4:55

the communication process and that's

4:57

where we were at last week right

4:58

dissecting the communication process

5:00

from the sender to the receiver what's

5:02

the first layer the upper layer of the

5:04

OSI model

5:06

application this is also known as layer

5:09

what

5:20

what happens here what's the

5:22

responsibilities if you were to a

5:24

designate you have a big Corporation

5:26

you're designating some people jobs

5:28

and you say Okay I want X number of

5:31

people to do layer seven what kind of

5:33

skills are you looking for a later seven

5:34

job description you have

5:39

okay so you're looking at programming

5:40

skills these are people that develop

5:43

applications design web pages and

5:45

nowadays we're just calling them web

5:47

apps right but in any case we're just

5:49

trying to say that these are our

5:51

software engineers

5:53

these are people that write code

5:55

and what does applications do for us

5:57

they give our computers purpose

6:00

you go with that so the application

6:02

layer acts as an interface

6:04

to the network

6:06

if you are writing code or developing

6:10

software that uses a network connection

6:13

like for instance if you are developing

6:15

a web browser it's always good to have

6:16

these examples if you're designing a web

6:18

browser not a web page but a web browser

6:22

what protocol do you need to agree to so

6:26

that your application understands

6:30

this process

6:32

what's that

6:34

http

6:36

so HTTP is an example of an application

6:41

layer protocol

6:43

and a list of others like DNS FTP pop

6:49

SMTP and we'll get into those as the

6:52

semester progresses like I said lab for

6:54

this week you guys are going to be

6:55

getting into HTTP and

6:59

DNS

7:03

now when I say their application layer

7:05

protocols

7:06

I'm saying their responsibility is to

7:09

work with the user to prepare the data

7:13

to be ready for the network

7:16

and so the OSI models interconnected

7:18

layers

7:19

it's going to encapsulate things as it

7:23

goes down

7:24

so here I am at the application layer

7:25

I'm using a web browser and that's stuff

7:28

that I'm asking for or I'm sending via

7:31

my web browser it's passed down to the

7:33

layer six what is the name of this layer

7:41

what are the three responsibilities for

7:44

this layer what's it going to do with

7:45

that HTTP stuff

7:48

it's going to encode it we might use

7:51

ASCII

7:52

to accomplish that

7:55

encrypted which it might use what

7:59

SSL or TCL the list goes on and on in

8:03

fact this is a huge dwelling field

8:07

if you guys are looking to make a lot of

8:08

money with a very little bit of

8:10

Education you want to go on the security

8:13

try to give number security courses you

8:14

possibly can get and if you're really

8:17

good at it you're really fascinating

8:18

about and have great math skills in

8:21

cryptography or cryptography is the area

8:23

to go

8:25

trying to create code that can't be

8:27

cracked and right now the NSA is

8:29

bragging that they can crack every

8:30

encryption method out there in a couple

8:31

seconds

8:32

now what does that mean they're going to

8:34

hire more photographers the correct

8:36

credit card that they can't crack

8:37

because they can't crack it to make it

8:40

feel it's safe it's safe communication

8:42

all right the big growing area what's

8:46

the third

8:47

compression yeah they want to make this

8:49

stuff

8:50

smaller so it takes

8:52

less bandwidth to deliver it if you will

8:57

all right and so an example of

8:58

compression I believe I gave you guys

9:00

was like gzip but this stuff goes on and

9:03

on and on

9:05

what's the next layer and don't get cute

9:07

and say layer five

9:09

now eventually I will get lazy and I'll

9:12

say that stuff happens at the layer

9:13

three and then you need to say oh that's

9:15

the all right so here I am layer five

9:17

and uh we called it the session layer

9:21

if I had to uh roll that all up in one

9:24

word it's just going to be management

9:25

dialogue management to keep your

9:27

connections alive that's it

9:30

all right so I'm saying keeping

9:31

connections alive

9:33

see the application layer you're the

9:36

user

9:37

they could be using multiple

9:39

applications all at once

9:42

that require the internet

9:44

you can have an email program going on

9:47

you can have your torrent stuff going on

9:50

you can have your web browser going on

9:52

and it would gets really interesting is

9:54

with even those applications there could

9:57

be other connections like for instance

9:59

if you're browsing the web and you're

10:01

watching a video

10:05

and you could also be using email

10:08

which we call webmail

10:11

and you could also be using DNS

10:13

ironically

10:16

so just within one connection we can

10:18

have multiple other connections

10:21

I mean we talk about HTTP we're only

10:24

talking about HTML and a generic web

10:27

page but that has evolved we're on web2o

10:30

so we have plugins which are going to be

10:32

at the presentation layer that's

10:34

designed to sort of work with the

10:36

browser and the content provider does

10:39

that make sense

10:40

and the way we do that is by

10:42

establishing separate connections to

10:45

each of those services

10:49

and as for this layer comes in

10:55

anybody tell me what the layer for

10:57

transport layer

11:02

do not think transport as being this

11:06

the bottle

11:08

and you move it over here to its final

11:10

destination that's not what we're

11:12

referring to at the transport layer

11:15

it's your job it's responsibility

11:18

you get the segment

11:19

to the right application or service now

11:24

when I say application you guys need to

11:26

think client when I say service you need

11:29

to think server

11:30

is the symbiotic relationship between

11:32

client and service clients make the

11:35

request service try to fulfill their

11:37

requests so clients use applications

11:39

servers use services

11:44

are applications

11:47

they just are designed to run in the

11:48

background if you're a Linux person what

11:50

do you call services

11:53

demons

11:55

got its name because they're running in

11:57

the background taking over the server

11:59

right

12:01

fulfilling a role so if you are running

12:04

a Linux web server you might have Tomcat

12:07

or Apache web service running in the

12:10

background

12:11

and it's listening

12:13

it's listening to a particular port

12:16

now I said Apache I said web server

12:18

right web services what port is This

12:21

Server going to be listening to what

12:23

number or what address is it going to be

12:26

listening to

12:28

or an 80.

12:30

480 is the default port for web delivery

12:34

so on my server

12:38

obviously if it's going to be accessed

12:40

from the public it's going to have a

12:42

connection to it but inside This Server

12:44

I could have different Services running

12:49

so this server needs some kind of

12:51

mechanism

12:52

to identify

12:55

what the communication is

12:58

so when a message comes in here

13:02

this server's transport layer

13:05

you're going to be looking for

13:07

the destination port address

13:11

and if that port address is 80 and this

13:14

service is configured to listen to Port

13:16

80 the transport layer will now deliver

13:20

or

13:21

transport the message to the right

13:24

service okay see where the name came

13:26

from

13:27

not about picking it up from one source

13:29

and sending it to the receiver that's

13:31

another layer

13:33

what it's about is when the message gets

13:35

to the server

13:37

what service on the server needs it

13:39

so think about it as software delivery

13:43

okay

13:45

how does it accomplish that

13:48

how does the server know to look for

13:51

Port 80.

13:54

is that the header

13:56

see at this point in time

14:00

we have generated data

14:06

and the transport layer is going to take

14:08

that data and break it up when we break

14:11

it up what do we call it

14:15

and that's what the pdu is

14:22

for the transport layer

14:28

that happens guys let me know if I

14:31

misspell something

14:33

so the transport layer is going to take

14:35

the data it's going to segment we call

14:38

the segmentation

14:39

why why take something

14:42

that makes sense

14:44

and rip it all into a bunch of pieces I

14:46

mean if I deliver this all crumbled up I

14:49

can do this

14:51

and I say to you guys

14:57

here it is see if this makes sense to

15:01

you

15:03

doesn't it take all this extra time it

15:05

doesn't seem like it's wasteful that I'm

15:07

just taking that message and ripping it

15:10

up into tiny pieces just so somebody can

15:12

have fun gluing it back together

15:16

why would you do a thing like that

15:18

you notice I broke it up and destroyed

15:20

it to different people in this classroom

15:23

but that's only one page I got a whole

15:25

bunch more I really have some fun

15:30

it seems like the segment later could do

15:31

something else with its time instead of

15:33

just ripping my data apart

15:40

that's one

15:42

we don't depend on one and only one way

15:46

out of the classroom

15:48

so if one piece gets lost we have the

15:51

other stuff to work with

15:53

now that can work

15:55

sometimes

15:57

but that might not work other times like

16:00

what if that piece that I lose

16:02

is the end of my file

16:04

am I going to open up my file

16:06

I'm going to get like an EOS problem and

16:09

defile

16:10

problem

16:13

ah but that would be wasteful we only

16:16

have bandwidth that's only so much so it

16:18

wouldn't make sense to be sending

16:19

multiple copies of them all over the

16:21

place

16:23

gotta have some kind of system of

16:26

checking

16:27

to see if things got there we call this

16:30

reliable delivery

16:34

in order to ensure that we have reliable

16:36

delivery

16:38

we need to also make sure that once

16:42

but I'm taking these pieces and throwing

16:44

them all over the place

16:46

it's quite possible that maybe the end

16:48

is going to get there before the

16:50

beginning

16:52

so what do I need to do about that

16:56

this layer if it's going to rip it apart

16:58

better glue it back together but also

17:00

better glue it back together in order

17:02

so it makes sense for the application

17:05

layer to be able to display it to me

17:07

otherwise it's like taking a jigsaw

17:09

puzzle and just jamming the pieces

17:11

together and say I put it together well

17:13

it looks like crap the objective is to

17:15

put it together so it still looks like

17:17

the picture that you're working with

17:19

you good

17:21

so we get sort of

17:27

efficiency in the fact that the messages

17:30

are dispersed over multiple connections

17:32

multiple pathways

17:34

why do I say sort of efficiency well we

17:37

lose some by breaking it up right

17:40

because we've got to add all this other

17:42

stuff to keep track of it but we gain it

17:45

because we're saying if I had multiple

17:47

ways out of this classroom and everybody

17:49

wants to get out here in a hurry

17:50

after you go there if you go there if

17:52

you go there correct

17:55

that's like the difference between 17

17:57

and what 352.

18:00

one's a four-lane highway the other

18:01

one's a two

18:05

the other thing is sort of security

18:08

how many people take the same way to

18:09

work or same way to class all the time

18:11

from home

18:13

if you guys have a stalker it has made

18:15

my life a lot easier foreign

18:21

so if we're not encrypting the data it's

18:24

like a big Corporation covering their

18:25

assets

18:27

let's ask NASA they're known for this

18:29

the person making the handle for the

18:31

door doesn't know what door belongs to

18:33

and what project is part of

18:35

they're making one little part

18:37

a piece to larger puzzle

18:41

so it sort of builds Security in there

18:43

because you don't know what the left

18:44

hand is doing

18:45

so you guys can't collaborate

18:47

and try to you know sell the ideas to

18:50

another company

18:52

likewise if we send our segments all

18:54

over the place it makes it harder for

18:57

one person to get the whole entire

18:58

message

18:59

but is that the intent for the server to

19:02

get the message

19:05

so now we need to identify who gets the

19:07

whole entire message

19:09

that's another layer that's another

19:11

responsibility

19:13

right now I'm talking about managing the

19:17

data so that it can get there

19:20

in its entirety

19:23

transport layer

19:25

there's all Communications need to be

19:27

reliable

19:32

thank you

19:37

that's saying reliable though

19:40

so it is all Communications process need

19:42

to be reliable

19:48

I really

19:50

like my job

19:54

could you fill in that blank

19:58

you could try

20:00

what if I said I'm on a phone with you

20:03

guys

20:04

and we're talking about meeting I don't

20:07

know about dinner or for a movie

20:11

and we say okay well I'll be available

20:13

at 6 30.

20:16

and all you hear is at 6 30.

20:20

we already made plans that we're gonna

20:22

go to the movies but we didn't know what

20:23

time

20:24

right because you heard well let's plan

20:26

on going to movies but what time would

20:28

you like to go to the movies

20:29

and then all of a sudden I'm answering

20:30

back to you I say I will be available at

20:32

6 30 but all you hear is at 6 30.

20:37

could you say oh I guess he's available

20:38

at 6 30.

20:41

what if they didn't come in there and

20:43

all you heard was I'll be available at

20:46

would that work

20:47

but it's the same communication right

20:49

we're talking about going to the movies

20:51

I can't switch between reliable delivery

20:54

and unreliable delivery

20:57

it's either going to be one or the other

20:59

either you want me to make sure

21:00

everything got there

21:02

or you don't

21:04

you want me to stay out of this

21:06

conversation so that the conversation is

21:08

lean and mean more efficient

21:13

so as a programmer I'm going to decide

21:18

what protocols

21:21

my communication my application are

21:24

going to use

21:25

if I'm developing a web browser I'm

21:28

going to require that I use the TCP

21:31

protocol of the transport layer

21:34

TCP is short for transmission control

21:36

protocol

21:38

in short same order delivery

21:40

reliable Communications

21:46

no no problem

21:48

so we said same order delivery reliable

21:51

communication and develops a mechanism

21:54

to detect when things fail and to regain

21:58

those we call this flow control remember

22:00

we're talking about flow control where

22:01

our server can get inundated with too

22:03

much information or a client can get

22:05

inundated so it starts dropping things

22:06

so TCP has a mechanism to control how

22:10

much segments it's going to be sending

22:12

out

22:13

so it doesn't overwhelm

22:15

the receiving person

22:18

but in order for TCP to do that what's

22:21

going to happen is it's going to take

22:24

part of that data

22:26

and it's going to slap a header on there

22:32

and that header is going to be pretty

22:34

massive sometimes it might even bigger

22:36

than the data that you send

22:38

and in that header they're going to have

22:39

what they call sequence numbers we call

22:41

these fields it's going to have

22:43

acknowledgment numbers

22:44

see the sequence numbers are like little

22:46

tags that we know okay you got part one

22:49

you got part two you got part three the

22:52

acknowledgment numbers are away for the

22:53

server to tell them which one it has

22:55

received or what it expects to receive

22:57

next

22:58

acknowledging what it's already came in

23:02

what else

23:03

well we need to be able to put these

23:06

things back together some sequence

23:07

numbers help but we also need to

23:09

identify

23:10

what service or what application

23:14

is using it

23:15

so there's going to be Port addresses in

23:17

this header and that's the only kind of

23:19

fields that we need to know at this

23:21

particular moment is going to be a

23:23

source port

23:24

and a destination port address

23:31

The Source Port is randomly assigned by

23:34

the client's operating system by

23:37

definition the client is the one sending

23:40

the data in this communication okay

23:43

so the sender's operating system

23:47

is going to randomly assign a port

23:50

address why would the operating system

23:52

be responsible for randomly assigning

23:54

Port addresses for the source and only

23:55

the source

23:58

well we talk about using a web browser

24:01

right in this example

24:04

is Internet Explorer the only web

24:06

browser out there thank God

24:09

so there are certain applications or

24:12

websites that require you to use that

24:14

awful web browser correct

24:17

so it could be possible you guys could

24:19

have multiple web browsers

24:21

on your computer running at the same

24:23

time

24:23

that understand Port 80 or http

24:26

but

24:28

when I click in Internet Explorer I

24:30

don't want that page to reappear in

24:32

Firefox

24:35

otherwise every time I click on things

24:37

I'm going to be wondering where the hell

24:38

to go in my computer

24:40

so the operating system will stamp some

24:43

identifier

24:44

to the application

24:46

that started the communication process

24:49

so web browser doesn't have to have Port

24:52

80 as the source address none of them

24:54

will

24:55

it's going to be any number over 1024.

24:58

it's going to be randomly assigned up to

24:59

65 535 yes you will have to know these

25:02

addresses not all 65 000 of them but the

25:05

ranges we'll get into that we get the

25:08

transport layer all this is the grand

25:10

overview

25:12

so when I have multiple web browsers

25:13

I'll be randomly assigning The Source

25:15

port

25:16

what about the destination Port I cannot

25:18

randomly assign that if I'm using HTTP

25:21

I'll be putting in Port 80 here for

25:23

Destination so this way my server

25:27

nose

25:28

what to look for and what to grab from

25:31

their resources you've been there

25:35

all right

25:37

what if our communication process

25:39

doesn't want all this extra overhang

25:43

adding all these fields keeping track of

25:45

things controlling the flow what if I

25:47

throw it out there like I'm doing today

25:50

I didn't say David did you just get that

25:51

did you understand what I said

25:54

Tony did you get that do you understand

25:55

what I said

25:57

Dominic did you get that no you didn't

25:59

get it okay so let me say this again so

26:01

the destination Port is going to be port

26:03

80. do you see how long it would take me

26:06

to accomplish a lecture in this class if

26:08

I tried to verify every single one

26:12

of you making sure you understand that

26:14

would your education be improved yeah

26:17

because I'm not letting you guys go

26:19

I'm making sure that you get it and I

26:21

will drill it until you say acknowledged

26:26

and sometimes that might take me months

26:29

to do

26:30

and we only scraped the first chapter

26:33

you guys going to be experts in the

26:35

first chapter

26:36

do I do that in this class

26:38

no

26:40

I use unreliable delivery

26:43

unreliable

26:45

that's got to be awful

26:47

seems to be working for the last couple

26:49

of centuries

26:52

most of the time that we're lecturing

26:54

we're using unreliable delivery

26:57

most of the time people is like hearing

26:59

themselves talk they don't care whether

27:00

you guys get to each other or not

27:03

so an unreliable delivery

27:07

the transport layer uses another

27:09

protocol

27:10

called UDP

27:12

use your datagram protocol and in that

27:16

protocol we want to be really simple we

27:18

want to send as much of data as possible

27:20

we're still going to segment it okay

27:22

guys we're still going to segment it

27:25

but the size of my segments might be a

27:28

little bit bigger

27:29

than the TCP

27:32

we good there that allows me to send

27:34

more data

27:37

at a single time which would make the

27:40

process more effective

27:42

so I'm not wasting it by resending it

27:45

I'm not wasting it by creating all the

27:47

overhead

27:48

I'm just saying I'm going to send it to

27:50

you guys and if you don't get it what

27:52

are you supposed to do

27:54

raise your hand right

27:56

let me know

27:58

that's instructions I'm telling you guys

28:00

that's the application so if I choose to

28:03

use UDP

28:05

and I choose to say that this

28:06

conversation is either important or not

28:08

important if it is and I want as quick

28:11

as possible delivery method and I'm

28:14

going to build up in here way to

28:16

checking

28:18

the data myself

28:20

and that's what uTorrent does

28:23

I mean after all in order for you to

28:25

successfully download a file off a

28:27

uTorrent you need all the bits from

28:30

beginning to the end

28:31

but it would take uTorrent a very long

28:33

time every time they send five bits did

28:36

you guys get those last five bits yeah

28:39

send the next five all right send in the

28:41

next five

28:42

you guys get those next five yep and the

28:45

next five all right send the next five

28:48

the year before it's like you know what

28:51

send it send it out of order so when you

28:53

guys are watching your little progress

28:55

bar you might see certain areas filling

28:57

in it doesn't go from beginning to end

28:59

unlike when you download a file using a

29:02

web browser

29:03

you know like on blackboard you click on

29:05

a link like package here so you download

29:07

it doesn't it start at the beginning you

29:09

work its way to the end of progression

29:11

because HTTP uses TCP

29:15

and it takes it a lot longer

29:18

but ensures that every piece got there

29:20

nudity

29:23

so examples of UDP delivery is videos

29:27

and audio why are those two the prime

29:30

examples they don't have to do but they

29:33

are

29:35

the massiveness and you need it as close

29:38

to real time as possible

29:40

otherwise if I was having a conversation

29:42

or if I was watching with a video using

29:45

TCP every frame I get is going to want

29:48

to verify it

29:49

so I'm watching One frame and there's a

29:51

lag and another frame and then there's a

29:53

lag and then another frame

29:54

or I'm having a conversation with you

29:56

and it says I

29:59

my

30:01

name

30:03

is

30:05

and that's going to take a long time to

30:06

get there

30:07

so anything that's really time sensitive

30:13

the other thing is let's think about

30:15

videos and conversations vocal

30:18

conversations

30:19

you know ideally a video is about 30

30:22

frames per second that means every frame

30:25

is only about one-third of a second

30:28

and here I can detect that anything

30:29

beyond that your eye can

30:31

but

30:33

a whole length movie could have billions

30:34

of Franks

30:36

are you going to be too upset that you

30:37

lost one frame at the billion

30:39

no what if happens if you start losing

30:42

more of those things

30:45

yeah you just drag that you grab that

30:47

little status bar and drag it back and

30:49

let it rebuffer

30:50

and that's why we buffer

30:52

you ever also notice that certain parts

30:55

of the movie will load up faster when

30:56

you're streaming it over the internet in

30:58

other parts because remember we break it

31:00

out in segments the end could happen

31:02

before the beginning

31:03

but the application layer knows not to

31:06

play that just yet so it queues it up in

31:09

its buffer

31:10

until that time code is reached

31:14

so it's not like oh gee now everybody's

31:16

off the internet and it's going by fast

31:18

that could be possible but it could also

31:20

be it took that one message a long time

31:22

to get there and all the other messages

31:23

sound a shortcut

31:26

all right

31:27

so you're not you're only forced from

31:30

doing that by what the programmer so I

31:32

chose to use as a developer you have to

31:35

decide what you're going to give up with

31:37

reliability over performance

31:40

but if you're in a really questionable

31:42

area

31:43

you might choose liability just to make

31:45

sure that everything gets there

31:48

so we start the encapsulation process

31:51

excuse me by adding a header a UDP

31:54

header is going to be a lot smaller than

31:55

a TCP header hence

31:57

more efficient better performance

32:02

earlier I proposed oh before I get there

32:04

I got to tell you something else

32:08

remember I told you that we're going to

32:10

have multiple applications probably

32:11

running concurrently

32:14

and we're probably going to have

32:15

multiple computers on our network using

32:17

this uh using our connection

32:19

probably concurrently as well

32:21

so not only do we gain segmentation as a

32:24

way of disbursing our messages across

32:27

several connections

32:28

but we also allow multiple people to use

32:31

the same connection rather

32:33

simultaneously now I put the word rather

32:35

simultaneously it's just like time

32:38

sharing when it comes to your processor

32:40

it happens so fast it looks like your

32:41

computer is multitasking

32:43

which doesn't really do it at least the

32:45

old process is never really multicast it

32:47

did one task and the other task rather

32:50

extremely fast it looked like it did it

32:52

at the same time all right guys

32:54

so likewise when it comes to networks

32:56

most of our connections can't handle

32:59

parallel connections that is concurrent

33:01

connections at the same time so what we

33:03

do is we Multiplex the conversation that

33:06

is we take segments from different

33:07

conversations and interweave them

33:10

together so it looks like everybody's

33:12

using the same network connection at the

33:14

same time

33:15

clear about that so by segmentating the

33:18

data it also allows for multiple people

33:21

to use the same connection

33:23

so there's no monopolization happening

33:25

all right so earlier I posed a problem I

33:28

said that the transport layer is

33:30

designed to identify the application the

33:32

services that are receiving it but

33:35

because these packets sorry these

33:36

segments are going to be traveling all

33:38

over the internet

33:39

different Pathways we need some kind of

33:42

mechanism

33:43

that when that message gets to it it

33:47

knows what Pathway to send it down to

33:50

so all three gets to the Final

33:52

Destination

33:54

that's what this layer is all about this

33:56

is called the network layer it gets its

33:59

name because

34:04

when those messages or the segments are

34:07

being distributed across the network

34:09

this layer has got to be used by a

34:12

particular device

34:14

to Route it along its way

34:16

and that device is called a

34:18

router

34:20

so not only do we have protocols

34:23

to identify each layer we also have

34:26

devices

34:27

so when you get to about layer three

34:30

you're going to get into specialized

34:32

devices layer four and up probably going

34:35

to be internal on your computer into

34:36

your operating system into your end

34:37

device

34:39

in fact when you get into Windows you'll

34:41

see the transport layer there's a

34:42

protocol installed called TCP slash IP

34:46

and you can go in there and make some

34:47

settings like the flow control

34:49

like segment size

34:51

so here we are layer three it's going to

34:55

take that segment and once again

34:57

re-encapsulate it so now we have the

35:00

segment

35:03

we're going to add a header to it

35:06

that's for each segment by the way

35:11

we re-encapsulate it we're going to call

35:14

this

35:15

a packet

35:23

what's the difference between a packet

35:25

and a segment

35:27

a packet has information

35:30

used to identify end devices

35:37

the key is identifying end devices so

35:40

the sender

35:41

and the receiver

35:50

I before you accept after C is that the

35:52

rule

35:53

I hate the English protocol

35:55

that's just crazy I always misspell

35:57

receiver

35:59

so that is to say

36:02

in this header

36:04

there's got to be an addressing

36:06

mechanism

36:08

what addressing mechanism have we

36:10

learned so far

36:12

or at least explored I should say

36:17

exactly hence

36:20

the protocol used in layer three

36:23

is typically ipv4

36:27

but it's not the only and I gotta beat

36:28

this out of you guys because it took me

36:30

a lot of years myself to convince myself

36:32

all the protocols do exist

36:35

IP is one

36:37

we have apple talk is another we have

36:41

net value is another we have ipx is

36:45

another we have something called

36:47

connectionless Network Services

36:49

so they go on and on IP is the most

36:51

popular why why is the IP protocol the

36:54

most popular compared to uh let's just

36:56

throw apple on the bus so Apple talk why

36:59

is IP more profit than Apple talk

37:02

open

37:04

as an open protocol

37:06

and so more people more willing to adopt

37:09

that because it'll cost them any money

37:10

so when HP decided to make a network

37:13

connected printer

37:15

and decided to say oh I'm not going to

37:18

go buy Apple talk and at one time

37:20

especially in the 80s you would have to

37:22

buy several different interfaces for

37:24

your printer to get them to connect or

37:26

your end device

37:28

and so now it's like you look back out

37:30

of there the only thing you're going to

37:30

see is either a USB port or an ethernet

37:32

port that's it

37:34

nowadays you can buy these computer

37:36

documents I'm sorry these printers

37:37

without connecting wires to it as long

37:39

they agree to the 802.11. so this is the

37:42

nice thing about openness

37:44

if more people start to use it it starts

37:46

to become a standard

37:48

and if popularity dictates that's the

37:51

only thing we're going to learn

37:53

in this course but I will put that

37:55

little slime print it's not the only one

37:58

okay if I'm making this point expect to

38:01

see it on one of your exams one of my

38:03

exams that I make for you

38:05

question

38:09

they won't ever do it again they it cost

38:11

them too much financially they realize

38:13

they weren't as powerful as they thought

38:14

they were so they had to start

38:16

developing things that were more

38:17

accommodating yes because when you start

38:20

seeing the popularity of the internet

38:21

and by the way that's the only reason

38:24

why we got rid of all this well not all

38:26

of it but most of proprietary bullshit's

38:28

been gone because of the eye socket or

38:31

the isos the internet Society

38:33

hosting and making things open and free

38:35

for the market has caused other

38:37

companies Say Hey I want to use my

38:39

product well I'm only going to use a

38:41

product if I can get on Facebook

38:43

in fact isn't that the biggest complaint

38:44

about going from Android to iPhones

38:47

or the iOS

38:49

what's the biggest thing that Android

38:50

has going for itself right now

38:53

it still plays Flash

38:58

whereas the iOS says Apple's like

39:01

sticking it to uh Adobe saying nope

39:04

got security problems and you're too

39:06

battery hungry so we're not going to

39:08

allow any flash content through our

39:10

devices and it's annoying it's really

39:13

annoying and you're trying to go onto a

39:15

website in this open free platform and

39:18

it says oh you're using iPad sorry tough

39:20

luck

39:23

so people buy Android tablets

39:28

so this is that philosophy come into

39:30

effect so the network layer is going to

39:33

basically set a source IP address and a

39:35

destination IP address

39:38

The Source where it came from

39:41

destination where it's going the

39:44

important thing is in that address is

39:45

going to be a network address and that's

39:47

how routers know where to pass things

39:49

along

39:51

all right after we get done with the

39:52

network layer we go to Layer Two

39:56

this is my favorite layer out of all of

39:58

them folks

40:01

data link layer

40:06

okay when I say the word link what are

40:08

you guys thinking

40:09

give me a basic Bare Bones generic

40:13

definition of a link

40:16

yeah it's going to connect two things

40:17

together right

40:19

all right

40:20

everything up to this point looks like

40:23

this

40:29

if you see that what's the generic term

40:32

for that

40:33

what would you guys call it and don't

40:35

call it binary

40:36

but it's what the machine uses to store

40:39

what

40:43

data

40:44

because what's the definition of a

40:46

computer

40:48

anything that receives

40:50

data processes it and converts it into

40:53

information right

40:55

so that means the machine sees it like

40:57

this this is data so this layer is

40:59

called the data link layer

41:01

it's taking that and linking it to what

41:05

the last layer layer one

41:08

which is known as the physical layer

41:21

this is Layer Two is the last layer that

41:24

the encapsulation process

41:26

occurs

41:27

in fact we get done day in the layer two

41:31

data link layer we produce a frame

41:36

what is a frame it is a packet

41:44

with a header

41:48

and a trailer

41:55

this is the only layer that we add a

41:57

trailer to the encapsulation process all

42:01

the other layers said a header is just

42:03

fine

42:05

why does this one have

42:07

a trailer

42:09

this is the last time in fact this layer

42:12

has two sub layers one's called The

42:14

Logical layer then the other one's

42:15

called oh we're blinking so I'll lose

42:17

this I hate that hopefully it's still

42:19

recording but whatever you guys are

42:21

watching this video it probably got cut

42:22

right here at this point which is almost

42:25

just in time but regardless

42:27

what this layer has two sub layers one's

42:31

called The Logical layer the other one's

42:32

called the Mac layer the media Access

42:35

Control layer and it's linking the

42:38

physical world with the logical world

42:40

how does it do that

42:42

with things called Mac addresses

42:45

see earlier we talked about IP addresses

42:48

as identifying the sender

42:51

and the receiver the source and

42:52

destination before that we talked about

42:55

Port addresses right and what were they

42:57

used to used for

43:00

to identify the application and the

43:03

service correct so these addresses are

43:05

used for identification

43:07

transport applications and Services

43:09

Network

43:11

Thunder receiver because that's there's

43:15

addresses here we call them physical

43:17

addresses what do you guys think they're

43:19

going to be used for

43:23

along this journey to get from here

43:27

to there

43:29

might be several different Pathways

43:31

several physical connections like for me

43:34

to get from here to my office I gotta go

43:36

out of that do a walk across this carpet

43:38

run go up these concrete steps or across

43:41

a tile floor back on the carpet rug and

43:44

in my office

43:46

now since it's Corning I really don't

43:49

care but if it's at home

43:51

you might want to take off my shoes

43:54

right

43:55

if I'm walking on tile at my house I

43:58

really don't care to take off my shoes

44:00

grab the mop clean it up gun

44:03

if I got muddy shoes and I walk on my

44:05

rug

44:06

somebody's gonna kick my ass

44:09

right you see these different physical

44:11

properties and how it affects Behavior

44:14

so somebody told me you see rug take off

44:17

your shoes you see tile walk on it

44:20

likewise this layer right here

44:24

there's rules protocol that we tend to

44:27

use in a wired based Network like the

44:29

one that you guys have right in front of

44:30

you is the ethernet protocol or the

44:33

ethernet standard

44:34

and in that protocol they are going to

44:37

tell me

44:40

when a frame begins and when a frame

44:43

ends and that's why it's important

44:49

that this layer produces a trailer

44:52

can you guys tell me this wire is

44:54

actually unplugged now

44:57

are there any zeros and ones on this

44:59

wire

45:01

why do you say that

45:05

does not plug in anything

45:07

well let me tell you this water is made

45:09

of Papa

45:11

what have we learned about copper

45:14

it conducts electricity it's also

45:16

susceptible to what we call EMS you guys

45:19

don't believe there's any zeros and ones

45:21

on there when you get home tonight and

45:22

you're bored go grab a metal pipe

45:26

yeah six feet ten feet will do

45:28

and take this wire strip the insulation

45:30

off because you need to get a charge out

45:32

of this exercise

45:33

and wrap it around that metal pipe

45:36

and then go find the 600 volt power

45:38

lines those big transmission power lines

45:40

and drop it underneath it

45:44

and hold it for a second

45:48

the longer the pipe The More Voltage

45:51

the more charge you'll get out of it

45:54

they call this induction you're starting

45:57

to see this with wireless chargers

45:58

we get in charge of batteries without

46:00

any wires

46:01

so once again are there zeros and ones

46:04

on this wire

46:05

absolutely

46:06

the tree falls in the forest and

46:08

nobody's around to hear it it does make

46:09

a sound does make noise

46:12

so

46:14

where is it coming from our atmosphere

46:16

David question

46:20

protect it yeah yeah exactly you're

46:23

using the same induction all right so

46:26

there are zeros and ones on this wire

46:28

all the time

46:29

how do I know those zeros and ones are

46:32

my data or they're just bogus signals

46:38

how do I know that this is just some

46:40

random mess

46:44

verse

46:46

I'm sending Morris code

46:52

this very rarely happens

46:56

in nature where it's very systematic it

47:01

has a beat it has a tone there's timing

47:04

involved and you guys could time in if

47:06

you want because you know

47:09

the intervals right

47:11

when I start seeing that I'm like wait a

47:15

minute that's pretty weird

47:17

that

47:19

I'm getting clap nothing clap nothing

47:22

clap

47:24

I might get

47:27

some random crap

47:29

but this seems like it's done

47:31

intentionally

47:32

so your interface card perks up

47:34

it says I know that pattern

47:37

this pattern

47:38

is telling me the beginning of a frame

47:43

now this pattern goes on for so many

47:46

seconds I don't necessarily know

47:49

when it began but I do know this

47:54

that should end the pattern

47:57

right

47:58

so anything after that is going to be my

48:01

data

48:03

now we need a trailer

48:05

and that might be something like this

48:12

and that ends the transmission

48:15

that's how I know to grab a frame

48:19

where the frame begins and where it ends

48:20

because once I know the beginning of my

48:22

frame I can remove the header

48:25

and what do I get when I remove the

48:26

header in the trailer

48:28

I get the packet I pass it up

48:31

now that I got the packet I remove the

48:34

header and what do I get

48:37

and I pass it up now I remove that

48:39

header and a way to build the data back

48:42

up to its entirety and I pass it back up

48:44

to the application there

48:46

and that's the communication process so

48:49

I ran over I will see you guys some of

48:52

you tomorrow other of you definitely on

48:54

Wednesday you guys take care watch those

48:56

videos

48:58

and uh

48:59

stay tuned

49:00

yeah

Interactive Summary

This instructional video provides a detailed overview of the OSI model and network standards. The speaker explains the role of organizations like ISO and IEEE in developing open protocols to foster competition and compatibility. The lecture systematically covers the OSI layers, from the Application layer's interface to the network, down to the Physical layer's electrical signals. Key concepts discussed include the differences between TCP and UDP, the process of encapsulation and segmentation, and the use of logical versus physical addressing in data transmission.

Suggested questions

5 ready-made prompts