WEBVTT

0:00:08.100000 --> 0:00:12.480000
 Okay, so now we have the
 concept of a device.

0:00:12.480000 --> 0:00:16.480000
 You can envision it being a server,
 a mainframe, whatever you want, but

0:00:16.480000 --> 0:00:22.500000
 we've got the concept of a networking
 device connecting to a cable.

0:00:22.500000 --> 0:00:26.080000
 And that networking device says, okay,
 I'm running the Ethernet protocol,

0:00:26.080000 --> 0:00:30.840000
 which means I'm not the
 only one on this cable.

0:00:30.840000 --> 0:00:36.460000
 There could be an unknown quantity of
 devices on this same cable as me.

0:00:36.460000 --> 0:00:40.000000
 I don't know. Before
 Ethernet, I did know.

0:00:40.000000 --> 0:00:43.980000
 Before Ethernet back in 1969, I just knew
 it was me and one other mainframe

0:00:43.980000 --> 0:00:47.320000
 and that's it. Well, we can't
 make that assumption anymore.

0:00:47.320000 --> 0:00:50.120000
 Now that this device is running Ethernet,
 he says, I'm in a broadcast

0:00:50.120000 --> 0:00:54.120000
 of Maine, it could be me and one other
 guy or could be me and 20 guys

0:00:54.120000 --> 0:00:56.940000
 on this cable. I just don't know.

0:00:56.940000 --> 0:01:00.720000
 So now the developers of Ethernet said,
 okay, well, so when I'm communicating

0:01:00.720000 --> 0:01:04.980000
 on this cable, as I communicate, I could
 do it in one of three different

0:01:04.980000 --> 0:01:10.000000
 ways. I could do a broadcast, which means
 as I'm putting my ones and zeros

0:01:10.000000 --> 0:01:12.840000
 on this cable, it's
 meant for everybody.

0:01:12.840000 --> 0:01:17.220000
 Now, in the case of a broadcast, really,
 we don't even need any kind of

0:01:17.220000 --> 0:01:19.000000
 an address, right?

0:01:19.000000 --> 0:01:21.980000
 I mean, if Ethernet had been developed,
 let's just imagine this.

0:01:21.980000 --> 0:01:27.860000
 If the developers of Ethernet had said,
 okay, any time anything goes into

0:01:27.860000 --> 0:01:32.300000
 an Ethernet frame, regardless of what
 it is, it's going to go to everybody.

0:01:32.300000 --> 0:01:34.580000
 It's just always going
 to be like that.

0:01:34.580000 --> 0:01:36.960000
 Then they would not have
 needed an address at all.

0:01:36.960000 --> 0:01:39.420000
 So there wouldn't
 be a need for it.

0:01:39.420000 --> 0:01:43.120000
 But clearly, that's not the way it
 works and that doesn't really make

0:01:43.120000 --> 0:01:44.580000
 sense to develop it that way.

0:01:44.580000 --> 0:01:46.900000
 So they said, okay, we
 could do broadcast.

0:01:46.900000 --> 0:01:48.680000
 There might be a need for that.

0:01:48.680000 --> 0:01:50.760000
 Or we could do unicast.

0:01:50.760000 --> 0:01:53.240000
 Maybe when someone's putting something
 in the wire, it's going to be meant

0:01:53.240000 --> 0:01:57.820000
 for one other device
 on that same wire.

0:01:57.820000 --> 0:02:01.760000
 So they said, okay, in that particular
 case, we need an address.

0:02:01.760000 --> 0:02:05.100000
 So when this data is being put on the
 wire, it needs to have a unique

0:02:05.100000 --> 0:02:09.760000
 source address of where it came from and
 it needs to have a unique destination

0:02:09.760000 --> 0:02:15.360000
 address of where it's going to.

0:02:15.360000 --> 0:02:19.200000
 And also keep in mind right here, now
 we've got devices that have two

0:02:19.200000 --> 0:02:20.680000
 addresses that they're using.

0:02:20.680000 --> 0:02:23.300000
 Because remember, IP came first.

0:02:23.300000 --> 0:02:26.780000
 So I've got this device connected to
 a network that for several years

0:02:26.780000 --> 0:02:31.180000
 has been utilizing this 32
-bit number, this IP number.

0:02:31.180000 --> 0:02:34.020000
 And the first eight bits
 have been the network.

0:02:34.020000 --> 0:02:38.620000
 The remaining 24 bits at the end have
 been my own unique host identifier.

0:02:38.620000 --> 0:02:43.420000
 Now, in addition to that, if I'm coupling
 Ethernet to IP, if I'm saying,

0:02:43.420000 --> 0:02:47.040000
 okay, well, layer two, you're now running
 Ethernet, now in addition to

0:02:47.040000 --> 0:02:52.180000
 an IP address, I have to also utilize
 a second address, a MAC address,

0:02:52.180000 --> 0:02:56.840000
 a layer two media access control address,
 which is what Ethernet uses.

0:02:56.840000 --> 0:03:01.420000
 So the developers of these addresses
 said, okay, we need to structure

0:03:01.420000 --> 0:03:12.040000
 the address in the 3 IP address and my
 layer two MAC address need to reflect

0:03:12.040000 --> 0:03:15.280000
 that. I need to come up with some kind
 of address that says this is for

0:03:15.280000 --> 0:03:17.060000
 everybody on this cable.

0:03:17.060000 --> 0:03:19.400000
 And I'll show you in just a
 second what that looks like.

0:03:19.400000 --> 0:03:24.000000
 Then they said, okay, what if I'm sending
 it directly to Bob's computer?

0:03:24.000000 --> 0:03:26.920000
 Bob's computer is on the same
 broadcast domain as me.

0:03:26.920000 --> 0:03:31.000000
 But once again, at layer three, I need
 to say in the world of IP, this

0:03:31.000000 --> 0:03:35.040000
 came from my IP address and it's
 going to Bob's IP address.

0:03:35.040000 --> 0:03:38.620000
 And at layer two in the world of Ethernet,
 I need to say it came from

0:03:38.620000 --> 0:03:42.660000
 my MAC address and it's going
 to Bob's MAC address.

0:03:42.660000 --> 0:03:47.080000
 And then the third form of communication
 was multicast.

0:03:47.080000 --> 0:03:51.160000
 Multicast is the concept where, okay,
 on this cable, this Ethernet broadcast

0:03:51.160000 --> 0:03:58.080000
 domain, let's say there's 100 devices,
 100 PCs and servers and stuff.

0:03:58.080000 --> 0:04:05.920000
 Now, I am going to start transmitting
 data on this cable and of the 99

0:04:05.920000 --> 0:04:14.620000
 devices on this cable in addition to me,
 maybe six of them need this information.

0:04:14.620000 --> 0:04:19.760000
 Well, broadcast is not appropriate because
 I don't want to go out to everybody.

0:04:19.760000 --> 0:04:21.420000
 And I could do unicast.

0:04:21.420000 --> 0:04:28.120000
 I could take this information, send
 one copy of it to Sally's unicast

0:04:28.120000 --> 0:04:32.680000
 address, copy it again and send another
 copy on the cable to Tom's unicast

0:04:32.680000 --> 0:04:36.800000
 address. But that would put a lot of
 burden on me to make multiple copies

0:04:36.800000 --> 0:04:39.980000
 of the same data and send it
 out there multiple times.

0:04:39.980000 --> 0:04:43.480000
 So they came up with a third alternative
 which is called multicast.

0:04:43.480000 --> 0:04:48.500000
 Multicast is the idea that just like
 unicast or broadcast, I'm putting

0:04:48.500000 --> 0:04:50.520000
 one copy of the data on the wire.

0:04:50.520000 --> 0:04:52.760000
 I'm just sending out once.

0:04:52.760000 --> 0:04:57.460000
 But at the layer three address and
 at the layer two address, it has a

0:04:57.460000 --> 0:05:00.980000
 special address that says this
 is going to a group of people.

0:05:00.980000 --> 0:05:02.800000
 It's not going to everybody.

0:05:02.800000 --> 0:05:04.800000
 It's not going to just one person.


0:05:04.800000 --> 0:05:07.680000
 It's going to a group of people.

0:05:07.680000 --> 0:05:11.500000
 Now, what's kind of interesting is
 that in the world of multicast, the

0:05:11.500000 --> 0:05:15.000000
 sender of the information, which is
 me, the one who's transmitting the

0:05:15.000000 --> 0:05:20.320000
 information, really doesn't know and
 doesn't care how many people are

0:05:20.320000 --> 0:05:23.980000
 in that group. It's sort of like
 broadcast in that regard.

0:05:23.980000 --> 0:05:27.660000
 When you put a broadcast on the wire,
 you don't know who's out there.

0:05:27.660000 --> 0:05:30.260000
 You don't know who's going to get it
 or how many people are going to get

0:05:30.260000 --> 0:05:31.300000
 it. You don't care.

0:05:31.300000 --> 0:05:34.920000
 You're just saying, hey everybody, whoever's
 out there, this is for everyone.

0:05:34.920000 --> 0:05:37.820000
 Multicast is kind of the same way where
 you're saying, okay, hey, I'm

0:05:37.820000 --> 0:05:39.660000
 putting some data on the wire.

0:05:39.660000 --> 0:05:43.900000
 If there are any interested
 individuals, here you go.

0:05:43.900000 --> 0:05:47.740000
 It's actually, in my example of the
 100 people on the wire where there's

0:05:47.740000 --> 0:05:53.860000
 six people who actually want this and
 the other people don't, I have to

0:05:53.860000 --> 0:05:58.320000
 use a special address at layer three
 and layer two called a multicast

0:05:58.320000 --> 0:06:01.100000
 address. It's formatted
 in a unique way.

0:06:01.100000 --> 0:06:06.200000
 It's still 32 bits at layer three and
 it's still 48 bits at layer two.

0:06:06.200000 --> 0:06:10.940000
 The structure of a multicast address
 is such a way that the receivers,

0:06:10.940000 --> 0:06:13.540000
 those six people are
 looking for it.

0:06:13.540000 --> 0:06:17.580000
 They're saying, okay, I'm looking as
 data comes in the wire, as I'm seeing

0:06:17.580000 --> 0:06:22.180000
 the electrical voltage going across,
 I'm saying, okay, well, see, I'm

0:06:22.180000 --> 0:06:27.740000
 running Ethernet, which tells me that
 60 bits into it is where I will

0:06:27.740000 --> 0:06:30.900000
 find the destination MAC address,
 who it's going to.

0:06:30.900000 --> 0:06:35.120000
 Now if I'm a unique individual, I will
 say, okay, well, if that destination

0:06:35.120000 --> 0:06:39.200000
 MAC address is broadcast,
 I've got to pick it up.

0:06:39.200000 --> 0:06:40.100000
 I have to look at it.

0:06:40.100000 --> 0:06:41.800000
 See if I'm interested.

0:06:41.800000 --> 0:06:47.020000
 If that destination address is mine,
 my own unicast address will clearly,

0:06:47.020000 --> 0:06:49.520000
 I have to pick that
 up and look at it.

0:06:49.520000 --> 0:06:51.920000
 But now I'm looking for
 a third type of address.

0:06:51.920000 --> 0:06:56.020000
 If that destination address is a special
 multicast address that I have

0:06:56.020000 --> 0:07:01.060000
 been told I need to look for, I
 will pick it up and process it.

0:07:01.060000 --> 0:07:06.540000
 So in the world of multicast, you've got
 this concept of senders and receivers.

0:07:06.540000 --> 0:07:10.740000
 You've got one sender who's sending
 one copy of the data and you've got

0:07:10.740000 --> 0:07:13.660000
 potentially multiple receivers.

0:07:13.660000 --> 0:07:18.780000
 And it's really the job of the receivers
 to somehow discover what that

0:07:18.780000 --> 0:07:22.440000
 special address is going to be and for
 them to start listening to that.

0:07:22.440000 --> 0:07:24.040000
 Now that's a whole
 different world.

0:07:24.040000 --> 0:07:26.820000
 We're not going to get into that today
 about, well, you know, how do the

0:07:26.820000 --> 0:07:29.400000
 receiver discover that special
 multicast address?

0:07:29.400000 --> 0:07:30.780000
 How do they know what to look for?


0:07:30.780000 --> 0:07:33.000000
 Well, there's various different
 ways to do that.

0:07:33.000000 --> 0:07:36.420000
 But the idea is what makes multicast
 different from broadcast is that

0:07:36.420000 --> 0:07:41.320000
 it's only a select group of people that's
 actually looking for that data.

0:07:41.320000 --> 0:07:44.340000
 In a broadcast domain, everybody's still
 going to see it because remember

0:07:44.340000 --> 0:07:47.520000
 in the broadcast domain, the concept
 is you put something in that wire

0:07:47.520000 --> 0:07:52.480000
 that electrical energy is seen
 by everyone on that wire.

0:07:52.480000 --> 0:07:56.720000
 The question is what people when they
 see that electrical energy are going

0:07:56.720000 --> 0:08:01.280000
 to ignore it, what people are going
 to process it and say this is for

0:08:01.280000 --> 0:08:05.020000
 me. And in the case of multicast,
 it's a group of people.

0:08:05.020000 --> 0:08:08.440000
 So now we've got this concept of devices
 having two addresses, a layer

0:08:08.440000 --> 0:08:12.600000
 three IP address and a
 layer two MAC address.

0:08:12.600000 --> 0:08:16.200000
 And now we know that those two addresses
 can be formatted in one of three

0:08:16.200000 --> 0:08:20.720000
 different ways as broadcast,
 unicast and multicast.

0:08:20.720000 --> 0:08:26.800000
 Now what comes to network software applications,
 as we can see here, they've

0:08:26.800000 --> 0:08:28.720000
 fallen into two different
 categories.

0:08:28.720000 --> 0:08:33.540000
 There's some network software that just
 makes the assumption, like ARP,

0:08:33.540000 --> 0:08:36.520000
 the address resolution protocol, that
 when you invoke the software, when

0:08:36.520000 --> 0:08:40.940000
 you tell it to start up, that software
 will say, okay, I am designed in

0:08:40.940000 --> 0:08:44.700000
 such a way that I am only going to
 talk to people in my own broadcast

0:08:44.700000 --> 0:08:47.940000
 domain. I don't even know about
 other broadcast domains.

0:08:47.940000 --> 0:08:49.260000
 I don't even know they exist.

0:08:49.260000 --> 0:08:52.040000
 I'm just going to talk to people
 in my broadcast domain.

0:08:52.040000 --> 0:08:56.520000
 So those types of software applications,
 technically, they don't even

0:08:56.520000 --> 0:09:00.080000
 need IP. All they really need is a
 layer two address if they're going

0:09:00.080000 --> 0:09:02.220000
 to talk in their own
 broadcast domain.

0:09:02.220000 --> 0:09:05.180000
 But most software falls into
 the second category.

0:09:05.180000 --> 0:09:12.360000
 Those capable of intra or inter
 broadcast domain communications.

0:09:12.360000 --> 0:09:18.360000
 So a common misconception when people
 are first starting to learn about

0:09:18.360000 --> 0:09:25.300000
 IP is they think, okay, well, an IP address
 then is equivalent to a broadcast

0:09:25.300000 --> 0:09:30.020000
 domain. I've got one cable here, and
 so that's going to be one network.

0:09:30.020000 --> 0:09:34.440000
 So that's going to need an IP address,
 going to need a network address.

0:09:34.440000 --> 0:09:37.700000
 And then I've got another cable over
 here in a different building.

0:09:37.700000 --> 0:09:39.360000
 That's a different
 broadcast domain.

0:09:39.360000 --> 0:09:41.860000
 So that's going to need
 a network address.

0:09:41.860000 --> 0:09:44.660000
 So people think, okay,
 they're equivalent.

0:09:44.660000 --> 0:09:48.340000
 IP address equals
 broadcast domain.

0:09:48.340000 --> 0:09:51.980000
 And that's not quite the case.

0:09:51.980000 --> 0:09:55.640000
 So as we see here, IP is
 used to address networks.

0:09:55.640000 --> 0:09:59.580000
 Those networks might take the form of
 a broadcast domain if they're using

0:09:59.580000 --> 0:10:04.340000
 ethernet or token ring, or they could
 be using some other protocol that

0:10:04.340000 --> 0:10:08.680000
 makes it a point to point
 network like HDLC or PPP.

0:10:08.680000 --> 0:10:15.160000
 The main idea is that whenever you have
 a cable and you expect IP packets

0:10:15.160000 --> 0:10:20.520000
 to go across that cable, either end of
 that cable needs to know that this

0:10:20.520000 --> 0:10:22.240000
 is part of a network.

0:10:22.240000 --> 0:10:27.180000
 We need an IP address to represent this
 network, whether it be point to

0:10:27.180000 --> 0:10:33.280000
 point or a broadcast domain, a
 collection of ethernet devices.

0:10:33.280000 --> 0:10:37.140000
 So an IP address, we know that the original
 developers of IP, they structured

0:10:37.140000 --> 0:10:40.800000
 it in such a way that
 had two parts to it.

0:10:40.800000 --> 0:10:44.460000
 The first 25% of that address, so I guess
 if you're looking at this, this

0:10:44.460000 --> 0:10:45.280000
 would be the left here.

0:10:45.280000 --> 0:10:49.240000
 The first 8 bits represent
 the network.

0:10:49.240000 --> 0:10:52.440000
 So let's just say if we're talking
 about ethernet, that represents the

0:10:52.440000 --> 0:10:53.480000
 broadcast domain.

0:10:53.480000 --> 0:10:57.580000
 Everybody on that ethernet segment
 has the same 8 bits in common.

0:10:57.580000 --> 0:11:01.620000
 They're part of the same group,
 okay, part of the same click.

0:11:01.620000 --> 0:11:07.140000
 And then the remaining 24 bits at the
 end are unique on every single host.

0:11:07.140000 --> 0:11:09.540000
 So if we're talking about a broadcast
 domain, if I'm talking about an

0:11:09.540000 --> 0:11:14.000000
 ethernet segment that's got 100 devices
 on it, because they're all part

0:11:14.000000 --> 0:11:17.040000
 of the same broadcast domain, they
 can all see each other's electrical

0:11:17.040000 --> 0:11:22.540000
 energy from a layer 3 perspective, from
 an IP perspective, it was originally

0:11:22.540000 --> 0:11:26.700000
 designed that they would all have
 the first 8 bits in common.

0:11:26.700000 --> 0:11:28.960000
 They'd all have the same 8 bits, they're
 all part of the same group.

0:11:28.960000 --> 0:11:32.820000
 But then of all those 100 devices, the
 remaining 24 bits would have unique

0:11:32.820000 --> 0:11:36.800000
 patterns. Each device would have its own
 unique what they call host address

0:11:36.800000 --> 0:11:43.980000
 or host bits. Okay, so we have devices
 that have two addresses, a layer

0:11:43.980000 --> 0:11:47.180000
 3 IP address and a
 layer 2 address.

0:11:47.180000 --> 0:11:50.360000
 Let's just say it's a MAC address.


0:11:50.360000 --> 0:11:56.160000
 And some application running way up
 here, you know, layer 7 of the OSI

0:11:56.160000 --> 0:12:00.500000
 model. So that application gets invoked
 and that application says, okay,

0:12:00.500000 --> 0:12:06.080000
 I need to hook into IP so I can actually
 get out of my chassis, get out

0:12:06.080000 --> 0:12:10.120000
 of my box and put some
 data on the wire.

0:12:10.120000 --> 0:12:20.180000
 Okay, well, we know that as far as layer
 2 is concerned, the MAC layer,

0:12:20.180000 --> 0:12:22.020000
 the data link layer, let's say.

0:12:22.020000 --> 0:12:27.500000
 We know that application has one fundamental
 question, it has to answer.

0:12:27.500000 --> 0:12:31.340000
 As far as networking is concerned,
 it has to answer the question, the

0:12:31.340000 --> 0:12:35.880000
 destination I'm trying to reach, the
 person I want to talk to, are they

0:12:35.880000 --> 0:12:41.880000
 on the same wire as me, are they the
 same broadcast domain, or are they

0:12:41.880000 --> 0:12:45.580000
 not? Are they in some other broadcast
 domain, meaning that when I put

0:12:45.580000 --> 0:12:49.260000
 my electrical energy on this wire, they
 can't see it because they're not

0:12:49.260000 --> 0:12:51.180000
 on this broadcast domain.

0:12:51.180000 --> 0:12:56.960000
 So every application that's network
 aware has to answer that question.

0:12:56.960000 --> 0:13:02.120000
 So if the application determines that,
 okay, the destination I'm trying

0:13:02.120000 --> 0:13:07.300000
 to reach is in my broadcast domain,
 I can talk to him directly, he will

0:13:07.300000 --> 0:13:11.820000
 see my electrical energy as soon as
 I start putting it on the wire.

0:13:11.820000 --> 0:13:15.580000
 Well, that application can't skip past
 IP, you might think, okay, well,

0:13:15.580000 --> 0:13:18.680000
 in that particular case, we
 don't need to use IP at all.

0:13:18.680000 --> 0:13:22.080000
 Let's just skip past it and just
 go straight to layer 2 addresses.

0:13:22.080000 --> 0:13:28.960000
 Can't do that. If a system like a laptop
 or a PC is running both IP and

0:13:28.960000 --> 0:13:32.140000
 Ethernet, you can't skip past IP.

0:13:32.140000 --> 0:13:34.940000
 So when you put your date on the wire,
 you're going to have an IP address

0:13:34.940000 --> 0:13:37.240000
 in there and a MAC address.

0:13:37.240000 --> 0:13:41.380000
 Now in this particular case, if the
 person I'm talking to is on my wire,

0:13:41.380000 --> 0:13:46.040000
 the IP address is kind of irrelevant
 because I'm talking to them directly

0:13:46.040000 --> 0:13:47.640000
 via their layer 2 address.

0:13:47.640000 --> 0:13:51.100000
 If they're on my wire and now I discover
 what their layer 2 address is,

0:13:51.100000 --> 0:13:56.020000
 so as I'm transmitting my bits at layer
 2, their nitcar can say, oh, this

0:13:56.020000 --> 0:13:59.860000
 is for me. There's other people
 seeing it, but this is for me.

0:13:59.860000 --> 0:14:04.260000
 And once my nitcar identifies that as
 a unicast transmission, it doesn't

0:14:04.260000 --> 0:14:07.980000
 really need to see the IP address, but we
 can't skip past it so the destination

0:14:07.980000 --> 0:14:10.660000
 IP address will be
 in there as well.

0:14:10.660000 --> 0:14:14.540000
 Now, let's say I'm trying to talk to
 somebody that's not on my wire, so

0:14:14.540000 --> 0:14:18.260000
 it's on a different
 broadcast domain.

0:14:18.260000 --> 0:14:19.700000
 Well, same thing.

0:14:19.700000 --> 0:14:23.800000
 When I put my data on the wire,
 I can't skip past layer 2.

0:14:23.800000 --> 0:14:27.180000
 Even though the person I'm trying to
 talk to technically can't see my

0:14:27.180000 --> 0:14:32.540000
 layer 2, they can't see my electrical
 energy, I can't just take data,

0:14:32.540000 --> 0:14:36.680000
 address it with the destination IP
 address of the person that's 5,000

0:14:36.680000 --> 0:14:41.180000
 miles away, and put on my cable because
 my cable says, well, wait a second,

0:14:41.180000 --> 0:14:42.940000
 I'm running a layer 2 protocol.

0:14:42.940000 --> 0:14:47.640000
 I'm running Ethernet and the rules
 of Ethernet state, I need a layer 2

0:14:47.640000 --> 0:14:52.120000
 address. So when you're talking to somebody
 that's not in the same broadcast

0:14:52.120000 --> 0:14:56.520000
 domain as you, you say, okay, well,
 what do I use as a layer 2 address

0:14:56.520000 --> 0:14:58.620000
 because they're not in the
 same broadcast domain?

0:14:58.620000 --> 0:15:01.800000
 And this is where the concept
 of a default gateway comes in.

0:15:01.800000 --> 0:15:06.600000
 A router. A router is someone is a device
 that should know not only the

0:15:06.600000 --> 0:15:11.180000
 broadcast domain he's connected to,
 which is the same one you are on,

0:15:11.180000 --> 0:15:14.540000
 but he should also know about
 other broadcast domains.

0:15:14.540000 --> 0:15:17.580000
 So he's like, you know,
 an intermediary device.

0:15:17.580000 --> 0:15:21.460000
 So in the case of that, if my application
 says, okay, let's see here,

0:15:21.460000 --> 0:15:25.860000
 the destination I need to talk to is
 not on my broadcast domain, it's

0:15:25.860000 --> 0:15:29.640000
 somewhere else. Then the destination
 says, okay, here's what I need to

0:15:29.640000 --> 0:15:35.460000
 do. At layer 3, I will source the data
 from my IP address from my unique

0:15:35.460000 --> 0:15:38.940000
 8-bit combination of my network.

0:15:38.940000 --> 0:15:44.560000
 And then at layer 3, I will put the destination
 IP address as the destination

0:15:44.560000 --> 0:15:50.660000
 I'm trying to reach, and he has a
 unique 8-bit combination of bits.

0:15:50.660000 --> 0:15:52.960000
 Then we send that down to layer 2.


0:15:52.960000 --> 0:15:58.760000
 At layer 2, I will put the source address
 as my own NIT cards MAC address,

0:15:58.760000 --> 0:16:00.380000
 my layer 2 address.

0:16:00.380000 --> 0:16:05.500000
 And the destination address will be, okay,
 well, who on my broadcast domain

0:16:05.500000 --> 0:16:09.660000
 can help me get this data
 to where it needs to go?

0:16:09.660000 --> 0:16:12.280000
 The router, the default gateway.

0:16:12.280000 --> 0:16:15.960000
 So at layer 2, the layer 2
 address will be the router.

0:16:15.960000 --> 0:16:18.520000
 And this is, for those of you who are
 studying for your CCN, this is a

0:16:18.520000 --> 0:16:22.840000
 foundational thing you need to be aware
 of, is that when you've got a

0:16:22.840000 --> 0:16:26.120000
 device running Ethernet and IP, whenever
 it puts data on the wire, you

0:16:26.120000 --> 0:16:30.000000
 will always see two addresses
 in that data.

0:16:30.000000 --> 0:16:34.240000
 You'll see a layer 2 MAC
 and a layer 3 IP address.

0:16:34.240000 --> 0:16:36.620000
 Both of them will be in there.

0:16:36.620000 --> 0:16:41.200000
 Now, the person you're trying to talk to
 is on your wire, is in your broadcast

0:16:41.200000 --> 0:16:45.520000
 domain. The destination layer 3 address
 will be the person you're trying

0:16:45.520000 --> 0:16:49.900000
 to talk to, and the destination layer
 2 address will be the person you're

0:16:49.900000 --> 0:16:50.520000
 trying to talk to.

0:16:50.520000 --> 0:16:53.040000
 It's being unicast
 directly to them.

0:16:53.040000 --> 0:16:57.160000
 But the person you're trying to talk
 to is in a remote broadcast domain,

0:16:57.160000 --> 0:17:03.540000
 which might be a dozen feet or 2,000 miles
 away, at layer 3 nothing changes.

0:17:03.540000 --> 0:17:07.720000
 At layer 3 it's still your source IP
 address going to their destination

0:17:07.720000 --> 0:17:10.980000
 IP address. What changes
 is layer 2.

0:17:10.980000 --> 0:17:15.200000
 At layer 2, because you can't talk to
 them directly, you use your source

0:17:15.200000 --> 0:17:21.340000
 MAC address, and you use your default gateways
 MAC address as the destination.

0:17:21.340000 --> 0:17:23.580000
 And the assumption is, okay, as I'm
 putting the electrical energy on the

0:17:23.580000 --> 0:17:27.000000
 wire, the default gateway will
 say, oh, that's for me.

0:17:27.000000 --> 0:17:28.980000
 I see my MAC address here.

0:17:28.980000 --> 0:17:32.480000
 And then when he gets that Ethernet
 frame and he removes it, and he goes

0:17:32.480000 --> 0:17:37.160000
 up to layer 3, that's when the router
 will say, ah, well, at layer 2 it

0:17:37.160000 --> 0:17:42.380000
 looked like this is a unicast transmission
 for me, but at layer 3 it's

0:17:42.380000 --> 0:17:46.680000
 not. At layer 3 it says, oh, the destination
 IP address is not one of

0:17:46.680000 --> 0:17:48.960000
 mine, it's somebody else's.

0:17:48.960000 --> 0:17:52.360000
 And now it's the router's job to forward
 that data into another broadcast

0:17:52.360000 --> 0:17:57.620000
 domain, and it'll hop through various
 broadcast domains until it reaches

0:17:57.620000 --> 0:18:04.580000
 the destination broadcast domain.

0:18:04.580000 --> 0:18:06.500000
 So this is what we're
 talking about here.

0:18:06.500000 --> 0:18:10.840000
 You know, on the top we've got one broadcast
 domain which is called LAN1,

0:18:10.840000 --> 0:18:14.700000
 and so, you know, in the original days
 of IP we reserved the first 8 bits

0:18:14.700000 --> 0:18:20.580000
 for that network, and so it might
 be, you know, 7 zeros and a 1.

0:18:20.580000 --> 0:18:25.540000
 On the bottom we have LAN2, a second
 broadcast domain, so that needs a

0:18:25.540000 --> 0:18:30.800000
 different unique group number, a
 different unique network number.

0:18:30.800000 --> 0:18:42.300000
 So how do computers and mainframes
 stuff actually see this?

0:18:42.300000 --> 0:18:46.800000
 So we know that a MAC address is in
 binary 48 bits long, so there's 48

0:18:46.800000 --> 0:18:48.860000
 bits right there.

0:18:48.860000 --> 0:18:54.840000
 An IP address, a little bit
 shorter, 32 bits long.

0:18:54.840000 --> 0:18:57.640000
 So what does a computer see when
 it looks at incoming data?

0:18:57.640000 --> 0:18:59.940000
 I'll go ahead and expand this
 a little bit for you here.

0:18:59.940000 --> 0:19:05.700000
 So there's the source on the right,
 sending data to the destination on

0:19:05.700000 --> 0:19:14.840000
 the left. What's coming in is just a
 string of thousands of 1's and 0's.

0:19:14.840000 --> 0:19:16.960000
 So where are these addresses
 and all this?

0:19:16.960000 --> 0:19:22.540000
 Well, if that destination device is
 running the Ethernet protocol, he's

0:19:22.540000 --> 0:19:27.720000
 going to say, okay, the first 64 bits
 that I saw coming in is a bunch

0:19:27.720000 --> 0:19:28.900000
 of Ethernet stuff.

0:19:28.900000 --> 0:19:33.780000
 Basically what we
 call the preamble.

0:19:33.780000 --> 0:19:41.060000
 Then from bits 65 to bit 112, that's
 the destination MAC address.

0:19:41.060000 --> 0:19:49.020000
 And then bits 113 through 160
 are the source MAC address.

0:19:49.020000 --> 0:19:54.100000
 Now hopefully nobody will ever actually
 ask you to do this, but if someone

0:19:54.100000 --> 0:19:58.220000
 said, hey, I'm going to give you a
 piece of paper that's got 2000 bits

0:19:58.220000 --> 0:19:59.740000
 in binary written on it.

0:19:59.740000 --> 0:20:03.880000
 Can you tell me what the destination
 MAC address is in this long string

0:20:03.880000 --> 0:20:06.180000
 of bits? This is how you do it.

0:20:06.180000 --> 0:20:09.940000
 You'd say, okay, well, if this thing is
 Ethernet and it means that somewhere

0:20:09.940000 --> 0:20:14.680000
 in here is a MAC address, you would
 look right at bit 65 and go from 65

0:20:14.680000 --> 0:20:18.720000
 to 112. And that would be
 your destination MAC.

0:20:18.720000 --> 0:20:22.860000
 And then 113 to 160 would
 be your source MAC.

0:20:22.860000 --> 0:20:26.820000
 And then Ethernet says, okay, I've got
 another 16 bits of Ethernet stuff

0:20:26.820000 --> 0:20:32.820000
 and I'm done. So as far as Ethernet
 is concerned, all of that is layer

0:20:32.820000 --> 0:20:38.260000
 1 and layer 2. So that's layer 2
 stuff that Ethernet interprets.

0:20:38.260000 --> 0:20:44.020000
 Then once Ethernet is done, it removes
 all of that stuff, sends it up

0:20:44.020000 --> 0:20:55.160000
 to layer 3. By looking right here, this
 is what IP version 4c says, okay,

0:20:55.160000 --> 0:21:00.300000
 the first 96 bits are IP stuff.

0:21:00.300000 --> 0:21:06.460000
 So if you ever do a Google search on
 an IPv4 header, you'll see that IPv4

0:21:06.460000 --> 0:21:09.740000
 actually has a lot of bits it needs
 to look at before it ever gets to

0:21:09.740000 --> 0:21:15.340000
 any address. It has like an IP version
 field, IP header length, whole

0:21:15.340000 --> 0:21:20.500000
 bunch of stuff. So it's 96 bits
 of stuff that IP looks at.

0:21:20.500000 --> 0:21:29.620000
 And then at bit number 273, that's
 where we see our source IP address.

0:21:29.620000 --> 0:21:33.880000
 And because an IP address is 32 bits
 long, that goes from bit 273 to bit

0:21:33.880000 --> 0:21:40.500000
 304. And then from bit 305 to 336
 is the destination IP address.

0:21:40.500000 --> 0:21:45.040000
 And then there's more bits beyond this
 that are other IP stuff like IP

0:21:45.040000 --> 0:21:49.260000
 options. And then you're going to have
 a whole string of bits after that,

0:21:49.260000 --> 0:21:51.680000
 which is what TCP looks at.

0:21:51.680000 --> 0:21:55.280000
 And then you're going to have a whole
 string of bits after that for, you

0:21:55.280000 --> 0:22:00.100000
 know, what FTP looks at
 or telnet looks like.

0:22:00.100000 --> 0:22:06.060000
 So really, a simple packet of like telnet
 or email is going to be thousands

0:22:06.060000 --> 0:22:11.600000
 of bits long. But within the first few
 hundred bits is where you're going

0:22:11.600000 --> 0:22:16.400000
 to see your Mac addresses and
 your IP addresses encoded.

0:22:16.400000 --> 0:22:18.280000
 So that's what your computer sees.


