1 00:00:09,150 --> 00:00:10,310 Welcome back. 2 00:00:10,350 --> 00:00:12,640 My name is David Bumble s.c.i. 3 00:00:12,690 --> 00:00:14,490 Eleven thousand twenty three. 4 00:00:14,490 --> 00:00:17,420 And in this section we're gonna look at IP version 6. 5 00:00:17,420 --> 00:00:22,440 We have been talking about the transition to Activision six for many years in the networking industry 6 00:00:22,830 --> 00:00:25,580 that it looks like we finally run out of time. 7 00:00:25,650 --> 00:00:34,290 It looks like this is the final year 2011 of being able to delay the transition to IPV six in production 8 00:00:34,290 --> 00:00:35,890 in real world environments. 9 00:00:36,180 --> 00:00:43,110 It's expected that in 2011 we will finally run out of IP version 4 addresses and be forced to move to 10 00:00:43,110 --> 00:00:44,790 IP version 6. 11 00:00:44,790 --> 00:00:52,300 So it looks like we can no longer procrastinate the conversion of our networks to IP version 6 but start 12 00:00:52,300 --> 00:00:55,160 with this news item from the BBC. 13 00:00:55,220 --> 00:00:58,110 Now it is dated 28 of January 2011. 14 00:00:58,340 --> 00:01:04,460 Were they talking about the last big blocks of the Nates dwindling stock of addresses about to be handed 15 00:01:04,460 --> 00:01:05,390 out. 16 00:01:05,430 --> 00:01:13,880 They are talking about total exhaustion in September 2011 however notice what the Internet Corporation 17 00:01:13,880 --> 00:01:22,460 for Assigned Names and Numbers is stating on their Web site last IPV for addresses are allocated today. 18 00:01:22,700 --> 00:01:27,770 And I mean you can read more about it on the web site but notice they say that today is a historic milestone 19 00:01:27,770 --> 00:01:32,290 for the Internet where the last addresses have been allocated. 20 00:01:32,330 --> 00:01:38,150 So after years of rapid Internet expansion the pool of available unallocated addresses for IP version 21 00:01:38,150 --> 00:01:41,120 4 is completely depleted. 22 00:01:41,150 --> 00:01:49,100 Notice the news release February 3 2011 available pool of unallocated our provision for Internet addresses 23 00:01:49,100 --> 00:01:50,880 is now completely emptied. 24 00:01:51,930 --> 00:01:56,790 They talk about a critical point in history was reached today with the allocation of the last remaining 25 00:01:56,820 --> 00:02:00,240 IP version of four addresses from a central pool. 26 00:02:00,690 --> 00:02:05,010 So this is a major turning point in the ongoing development of the Internet. 27 00:02:05,220 --> 00:02:11,070 So nerdish two blocks of the dwindling provision for addresses about 33 million of them were allocated 28 00:02:11,160 --> 00:02:15,150 earlier this week to the Asia-Pacific region. 29 00:02:15,210 --> 00:02:20,790 When that happened it meant the pool of IPV for dresser's had been depleted to a point where global 30 00:02:20,790 --> 00:02:26,820 policy was triggered to immediately allocate the remaining small pool of addresses equally among the 31 00:02:26,820 --> 00:02:30,150 five global regional Internet registries. 32 00:02:30,150 --> 00:02:38,360 This has now taken place so they were allocated in a ceremony in Miami so the procrastination for the 33 00:02:38,360 --> 00:02:41,450 convergence to IP version 6 is now finally over. 34 00:02:41,660 --> 00:02:47,510 We have to make sure we know how IP version 6 works and functions because we're going to come across 35 00:02:47,510 --> 00:02:50,850 it a lot more in the coming months and years. 36 00:02:51,230 --> 00:02:54,840 So what we're going to cover is firstly looking at the need for IP version 6. 37 00:02:54,890 --> 00:02:56,810 And I think I've covered that already. 38 00:02:56,840 --> 00:03:02,510 We have run out of IP version 4 addresses and we are now forced to convert or migrate to argue version 39 00:03:02,510 --> 00:03:03,350 6. 40 00:03:03,570 --> 00:03:10,130 Mean explain the format of an IP version 6 address an IP version 6 addresses 128 bits in length. 41 00:03:10,310 --> 00:03:15,970 So a lot larger than the city but our provision for address that we used to working with. 42 00:03:16,220 --> 00:03:19,460 We're gonna look at the methods of assigning an IP version 6 address. 43 00:03:19,650 --> 00:03:21,250 We can look at routing protocols. 44 00:03:21,410 --> 00:03:23,510 We're going to look at implementation strategies. 45 00:03:23,600 --> 00:03:26,730 And I'd like to show Europe in G configuration. 46 00:03:26,940 --> 00:03:32,390 So in other words I'll get a little network running using IP version 6 with Engy. 47 00:03:32,490 --> 00:03:37,550 The thing that seems to escape people most is the format of an IP version 6 address. 48 00:03:37,560 --> 00:03:43,440 The great thing about Activision 6 you can take a lot of your knowledge of IP version 4 and just apply 49 00:03:43,440 --> 00:03:51,780 it in an IP version 6 environment routing protocols like OSPF rip GOP and so forth are available in 50 00:03:51,780 --> 00:03:53,310 IP version 6. 51 00:03:53,310 --> 00:03:58,870 The version in the text might be slightly different but a lot of the concepts remain the same. 52 00:03:58,890 --> 00:04:03,420 We still have TCAP and UDP and a lot of the other protocols. 53 00:04:03,510 --> 00:04:10,320 So you don't have to learn everything from scratch which is a great benefit in Activision for an address 54 00:04:10,320 --> 00:04:14,530 consists of four tests which equals 32 bits in binary. 55 00:04:14,550 --> 00:04:20,480 So this is what an IP version for address would look like in binary or in Dr decimal notation. 56 00:04:20,850 --> 00:04:26,970 This is the number of IP addresses available in IP version for now an IP version 6. 57 00:04:27,010 --> 00:04:32,220 The address is 16 octets in Lintz which equates to 128 bits. 58 00:04:32,220 --> 00:04:34,860 This is an IP version 6 address written in binary. 59 00:04:34,890 --> 00:04:41,040 And as you can see it's a lot lot longer IP version 6 addresses are typically written in hexadecimal. 60 00:04:41,280 --> 00:04:46,350 So this is the hex representation of this binary IPV 6 address. 61 00:04:46,350 --> 00:04:51,500 They are 3.4 times ten to the thirty eight IP addresses available. 62 00:04:51,510 --> 00:04:54,510 The pool is a much much larger. 63 00:04:54,570 --> 00:04:57,490 The industry is learning from the mistakes of the past. 64 00:04:57,600 --> 00:05:03,810 And in this case they're making the pool very large so that we don't run into the same issue in a few 65 00:05:03,810 --> 00:05:07,440 years time where we run out of IP version 6 addresses. 66 00:05:07,470 --> 00:05:13,820 It's a dangerous thing to say this but this should be enough addresses for future Internet growth requirements. 67 00:05:14,070 --> 00:05:20,890 But just to put this in perspective there are enough IP version 6 addresses that we could allocate the 68 00:05:20,900 --> 00:05:27,900 entire equivalent IPV for Internet address space to every individual on Earth. 69 00:05:28,170 --> 00:05:31,370 That's how big this address space is. 70 00:05:31,600 --> 00:05:40,480 When comparing the same model of IP version 4 to IP version 6 you'll notice that all the layers except 71 00:05:40,540 --> 00:05:46,280 for Layer 3 have remained the same or only had slight modifications. 72 00:05:46,420 --> 00:05:53,170 So the application presentation session and transport will function in IP version 6 in the same way 73 00:05:53,170 --> 00:05:58,330 as they function an IP version for the network layer is where the changes have been made. 74 00:05:58,390 --> 00:06:05,920 For instance an IP version 4 address consists of only 32 bits but an IPV 6 address consists of 128 bits. 75 00:06:06,100 --> 00:06:10,690 The data link layer and physical layer Orser remain the same. 76 00:06:10,690 --> 00:06:16,240 So from a networking point of view this is great news because you can take all your knowledge and experience 77 00:06:16,330 --> 00:06:21,280 of IP version 4 protocols and apply it in an IP version 6 environment. 78 00:06:21,280 --> 00:06:27,610 It's not like in other rodded protocols we have to learn an entire new protocol stack protocols like 79 00:06:27,610 --> 00:06:35,870 TZP and UDP still remain at Layer 4 and reside on top of IPV 6 just like they do an IP version 4. 80 00:06:35,870 --> 00:06:39,050 So let's look at the IP V-6 address format in more detail. 81 00:06:39,050 --> 00:06:46,370 It consists of eight Xs where X is 16 but takes it a small field separated by colons. 82 00:06:46,370 --> 00:06:48,620 So it would look something like this. 83 00:06:48,650 --> 00:06:52,490 Please note that an IP B-6 address is case insensitive. 84 00:06:52,490 --> 00:06:58,900 So you could write if in lowercase and be in uppercase and it wouldn't make any difference. 85 00:06:58,940 --> 00:07:00,950 It's not case sensitive. 86 00:07:00,950 --> 00:07:07,700 There are some rules that you need to remember leading zeros or optional within the 16 but takes a decimal 87 00:07:07,700 --> 00:07:15,620 field and successive fields of zeros can be represented as Colon colon but only once per address. 88 00:07:15,650 --> 00:07:23,630 So as an example you could take this address and rewrite it as the following notice these two octets 89 00:07:23,870 --> 00:07:27,780 could be written as a Zira and notice these four states here. 90 00:07:28,010 --> 00:07:33,380 So the eight zeros in hexadecimal can be represented as Colon colon. 91 00:07:33,440 --> 00:07:39,950 However you cannot put colon colon twice within an IP address because the system would have no way of 92 00:07:39,950 --> 00:07:44,090 working out how many zeros are represented by these colons. 93 00:07:44,240 --> 00:07:47,530 Is this four zeros and those eight zeros. 94 00:07:47,540 --> 00:07:50,730 Or is this eight zeros and there's four zeros. 95 00:07:50,960 --> 00:07:55,470 So you could only put colon colon once in a mid-race OK. 96 00:07:55,470 --> 00:07:57,030 Here's another example. 97 00:07:57,180 --> 00:08:00,390 We have an IP version 6 address written as follows. 98 00:08:00,630 --> 00:08:04,830 Correct representations of this address would be as follows. 99 00:08:04,860 --> 00:08:07,140 Two thousand and one remains the same. 100 00:08:07,140 --> 00:08:09,980 This leadings zero can be removed. 101 00:08:10,050 --> 00:08:19,160 So we have one two three these four zeros and these four zeros can be condensed down to only colon colon. 102 00:08:19,170 --> 00:08:25,350 So those eight zeros can be compressed down to Colon colon before it's for remain the same. 103 00:08:25,350 --> 00:08:29,220 Now you also have four zeros followed by four zeros. 104 00:08:29,280 --> 00:08:35,690 However you can only represent a string of zeros by colon colon once in an address. 105 00:08:35,880 --> 00:08:37,900 And you've already done that. 106 00:08:37,920 --> 00:08:44,340 So what you can do is remove the leading zeros and when you remove leading zeros you have to have one 107 00:08:44,340 --> 00:08:47,020 value that remains between the colon. 108 00:08:47,310 --> 00:08:50,080 So notice here we've removed three leading zeros. 109 00:08:50,160 --> 00:08:52,510 And here we've removed three leading zeros. 110 00:08:52,860 --> 00:08:59,370 Yeah we've removed the leading zero in front of ABC so that 0 is also being removed. 111 00:08:59,370 --> 00:09:02,360 So this is a correct representation of the address. 112 00:09:02,450 --> 00:09:09,420 Or you could do something similar way these eight zeros are represented by Colon's era column 0. 113 00:09:09,690 --> 00:09:13,650 But these eight zeros are represented by colon colon. 114 00:09:13,670 --> 00:09:19,470 Remember you can only have two colons written in this format once in an address. 115 00:09:19,470 --> 00:09:23,760 So this would be an incorrect format for an IP V-6 address. 116 00:09:23,970 --> 00:09:30,720 A rat will not accept you typing this address on an interface as it cannot work out how many zeros are 117 00:09:30,720 --> 00:09:34,520 between these two colons and how many zeros are between these two colons. 118 00:09:34,620 --> 00:09:38,760 You can only write code on code on once in an address. 119 00:09:38,780 --> 00:09:42,360 So here are some more examples in this IPV 6 address we have. 120 00:09:42,360 --> 00:09:51,720 If it's 0 1 followed by a bunch of zeros ending in a 1 so we could represent that address by this or 121 00:09:51,720 --> 00:09:54,130 by this or by this. 122 00:09:54,300 --> 00:09:58,000 And I'm sure you can think of other variations of this address. 123 00:09:58,170 --> 00:10:01,070 Please note this is the same address. 124 00:10:01,080 --> 00:10:07,300 It's like saying tomato juice is tomato or napkin versus serviette. 125 00:10:07,440 --> 00:10:12,030 It's the same thing just represented in different formats. 126 00:10:12,030 --> 00:10:13,550 Here's another example. 127 00:10:13,860 --> 00:10:18,660 We've got four ones followed by one two three four followed by eight zeros followed by one two three 128 00:10:18,660 --> 00:10:22,380 four followed by eight zeros followed by four ones. 129 00:10:22,620 --> 00:10:25,750 These four zeros can be condensed down to zero. 130 00:10:26,070 --> 00:10:28,770 These four zeros can be condensed down to zero. 131 00:10:29,160 --> 00:10:33,020 And these eight zeros can be condensed down to come along come along. 132 00:10:33,600 --> 00:10:40,570 Or you can say those eight zeros are represented by colon colon and these four zeros by a zero. 133 00:10:40,920 --> 00:10:43,730 And those four zeros by zero. 134 00:10:43,800 --> 00:10:49,660 Once again it's the same address different representations whichever you prefer. 135 00:10:50,100 --> 00:10:55,970 Once again this address a bunch of zeros followed by one could be represented as column column one. 136 00:10:56,010 --> 00:11:02,360 This is the loopback address of an interface and a string of zeros could be represented as Colon colon. 137 00:11:02,370 --> 00:11:10,170 This is an example of an unassigned address cómo on a Windows machine occupying 127 0 0 1 the loopback 138 00:11:10,740 --> 00:11:12,860 in IP version 4. 139 00:11:13,090 --> 00:11:19,560 By the same token I can think colon colon one which is the loopback in IP version 6. 140 00:11:19,930 --> 00:11:23,430 If you remember the design is an IP version 4. 141 00:11:23,560 --> 00:11:29,740 Unfortunately chose a class A address for the loopback address and that's the IP version for address 142 00:11:29,740 --> 00:11:36,570 range lost 16 million host addresses because the loopback is across a address in ITV 6. 143 00:11:36,610 --> 00:11:41,110 The design is of try to avoid the same mistakes that were made in the past. 144 00:11:41,140 --> 00:11:46,370 So notice the loopback address is just called on call on one but I could also take an 145 00:11:54,240 --> 00:11:57,320 Which is the same address the loopback. 146 00:11:57,330 --> 00:11:58,770 All I could do the following 147 00:12:05,020 --> 00:12:06,250 or something like this. 148 00:12:12,060 --> 00:12:18,720 Notice it's all the same address my PC automatically converts it into Colon colon one which I think 149 00:12:18,720 --> 00:12:24,700 is the easiest representation of this address now in the real world this is going to be a lot of fun. 150 00:12:24,720 --> 00:12:31,260 It's difficult enough trying to get users to top HGP cold encored slash Ford slash an IP version 4 address 151 00:12:31,620 --> 00:12:32,970 into a web browser. 152 00:12:33,260 --> 00:12:38,340 Can you imagine trying to get them to do the following you know IP version 6 in a web browser you have 153 00:12:38,340 --> 00:12:43,230 to enclose the address within square brackets as follows. 154 00:12:43,440 --> 00:12:51,150 So in other words you would type HTP colon Ford slash Ford slash the IP version 6 address colon and 155 00:12:51,150 --> 00:12:53,880 then for instance the port number to ADHD. 156 00:12:54,150 --> 00:12:58,490 And then for instance a file name let's say indexed at HMO. 157 00:12:58,590 --> 00:13:01,280 This is obviously going to be very difficult for users. 158 00:13:01,410 --> 00:13:06,000 So I suppose you would use this mostly for diagnostic purposes but I can see that we're going to have 159 00:13:06,000 --> 00:13:08,310 to ask users to do this at some point. 160 00:13:08,310 --> 00:13:09,890 So good luck with that. 161 00:13:09,900 --> 00:13:14,390 So it's recommended to use fully qualified domain names rather than IP addresses. 162 00:13:14,430 --> 00:13:19,830 So rather than typing something like this you would say Cisco dot com and then rely on DNS to do the 163 00:13:19,830 --> 00:13:21,290 conversion. 164 00:13:21,330 --> 00:13:30,090 Now to test your IP version 6 connectivity you can go to this Web site HTP sports Ford slash test IPV 165 00:13:30,090 --> 00:13:37,360 six dot com and this will run a series of tests to check your connectivity to IP version 6 as you can 166 00:13:37,360 --> 00:13:37,590 see. 167 00:13:37,590 --> 00:13:45,600 I'm going to have a problem where I'm currently residing is also information about IPB 6 day which depending 168 00:13:45,600 --> 00:13:48,820 on when you're viewing this may have taken place already. 169 00:13:48,910 --> 00:13:55,140 It's scheduled for eight of June 2011 when there's going to be a global scale test flight of IP version 170 00:13:55,140 --> 00:13:56,120 6. 171 00:13:56,210 --> 00:14:02,310 So major web companies and other industry players will enable IP version 6 on their main Web sites for 172 00:14:02,310 --> 00:14:09,530 24 hours or the different types of addresses in Activision 6 some of which you'll recognize already. 173 00:14:09,620 --> 00:14:14,720 The first one is a unique cost address which has an address allocated to single interface for example 174 00:14:15,260 --> 00:14:21,420 and several types of unicast addresses and I'll go through all of these in more detail in upcoming slides. 175 00:14:21,510 --> 00:14:24,820 But first we have a global unique cost race. 176 00:14:24,830 --> 00:14:28,650 There is no need for net in IP version 6. 177 00:14:28,760 --> 00:14:30,700 That comes as a big shock to a lot of people. 178 00:14:30,770 --> 00:14:36,890 Remember next was introduced to try and conserve ATI version for addresses yet we have plenty of addresses 179 00:14:36,890 --> 00:14:41,780 so there's no need for net a lot of people say that that's a security vulnerability. 180 00:14:41,930 --> 00:14:47,460 But remember that net will network address translation was not developable security originally. 181 00:14:47,540 --> 00:14:49,720 That's a byproduct of net. 182 00:14:49,830 --> 00:14:58,310 We have globally unique unicast addresses the address on your interface on your PC at home will be unique 183 00:14:58,350 --> 00:14:59,340 globally. 184 00:14:59,690 --> 00:15:06,230 There is no need for your IP address to be netted to an external or public address or a public if you 185 00:15:06,230 --> 00:15:10,460 like global unicast address is available for all devices in the world. 186 00:15:10,700 --> 00:15:14,450 They're are also reserved unicast of racism we won't worry too much about them. 187 00:15:14,450 --> 00:15:20,520 We also have link local unicast addresses and I only refer to a particular physical link. 188 00:15:20,520 --> 00:15:26,780 Raptor's do not forward link local addresses link local addresses will allow two hosts to communicate 189 00:15:26,780 --> 00:15:30,460 with each other without IP addresses being assigned to those devices. 190 00:15:30,470 --> 00:15:35,870 So two users could connect that PCs back to back using for instance a crossover cable and they'll have 191 00:15:35,870 --> 00:15:43,420 immediate IP connectivity without the need for manual configuration of addresses or for a DHP server. 192 00:15:43,700 --> 00:15:49,610 Many ITV six routing protocols also use Linked local addresses to communicate with each other link local 193 00:15:49,610 --> 00:15:55,250 addresses are also used for Link communication such as automatic address configuration neighbor discovery 194 00:15:55,280 --> 00:15:56,900 and rodded discovery. 195 00:15:56,990 --> 00:15:59,840 I'll show you a link local address looks like in a moment. 196 00:15:59,930 --> 00:16:06,800 We also have Cyke local unicast addresses which are similar in concept to RAFC 19:18 private addresses. 197 00:16:06,910 --> 00:16:11,110 These are addresses assigned to an entire site within an organization. 198 00:16:11,540 --> 00:16:18,170 So site local address would only be valid within the site makework of an organization so that local 199 00:16:18,170 --> 00:16:23,490 addresses were part of the original addressing architecture from 1995. 200 00:16:23,530 --> 00:16:31,150 But please note that site local unicast addresses have been deprecated since September 2004. 201 00:16:31,400 --> 00:16:40,300 And you can read more about this in RAFC 3 8 7 9 where they talk about deprecating site local addresses. 202 00:16:40,370 --> 00:16:46,430 It's important to note that the development of IP B-6 has been ongoing for a number of years and certain 203 00:16:46,430 --> 00:16:51,860 terms that you come across such a site local addresses will have changed or been updated or in this 204 00:16:51,860 --> 00:16:53,200 case deprecated. 205 00:16:53,510 --> 00:16:59,280 So they no longer use because of the confusion and ambiguity of the term site. 206 00:16:59,510 --> 00:17:03,750 They have not been replaced with what are called unique local addresses. 207 00:17:03,770 --> 00:17:08,660 There are also some special purpose unicast addresses such as unspecified whichever it is shown you 208 00:17:08,660 --> 00:17:15,230 it's just colon colon and is used to refer to the host itself and is used when a device does not know 209 00:17:15,230 --> 00:17:17,030 its own IP address. 210 00:17:17,030 --> 00:17:22,580 This would be typically used in the source field of a datagram that is sent by a device that seeks to 211 00:17:22,580 --> 00:17:24,500 have its IP address configured. 212 00:17:24,770 --> 00:17:27,070 So colon colon means unspecified. 213 00:17:27,320 --> 00:17:29,030 I've already demonstrated loopback. 214 00:17:29,060 --> 00:17:35,050 That would be colon colon one which is very similar to 1:27 001 for example. 215 00:17:35,330 --> 00:17:39,650 Now IP version for compatible addresses have also been deprecated. 216 00:17:39,650 --> 00:17:45,410 It would allow for the representation of an IP version for address with an IP version 6. 217 00:17:45,410 --> 00:17:52,190 The most significant 96 bits of the address would be set to zero while the last 32 bits are the IP version 218 00:17:52,190 --> 00:17:54,150 for address that is represented. 219 00:17:54,350 --> 00:17:57,200 This was deprecated in 2006. 220 00:17:57,200 --> 00:18:02,400 The reason I still mention these addresses is that you may come across them an IP version 6 literature. 221 00:18:02,690 --> 00:18:08,480 Just be aware like a lot of things and life changes have taken place and certain technologies and addresses 222 00:18:08,480 --> 00:18:10,810 have been dropped or deprecated. 223 00:18:10,850 --> 00:18:16,040 So be aware the first top of address and ATI version 6 is unicast. 224 00:18:16,110 --> 00:18:23,100 The second is multicast where one host speaks to many hosts and this is very similar to multicasting 225 00:18:23,100 --> 00:18:29,870 and I provision for because it enables more efficient use of the network but uses a larger address range. 226 00:18:29,880 --> 00:18:36,180 The advantage of multicasting is that a single stream from a single server can go to many many devices 227 00:18:36,620 --> 00:18:42,420 so a hundred devices could be receiving the same video stream of one megabits per second rather than 228 00:18:42,420 --> 00:18:48,530 having a hundred one megabits per second streams and thus using up a hundred megabits per second. 229 00:18:48,630 --> 00:18:52,140 If the cost was used the third type is any cost. 230 00:18:52,140 --> 00:18:55,690 Now this does exist in IP version 4 as well. 231 00:18:55,740 --> 00:19:02,640 This is known as one to nearest Unix addresses are used but the same address is configured on two or 232 00:19:02,640 --> 00:19:04,200 more devices. 233 00:19:04,200 --> 00:19:09,270 The idea here is that routers will decide on the closest device to reach the destination. 234 00:19:09,270 --> 00:19:14,850 If you are going to Amazon Dot com for example you wouldn't care if that server was hosted in California 235 00:19:15,000 --> 00:19:16,300 or in New York. 236 00:19:16,620 --> 00:19:20,020 You just want to purchase a book for example from Amazon. 237 00:19:20,190 --> 00:19:26,220 If you are on the West Coast of the US you would be closer to a server in California than you would 238 00:19:26,220 --> 00:19:28,040 be to a server in New York. 239 00:19:28,170 --> 00:19:34,320 So at any cost to servers one in New York one in San Francisco for example are configured with the same 240 00:19:34,350 --> 00:19:35,450 IP address. 241 00:19:35,550 --> 00:19:41,310 If you are on the West Coast of the US and you are going to Amazon Dot com for example you'd be routed 242 00:19:41,490 --> 00:19:47,520 to the server in San Francisco because it's physically closer to you than the server in New York. 243 00:19:47,520 --> 00:19:53,160 By the same token if you're on the east coast you'd be routed to the server in New York. 244 00:19:53,160 --> 00:19:56,040 It allows for load balancing and content delivery services. 245 00:19:56,340 --> 00:19:59,180 As I've mentioned it already exists an IP version 4. 246 00:19:59,430 --> 00:20:02,550 So they are three address types not version 6. 247 00:20:02,640 --> 00:20:08,560 So we have broad costs which are so common in IP version for broadcast addresses no longer exist. 248 00:20:08,880 --> 00:20:16,260 Broadcast costs cause lots of issues on networks and broadcasting has been replaced with multicasting 249 00:20:16,260 --> 00:20:18,480 in an IP version 6 environment. 250 00:20:18,480 --> 00:20:23,410 We no longer send broadcasts if we want to contact multiple devices. 251 00:20:23,610 --> 00:20:32,270 We send a multicast instead of a broadcast as mentioned an IP version 6 address is 120 a but since lenth 252 00:20:32,710 --> 00:20:38,590 it consists of two main portions we have the network portion when they took prefix and the interface 253 00:20:38,590 --> 00:20:41,200 identifier or host portion. 254 00:20:41,410 --> 00:20:44,060 Each of these is 64 bits in length. 255 00:20:44,290 --> 00:20:50,350 Now it may come as a surprise to you but there's no submitting an IP version 6 like an IP version for 256 00:20:50,860 --> 00:20:56,710 we're not going to subnet is say a slash city or slashed 28 or slash 16. 257 00:20:56,710 --> 00:21:02,980 We're not going to have classes of addresses like class A B and C and subnets of those like taking a 258 00:21:02,980 --> 00:21:06,750 class C address and submitting it to slash 28 or slash 30. 259 00:21:07,000 --> 00:21:08,990 That no longer exists. 260 00:21:09,010 --> 00:21:11,590 The following statement is important to understand. 261 00:21:11,770 --> 00:21:18,150 Every interface has a mosque slash 64 in your enterprise environments. 262 00:21:18,280 --> 00:21:23,740 Every interface when using a Unicode address as a Moscow slash 64. 263 00:21:24,210 --> 00:21:25,420 I'll say that again. 264 00:21:25,420 --> 00:21:29,190 All interfaces have a subnet mask of slash 64. 265 00:21:29,530 --> 00:21:32,950 In other words the network prefix is always slash 64. 266 00:21:33,160 --> 00:21:38,000 In our enterprise environments the host portion is always 64 bits. 267 00:21:38,050 --> 00:21:43,060 So this actually makes our lives a lot easier because we don't have to do crazy subsetting in IP version 268 00:21:43,060 --> 00:21:44,710 6 in a similar way. 269 00:21:44,720 --> 00:21:46,560 We had to do an IP version 4. 270 00:21:47,020 --> 00:21:49,520 So there's no subsetting like an IP version 4. 271 00:21:49,690 --> 00:21:52,870 There's also no net like an IP version for. 272 00:21:53,170 --> 00:22:01,230 NET is no longer required addresses and organizations use what are called aggregated all global unicast 273 00:22:01,230 --> 00:22:02,140 addresses. 274 00:22:02,340 --> 00:22:03,890 Which is quite a mouthful. 275 00:22:03,930 --> 00:22:09,450 I'll just refer to these as global unicast addresses but the full name once again is aggregated all 276 00:22:09,570 --> 00:22:11,920 global unicast addresses. 277 00:22:11,970 --> 00:22:15,830 In other words addresses within your organization or globally unique. 278 00:22:16,020 --> 00:22:22,170 There is no need to net those addresses when going onto the Internet because they all like public IP 279 00:22:22,170 --> 00:22:24,040 addresses within organizations. 280 00:22:24,110 --> 00:22:27,900 So globally unique there are also a unique cost addresses. 281 00:22:28,170 --> 00:22:34,460 The term aggregate A-ball means that they can be aggregated or summarized in the global Internet. 282 00:22:34,470 --> 00:22:41,430 The design is of IP version 6 that specifically looked at aggregation of addresses to reduce writing 283 00:22:41,430 --> 00:22:44,450 table sizes within the global Internet. 284 00:22:44,450 --> 00:22:47,130 Now I'll show you an example of that in a moment. 285 00:22:47,130 --> 00:22:51,830 Each Milenko interface will have a slash 64 subnet mask. 286 00:22:51,840 --> 00:22:54,390 Once again this makes life a lot easier. 287 00:22:54,390 --> 00:23:03,540 The interface identifier or ID which is 64 bits in length can use a modified UI 64 format address which 288 00:23:03,540 --> 00:23:08,790 I'll explain in a moment but it's essentially a modified Mac address. 289 00:23:08,970 --> 00:23:14,820 For those of you who have been in networking for a long time you may remember how IPX also use the Mac 290 00:23:14,820 --> 00:23:19,080 address and that same thinking can be used in IP version 6. 291 00:23:19,380 --> 00:23:25,580 So the EU address allows us to get the interface ID portion of an IP version 6 address. 292 00:23:25,650 --> 00:23:32,050 This can be used in multiple IP version 6 addresses including link local site local as well as the stateless 293 00:23:32,070 --> 00:23:34,580 order configuration mechanism. 294 00:23:34,590 --> 00:23:35,740 Don't worry too much about those. 295 00:23:35,740 --> 00:23:41,740 Now we'll be talking about them in a moment but please note an email address can also be used in an 296 00:23:41,780 --> 00:23:44,480 aggregate all global unicast address. 297 00:23:44,520 --> 00:23:49,010 It doesn't have to be that you can use it if you so desire. 298 00:23:49,200 --> 00:23:51,900 And you just said that with a command on a Cisco router. 299 00:23:52,230 --> 00:23:58,390 So what happens is the Rotto other device takes its ethernet Mac address which is 48 bits in length. 300 00:23:58,620 --> 00:24:05,220 And he an example of an Ethernet Mac address and the address is split in half between the vendor portion 301 00:24:05,310 --> 00:24:07,670 and the unique portion of the Mac address. 302 00:24:07,830 --> 00:24:16,170 If f if he is inserted in the middle which results in a 64 bit address remember all of these values 303 00:24:16,170 --> 00:24:17,760 on hexadecimal. 304 00:24:17,760 --> 00:24:21,890 So this represents 64 bits. 305 00:24:21,900 --> 00:24:29,280 So again please note that this address is written in hexadecimal because IP version 6 addresses are 306 00:24:29,280 --> 00:24:31,930 written in hexadecimal. 307 00:24:31,960 --> 00:24:36,100 These two hexadecimal values equate to 8 binary bits.