WEBVTT

0:00:08.400000 --> 0:00:12.700000
 So now that we've seen that the IPv6
 address itself has been changed,

0:00:12.700000 --> 0:00:16.800000
 it's much larger, and it's now represented
 in hexadecimal, let's see what

0:00:16.800000 --> 0:00:19.880000
 other things about
 IPv6 they modified.

0:00:19.880000 --> 0:00:25.140000
 So I'm going to zoom in on this.

0:00:25.140000 --> 0:00:29.640000
 So down up here we have our IP version
 4 header that we've already looked

0:00:29.640000 --> 0:00:33.400000
 at. And we talked about all these things,
 the version, IP header length,

0:00:33.400000 --> 0:00:35.800000
 identification, flags,
 and fragment offset.

0:00:35.800000 --> 0:00:37.140000
 We've looked at all that.

0:00:37.140000 --> 0:00:39.940000
 So now look at the IPv6 header.

0:00:39.940000 --> 0:00:42.840000
 And we can see there's some things
 that are the same, and some things

0:00:42.840000 --> 0:00:44.900000
 are different. First of
 all, what's the same?

0:00:44.900000 --> 0:00:47.040000
 Well, there's a version
 field in there.

0:00:47.040000 --> 0:00:51.100000
 Of course, in IP version 4, this had
 the number 4 in it, and now this

0:00:51.100000 --> 0:00:53.080000
 has the number 6 in it.

0:00:53.080000 --> 0:00:56.140000
 Okay, what else is similar?

0:00:56.140000 --> 0:00:59.180000
 Well, we certainly
 have the addresses.

0:00:59.180000 --> 0:01:07.600000
 Everything else is either
 gone, new, or renamed.

0:01:07.600000 --> 0:01:09.560000
 So let's look at each
 of these things.

0:01:09.560000 --> 0:01:11.700000
 First of all, traffic class.

0:01:11.700000 --> 0:01:15.700000
 This is the exact same thing
 as the type of service field.

0:01:15.700000 --> 0:01:16.620000
 They just renamed it.

0:01:16.620000 --> 0:01:21.560000
 Still the same size is used to identify
 the priority of a packet.

0:01:21.560000 --> 0:01:24.920000
 It's just now called
 traffic class.

0:01:24.920000 --> 0:01:30.760000
 And total length here, same
 thing as payload length.

0:01:30.760000 --> 0:01:33.400000
 So nothing's different about that.


0:01:33.400000 --> 0:01:39.020000
 The next header field is the same
 thing as the protocol field.

0:01:39.020000 --> 0:01:40.600000
 They just renamed it.

0:01:40.600000 --> 0:01:42.520000
 So here's a review question.

0:01:42.520000 --> 0:01:47.640000
 In IP version 4, what number would be
 in the protocol field if this IPv4

0:01:47.640000 --> 0:01:51.560000
 packet was carrying a
 TCP segment behind it?

0:01:51.560000 --> 0:01:54.960000
 That would be the number 6, right?


0:01:54.960000 --> 0:01:56.620000
 Because TCP was 6.

0:01:56.620000 --> 0:01:58.480000
 Well, that's what we'd have
 right here as well.

0:01:58.480000 --> 0:02:01.980000
 The number 6. What number would be
 in this field if it was carrying a

0:02:01.980000 --> 0:02:04.980000
 UDP datagram behind it?

0:02:04.980000 --> 0:02:06.400000
 That would be the number 17.

0:02:06.400000 --> 0:02:09.820000
 17 would be in here.

0:02:09.820000 --> 0:02:11.960000
 So the numbers are the same.

0:02:11.960000 --> 0:02:14.340000
 Just the name of the
 field is different.

0:02:14.340000 --> 0:02:21.740000
 And the time to live right here,
 that's just renamed hop limit.

0:02:21.740000 --> 0:02:25.340000
 Same exact functionality,
 just a different name.

0:02:25.340000 --> 0:02:29.720000
 Now, there is something that's
 brand new, flow label.

0:02:29.720000 --> 0:02:32.920000
 This is something that's
 new in IPv6.

0:02:32.920000 --> 0:02:36.740000
 The idea behind the flow label, and
 honestly, I'm not sure as of right

0:02:36.740000 --> 0:02:42.280000
 now 2016, how many operating systems
 actually make use of this field,

0:02:42.280000 --> 0:02:48.360000
 but the theory was that every unique
 flow of traffic from your laptop

0:02:48.360000 --> 0:02:50.300000
 would have a unique flow label.

0:02:50.300000 --> 0:02:53.780000
 In other words, if I have my internet
 browser open, I've got a tab open

0:02:53.780000 --> 0:02:59.960000
 to iini.com. All the packets from my
 laptop going to iini.com would have

0:02:59.960000 --> 0:03:01.260000
 a unique flow label.

0:03:01.260000 --> 0:03:06.220000
 If I open up a second tab going to google
.com, well, that's another different

0:03:06.220000 --> 0:03:10.340000
 unique flow. So my operating system would
 put a different number in there

0:03:10.340000 --> 0:03:11.620000
 in the flow label.

0:03:11.620000 --> 0:03:16.560000
 And the idea was this just gives us
 one more ability to track packets

0:03:16.560000 --> 0:03:18.780000
 that we didn't have before.

0:03:18.780000 --> 0:03:22.000000
 Now, I don't know if anybody actually
 uses that, but that's what the flow

0:03:22.000000 --> 0:03:27.260000
 label is for. Now, notice that there are
 several things that are conspicuously

0:03:27.260000 --> 0:03:29.380000
 absent from the IPv6 header.

0:03:29.380000 --> 0:03:33.900000
 For example, the IP
 header length field.

0:03:33.900000 --> 0:03:38.040000
 That's gone. Well, the reason why the
 IP header length field was necessary

0:03:38.040000 --> 0:03:41.720000
 in IP version 4 was because
 of the presence of options.

0:03:41.720000 --> 0:03:44.820000
 There may be options, there
 may not be options.

0:03:44.820000 --> 0:03:47.780000
 If there were options, who knows
 how many there could be.

0:03:47.780000 --> 0:03:51.900000
 So the size of this header was
 variable based on the options.

0:03:51.900000 --> 0:03:54.000000
 Well, the options don't
 exist anymore.

0:03:54.000000 --> 0:03:55.280000
 They're not in here.

0:03:55.280000 --> 0:03:58.020000
 So I shouldn't say they don't exist,
 but they're no longer considered

0:03:58.020000 --> 0:04:01.400000
 part of the IPv6 header.

0:04:01.400000 --> 0:04:05.880000
 So now anything that would be an option
 has been given its own unique

0:04:05.880000 --> 0:04:09.300000
 number, and it will show up here
 in the next header field.

0:04:09.300000 --> 0:04:16.320000
 So basically what you're looking at is
 if this is my v6 header, and let's

0:04:16.320000 --> 0:04:24.740000
 say I have two options, and then
 I have my TCP header after that.

0:04:24.740000 --> 0:04:26.200000
 Oops, that doesn't look very good.


0:04:26.200000 --> 0:04:29.280000
 I'll just leave a little TCP.

0:04:29.280000 --> 0:04:34.560000
 Okay, well, this option here, whatever
 it might be, will have a certain

0:04:34.560000 --> 0:04:39.220000
 number. Let's say that this
 is option number 50.

0:04:39.220000 --> 0:04:45.540000
 So in the next header field, right
 here, we would have the number 50,

0:04:45.540000 --> 0:04:47.560000
 which tells us that that's next.

0:04:47.560000 --> 0:04:52.800000
 Now, just like the IPv6 header has a
 next header field, each one of these,

0:04:52.800000 --> 0:04:54.800000
 these are called extension
 headers.

0:04:54.800000 --> 0:04:57.860000
 They also have next header fields.


0:04:57.860000 --> 0:05:03.780000
 So if the second option was option number
 five, we'd see the number five

0:05:03.780000 --> 0:05:07.480000
 here. This option would say, okay,
 after you're done with me, the next

0:05:07.480000 --> 0:05:09.240000
 header will be number five.

0:05:09.240000 --> 0:05:14.500000
 And then in this one right here, you
 would see six, saying the next thing

0:05:14.500000 --> 0:05:17.060000
 after me is TCP.

0:05:17.060000 --> 0:05:22.260000
 So the initial IPv6 header itself
 is always the exact same size.

0:05:22.260000 --> 0:05:26.500000
 And the next header field indicates
 what's coming next.

0:05:26.500000 --> 0:05:31.860000
 Is it an option coming next or is
 it TCP, UDP, or something else?

0:05:31.860000 --> 0:05:35.460000
 And then we've got all
 of these right here.

0:05:35.460000 --> 0:05:39.220000
 These have now been given their
 own additional header.

0:05:39.220000 --> 0:05:42.840000
 I'm not sure what the number is,
 but there's a next header field.

0:05:42.840000 --> 0:05:46.700000
 There's a next header number that says,
 which you're going to see next

0:05:46.700000 --> 0:05:50.360000
 is fragmentation, identification
 flags and fragment offsets.

0:05:50.360000 --> 0:05:56.260000
 So if a packet is fragmented, there
 will be something else inserted here

0:05:56.260000 --> 0:05:59.640000
 after the destination address and whatever
 that number is for containing

0:05:59.640000 --> 0:06:02.360000
 these three fields will
 be put right here.

0:06:02.360000 --> 0:06:06.120000
 I don't know what it is and you're
 never going to be tested on that.

0:06:06.120000 --> 0:06:10.680000
 And header checksum is missing.

0:06:10.680000 --> 0:06:12.460000
 If you recall, what is a checksum?


0:06:12.460000 --> 0:06:16.160000
 A checksum was a way of detecting if there
 were errors in something, detecting

0:06:16.160000 --> 0:06:21.140000
 if when I receive a stream of bits, if
 those bits have been changed since

0:06:21.140000 --> 0:06:23.000000
 they left the originator.

0:06:23.000000 --> 0:06:26.540000
 Well, the designers of IPv6,
 they said, you know what?

0:06:26.540000 --> 0:06:31.200000
 Most data link layer protocols, most
 layer two protocols already have

0:06:31.200000 --> 0:06:33.060000
 checksums in place.

0:06:33.060000 --> 0:06:37.160000
 And UDP and TCP have
 checksums in place.

0:06:37.160000 --> 0:06:40.840000
 So why do we need to do
 it again at layer three?

0:06:40.840000 --> 0:06:42.760000
 That seems like kind of overkill.

0:06:42.760000 --> 0:06:45.160000
 So they got rid of it.

0:06:45.160000 --> 0:06:49.440000
 And the last thing I want to talk about
 is a term that you'll hear frequently

0:06:49.440000 --> 0:06:51.760000
 called dual stack.

0:06:51.760000 --> 0:06:53.480000
 What is dual stack?

0:06:53.480000 --> 0:06:59.360000
 Right now, as people are still migrating
 to IPv6, you're not really going

0:06:59.360000 --> 0:07:03.240000
 to find networks and say, oh, okay, let's
 strip off all of our IPv4 addresses

0:07:03.240000 --> 0:07:05.620000
 and replace it with IPv6.

0:07:05.620000 --> 0:07:07.780000
 Most people don't move
 in that direction.

0:07:07.780000 --> 0:07:11.660000
 What they do is they take a device like
 a web server or an email server

0:07:11.660000 --> 0:07:17.680000
 that's currently running IPv4 and they
 add IPv6 on top of it so that device

0:07:17.680000 --> 0:07:19.000000
 can actually do both.

0:07:19.000000 --> 0:07:23.040000
 It'll have an IPv4 address on its net
 card, and it'll also have an IPv6

0:07:23.040000 --> 0:07:25.200000
 address on its net card.

0:07:25.200000 --> 0:07:30.920000
 When a device has both v4 and v6,
 we call it a dual stacked device.

0:07:30.920000 --> 0:07:33.980000
 So whenever you see that term dual
 stack, now you know, oh, that means

0:07:33.980000 --> 0:07:37.120000
 it's running IPv4 and IPv6.

