WEBVTT

0:00:08.700000 --> 0:00:12.200000
 I'm going to start with
 the early Internet.

0:00:12.200000 --> 0:00:14.500000
 What did that look like.

0:00:14.500000 --> 0:00:17.040000
 So what we're talking
 about here is the.

0:00:17.040000 --> 0:00:20.860000
 Nineteen sixties the early
 nineteen sixties.

0:00:20.860000 --> 0:00:25.140000
 I would like to say and yes I can actually
 say that was before I was born

0:00:25.140000 --> 0:00:30.760000
 good but. So the early Internet- some
 terms you made have heard of before

0:00:30.760000 --> 0:00:33.760000
 DR. Or ARPA so D.

0:00:33.760000 --> 0:00:40.180000
 ARPA stood for the defense advanced
 research projects agency okay.

0:00:40.180000 --> 0:00:44.100000
 And the early Internet start out as
 a project from I'm not sure if I'm

0:00:44.100000 --> 0:00:48.740000
 pronouncing it correctly if it's just people
 say DARPA or DRPA never actually

0:00:48.740000 --> 0:00:49.940000
 really looked that up.

0:00:49.940000 --> 0:00:53.540000
 But it started out as a research project
 from them and they created something

0:00:53.540000 --> 0:00:56.740000
 called the ARPA net the ARPA net.

0:00:56.740000 --> 0:01:01.440000
 And originally way back in the day
 the ARPA net was very simple.

0:01:01.440000 --> 0:01:05.780000
 It simply consisted of two hosts which
 were mainframes so this is even

0:01:05.780000 --> 0:01:10.020000
 before laptops were PCs were generating
 these two monstrous computers

0:01:10.020000 --> 0:01:13.440000
 that were talking to each other and that
 was the early form of networking

0:01:13.440000 --> 0:01:18.540000
 having one mainframe be able to connect
 and get the resources of another

0:01:18.540000 --> 0:01:23.780000
 mainframe it was a point to point connection
 using circuit switching lines

0:01:23.780000 --> 0:01:27.020000
 actually using the phone lines the mainframes
 were located at different

0:01:27.020000 --> 0:01:28.220000
 universities different colleges.

0:01:28.220000 --> 0:01:31.400000
 I think they were in the same state
 originally I think they were both

0:01:31.400000 --> 0:01:33.360000
 in California originally.

0:01:33.360000 --> 0:01:37.740000
 But they used basically the telephone lines
 to get to each other and transfer

0:01:37.740000 --> 0:01:42.280000
 their data. Wait a
 little fast there.

0:01:42.280000 --> 0:01:47.120000
 So keep in mind back in these early
 days here there was no such thing

0:01:47.120000 --> 0:01:50.040000
 as a LAN as a local area network.

0:01:50.040000 --> 0:01:54.780000
 And this is important to conceptualize
 because I don't know if you're

0:01:54.780000 --> 0:02:00.380000
 like me or not but when I try to visually
 think visually picture in my

0:02:00.380000 --> 0:02:05.900000
 mind data going across a network the
 image that comes to my head is number

0:02:05.900000 --> 0:02:11.780000
 one I imagine data coming in to my
 laptop so inbound or in-grass data

0:02:11.780000 --> 0:02:17.060000
 and I envision that as a series of electrical
 pulses right you know electrical

0:02:17.060000 --> 0:02:21.700000
 pulses coming in and these electrical
 pulses are being interpreted as

0:02:21.700000 --> 0:02:25.500000
 ones and zeros right so my nit card
 is seeing this electricity bouncing

0:02:25.500000 --> 0:02:29.440000
 around on the cable and it's interpreting
 that as a series of just thousands

0:02:29.440000 --> 0:02:33.240000
 of ones and zeros coming
 in really really quickly.

0:02:33.240000 --> 0:02:38.280000
 And when I think in terms of sort of
 the OSI model and the stack and all

0:02:38.280000 --> 0:02:40.900000
 that stuff the first thing that comes
 to my mind is okay those electrical

0:02:40.900000 --> 0:02:44.900000
 pulses that's my physical layer that's
 layer one of the OSI model the

0:02:44.900000 --> 0:02:49.660000
 electricity coming into the nit card
 and then I start going up the OSI

0:02:49.660000 --> 0:02:52.360000
 model this is the way I envision I say
 okay well the next one is the data

0:02:52.360000 --> 0:02:56.960000
 link layer layer two and at the data
 link layer my nit card says okay

0:02:56.960000 --> 0:03:00.460000
 let's see here what what rules am I following
 what protocol am I following

0:03:00.460000 --> 0:03:05.880000
 oh I'm doing ethernet so according
 to the rules of ethernet the first

0:03:05.880000 --> 0:03:10.460000
 few pulses of electricity are the preamble
 in the ethernet frame the next

0:03:10.460000 --> 0:03:14.740000
 few pulses of electricity are the destination
 Mac followed by the source

0:03:14.740000 --> 0:03:19.680000
 Mac and then eventually layer two says
 I'm done I've looked at you know

0:03:19.680000 --> 0:03:24.360000
 a few hundred bits I've been able to
 interpret that as an ethernet frame

0:03:24.360000 --> 0:03:29.280000
 within those few hundred bits it told
 me that the next section is going

0:03:29.280000 --> 0:03:33.760000
 to be IP and so now we go to the networking
 layer so when I visualize

0:03:33.760000 --> 0:03:37.180000
 this I start at layer one I go to layer
 two and then layer three and on

0:03:37.180000 --> 0:03:41.620000
 up and why I'm bringing that up right
 here is because originally when

0:03:41.620000 --> 0:03:48.200000
 the original ARPANET was designed there
 really wasn't a layer two I mean

0:03:48.200000 --> 0:03:51.120000
 there was a layer one right it was a
 circuit switch line using telephone

0:03:51.120000 --> 0:03:55.400000
 lines for one mainframe to call another
 mainframe but there was no such

0:03:55.400000 --> 0:03:59.980000
 thing as ethernet originally back in
 these days back in the early 1960s

0:03:59.980000 --> 0:04:04.900000
 so there was no such thing as Mac addresses
 you know a lot of times people

0:04:04.900000 --> 0:04:11.260000
 assume that historically layer two came
 out first Mac addresses and then

0:04:11.260000 --> 0:04:17.180000
 IP came out after that but it's actually
 just the opposite TCP IP came

0:04:17.180000 --> 0:04:23.480000
 out before local area networks came
 out before ethernet so as it says

0:04:23.480000 --> 0:04:27.520000
 here all communications originally were
 point-to-point and initially it

0:04:27.520000 --> 0:04:30.800000
 was like circuit switching which is
 another way of using of saying the

0:04:30.800000 --> 0:04:36.260000
 phone lines and then as more and more
 network start coming up they were

0:04:36.260000 --> 0:04:40.120000
 still point-to-point one device talking
 to another device but they start

0:04:40.120000 --> 0:04:44.660000
 using other types of media at the physical
 layer like satellite uplinks

0:04:44.660000 --> 0:04:48.620000
 like direct cable connections what I
 mean I don't mean like cable modem

0:04:48.620000 --> 0:04:52.600000
 I mean like a physical hardwired cable
 from one mainframe and one building

0:04:52.600000 --> 0:04:55.880000
 to another mainframe and another building
 that's what I'm talking about

0:04:55.880000 --> 0:05:02.920000
 there so as these point-to-point networks
 were being developed as it says

0:05:02.920000 --> 0:05:06.660000
 there was a need to develop a protocol
 so that hosts on these disparate

0:05:06.660000 --> 0:05:11.960000
 networks could communicate with each
 other so the idea was okay I've just

0:05:11.960000 --> 0:05:16.740000
 developed a very primitive network where
 my mainframe can talk to another

0:05:16.740000 --> 0:05:22.840000
 mainframe now what if I expand that
 to where my mainframe now has the

0:05:22.840000 --> 0:05:29.760000
 ability to talk to six other mainframes
 still direct connections what

0:05:29.760000 --> 0:05:34.800000
 if I expand that a little bit further
 what if I say I want my mainframe

0:05:34.800000 --> 0:05:41.840000
 to talk to you know Sally's mainframe and
 then jump through Sally's mainframe

0:05:41.840000 --> 0:05:47.000000
 to Bob's mainframe on the other side
 now it's not point-to-point it's

0:05:47.000000 --> 0:05:51.260000
 me talking to somebody else and then
 going through them to somebody else

0:05:51.260000 --> 0:05:53.920000
 and they start saying okay well we need
 some sort of address to do that

0:05:53.920000 --> 0:05:58.220000
 so when I connect to Sally I need to
 have some way of telling her hey

0:05:58.220000 --> 0:06:02.520000
 I don't really want to talk to you I
 don't really need your data I just

0:06:02.520000 --> 0:06:07.520000
 need you to take what I'm sending you
 and pass it on to Bob behind you

0:06:07.520000 --> 0:06:11.920000
 and so this is where the whole idea
 of TCP IP originally came in became

0:06:11.920000 --> 0:06:16.920000
 invented they said okay well we need
 some sort of of address so that when

0:06:16.920000 --> 0:06:20.600000
 I'm sending my data to Sally she knows
 it's not for her it's for the person

0:06:20.600000 --> 0:06:24.960000
 behind her so she can establish a connection
 and we also need to figure

0:06:24.960000 --> 0:06:28.440000
 out some ways to make you know that
 data reliable like you know how do

0:06:28.440000 --> 0:06:33.540000
 I know if I if I send something to
 Bob way out there how do I know if

0:06:33.540000 --> 0:06:37.800000
 it got there you know how long should
 I wait before I determine that oh

0:06:37.800000 --> 0:06:41.780000
 doesn't look like it got there what should
 I do about that so they actually

0:06:41.780000 --> 0:06:47.300000
 developed TCP right along the same
 time as IP so TCP was developed to

0:06:47.300000 --> 0:06:51.520000
 do you know answer questions of how
 do I make this very unreliable very

0:06:51.520000 --> 0:06:56.900000
 primitive connection reliable for me
 and what do I do when stuff is lost

0:06:56.900000 --> 0:07:00.740000
 and then of course they put IP along
 with that so we could have addressing

0:07:00.740000 --> 0:07:06.080000
 this give you some interesting terminology
 back in the original ARPANET

0:07:06.080000 --> 0:07:09.580000
 these these two or three colleges or
 universities that had mainframes

0:07:09.580000 --> 0:07:13.820000
 talking to each other that they actually
 developed a whole unique box

0:07:13.820000 --> 0:07:18.320000
 a whole unique system that the mainframe
 would connect to and then these

0:07:18.320000 --> 0:07:21.920000
 boxes these black boxes is actually
 what formed the network these black

0:07:21.920000 --> 0:07:26.240000
 boxes would use the circuit switching
 lines to talk to each other and

0:07:26.240000 --> 0:07:28.860000
 they were called anybody studied the
 history of the Internet does anybody

0:07:28.860000 --> 0:07:33.620000
 know what those original I would say
 routers what was the name of the

0:07:33.620000 --> 0:07:37.400000
 very first routers that were developed
 that these mainframes connected

0:07:37.400000 --> 0:07:42.140000
 to to talk each other anybody know it's
 actually has kind of a funny sounding

0:07:42.140000 --> 0:07:49.020000
 acronym they were called imps or Internet
 messaging processors they were

0:07:49.020000 --> 0:07:52.740000
 huge they were like the size of a refrigerator
 and of course you know

0:07:52.740000 --> 0:07:56.360000
 the mainframe was like the size of
 your whole house but the mainframe

0:07:56.360000 --> 0:07:59.840000
 would connect to this big refrigerator
 sized box called an imp and it

0:07:59.840000 --> 0:08:03.460000
 was actually the imp that needed to
 be addressed the imp need to have

0:08:03.460000 --> 0:08:07.640000
 an address so it could talk to you
 know the imp in Stanford could talk

0:08:07.640000 --> 0:08:11.640000
 to the imp in Berkeley or the imp in
 Stanford could talk to the imp in

0:08:11.640000 --> 0:08:14.720000
 Los Angeles and so that's where they
 originally came up with the idea

0:08:14.720000 --> 0:08:21.060000
 of layer three addressing okay so the
 the main point I want you to take

0:08:21.060000 --> 0:08:26.180000
 away from here is that number one the
 very very first networks were point

0:08:26.180000 --> 0:08:31.460000
 to point only because number two there
 was no concept of local area networks

0:08:31.460000 --> 0:08:35.080000
 there was no concept of something called
 a broadcast domain where a whole

0:08:35.080000 --> 0:08:39.580000
 bunch of devices could see each other
 on the same wire that had not been

0:08:39.580000 --> 0:08:45.960000
 created yet so this is what networks
 look like you know back in the early

0:08:45.960000 --> 0:08:51.420000
 days you had these Internet messaging
 processors connecting to always

0:08:51.420000 --> 0:08:59.220000
 up circuit you know and the original
 layer three protocol that they used

0:08:59.220000 --> 0:09:02.280000
 to address these things actually wasn't
 even IP they came up with a precursor

0:09:02.280000 --> 0:09:07.920000
 to that which was called the network
 control protocol NCP and NCP didn't

0:09:07.920000 --> 0:09:11.960000
 even really it the only kind of addressing
 it used was like for port numbers

0:09:11.960000 --> 0:09:17.040000
 like whatever protocols were running
 on that mainframe each protocol had

0:09:17.040000 --> 0:09:19.660000
 sort of its own unique port number
 and that's how they address things

0:09:19.660000 --> 0:09:25.540000
 and then of course we had dial up circuits
 where people would use modems

0:09:25.540000 --> 0:09:30.360000
 to connect to each other or satellite
 networks so these were the early

0:09:30.360000 --> 0:09:34.980000
 days then people said and this is why
 I described earlier is they will

0:09:34.980000 --> 0:09:40.240000
 what if I in the future need to jump
 through something you know what if

0:09:40.240000 --> 0:09:44.040000
 what if I need to connect as we can
 see here this mainframe on the far

0:09:44.040000 --> 0:09:49.620000
 left wants to connect all the way to
 the mainframe in the bottom so we've

0:09:49.620000 --> 0:09:54.380000
 got to jump through a couple things
 to do that so you know it was the

0:09:54.380000 --> 0:09:59.140000
 vision of these early Internet pioneers
 that have somehow people could

0:09:59.140000 --> 0:10:02.480000
 connect these disparate networks together
 a satellite network connected

0:10:02.480000 --> 0:10:06.880000
 to a modem network connected to a dial
 network if they could somehow connect

0:10:06.880000 --> 0:10:11.360000
 all these things together you would now
 have networks connected by a series

0:10:11.360000 --> 0:10:14.900000
 of hops and so there was going to be
 a need for some kind of networking

0:10:14.900000 --> 0:10:19.580000
 addressing scheme flow control error
 correction and detection and all

0:10:19.580000 --> 0:10:25.720000
 that stuff and that is where TCP IP
 was born with the need to solve the

0:10:25.720000 --> 0:10:31.640000
 problems introduced by what you see
 right here so the original desires

0:10:31.640000 --> 0:10:36.560000
 of TCP IP said okay one of things we're
 going to need is on each hop in

0:10:36.560000 --> 0:10:41.180000
 the network is going to need an address
 so when we send data that hop

0:10:41.180000 --> 0:10:46.280000
 knows is that data for you or for someone
 behind you and so the original

0:10:46.280000 --> 0:10:50.580000
 desires of IP said okay well let's see
 here you know everything is viewed

0:10:50.580000 --> 0:10:53.680000
 by computers is binary it's just ones
 and zeros ones and zeroes just a

0:10:53.680000 --> 0:10:59.280000
 string of binary so they said well in
 their in however many meetings they

0:10:59.280000 --> 0:11:03.340000
 had they decided that address is going
 to be 32 bits long they said that

0:11:03.340000 --> 0:11:07.820000
 a unique network address is going to
 be 32 bits long and they said okay

0:11:07.820000 --> 0:11:13.340000
 well you know remember this is like
 the late 1960s now like 1969 1970

0:11:13.340000 --> 0:11:19.320000
 and at this point in time there's literally
 a handful of these networks

0:11:19.320000 --> 0:11:25.300000
 and so they said well let's see here
 a 32 bit address I don't really see

0:11:25.300000 --> 0:11:28.340000
 how there's ever going to need to be
 any more than a couple of hundred

0:11:28.340000 --> 0:11:31.720000
 networks I mean this is all experimental
 we're just seeing if this works

0:11:31.720000 --> 0:11:38.420000
 so this 32 bit address will say that
 the first 25% of it the first 8 bits

0:11:38.420000 --> 0:11:43.160000
 will represent the network and then
 the remaining bits will represent

0:11:43.160000 --> 0:11:49.580000
 that unique imp or mainframe on the
 network so keep in mind the original

0:11:49.580000 --> 0:11:54.820000
 IP address was 32 bits long just like
 it is today but key difference was

0:11:54.820000 --> 0:12:01.300000
 it was understood that of that 32 bit
 address only the first 8 bits at

0:12:01.300000 --> 0:12:05.360000
 the front end represented the network
 address and if you think in terms

0:12:05.360000 --> 0:12:09.060000
 of binary you realize that with 8 bits
 to play with you're pretty limited

0:12:09.060000 --> 0:12:13.140000
 in how many networks you have as a matter
 of fact you only have 254 networks

0:12:13.140000 --> 0:12:17.980000
 available now with 8 bits technically if
 you think of every possible combination

0:12:17.980000 --> 0:12:23.600000
 of binary you can come up with from
 0 0 0 up to 1 1 1 1 and everything

0:12:23.600000 --> 0:12:31.320000
 in between technically that gives you
 256 combinations of numbers of bits

0:12:31.320000 --> 0:12:35.120000
 you can come up with with 8 bits to
 play with but the early designers

0:12:35.120000 --> 0:12:40.660000
 of IP said well two of those combinations
 are not going to be usable as

0:12:40.660000 --> 0:12:45.720000
 an address the combination where the
 network is all zeros so the first

0:12:45.720000 --> 0:12:50.180000
 8 bits of those are all zeros that represents
 like a default route a route

0:12:50.180000 --> 0:12:54.960000
 to anywhere and then the other combination
 is if all of those bits are

0:12:54.960000 --> 0:12:59.360000
 ones that's considered a broadcast it's
 like sending something to anybody

0:12:59.360000 --> 0:13:10.060000
 so those two numbers out of 256 you have
 about 59 1970 they were thinking

0:13:10.060000 --> 0:13:14.360000
 we're never going to use 254 networks
 I mean this is experimental this

0:13:14.360000 --> 0:13:19.480000
 is for fun of course we know that didn't
 turn out to be the case now what's

0:13:19.480000 --> 0:13:24.120000
 kind of interesting is it was actually
 very forward thinking of these

0:13:24.120000 --> 0:13:27.980000
 people to come up with a networking address
 where you had a network address

0:13:27.980000 --> 0:13:33.100000
 and then a bunch of host bits if you
 think about it there were no lands

0:13:33.100000 --> 0:13:37.840000
 back then there were no broadcast domains
 it was just point to point they

0:13:37.840000 --> 0:13:40.500000
 could have come up with a scheme where
 they said okay every device is

0:13:40.500000 --> 0:13:43.480000
 just going to have a 32-bit number we're
 not going to divide this between

0:13:43.480000 --> 0:13:47.260000
 network and host you're going to have
 a unique name I'm going to have

0:13:47.260000 --> 0:13:50.940000
 a unique name where else just all going
 to know each other's unique names

0:13:50.940000 --> 0:13:54.680000
 but they didn't do that they took this
 32-bit number and they divided

0:13:54.680000 --> 0:14:00.020000
 it eight bits for the network 24 bits
 on the end for host and because

0:14:00.020000 --> 0:14:04.820000
 they did that it was setting the stage
 for a few years later when lands

0:14:04.820000 --> 0:14:09.720000
 and ethernet would come out and those
 host bits would take on a lot more

0:14:09.720000 --> 0:14:17.880000
 relevance so we can see here in this
 particular case we've got four unique

0:14:17.880000 --> 0:14:22.700000
 networks so if we only have eight bits
 to play with they would say something

0:14:22.700000 --> 0:14:25.540000
 like okay network number one you can
 see there it's going to be seven

0:14:25.540000 --> 0:14:30.220000
 zeros followed by a one network number
 two it's going to be six zeros

0:14:30.220000 --> 0:14:34.640000
 followed by a one zero so as long as
 those eight-bit patterns are unique

0:14:34.640000 --> 0:14:39.420000
 from each other they're different they
 can be recognized as being different

0:14:39.420000 --> 0:14:53.840000
 networks all right now here we go into
 the 1970s and so in the late 1970s

0:14:53.840000 --> 0:15:01.500000
 now ethernet and that's not part of the
 CCNA you're right token ring died

0:15:01.500000 --> 0:15:06.060000
 out many many years ago but back in
 this day they were competing layer

0:15:06.060000 --> 0:15:10.760000
 two protocol data link layer protocols
 and both ethernet and token ring

0:15:10.760000 --> 0:15:17.000000
 were founded on the same idea that you
 could have a bunch of devices still

0:15:17.000000 --> 0:15:21.540000
 probably mainframes or big servers but
 a bunch of devices all connected

0:15:21.540000 --> 0:15:27.900000
 to some common network media and able
 to see each other able to talk to

0:15:27.900000 --> 0:15:31.440000
 each other so for example ethernet the
 original ethernet was a big thick

0:15:31.440000 --> 0:15:35.500000
 sort of coaxial cable very similar to
 the cable that goes into your cable

0:15:35.500000 --> 0:15:39.560000
 TV set it was big it was yellow it
 wasn't really bendable and the idea

0:15:39.560000 --> 0:15:44.320000
 was you could have several mainframes
 all clamped into that same cable

0:15:44.320000 --> 0:15:48.700000
 and if they were running ethernet now
 they could see each other on that

0:15:48.700000 --> 0:15:52.280000
 cable that if any mainframe start transmitting
 voltage start transmitting

0:15:52.280000 --> 0:15:57.220000
 electricity on that cable you had more
 than one device on that cable that

0:15:57.220000 --> 0:16:01.900000
 could see it and so this is the whole
 idea of a broadcast domain right

0:16:01.900000 --> 0:16:07.240000
 a broadcast domain is is a collection
 of devices connecting to a common

0:16:07.240000 --> 0:16:11.940000
 network media let's just say it's a
 cable to make it simple and in that

0:16:11.940000 --> 0:16:16.560000
 broadcast domain if one of those devices
 starts using that network media

0:16:16.560000 --> 0:16:20.860000
 starts transmitting electricity on it
 voltage on it all the other devices

0:16:20.860000 --> 0:16:25.680000
 see that they're privy to that so that
 was different right back in the

0:16:25.680000 --> 0:16:29.760000
 early internet it was just two devices
 connected to a cable and that was

0:16:29.760000 --> 0:16:36.080000
 it now with ethernet you've got the concept
 of three or four or five devices

0:16:36.080000 --> 0:16:39.480000
 could all be connected to that same
 cable and they could all see each

0:16:39.480000 --> 0:16:44.320000
 other so now we had another now we had
 a requirement that did not exist

0:16:44.320000 --> 0:16:50.460000
 previously you know previously with just
 two devices on a cable when device

0:16:50.460000 --> 0:16:55.120000
 A start fluctuating the electricity
 there's only one place it could go

0:16:55.120000 --> 0:16:59.660000
 device B device B new okay if I see
 some electricity coming in some ones

0:16:59.660000 --> 0:17:04.900000
 and zeros gotta be for me because there's
 only me and device A on the

0:17:04.900000 --> 0:17:08.380000
 cable nobody else it could be for so
 there was really no need for any

0:17:08.380000 --> 0:17:13.660000
 kind of addressing at layer two because
 it was point to point well now

0:17:13.660000 --> 0:17:17.360000
 with a broadcast domain with ethernet
 we do have the requirement for an

0:17:17.360000 --> 0:17:22.560000
 address because now we could potentially
 have 30 devices all seeing that

0:17:22.560000 --> 0:17:26.760000
 same electrical energy all being privy
 to these ones and zeros going across

0:17:26.760000 --> 0:17:31.400000
 the cable and now they need to know is
 that for me or can I safely ignore

0:17:31.400000 --> 0:17:36.620000
 it so that's why with ethernet they said
 okay we need to build in an address

0:17:36.620000 --> 0:17:40.400000
 called a MAC address a layer two address
 into ethernet so that when I

0:17:40.400000 --> 0:17:44.680000
 put stuff on the wire I can address it
 to a unique individual and so when

0:17:44.680000 --> 0:17:49.160000
 I see stuff coming on the wire I know
 if it's for me or if it's not for

0:17:49.160000 --> 0:17:54.600000
 me now also keep in mind that the original
 developers of ethernet and

0:17:54.600000 --> 0:18:00.360000
 token ring they said well you know ethernet
 and token ring there's there's

0:18:00.360000 --> 0:18:03.740000
 protocols out there right now that
 it could carry like ethernet might

0:18:03.740000 --> 0:18:09.380000
 be carrying IP behind it but maybe
 in the future someone will develop

0:18:09.380000 --> 0:18:13.720000
 other types of protocols we don't want
 to limit as a developer of ethernet

0:18:13.720000 --> 0:18:18.060000
 let's say I'm the designer of ethernet
 I don't want to limit or restrict

0:18:18.060000 --> 0:18:23.660000
 myself to where my ethernet protocol
 is only ever going to be able to

0:18:23.660000 --> 0:18:29.120000
 carry IP packets I want to design it
 so it's fluid so it's scalable so

0:18:29.120000 --> 0:18:33.240000
 that if anybody develops another protocol
 five ten fifteen years from

0:18:33.240000 --> 0:18:37.980000
 now my ethernet protocol which was developed
 way back in 1972 can carry

0:18:37.980000 --> 0:18:44.700000
 that new thing so this is why ethernet
 needed its own unique address you

0:18:44.700000 --> 0:18:47.660000
 know a lot of times when we think of
 ethernet logically in our minds we

0:18:47.660000 --> 0:18:52.180000
 think oh ethernet carries IP ethernet
 carries IP well that's true but

0:18:52.180000 --> 0:19:00.940000
 ethernet can carry hundreds of different
 protocols not just IP so the

0:19:00.940000 --> 0:19:04.540000
 desires of ethernet were to assume that
 a frame might carry non IP protocols

