WEBVTT

0:00:08.440000 --> 0:00:14.300000
 Within the ICND1 blueprint under the general
 bullet point of network fundamentals,

0:00:14.300000 --> 0:00:16.840000
 they include a section on IPv6.

0:00:16.840000 --> 0:00:21.000000
 This is the place where they want
 to first introduce you to IPv6.

0:00:21.000000 --> 0:00:23.880000
 These next several videos are going
 to be snippets of me talking about

0:00:23.880000 --> 0:00:26.200000
 various aspects of IPv6.

0:00:26.200000 --> 0:00:29.920000
 We're not actually going to get
 into the configuration of IPv6.

0:00:29.920000 --> 0:00:32.960000
 First of all, I have to go through basic
 iOS command lines before we even

0:00:32.960000 --> 0:00:34.160000
 think about that.

0:00:34.160000 --> 0:00:37.660000
 But I just want to introduce IPv6
 from a theoretical perspective.

0:00:37.660000 --> 0:00:41.780000
 So this is the first video in
 that series introducing IPv6.

0:00:41.780000 --> 0:00:45.460000
 So let's first talk a little bit
 about the history of IPv6.

0:00:45.460000 --> 0:00:54.680000
 We know that IPv4 was actually first
 developed back with RFC 791 in 1981.

0:00:54.680000 --> 0:01:00.900000
 I think it was 1981 or 1982 when
 IPv4 was first developed.

0:01:00.900000 --> 0:01:05.000000
 And initially at the very, very beginning
 stages, it was only developed

0:01:05.000000 --> 0:01:10.320000
 for institutions like colleges and universities
 that were experimenting

0:01:10.320000 --> 0:01:16.100000
 with IPv4. This idea of an internet
 was not even envisioned back then.

0:01:16.100000 --> 0:01:21.380000
 But as more and more people started
 connecting to the IPv4 backbone and

0:01:21.380000 --> 0:01:26.300000
 using it, and it began expanding from
 just research to communications

0:01:26.300000 --> 0:01:32.100000
 and gaming, this idea of IPv4 addresses
 became more and more and more

0:01:32.100000 --> 0:01:41.600000
 popular. So by 1992, there was an impending
 shortage of IPv4 address space.

0:01:41.600000 --> 0:01:46.300000
 I should say that in 1992 they recognized
 that, uh-oh, the way things

0:01:46.300000 --> 0:01:51.940000
 are going with how quickly IPv4 addresses
 are starting to be consumed,

0:01:51.940000 --> 0:01:55.840000
 we recognized that at some point
 there's going to be a shortage.

0:01:55.840000 --> 0:01:59.660000
 Now there was not a shortage back in
 1992, but that's when they first

0:01:59.660000 --> 0:02:02.360000
 recognized this is going
 to be a problem.

0:02:02.360000 --> 0:02:06.280000
 At some point in the future, if things
 keep going the way they're going,

0:02:06.280000 --> 0:02:10.200000
 we are going to run
 out of IPv4 subnets.

0:02:10.200000 --> 0:02:11.320000
 Now was that actually mean?

0:02:11.320000 --> 0:02:15.700000
 Well that means that whenever that point
 is, if somebody develops a new

0:02:15.700000 --> 0:02:19.640000
 company and they want to connect to the
 internet, we're not going to have

0:02:19.640000 --> 0:02:21.140000
 a subnet to give to them.

0:02:21.140000 --> 0:02:24.260000
 We're not going to, if there's an existing
 company that expands and they

0:02:24.260000 --> 0:02:27.500000
 add a new campus, we're not going to
 have any addresses that we can give

0:02:27.500000 --> 0:02:30.180000
 to them because they
 will all be gone.

0:02:30.180000 --> 0:02:35.460000
 So they recognized back in 1992
 that this was an inevitability.

0:02:35.460000 --> 0:02:40.780000
 So two years later, the internet engineering
 task force launched their

0:02:40.780000 --> 0:02:46.260000
 work into a new version
 of IP, IP version 6.

0:02:46.260000 --> 0:02:53.280000
 So IP version 6, the initial motivator
 for it was let's restructure the

0:02:53.280000 --> 0:02:56.340000
 address. Let's make
 the address bigger.

0:02:56.340000 --> 0:03:00.760000
 You know with 32 bits, there's billions
 of combinations of addresses with

0:03:00.760000 --> 0:03:03.400000
 32 bits with an IP
 version 4 address.

0:03:03.400000 --> 0:03:07.060000
 And you might think, wow, with that
 many combinations, how could we ever

0:03:07.060000 --> 0:03:11.420000
 run out? Well here we are in 2016 and
 we actually are starting to run

0:03:11.420000 --> 0:03:15.440000
 out in certain parts of the world,
 even with billions of addresses.

0:03:15.440000 --> 0:03:23.240000
 So the IETF decided let's redo the internet
 protocol version 6 of it and

0:03:23.240000 --> 0:03:28.440000
 let's make the address space much bigger
 so that it'll hopefully never

0:03:28.440000 --> 0:03:29.680000
 run out of addresses.

0:03:29.680000 --> 0:03:33.480000
 So that was the initial motivator
 of revising IP.

0:03:33.480000 --> 0:03:36.220000
 But then while they were at it,
 they thought, you know what?

0:03:36.220000 --> 0:03:40.860000
 Since we're redoing IP, why don't we
 take this opportunity because who

0:03:40.860000 --> 0:03:44.540000
 knows when we'll have this opportunity
 again to change some other things

0:03:44.540000 --> 0:03:48.300000
 about the internet protocol as well,
 not just making the address space

0:03:48.300000 --> 0:03:50.640000
 bigger but changing some
 other things as well.

0:03:50.640000 --> 0:03:53.460000
 And another video coming up, I'll show
 you the differences between the

0:03:53.460000 --> 0:03:57.740000
 IP version 4 header that we've looked
 at already and the IP version 6

0:03:57.740000 --> 0:04:07.580000
 header. So in 1998, RFC 2460, which
 was the first RFC document for IPV6

0:04:07.580000 --> 0:04:12.280000
 was written. Now let's put things
 in perspective here a little bit.

0:04:12.280000 --> 0:04:18.880000
 Remember I told you that when IP first
 came out in 1981 or 82, there was

0:04:18.880000 --> 0:04:20.720000
 no such things as subnet mask.

0:04:20.720000 --> 0:04:24.620000
 It was purely class A,
 class B and class C.

0:04:24.620000 --> 0:04:28.640000
 So the idea of a subnet mask
 actually came out in 1985.

0:04:28.640000 --> 0:04:30.900000
 So that was RFC 950.

0:04:30.900000 --> 0:04:33.500000
 No one's going to ever expect
 you to memorize this stuff.

0:04:33.500000 --> 0:04:36.500000
 None of these dates are going
 to be on the ICND1 exam.

0:04:36.500000 --> 0:04:39.860000
 I just want to sort of prep you and
 get your mind thinking about why did

0:04:39.860000 --> 0:04:41.640000
 they create this thing
 in the first place?

0:04:41.640000 --> 0:04:44.740000
 What problem was it
 designed to solve?

0:04:44.740000 --> 0:04:52.340000
 So IP 1991, subnet masks added to IP
 in 1985 and then seven years later

0:04:52.340000 --> 0:04:55.840000
 they recognize uh oh, we can see a future
 where things are going to start

0:04:55.840000 --> 0:05:02.720000
 running out. So 1998, they wrote the
 actual first document for IPV6.

0:05:02.720000 --> 0:05:08.860000
 Then in 2006, so it took eight years,
 you can see this from 98 to 2006,

0:05:08.860000 --> 0:05:15.420000
 it took eight years for IPV6 address
 spacing to really stabilize.

0:05:15.420000 --> 0:05:18.040000
 In other words, there was a lot of back
 and forth about well, addresses

0:05:18.040000 --> 0:05:19.060000
 should look like this.

0:05:19.060000 --> 0:05:20.600000
 Well, these addresses
 should be used.

0:05:20.600000 --> 0:05:22.400000
 No, these addresses should
 be kept private.

0:05:22.400000 --> 0:05:24.440000
 No, we should keep these
 addresses in reserve.

0:05:24.440000 --> 0:05:26.220000
 Oh no, we should look at the bits
 a little bit differently.

0:05:26.220000 --> 0:05:31.300000
 So it took eight years for them to finally
 settle down and stabilize on

0:05:31.300000 --> 0:05:35.300000
 what the IPV6 address structure would
 actually look like and how it would

0:05:35.300000 --> 0:05:38.480000
 be used. And that was RFC 4291.

0:05:38.480000 --> 0:05:45.880000
 Back in 2008, so now we're talking about
 eight years ago before this recording

0:05:45.880000 --> 0:05:51.480000
 was made, the United States federal government
 mandated that all backbone

0:05:51.480000 --> 0:05:53.540000
 devices running on
 federal agencies.

0:05:53.540000 --> 0:05:58.300000
 So for example, all the routers and
 devices that were owned by the CIA,

0:05:58.300000 --> 0:06:03.600000
 the FBI, the Social Security Administration,
 all federal government agencies,

0:06:03.600000 --> 0:06:04.600000
 they're backbone routers.

0:06:04.600000 --> 0:06:06.460000
 And what would we mean
 by backbone routers?

0:06:06.460000 --> 0:06:09.220000
 I know that I haven't talked
 about that term yet.

0:06:09.220000 --> 0:06:14.520000
 So in the structure of a network, we've
 talked about, I did talk about

0:06:14.520000 --> 0:06:18.420000
 earlier in a previous video about the
 three layer design model, the access

0:06:18.420000 --> 0:06:21.840000
 layer, which is what gives access to
 the network devices like your laptops

0:06:21.840000 --> 0:06:26.300000
 and your tablets, and then the distribution
 layer and then the core layer.

0:06:26.300000 --> 0:06:30.100000
 So what we're really talking about here
 is routers that would fit in that

0:06:30.100000 --> 0:06:33.880000
 core layer that would actually transmit
 traffic back and forth between

0:06:33.880000 --> 0:06:38.700000
 agencies. So there would be a router owned
 by the FBI that would be connected

0:06:38.700000 --> 0:06:42.020000
 to a router owned by the CIA that would
 be connected to a router owned

0:06:42.020000 --> 0:06:44.200000
 by the Social Security
 Administration.

0:06:44.200000 --> 0:06:46.040000
 And those would be considered
 backbone routers.

0:06:46.040000 --> 0:06:50.640000
 They formed the backbone of the federal
 governments and how they communicate

0:06:50.640000 --> 0:06:54.880000
 to each other. So back in 2008, the
 US federal government said that all

0:06:54.880000 --> 0:06:58.840000
 of those devices have
 to be IPv6 capable.

0:06:58.840000 --> 0:07:02.960000
 Now get that. They didn't say we have
 to configure IPv6 on those devices

0:07:02.960000 --> 0:07:08.320000
 and run IPv6. They just said whatever
 hardware and software is on those

0:07:08.320000 --> 0:07:12.200000
 devices has to support IPv6.

0:07:12.200000 --> 0:07:16.540000
 So back in 2008, there was a lot of
 purchasing going on to get some new

0:07:16.540000 --> 0:07:19.700000
 software and new equipment to make
 sure that that requirement would be

0:07:19.700000 --> 0:07:27.740000
 met. Now just last year in September
 of 2015, the American Registry of

0:07:27.740000 --> 0:07:32.380000
 Internet Numbers, the regional Internet
 Registry that supports North America,

0:07:32.380000 --> 0:07:35.320000
 ran out of IPv4 addresses.

0:07:35.320000 --> 0:07:38.240000
 So remember when I was first talking
 about IP addressing, I was saying,

0:07:38.240000 --> 0:07:42.060000
 well, sometimes you could just skip your
 service provider and go directly

0:07:42.060000 --> 0:07:46.500000
 to your regional Internet Registry and
 get provider independent addressing.

0:07:46.500000 --> 0:07:49.060000
 Can't do that with Aaron anymore.

0:07:49.060000 --> 0:07:52.880000
 They actually have a few addresses they've
 held in reserve for very special

0:07:52.880000 --> 0:07:57.500000
 use cases, but it's next to impossible
 for you to justify getting those.

0:07:57.500000 --> 0:08:01.380000
 So Aaron has basically run out
 of IP version 4 addresses.

0:08:01.380000 --> 0:08:05.300000
 So here in the United States and Canada,
 at this point, all the service

0:08:05.300000 --> 0:08:09.180000
 providers have gobbled up whatever remaining
 IP version 4 addresses are

0:08:09.180000 --> 0:08:13.860000
 left and there's none at any
 tiers higher than them.

0:08:13.860000 --> 0:08:15.540000
 So that's where we are today.

0:08:15.540000 --> 0:08:19.240000
 And I was just looking at some Internet
 statistics before I record this

0:08:19.240000 --> 0:08:24.880000
 video. And it's actually surprising
 me because about 15 years ago or so,

0:08:24.880000 --> 0:08:29.720000
 so around 2000, so this was right around
 when the first RFC for IPv6 was

0:08:29.720000 --> 0:08:32.220000
 written, everybody was pretty
 much laughing it off.

0:08:32.220000 --> 0:08:35.260000
 They said, ah, we're never going to
 run out of IP version 4 addresses.

0:08:35.260000 --> 0:08:38.080000
 This thing's too much work,
 too hard to understand.

0:08:38.080000 --> 0:08:39.640000
 We're not going to deal with it.

0:08:39.640000 --> 0:08:43.540000
 So for the longest time, year after
 year after year, people were pushing

0:08:43.540000 --> 0:08:48.880000
 back on IPv6 saying, oh, it's going
 to be decades before it's used.

0:08:48.880000 --> 0:08:54.760000
 And they were saying, oh, I think as
 early as like 2012 or 2013, not that

0:08:54.760000 --> 0:08:58.180000
 long ago, IPv6 traffic
 on the Internet.

0:08:58.180000 --> 0:09:01.800000
 So if you take a look at all the traffic
 running across the Internet globally,

0:09:01.800000 --> 0:09:05.540000
 at that point in time, like two, three
 years ago, IPv6 traffic was like

0:09:05.540000 --> 0:09:08.880000
 1%. Maybe not even 1%.

0:09:08.880000 --> 0:09:10.280000
 It was so small.

0:09:10.280000 --> 0:09:15.040000
 Well, I just looked at some statistics
 online that now say that IPv6 traffic

0:09:15.040000 --> 0:09:18.040000
 running across the Internet
 is as high as 20%.

0:09:18.040000 --> 0:09:19.720000
 Think about that.

0:09:19.720000 --> 0:09:23.680000
 One out of every five packets that's going
 across the Internet now globally

0:09:23.680000 --> 0:09:25.800000
 is an IPv6 packet.

0:09:25.800000 --> 0:09:28.720000
 It is ramping up really,
 really quickly.

0:09:28.720000 --> 0:09:31.640000
 So if you're going to go into the networking
 fields, an engineer or an

0:09:31.640000 --> 0:09:35.920000
 admin, you can no longer
 afford to ignore IPv6.

0:09:35.920000 --> 0:09:37.760000
 It will be a part of your life.

0:09:37.760000 --> 0:09:39.980000
 It is here. It is now.

0:09:39.980000 --> 0:09:42.160000
 So that being the case.

0:09:42.160000 --> 0:09:45.000000
 Also, I found this website right here,
 which I thought was kind of interesting

0:09:45.000000 --> 0:09:46.420000
 that I wanted to share with you.

0:09:46.420000 --> 0:09:48.940000
 This is IPv6.com.

0:09:48.940000 --> 0:09:49.960000
 You could go there.

0:09:49.960000 --> 0:09:54.820000
 And if you scroll down a little bit, this
 is under the history and timeline.

0:09:54.820000 --> 0:09:55.920000
 And shows you right here.

0:09:55.920000 --> 0:09:57.280000
 Look at this chart right
 in the middle.

0:09:57.280000 --> 0:10:03.860000
 So this shows how the address
 depletion of IPv4 went.

0:10:03.860000 --> 0:10:07.180000
 So back in 1985.

0:10:07.180000 --> 0:10:12.420000
 So this is just like three or four years
 after IPv6 was invented, already

0:10:12.420000 --> 0:10:17.300000
 1-16 of the total address space of those
 billions of addresses were already

0:10:17.300000 --> 0:10:24.600000
 consumed. And then in 2015, 16 years
 ago, half of the address space was

0:10:24.600000 --> 0:10:29.100000
 used. And then in that same year, 2000,
 two thirds of the address space,

0:10:29.100000 --> 0:10:31.220000
 actually, halfway through 2002.

0:10:31.220000 --> 0:10:32.720000
 And now here we are in 2016.

0:10:32.720000 --> 0:10:37.420000
 You can imagine it's virtually
 gone at this point.

0:10:37.420000 --> 0:10:42.080000
 So I found that to be a pretty
 interesting document there.

0:10:42.080000 --> 0:10:47.820000
 So now we have an idea as
 to why IPv6 was needed.

0:10:47.820000 --> 0:10:50.060000
 It was because they were
 running out of addresses.

0:10:50.060000 --> 0:10:55.380000
 Okay. So what does an IPv6
 address look like?

0:10:55.380000 --> 0:11:00.840000
 The main change with IPv6 is that the
 address is four times as big as

0:11:00.840000 --> 0:11:02.480000
 an IPv4 address.

0:11:02.480000 --> 0:11:07.960000
 Instead of 32 bits, it is
 now 128 bits in size.

0:11:07.960000 --> 0:11:14.320000
 So that would be like
 an IPv6 address.

0:11:14.320000 --> 0:11:16.160000
 Now I didn't actually
 count those bits.

0:11:16.160000 --> 0:11:18.760000
 I'm not exactly sure
 if that's 128 or not.

0:11:18.760000 --> 0:11:22.480000
 But in binary, it's a massively
 large number.

0:11:22.480000 --> 0:11:27.480000
 As a matter of fact, I heard someone
 say a long time ago that if you think

0:11:27.480000 --> 0:11:31.480000
 of two to the power of 128, that's
 how many combinations of addresses

0:11:31.480000 --> 0:11:34.480000
 there are. I don't think there's
 even a name for that.

0:11:34.480000 --> 0:11:39.020000
 Somebody has said that there were so
 many IPv6 addresses available that

0:11:39.020000 --> 0:11:44.540000
 every person could have a unique IPv6
 address for every single hair on

0:11:44.540000 --> 0:11:49.720000
 their head. And there would still
 be an infinite amount left over.

0:11:49.720000 --> 0:11:53.920000
 So hopefully, unless we expand throughout
 the galaxy like Star Trek and

0:11:53.920000 --> 0:11:59.080000
 populate distant planets, we'll be
 with IPv6 for a long, long time.

0:11:59.080000 --> 0:12:04.760000
 So we know that in IPv4, that binary
 number was divided into octets into

0:12:04.760000 --> 0:12:09.440000
 bytes. We had four bytes, and then each
 byte was converted into a decimal

0:12:09.440000 --> 0:12:12.780000
 number, and then separated
 by a dot.

0:12:12.780000 --> 0:12:14.260000
 So that was dotted decimal.

0:12:14.260000 --> 0:12:19.140000
 They could have done that with this,
 but they chose a different approach.

0:12:19.140000 --> 0:12:24.980000
 They chose to represent these
 as hexadecimal numbers.

0:12:24.980000 --> 0:12:26.760000
 Hexadecimal, that's right.

0:12:26.760000 --> 0:12:30.500000
 I know we haven't talked about hexadecimal
 yet, so now I need to do a

0:12:30.500000 --> 0:12:33.400000
 quick primer on hexadecimal.

0:12:33.400000 --> 0:12:35.860000
 It's actually not that hard.

0:12:35.860000 --> 0:12:39.060000
 I hope it will not be
 that hard for you.

0:12:39.060000 --> 0:12:44.760000
 So remember, let's go back to our binary
 tutorial and our decimal tutorial.

0:12:44.760000 --> 0:12:50.640000
 Remember how we said that you have
 a single placeholder, and how many

0:12:50.640000 --> 0:12:55.060000
 potential digits could go in there depends
 on what numbering system you're

0:12:55.060000 --> 0:13:00.100000
 using. If you're using base 10 decimal,
 that means you have 10 possible

0:13:00.100000 --> 0:13:04.060000
 things that could go in here, from
 a zero through a nine, base 10.

0:13:04.060000 --> 0:13:08.400000
 If you're using binary, it was base two,
 which means you had two possible

0:13:08.400000 --> 0:13:11.520000
 combinations, a zero, or a one.

0:13:11.520000 --> 0:13:20.200000
 Well, hexadecimal is
 a base 16 system.

0:13:20.200000 --> 0:13:24.580000
 What? I know, it's so weird, but
 actually it's a base 16 system.

0:13:24.580000 --> 0:13:28.800000
 So in this one placeholder, you have
 16 possible things that could go

0:13:28.800000 --> 0:13:32.000000
 in there. What could
 those possibly be?

0:13:32.000000 --> 0:13:36.860000
 Well, let me make my font
 here a little bit smaller.

0:13:36.860000 --> 0:13:43.220000
 The first 10 digits in hexadecimal
 are exactly the same as in decimal.

0:13:43.220000 --> 0:13:47.880000
 You have zero through nine.

0:13:47.880000 --> 0:13:52.540000
 So that covers the first 10 out
 of my 16 possible characters.

0:13:52.540000 --> 0:13:54.320000
 That's no different.

0:13:54.320000 --> 0:13:57.660000
 And then for the remaining
 characters, we use letters.

0:13:57.660000 --> 0:14:02.460000
 So A is the equivalent
 of 10 in decimal.

0:14:02.460000 --> 0:14:05.140000
 B is the equivalent of 11.

0:14:05.140000 --> 0:14:07.900000
 C is the equivalent of 12.

0:14:07.900000 --> 0:14:09.900000
 D, I'm running out of space here.

0:14:09.900000 --> 0:14:11.800000
 All right, hold on a second.

0:14:11.800000 --> 0:14:20.080000
 Okay, so we have zero
 through nine.

0:14:20.080000 --> 0:14:23.740000
 And then we have our letters.

0:14:23.740000 --> 0:14:35.280000
 A equals 10, B equals 11, C equals 12,
 D equals 13, E equals 14, and lastly,

0:14:35.280000 --> 0:14:42.420000
 F equals 15. So that gives us our 16
 possible characters from zero to

0:14:42.420000 --> 0:14:47.000000
 F. That's 16 possible
 combinations.

0:14:47.000000 --> 0:14:53.540000
 And also remember, when we were talking
 about decimal, if I had a three

0:14:53.540000 --> 0:14:58.300000
-digit number, the first position
 was always the one's position.

0:14:58.300000 --> 0:15:03.460000
 And then depending on what base system
 we were using, to determine what

0:15:03.460000 --> 0:15:04.480000
 the next one was.

0:15:04.480000 --> 0:15:07.160000
 So in decimal, we just kept
 multiplying by tens.

0:15:07.160000 --> 0:15:11.380000
 So we had the tens position next, 10
 times 10 is 100, so on and so forth.

0:15:11.380000 --> 0:15:14.080000
 With binary, it is
 multiplying by two.

0:15:14.080000 --> 0:15:16.960000
 So we had the ones, and then
 we had the two's position.

0:15:16.960000 --> 0:15:20.520000
 Two times two is four, four
 times two is eight.

0:15:20.520000 --> 0:15:22.660000
 Well, you can probably see
 where I'm going with this.

0:15:22.660000 --> 0:15:26.800000
 With hexadecimal, we
 multiply by 16s.

0:15:26.800000 --> 0:15:32.500000
 So we have the ones position, and then
 the next one is the 16s position,

0:15:32.500000 --> 0:15:36.860000
 and 16 times 16 is the 256s.

0:15:36.860000 --> 0:15:39.160000
 And after that, I can't
 do it from memory.

0:15:39.160000 --> 0:15:41.380000
 I can only do three positions.

0:15:41.380000 --> 0:15:45.560000
 So the way we had, and so with the way
 a hexadecimal number would look,

0:15:45.560000 --> 0:15:48.080000
 they're not always represented this
 way, but if you ever see a number

0:15:48.080000 --> 0:15:54.240000
 that says zero x something, that's
 representing a hexadecimal number.

0:15:54.240000 --> 0:16:03.040000
 So for example, zero x, zero, zero,
 three, well, that's just the number

0:16:03.040000 --> 0:16:05.340000
 three. It's no different
 than in decimal.

0:16:05.340000 --> 0:16:12.000000
 But if I say zero x, zero, zero, a,
 that's the number 10 in hexadecimal.

0:16:12.000000 --> 0:16:18.200000
 Or I could say, and usually the
 leading zeros are left off.

0:16:18.200000 --> 0:16:20.740000
 So if I was going to give you the hexadecimal
 number of 10, I would just

0:16:20.740000 --> 0:16:27.400000
 say zero x a. There's only one character,
 so that one character has to

0:16:27.400000 --> 0:16:28.860000
 be in the ones position.

0:16:28.860000 --> 0:16:31.560000
 So that's 10 times
 one, which is 10.

0:16:31.560000 --> 0:16:37.960000
 Or I could say zero x one b.

0:16:37.960000 --> 0:16:44.540000
 Well, that means I've got a b in the
 ones position and a one in the 16s

0:16:44.540000 --> 0:16:49.360000
 position. So that's 16 plus 11.

0:16:49.360000 --> 0:16:58.040000
 That's 27. Zero x one
 b is 27 in decimal.

0:16:58.040000 --> 0:17:07.400000
 Or I could go zero x one a three.

0:17:07.400000 --> 0:17:08.880000
 That's going to be a
 pretty big number.

0:17:08.880000 --> 0:17:12.660000
 So that means I have a three
 in the ones position.

0:17:12.660000 --> 0:17:19.400000
 I have a a, which is 10 in the 16s position,
 and I have a one in the 256s.

0:17:19.400000 --> 0:17:31.260000
 So that would be 256 plus 160, because
 10 times 16 is 160 plus three.

0:17:31.260000 --> 0:17:34.240000
 I'm not going to add that up in my
 head, but whatever number that is,

0:17:34.240000 --> 0:17:39.700000
 that would be the decimal equivalent
 of zero x one a three.

0:17:39.700000 --> 0:17:44.100000
 So how does this relate
 to an IPv6 address?

0:17:44.100000 --> 0:17:54.980000
 All right, so let me actually
 write a real IPv6 address.

0:17:54.980000 --> 0:18:01.100000
 So that's one. Two.

0:18:01.100000 --> 0:18:08.300000
 Three. Four. I'm not going
 to do the whole thing.

0:18:08.300000 --> 0:18:10.500000
 I'm just going to do some of it.

0:18:10.500000 --> 0:18:18.640000
 Okay, so in reality, an actual IPv6
 address would have eight of these

0:18:18.640000 --> 0:18:22.780000
 things. I've drawn one, two,
 three, four, I've drawn five.

0:18:22.780000 --> 0:18:26.720000
 So still a little bit leftover, but
 not going to worry about that right

0:18:26.720000 --> 0:18:31.660000
 now. So how do we actually convert this
 into a number that we can read?

0:18:31.660000 --> 0:18:36.600000
 Well, what you would do is starting
 from left to right, you would take

0:18:36.600000 --> 0:18:43.300000
 every four binary characters and convert
 that into a hex character.

0:18:43.300000 --> 0:18:48.060000
 So that is in decimal, that's
 the number two, right?

0:18:48.060000 --> 0:18:52.160000
 The ones is off, the two is on, the
 four is off, and the eight is off.

0:18:52.160000 --> 0:18:53.760000
 So that's the number two.

0:18:53.760000 --> 0:18:57.340000
 And then we do it again
 with the next one.

0:18:57.340000 --> 0:19:01.200000
 The next four, that's pretty easy.


0:19:01.200000 --> 0:19:03.000000
 That's just the number zero.

0:19:03.000000 --> 0:19:06.200000
 And then we do it again
 with the next four.

0:19:06.200000 --> 0:19:12.160000
 So we've got the ones position turned
 on and the eights position turned

0:19:12.160000 --> 0:19:14.100000
 on. So that's nine.

0:19:14.100000 --> 0:19:16.600000
 And then we do it one more time.

0:19:16.600000 --> 0:19:22.120000
 Now in decimal, we've got
 the eight and the four.

0:19:22.120000 --> 0:19:23.920000
 So that's the number 12.

0:19:23.920000 --> 0:19:29.320000
 But in hexadecimal, we
 don't say 12, we say C.

0:19:29.320000 --> 0:19:37.440000
 So so far, I've represented 16 bits
 in binary by using four hexadecimal

0:19:37.440000 --> 0:19:39.840000
 characters. And here's
 why that's important.

0:19:39.840000 --> 0:19:47.100000
 After every 16 binary bits, or after
 every four hexadecimal characters,

0:19:47.100000 --> 0:19:51.440000
 we put a colon and then we repeat.


0:19:51.440000 --> 0:19:53.880000
 So this will be zero.

0:19:53.880000 --> 0:20:00.820000
 This will be F. I got to
 put a box around here.

0:20:00.820000 --> 0:20:04.780000
 Zero. So this one here is F because
 that's the number 15.

0:20:04.780000 --> 0:20:10.180000
 This one right here, we're back
 to the number 12 again.

0:20:10.180000 --> 0:20:12.880000
 No, that's the number 10 actually,
 the eight and the two.

0:20:12.880000 --> 0:20:14.660000
 So that would be an A.

0:20:14.660000 --> 0:20:17.600000
 And then this here is a two.

0:20:17.600000 --> 0:20:20.440000
 And then we put a colon.

0:20:20.440000 --> 0:20:29.280000
 So an IPv6 address, because we clearly
 don't represent it in binary, is

0:20:29.280000 --> 0:20:31.620000
 represented as hexadecimal.

0:20:31.620000 --> 0:20:34.560000
 So this is what an IPv6 address
 would actually look like.

0:20:34.560000 --> 0:20:38.100000
 I can actually fit
 this one in here.

0:20:38.100000 --> 0:20:39.680000
 I'm just going to make up one.

0:20:39.680000 --> 0:20:45.980000
 Two zero zero one colon zero zero A
 five colon zero zero zero zero colon

0:20:45.980000 --> 0:20:51.640000
 five five E a colon
 BBB colon CCC colon.

0:20:51.640000 --> 0:20:53.480000
 Now there's going to
 be eight of these.

0:20:53.480000 --> 0:20:57.160000
 One, two, three, four, five,
 six, one one one one.

0:20:57.160000 --> 0:21:02.720000
 That's seven zero
 zero zero zero C.

0:21:02.720000 --> 0:21:05.540000
 So that is an IPv6 address.

0:21:05.540000 --> 0:21:10.020000
 And if we actually did the math, you'd
 see that this is 128 bits in binary.

0:21:10.020000 --> 0:21:13.920000
 Each one of these characters
 represents four bits.

0:21:13.920000 --> 0:21:16.520000
 Remember, here's the two, there's
 four bits for that.

0:21:16.520000 --> 0:21:18.700000
 Here's a zero, that's
 four bits for that.

0:21:18.700000 --> 0:21:24.380000
 So if you count up all of these characters
 multiplied times four, that

0:21:24.380000 --> 0:21:27.680000
 would give you 128 bits in binary.


0:21:27.680000 --> 0:21:31.080000
 So that's how an IPv6 address
 is represented.

0:21:31.080000 --> 0:21:36.000000
 You have four hexadecimal characters,
 a colon, and then repeat.

0:21:36.000000 --> 0:21:41.280000
 And you'll have a maximum of eight
 of these groupings right here.

0:21:41.280000 --> 0:21:46.820000
 Actually, I've heard, you know how
 we say, I'll write this on here.

0:21:46.820000 --> 0:21:53.620000
 You know how we say that eight, so
 that one unit, I'll just say equals

0:21:53.620000 --> 0:21:59.940000
 a bit. And eight bits
 equals a byte.

0:21:59.940000 --> 0:22:06.820000
 Well, 16 bits equals
 what's called a word.

0:22:06.820000 --> 0:22:11.860000
 So this is a word.

0:22:11.860000 --> 0:22:15.520000
 So you have a colon
 after every word.

0:22:15.520000 --> 0:22:20.920000
 All right, let's go back to here.

0:22:20.920000 --> 0:22:24.860000
 Expressed in hexadecimal
 instead of decimal.

0:22:24.860000 --> 0:22:29.240000
 Four bits equals one hexadecimal
 character.

0:22:29.240000 --> 0:22:30.460000
 And there's an example.

0:22:30.460000 --> 0:22:36.000000
 Now before I stop, there are ways,
 if the IPv6 address takes a certain

0:22:36.000000 --> 0:22:40.980000
 format, there are ways to make it
 shorter, make it more manageable.

0:22:40.980000 --> 0:22:44.940000
 And I'm going to teach you what
 those two tricks are to do that.

0:22:44.940000 --> 0:22:51.520000
 And it all has to do with
 consecutive zeros.

0:22:51.520000 --> 0:22:55.300000
 What you're looking for in an IPv6 address
 to make it shorter are consecutive

0:22:55.300000 --> 0:22:59.360000
 zeros. So let me give you
 an IPv6 address, 2001.

0:22:59.360000 --> 0:23:01.880000
 And I'm going to put
 some spaces in here.

0:23:01.880000 --> 0:23:12.100000
 One, two, three, four,
 five, six, seven.

0:23:12.100000 --> 0:23:17.100000
 Okay, so here is the format
 for making this shorter.

0:23:17.100000 --> 0:23:21.720000
 So the first thing you would look for
 in a long address like this is I

0:23:21.720000 --> 0:23:24.860000
 would look for a long string
 of contiguous zeros.

0:23:24.860000 --> 0:23:29.000000
 And what I mean by that is, look at the
 address and ask yourself, is there

0:23:29.000000 --> 0:23:32.680000
 any word? I remember what
 do I mean by a word?

0:23:32.680000 --> 0:23:36.680000
 This is a word, this is
 a word, that's a word.

0:23:36.680000 --> 0:23:40.360000
 Okay, so you look at your IPv6 address
 and you say, is there any word

0:23:40.360000 --> 0:23:43.040000
 that begins with a zero?

0:23:43.040000 --> 0:23:44.800000
 I'll just put some arrows
 on the ones that do.

0:23:44.800000 --> 0:23:50.740000
 Yep, that one does, that one does,
 that one does, that one does, that

0:23:50.740000 --> 0:23:54.660000
 one does. Okay, next.

0:23:54.660000 --> 0:23:59.780000
 Is there any place in this IPv6 address
 where we have a long contiguous

0:23:59.780000 --> 0:24:04.300000
 string of zeros where it starts
 at a word and keeps on going?

0:24:04.300000 --> 0:24:06.360000
 Well, actually we do.

0:24:06.360000 --> 0:24:08.980000
 We have a couple places
 in here like that.

0:24:08.980000 --> 0:24:12.860000
 Here's one that starts at
 a word and keeps on going.

0:24:12.860000 --> 0:24:18.040000
 Here's one that starts at
 a word and keeps on going.

0:24:18.040000 --> 0:24:23.220000
 Now, when you look at that, each one
 of those things can be condensed

0:24:23.220000 --> 0:24:28.620000
 down by using a special character
 which is the double colon.

0:24:28.620000 --> 0:24:32.380000
 But here's the rule about
 the double colon.

0:24:32.380000 --> 0:24:37.220000
 It can only be used once
 in an IPv6 address.

0:24:37.220000 --> 0:24:40.520000
 Let me give you the logic
 behind why that's true.

0:24:40.520000 --> 0:24:42.440000
 Let's say theoretically that
 I could use it twice.

0:24:42.440000 --> 0:24:55.440000
 Let's say I could do this, 2001 and then
 colon colon 30 colon eaf 0 colon

0:24:55.440000 --> 0:25:02.760000
 and then we'll just say
 colon colon 2004.

0:25:02.760000 --> 0:25:06.520000
 Let's say theoretically that I could
 type in an IPv6 address like this

0:25:06.520000 --> 0:25:11.380000
 on my laptop. Now remember, when you're
 entering an IPv6 address into

0:25:11.380000 --> 0:25:16.280000
 a system, that system is expecting
 you to give it 128 bits.

0:25:16.280000 --> 0:25:18.960000
 Now it knows that you're
 typing it in hexadecimal.

0:25:18.960000 --> 0:25:22.860000
 But for every letter or every character
 you type in, it's saying, okay,

0:25:22.860000 --> 0:25:23.820000
 there's four bits.

0:25:23.820000 --> 0:25:24.860000
 There's another four bits.

0:25:24.860000 --> 0:25:26.740000
 It's converting it into binary.

0:25:26.740000 --> 0:25:31.200000
 So if I typed it in like this, here's
 how my system would interpret this.

0:25:31.200000 --> 0:25:38.860000
 It would say, okay, what we've got
 here is we've got one, two, three,

0:25:38.860000 --> 0:25:40.700000
 four. So this is very easy.

0:25:40.700000 --> 0:25:45.320000
 The human being has provided
 us all 16 bits of that word.

0:25:45.320000 --> 0:25:48.780000
 All right. And then
 we've got one, two.

0:25:48.780000 --> 0:25:52.360000
 All right. So we've got
 eight bits of that word.

0:25:52.360000 --> 0:25:54.140000
 We're missing some stuff.

0:25:54.140000 --> 0:25:58.100000
 And then here we've got
 another 16 bits of that.

0:25:58.100000 --> 0:26:05.120000
 And then down here, we've got another
 16 bits supplied to us.

0:26:05.120000 --> 0:26:07.940000
 Okay. Now the system
 would say, hmm.

0:26:07.940000 --> 0:26:09.640000
 Okay. Let me add this up here.

0:26:09.640000 --> 0:26:15.340000
 16 times three is 48
 plus eight is 56.

0:26:15.340000 --> 0:26:27.560000
 So my laptop would say, this idiotic
 human has only given me 56 bits of

0:26:27.560000 --> 0:26:33.740000
 an address that requires 128 bits.


0:26:33.740000 --> 0:26:37.800000
 And so the system would say, all right,
 I guess I can assume that the

0:26:37.800000 --> 0:26:40.500000
 remaining bits that are
 left over are zeros.

0:26:40.500000 --> 0:26:43.820000
 But okay. So how many bits
 are left over here?

0:26:43.820000 --> 0:26:45.700000
 I don't have my calculator
 in front of me.

0:26:45.700000 --> 0:26:49.240000
 So let's just do this real quick here
 because I can't do that in my head

0:26:49.240000 --> 0:26:55.240000
 quickly enough. So
 128 minus 56 is 72.

0:26:55.240000 --> 0:26:57.460000
 So there's 72 bits missing.

0:26:57.460000 --> 0:27:02.720000
 So what if the system said, all right,
 I'm going to put maybe 70 zeros

0:27:02.720000 --> 0:27:04.580000
 here and two zeros here.

0:27:04.580000 --> 0:27:09.580000
 Or maybe I should split up equally
 36 zeros here and 36 zeros here.

0:27:09.580000 --> 0:27:14.160000
 You can see that if it actually allowed
 you to put in double colons, there's

0:27:14.160000 --> 0:27:18.140000
 no way it could figure out where
 these zeros were supposed to be.

0:27:18.140000 --> 0:27:20.180000
 It just could not figure that out.


0:27:20.180000 --> 0:27:24.320000
 That's why we can only put
 in the double colons once.

0:27:24.320000 --> 0:27:29.340000
 And so when selecting it, it makes
 sense to only put the double colons

0:27:29.340000 --> 0:27:32.520000
 to represent the biggest string
 of contiguous zeros.

0:27:32.520000 --> 0:27:36.280000
 If I'm trying to shorten this thing down,
 it makes more sense to represent

0:27:36.280000 --> 0:27:40.940000
 this big long thing with a double colon
 than it does to represent this.

0:27:40.940000 --> 0:27:43.980000
 So let's shorten it down
 a little bit right now.

0:27:43.980000 --> 0:27:52.720000
 So 2001, 000, 000, 000,
 000, 30, eaf, zero.

0:27:52.720000 --> 0:27:58.720000
 And then I'm going to do a double
 colon to represent that, 2004.

0:27:58.720000 --> 0:28:01.280000
 So so far, I've been able
 to shorten it to this.

0:28:01.280000 --> 0:28:05.300000
 I'll put it all together.

0:28:05.300000 --> 0:28:11.540000
 So already, you can see that this
 is much shorter than this.

0:28:11.540000 --> 0:28:15.820000
 Just by taking this long contiguous
 string of zeros and condensing it

0:28:15.820000 --> 0:28:17.020000
 down with a double colon.

0:28:17.020000 --> 0:28:19.160000
 Now I'm going to emphasize this.

0:28:19.160000 --> 0:28:24.020000
 I had to start with a word that began
 with a zero because you might be

0:28:24.020000 --> 0:28:26.260000
 wondering, well, why didn't
 I start right here?

0:28:26.260000 --> 0:28:28.500000
 Because that's not considered
 a leading zero.

0:28:28.500000 --> 0:28:29.920000
 That is a trailing zero.

0:28:29.920000 --> 0:28:33.160000
 It trails at the tail
 end of the word.

0:28:33.160000 --> 0:28:38.620000
 I need a zero that leads the word and
 then a string of zeros after that.

0:28:38.620000 --> 0:28:41.920000
 That's why I had to
 start right here.

0:28:41.920000 --> 0:28:43.100000
 So that's one thing.

0:28:43.100000 --> 0:28:47.480000
 A long contiguous string of zeros that
 starts with a word can be replaced

0:28:47.480000 --> 0:28:49.300000
 with a double colon.

0:28:49.300000 --> 0:28:51.220000
 There's one other thing.

0:28:51.220000 --> 0:28:56.500000
 After you have what's left, look and
 ask yourself, do I have any remaining

0:28:56.500000 --> 0:29:00.800000
 words that still start
 with a zero?

0:29:00.800000 --> 0:29:04.020000
 Well, yep, that one
 starts with a zero.

0:29:04.020000 --> 0:29:06.140000
 That one starts with a zero.

0:29:06.140000 --> 0:29:15.640000
 So in those words, we can get rid
 of all of the leading zeros.

0:29:15.640000 --> 0:29:17.360000
 So I'm going to put
 a line through them.

0:29:17.360000 --> 0:29:20.940000
 Those three zeros in that
 word, we can get rid of.

0:29:20.940000 --> 0:29:23.900000
 Can't get rid of the zero at the end
 because that's a trailing zero.

0:29:23.900000 --> 0:29:28.360000
 And we can get rid of these two zeros
 because these are leading zeros.

0:29:28.360000 --> 0:29:33.620000
 So in its final form and its shortest
 form I could possibly come up with.

0:29:33.620000 --> 0:29:41.740000
 So I've now taken it from this black
 down all the way to this one here

0:29:41.740000 --> 0:29:48.320000
 in green. And that is the shortest way
 I could condense an IPv6 address.

0:29:48.320000 --> 0:29:53.360000
 Let me give you a couple that you can
 pause the video on and practice.

0:29:53.360000 --> 0:29:55.160000
 And see if you can get it right.

0:29:55.160000 --> 0:29:57.600000
 You might want to pause right now and
 take a screenshot of this before

0:29:57.600000 --> 0:30:01.180000
 I move on to the next one.

0:30:01.180000 --> 0:30:16.100000
 Go ahead and pause the video.

0:30:16.100000 --> 0:30:19.620000
 Try to abbreviate or condense this
 as much as possible using the rules

0:30:19.620000 --> 0:30:23.260000
 I just talked about and then press
 play when you think you've got your

0:30:23.260000 --> 0:30:30.000000
 answer. Okay, so doing the way I did,
 I would say once again, look for

0:30:30.000000 --> 0:30:33.540000
 any word that begins with a zero.

0:30:33.540000 --> 0:30:37.620000
 That one does. That one does.

0:30:37.620000 --> 0:30:41.640000
 That one does. That one does.

0:30:41.640000 --> 0:30:47.640000
 At that point, look for a long contiguous
 string of zeros beginning with

0:30:47.640000 --> 0:30:51.660000
 a word. And this is the longest
 string we have right there.

0:30:51.660000 --> 0:30:55.740000
 So I can get rid of that
 with my double colon.

0:30:55.740000 --> 0:31:01.860000
 And then with what's left over, draw
 a line through any of the leading

0:31:01.860000 --> 0:31:03.800000
 zeros of any of the
 remaining words.

0:31:03.800000 --> 0:31:07.860000
 So I can get rid of those
 three and that's it.

0:31:07.860000 --> 0:31:13.440000
 So the smallest I could make this
 address would be 200 E colon zero.

0:31:13.440000 --> 0:31:15.400000
 I'll leave in that trailing zero.

0:31:15.400000 --> 0:31:19.160000
 4000 can't get rid of any of those zeros
 behind the four because they're

0:31:19.160000 --> 0:31:20.960000
 not leading. They're trailing.

0:31:20.960000 --> 0:31:32.640000
 600 EADE1100. So that is the smallest
 that you could do that one.

0:31:32.640000 --> 0:31:51.500000
 Let's do one more.

0:31:51.500000 --> 0:31:55.440000
 Okay, go ahead and press pause and
 try to condense this one down.

0:31:55.440000 --> 0:32:02.340000
 Okay, so once again, let's take a look
 at any words that begin with a

0:32:02.340000 --> 0:32:05.340000
 zero. That one does.

0:32:05.340000 --> 0:32:13.440000
 That one does. Actually, let
 me do the entire word.

0:32:13.440000 --> 0:32:17.360000
 That one does. That one
 leads with zeros.

0:32:17.360000 --> 0:32:18.940000
 That one leads with zeros.

0:32:18.940000 --> 0:32:20.660000
 And this one leads with zeros.

0:32:20.660000 --> 0:32:26.620000
 Okay, so of this, where am I
 continuous string of zeros?

0:32:26.620000 --> 0:32:28.800000
 Well, I've got one that
 starts right here.

0:32:28.800000 --> 0:32:31.800000
 The ends there, so that
 cover is seven zeros.

0:32:31.800000 --> 0:32:39.440000
 Here's one that has just two zeros,
 another two, and then four.

0:32:39.440000 --> 0:32:44.180000
 So I would say the seven zeros would
 be the best way to get rid of those.

0:32:44.180000 --> 0:32:47.940000
 And then I'm going to put a line
 through the remaining ones.

0:32:47.940000 --> 0:32:51.780000
 So I'm going to be able to cut out those
 because those are leading zeros,

0:32:51.780000 --> 0:32:57.340000
 cut out those, and I'll be able to cut
 out these three, leaving the last

0:32:57.340000 --> 0:33:04.300000
 one. So in its final form, this address
 will look like 2560 colon 1000

0:33:04.300000 --> 0:33:16.500000
 colon EA05, colon colon five
 colon EA colon 3D colon zero.

