WEBVTT - The IPv6 Switchover 0:00:00.280 --> 0:00:03.080 Brought to you by the reinvented two thousand twelve Camray. 0:00:03.160 --> 0:00:08.920 It's ready. Are you get in touch with technology? With 0:00:09.000 --> 0:00:17.680 tech Stuff from how stuff works dot com. Hello again, everyone, 0:00:17.720 --> 0:00:20.000 Welcome to tech stuff. My name is Chris Poulette and 0:00:20.040 --> 0:00:22.280 I am an editor at how stuff works dot com. 0:00:22.320 --> 0:00:25.759 Sitting across from me, as always his senior writer, Jonathan Strickland. 0:00:25.920 --> 0:00:30.400 One is the loneliest number that you ever knew. Nice, 0:00:30.600 --> 0:00:33.360 Thank you, Except today we're gonna talk about something that 0:00:33.440 --> 0:00:35.600 lets you do a whole lot more than one. Yes, 0:00:35.720 --> 0:00:37.360 but you know two can be as sad as one. 0:00:37.560 --> 0:00:40.280 That's true. That's true. That's one. I here. So we 0:00:40.280 --> 0:00:43.240 we've talked about this before, I think on the podcast, 0:00:43.600 --> 0:00:47.320 but we've never really delved into it and gotten really 0:00:47.400 --> 0:00:49.800 like knee deep in this. In this topic, we're talking 0:00:49.840 --> 0:00:55.200 about the I p V six switchover and why it's 0:00:55.280 --> 0:00:59.160 necessary and why it's going a little slowly. Although that 0:00:59.720 --> 0:01:02.440 that that's a little more difficult to answer, because that's 0:01:02.480 --> 0:01:05.880 that's getting into lots of different factors. But really you've 0:01:05.880 --> 0:01:09.000 probably heard about this. You may have been following the news. 0:01:09.040 --> 0:01:11.000 You might have even seen that back in February of 0:01:12.600 --> 0:01:17.160 that the last big batch of I p V four 0:01:17.200 --> 0:01:21.840 addresses was assigned and that this means that we are 0:01:21.920 --> 0:01:25.640 running out of I p v four addresses. Before we 0:01:25.680 --> 0:01:27.120 get too far into it, I guess we need to 0:01:27.200 --> 0:01:33.440 kind of talk about protocols and addresses. Yep, yep. And uh, 0:01:33.560 --> 0:01:37.760 this is something that is hardly new. I mean, uh, 0:01:37.800 --> 0:01:41.520 people like uh, you know, the the Internet founders, people 0:01:41.520 --> 0:01:45.280 like J. C. R. Licklider and so many of the others, 0:01:45.920 --> 0:01:49.440 um vent Surf among them. Back in the day Con 0:01:49.760 --> 0:01:52.720 Robert Con and the sixties and seventies were looking into 0:01:52.840 --> 0:01:57.760 how to share information between machines and um they basically 0:01:57.880 --> 0:02:01.360 they had a couple of trials, but the version of 0:02:01.520 --> 0:02:05.080 the protocols that we use to communicate on the Internet 0:02:05.120 --> 0:02:08.720 today date back decades at this point, right, yeah. Now, 0:02:08.720 --> 0:02:11.720 Originally they had a protocol they called the Network Control 0:02:11.760 --> 0:02:15.359 Protocol or in CP, but that was not nearly robust 0:02:15.480 --> 0:02:18.640 enough for it to truly allow networks of machines to 0:02:18.680 --> 0:02:22.880 communicate with one another. And thankfully, the people working on 0:02:22.919 --> 0:02:25.760 our pannet recognize that, and they began to work immediately 0:02:25.880 --> 0:02:29.239 on a a system that would or a set of 0:02:29.280 --> 0:02:32.600 protocols that would replace in CP and that ended up 0:02:32.639 --> 0:02:35.679 being a pair of protocols UH, I P and t 0:02:35.919 --> 0:02:40.000 c P, which are almost always grouped together when you're 0:02:40.000 --> 0:02:43.040 talking about them because they are so closely related one 0:02:43.240 --> 0:02:45.919 the first is a transmission control protocol and the other 0:02:45.960 --> 0:02:49.240 is Internet protocol and it's they're often UH separated by 0:02:49.280 --> 0:02:51.080 just a slash, So you hear people talk about a 0:02:51.120 --> 0:02:54.040 t c P, I P, yeah, and and connection. And 0:02:54.080 --> 0:02:57.920 here's why they're connected so closely. So the transport the 0:02:57.919 --> 0:03:03.040 the TCP that in charge of taking streams of data, 0:03:03.200 --> 0:03:06.720 essentially chopping up those streams of data UH and then 0:03:06.880 --> 0:03:09.760 handing it over to the I P, and then the 0:03:09.800 --> 0:03:13.400 IP handles the actual packet routing. The packets are the 0:03:13.440 --> 0:03:16.720 packets of information. Files are are essentially divided up into 0:03:16.760 --> 0:03:21.440 packets of bits, and those are sent off across the 0:03:21.440 --> 0:03:25.919 the Internet and then TCP once uh IT the the 0:03:25.919 --> 0:03:28.959 packets arrive at their destination, is in charge of placing 0:03:29.000 --> 0:03:32.840 those packets together again to reform a data stream so 0:03:32.880 --> 0:03:36.680 that the receiving computer is able to see the actual 0:03:36.880 --> 0:03:39.840 file or information that was being sent across rather than 0:03:39.880 --> 0:03:45.720 just a bunch of seemingly meaningless bits and bytes. Because otherwise, 0:03:45.760 --> 0:03:47.600 if you know if you didn't have those protocols in place, 0:03:47.920 --> 0:03:50.920 It's would be kind of like if I were to say, 0:03:51.040 --> 0:03:56.120 take a framed uh picture, and then I cut it 0:03:56.200 --> 0:03:58.840 up all into these tiny little pieces, and then I 0:03:58.880 --> 0:04:02.400 put all those tiny little pieces into various envelopes and 0:04:02.400 --> 0:04:05.440 then sent all the envelopes to Chris and did not 0:04:05.560 --> 0:04:08.400 give Chris a way of finding out how to put 0:04:08.440 --> 0:04:11.000 those pieces back together. Well, that would just mean that 0:04:11.040 --> 0:04:13.360 I sent Chris a whole bunch of envelopes filled with 0:04:13.360 --> 0:04:17.160 broken glass and pieces of picture, which frankly I do anyway, 0:04:17.240 --> 0:04:20.080 but that's just for funzies. But if I wanted to 0:04:20.080 --> 0:04:22.839 actually give him something that was meaningful, I would have 0:04:22.880 --> 0:04:25.279 to have something in place that would reassemble all those 0:04:25.279 --> 0:04:27.920 pieces back into the original format that it was in 0:04:28.040 --> 0:04:29.799 when I sent it the first in the first place, 0:04:29.839 --> 0:04:32.880 so that Chris could see it. So, come on, boys, 0:04:32.960 --> 0:04:38.520 let's take some pictures. Hey, airplane reference and so um uh. 0:04:38.880 --> 0:04:42.080 That's that's how the the information gets spread across the internet, 0:04:42.080 --> 0:04:44.440 how you send information across the internet. But but one 0:04:44.560 --> 0:04:47.680 key component of this is you have to have an 0:04:47.720 --> 0:04:51.520 address for your machine so that when you send information 0:04:51.560 --> 0:04:55.120 across the internet. Uh. There the systems on the Internet. No, 0:04:56.160 --> 0:05:00.400 what direction to send that that information in? Right? Yeah, 0:05:00.480 --> 0:05:04.359 that's this is the thing about Internet protocol is it 0:05:04.360 --> 0:05:07.839 serves the sort of a lingua franca for uh, different 0:05:07.880 --> 0:05:11.000 computers on the net. So you can be running Linux 0:05:11.040 --> 0:05:14.039 and talk to a Windows machine or a Mac and 0:05:14.320 --> 0:05:16.760 come on, Max, don't talk to anyone but other Max. 0:05:16.800 --> 0:05:18.880 Have you seen those people? They just sit in a 0:05:18.920 --> 0:05:21.479 click and they're all cool kids, and they all look 0:05:21.560 --> 0:05:24.480 like they've just stepped out of a hipster boutique and 0:05:25.520 --> 0:05:27.760 nobody said you have an anti Mac bias. In sometime 0:05:27.839 --> 0:05:30.200 you just enjoy that, don't you. Yeah, once in a while, 0:05:30.200 --> 0:05:32.240 I like to, I like to you don't bring that back, 0:05:32.320 --> 0:05:36.479 which is just funny. That's why I totally just being silly. Yeah, 0:05:36.520 --> 0:05:39.919 but no, any any computer that is able to communicate 0:05:40.560 --> 0:05:43.760 UM with T C P I P to the Internet 0:05:43.800 --> 0:05:46.320 and back should be able to communicate with other machines. 0:05:46.360 --> 0:05:48.800 So you you should be able to to share information 0:05:48.839 --> 0:05:51.760 pretty easily. That's the beauty of this. But as you said, 0:05:51.839 --> 0:05:54.600 the the addressing system has to support that, and there 0:05:54.600 --> 0:05:56.760 has to be a way to know where the packets 0:05:56.760 --> 0:05:59.279 are are being sent to, especially since you know there's 0:05:59.279 --> 0:06:02.760 some redundant in this, you know network, their packets being 0:06:02.800 --> 0:06:04.599 sent to one machine and then to another machine and 0:06:04.600 --> 0:06:06.760 hopefully one of them will get there on time to 0:06:06.760 --> 0:06:09.080 build the file back. And let's say let's say that 0:06:09.200 --> 0:06:11.800 one server is sending out the same file to like 0:06:11.880 --> 0:06:14.840 eight different computers. Well, has to know how you know, 0:06:14.920 --> 0:06:16.839 it has to be able to identify those computers to 0:06:16.880 --> 0:06:19.040 send in the right information. Has to send the right 0:06:19.040 --> 0:06:21.320 packets to each one, even if it's the same file. 0:06:21.360 --> 0:06:24.120 You wouldn't want to send the same packet to computer 0:06:24.200 --> 0:06:26.720 number one and a different packet to computer number two 0:06:26.720 --> 0:06:29.280 and a different because you wouldn't be able to to 0:06:29.320 --> 0:06:32.720 put those packets into any meaningful form, right. You would 0:06:32.720 --> 0:06:35.680 have to set the same series of packets, not necessarily 0:06:35.720 --> 0:06:37.240 in the same order either. That's the one of the 0:06:37.279 --> 0:06:39.680 wonderful thing about the Internet is that the routing system 0:06:39.720 --> 0:06:43.280 is really flexible. So if machines go down on the Internet, 0:06:43.800 --> 0:06:46.600 the packets can be rerouted by other machines to go 0:06:46.680 --> 0:06:50.279 around the outage and still get to their final destination. 0:06:50.360 --> 0:06:52.159 So as long as the host computers that are in 0:06:52.279 --> 0:06:56.440 charge of sending and receiving the information remain on the network. 0:06:56.960 --> 0:06:59.880 Theoretically that information should eventually get there. It may take 0:07:00.040 --> 0:07:04.040 little longer than ideally, just because computers that are on 0:07:04.120 --> 0:07:07.599 that pathway may have failed along the way, but the 0:07:07.640 --> 0:07:09.880 information should still get there. I mean, that's the whole 0:07:10.520 --> 0:07:13.920 robust nature of the Internet. So we've got this address 0:07:14.040 --> 0:07:17.560 issue now. The issue here is that the uh, the 0:07:17.600 --> 0:07:23.280 Internet protocol address that was set up was for reasons 0:07:23.320 --> 0:07:25.680 that I could not figure out, really, reasons that are 0:07:25.760 --> 0:07:28.600 so obscure that that it might as well be forgotten. 0:07:29.120 --> 0:07:31.680 Um is called i p v C V four. Rather, 0:07:32.480 --> 0:07:34.880 this was the the protocol that was settled upon for 0:07:34.920 --> 0:07:39.960 the addresses, and it uses a thirty two bit address, 0:07:40.560 --> 0:07:43.320 all right, three two bit address, and it's in the 0:07:43.360 --> 0:07:48.160 format of four eight bit values separated by periods. Right, 0:07:48.760 --> 0:07:51.400 so it could be anything from zero dot zero dot 0:07:51.480 --> 0:07:56.840 zero dot zero to accept. And that that's your range 0:07:56.840 --> 0:07:59.960 of addresses. Some of those you can't use. Yeah, Actually, technically, 0:08:00.120 --> 0:08:02.560 if if you could use all of the addresses, you 0:08:02.560 --> 0:08:07.000 would have access to four billion, two d million, nine 0:08:07.120 --> 0:08:10.600 hundred sixty seven thousand, two d addresses. If you could 0:08:10.680 --> 0:08:12.840 use all of them, you can't. There are more than 0:08:12.920 --> 0:08:16.800 half a half a billion of them that are off limits. 0:08:16.920 --> 0:08:19.480 So and and we've we've had people right into us 0:08:19.520 --> 0:08:22.240 before to explain that, you know, there are certain you 0:08:22.280 --> 0:08:26.480 cannot use zero in four times and two four times, 0:08:26.480 --> 0:08:28.840 there are some that that you cannot use. But that 0:08:28.880 --> 0:08:31.280 does give you an awful lot of addresses. Three point 0:08:31.360 --> 0:08:37.360 seven billion with a B addresses are we're available initially. Now, 0:08:38.320 --> 0:08:41.599 the problem was that even back as early as the 0:08:42.040 --> 0:08:45.880 ninety nineties, I mean back even further than that, but 0:08:45.920 --> 0:08:48.400 in the ninety n it was recognized that there was 0:08:48.440 --> 0:08:51.000 gonna come a time where we'd run out of these addresses. 0:08:51.240 --> 0:08:54.160 Now there's certain ways to kind of uh to to 0:08:54.320 --> 0:08:58.240 mitigate that somewhat. One of those ways is called network 0:08:58.320 --> 0:09:02.680 address translation or not yes, network address translation that we've 0:09:02.679 --> 0:09:04.720 had people right into us about this as well. That's 0:09:04.720 --> 0:09:08.360 when you have a system like a router that has 0:09:08.480 --> 0:09:11.360 its own IP address, So the router has an IP 0:09:11.440 --> 0:09:14.480 address that's public. That's the other part of the system 0:09:14.520 --> 0:09:17.280 is that these addresses have to be public. If they're private, 0:09:17.320 --> 0:09:20.480 then the system cannot won't be able to see the 0:09:20.880 --> 0:09:23.920 computer and won't be able to send information to that computer. 0:09:24.320 --> 0:09:26.320 So you have to have these public addresses. So the 0:09:26.440 --> 0:09:29.920 router has a public address, and then the machines connected 0:09:30.000 --> 0:09:34.360 to the router all are assigned private addresses by the router. 0:09:34.559 --> 0:09:36.720 So let's say that I have a computer connected to 0:09:36.760 --> 0:09:40.080 this router, I send I wanna go check a website, 0:09:40.080 --> 0:09:42.360 So I type in an address in my my browser 0:09:42.440 --> 0:09:47.400 bar uh. The request is sent to the router. The 0:09:47.520 --> 0:09:51.560 router then replaces my private address that the router has 0:09:51.600 --> 0:09:56.240 assigned me with the router's own public address, then sends 0:09:56.280 --> 0:09:59.439 the request out to the Internet. So then the request 0:09:59.440 --> 0:10:03.319 goes out to whatever server has that website stored on it. 0:10:03.520 --> 0:10:07.240 The server then sends the information back to the router. Now, 0:10:07.280 --> 0:10:09.640 at this point, the router has to determine which of 0:10:09.720 --> 0:10:13.160 the computers connected or devices connected to its system is 0:10:13.200 --> 0:10:16.120 the one that requested the information in the first place. 0:10:16.600 --> 0:10:19.040 So there's some protocols that are that you need in 0:10:19.120 --> 0:10:21.720 addition support mapping that you need to do in order 0:10:21.720 --> 0:10:24.160 for this to work. But in general, you can create 0:10:24.200 --> 0:10:26.800 a system where the router then sends that information to 0:10:26.840 --> 0:10:29.160 the right device, in this case, my computer and I 0:10:29.280 --> 0:10:32.600 get to see the website. Now you might ask, well, 0:10:32.600 --> 0:10:35.800 why would you bother to do this, Well, it conserves 0:10:36.200 --> 0:10:39.160 I P addresses because the router is the only one 0:10:39.200 --> 0:10:42.640 that has a public IP address, And so you might 0:10:42.720 --> 0:10:45.920 have a whole network of computers hooked up through this router, 0:10:46.320 --> 0:10:49.439 but those computers don't have their individual I P addresses. 0:10:49.440 --> 0:10:54.080 They have a little private address that's assigned by the router. UM. 0:10:54.240 --> 0:10:57.120 But so, so anything that comes back I'm sorry, didn't 0:10:57.280 --> 0:11:00.760 go ahead. UM. So your computer or sends a request 0:11:00.800 --> 0:11:03.000 to your router in your house. Say you have two 0:11:03.000 --> 0:11:06.320 computers in your house, and from there, the router sends 0:11:06.320 --> 0:11:09.200 a request to wherever it is that the information you're 0:11:09.240 --> 0:11:12.680 looking for is coming from. UM. Meanwhile, the person using 0:11:12.679 --> 0:11:17.439 the other computer UM in the household makes a request 0:11:17.480 --> 0:11:20.679 and it goes to somewhere else. Well, the information is 0:11:20.720 --> 0:11:24.520 all coming back to the router. The router itself in 0:11:24.559 --> 0:11:28.160 your house is making the determination of which packet needs 0:11:28.160 --> 0:11:30.800 to go to which machine. So that that cuts down 0:11:30.800 --> 0:11:32.600 on some of the confusion and it and it helped 0:11:32.600 --> 0:11:35.560 to support I V I P V four addresses for 0:11:35.600 --> 0:11:39.720 a while past there, I would say, past their shelf life. UM, 0:11:39.800 --> 0:11:42.360 but yeah, this is the decision. They realized this was 0:11:42.400 --> 0:11:45.319 going to happen in the early nineties and in the 0:11:45.360 --> 0:11:47.840 mid nineties they were working on a way to to 0:11:47.960 --> 0:11:50.920 figure this out, and it wasn't until the UH till, 0:11:51.960 --> 0:11:54.120 which at this point seems like a long time ago. 0:11:55.120 --> 0:11:56.720 But it's a long time ago when you think that 0:11:56.720 --> 0:11:59.480 that was when this was proposed. Yes, but the Internet 0:11:59.480 --> 0:12:02.560 Engineering hask Force, by the way, it does not much 0:12:02.600 --> 0:12:07.040 care for that. Yeah. Well, and they actually prefer the 0:12:07.080 --> 0:12:11.360 idea of every device having its own public address as 0:12:11.360 --> 0:12:15.280 opposed to having a middleman like you can think of 0:12:15.280 --> 0:12:18.520 that router almost like a mailman, Like the mailman gets 0:12:18.559 --> 0:12:19.920 all the mail in the bag and then has to 0:12:20.000 --> 0:12:21.720 deliver it to the right houses. The only thing is 0:12:21.760 --> 0:12:23.440 that in this case the mailman is also the one 0:12:23.480 --> 0:12:26.960 who assigns the addresses to the houses, and the addresses 0:12:27.000 --> 0:12:31.040 can change over time. Yeah, it is, it is inelegant, 0:12:31.880 --> 0:12:35.960 but it is a solution. But the thing is um 0:12:36.000 --> 0:12:38.800 another another thing that factored into this that I I 0:12:38.880 --> 0:12:42.080 haven't read, but I'm guessing based on my UH history 0:12:42.080 --> 0:12:45.320 of working at an Internet service provider, I would guess 0:12:45.360 --> 0:12:48.600 that I I p V four also survived a little 0:12:48.600 --> 0:12:51.800 longer than it probably would have ordinarily because so many 0:12:51.880 --> 0:12:56.960 people in the nineties were using dial up service and 0:12:57.480 --> 0:13:02.280 it's really coming to uh, you know a point where 0:13:02.320 --> 0:13:05.400 we have to make a move now, especially because so 0:13:05.440 --> 0:13:09.120 many more people are using um, you know, broadband connections 0:13:09.120 --> 0:13:11.080 that don't that you don't have to get off. And 0:13:11.120 --> 0:13:13.800 then we're getting things so you stay connected all the time, 0:13:13.880 --> 0:13:16.120 and you've got things like lt E and y max 0:13:16.200 --> 0:13:20.080 that are also starting to to create issues as well. 0:13:20.320 --> 0:13:22.920 You're you know, your tablet has an IP address, your 0:13:22.960 --> 0:13:25.680 phone has an IP address, your computer has an IP address, 0:13:25.720 --> 0:13:28.199 your netbook has an IP address, and then so does 0:13:28.240 --> 0:13:31.920 everyone else's. Yeah, and that they're not giving them up exactly. 0:13:32.120 --> 0:13:34.880 And like we said in February two eleven, the last 0:13:34.960 --> 0:13:37.720 free block of I p V four addresses was a sign. 0:13:37.800 --> 0:13:40.079 Now that doesn't mean again like there's still I P 0:13:40.240 --> 0:13:43.480 addresses out there in these various blocks that have not 0:13:43.640 --> 0:13:48.720 been assigned. Um uh two individuals or two machines. But 0:13:49.440 --> 0:13:51.480 it's just a matter of time before those run out. 0:13:51.840 --> 0:13:55.880 So the solution really that the I E t F. 0:13:56.120 --> 0:13:58.439 That's the that's the Internet Engineering Task Force that we 0:13:58.520 --> 0:14:02.480 talked about a couple of times eight I need UM. 0:14:02.559 --> 0:14:06.680 The solution that they proposed was sort of a a 0:14:06.760 --> 0:14:10.440 nuclear bomb solution to this problem. You know, there are 0:14:10.480 --> 0:14:14.480 times where we accuse engineers of taking the the bare 0:14:14.520 --> 0:14:17.160 minimum number of steps in order to solve a problem. 0:14:17.200 --> 0:14:19.960 For example, the Y two K problem. Part of that 0:14:20.040 --> 0:14:23.000 was an issue with encoding the year as a two 0:14:23.000 --> 0:14:25.840 digit number, and so what happens when it hits zero 0:14:25.920 --> 0:14:28.720 zero and rolls over and there? That was what caused 0:14:28.720 --> 0:14:31.160 that whole y two k panic, which some of you 0:14:31.200 --> 0:14:33.840 may not even be old enough to remember. I remember 0:14:33.880 --> 0:14:36.240 it very well because I remember having a Y two 0:14:36.320 --> 0:14:39.080 k New Year's Eve party in Athens, Georgia with a 0:14:39.120 --> 0:14:41.960 bunch of my friends where we dance to the song 0:14:43.040 --> 0:14:47.440 about fifty billion times um. So the I E T 0:14:47.560 --> 0:14:50.120 F solution was, well, if the I p V four 0:14:50.200 --> 0:14:53.960 uses a thirty two bit system, let's let's amp that 0:14:54.040 --> 0:14:56.360 up a bit. And they didn't go to sixty four bit, 0:14:56.680 --> 0:14:59.720 which would have made quite a few more addresses. No, no, no, 0:15:00.120 --> 0:15:03.000 they went all the way to one hundred twenty eight bit, 0:15:03.520 --> 0:15:08.320 which increases the number of addresses dramatically. And that's an 0:15:08.400 --> 0:15:11.760 understatement if ever there was one. Yes, do you know 0:15:11.880 --> 0:15:14.360 how many addresses there will be under a hundred twenty 0:15:14.400 --> 0:15:18.160 eight bit? Would you like to? Actually I did have 0:15:18.280 --> 0:15:24.000 that down according to mine notes too to the hundred power. 0:15:24.440 --> 0:15:28.800 That's no one understands that number. Chris, Well, you you 0:15:28.840 --> 0:15:34.160 provide a better solution. Here we go three hundred forty death, sillion, 0:15:34.280 --> 0:15:38.240 two hundred eighty two, non nillion, three hundred sixty six, octillion, 0:15:38.320 --> 0:15:41.560 nine hundred twenty septillion, nine hundred thirty eight, sex tillion, 0:15:41.640 --> 0:15:45.120 four hundred sixty three, quintillion, three hundred seventy four, quadrillion, 0:15:45.200 --> 0:15:48.080 six hundred seven trillion, four hundred thirty one billion, seven 0:15:48.320 --> 0:15:51.440 sixty eight million, two hundred eleven thousand, four hundred fifty six. 0:15:55.400 --> 0:15:57.600 Or if you want to really just make that simple, 0:15:57.800 --> 0:16:00.120 you can write down three four zero and then at 0:16:00.200 --> 0:16:04.320 thirty six zeros behind it. That's that's a that's rounding 0:16:04.440 --> 0:16:08.240 down how many addresses there will be under there are 0:16:08.320 --> 0:16:10.360 under I p V six. I shouldn't say will be, 0:16:10.360 --> 0:16:14.400 because I p V six is implemented right now, it's 0:16:14.440 --> 0:16:18.440 just not widely deployed. I'm sorry. While you were doing that, 0:16:18.480 --> 0:16:22.040 I got you a sandwich. I hope it's awesome. So, 0:16:22.160 --> 0:16:26.200 um yeah, there, that's that's you might wonder it's spicy 0:16:26.360 --> 0:16:31.520 must now, um you might. Well, let's let's before we 0:16:31.560 --> 0:16:34.520 go into adoption. Well, Yeah. One of the things that's 0:16:34.600 --> 0:16:39.400 kind of neat about this UM is it's it's much 0:16:39.440 --> 0:16:42.280 the address is here much longer now, as I was 0:16:42.280 --> 0:16:45.560 saying before, UM, with some exceptions, the minimum value you 0:16:45.600 --> 0:16:48.480 have you have four sets of numbers and an IPv 0:16:48.640 --> 0:16:52.000 four address, four sets of eight bit number, dot number, 0:16:52.040 --> 0:16:54.800 dot number, dot number, and the number can be between 0:16:54.920 --> 0:16:58.080 zero and two five five there. You can't add any 0:16:58.080 --> 0:17:00.440 more numbers on top of that. That's as far as 0:17:00.440 --> 0:17:04.040 it goes, and that's how you create these these addresses. 0:17:04.400 --> 0:17:09.719 But for my research, the the addresses are physically longer 0:17:09.800 --> 0:17:13.639 as well, because in yes, in addition to and in 0:17:13.720 --> 0:17:17.439 addition to numbers, you can also include letters address. It's 0:17:17.480 --> 0:17:20.640 because it's uh an IPv six address, you can write 0:17:20.680 --> 0:17:23.240 that out as an it's a series of well, it's 0:17:23.320 --> 0:17:27.600 eight sixteen bit values. So instead of four eight bit values, 0:17:27.600 --> 0:17:29.639 which is the thirty two bit address of I p 0:17:29.800 --> 0:17:33.679 V four, it's eight sixteen bit values. And you can 0:17:33.760 --> 0:17:38.200 use hexadecimal format, and instead of periods between the numbers, 0:17:38.280 --> 0:17:41.040 which is what how we see an IPv for address, 0:17:41.440 --> 0:17:44.600 use Colon's so UM. I got this from ours Technica. 0:17:44.680 --> 0:17:47.320 Ours Technica has a great article about I p V 0:17:47.520 --> 0:17:50.840 six um, and so I would I'm just gonna read 0:17:50.840 --> 0:17:53.760 off the sample address that they used in their article, 0:17:54.400 --> 0:17:59.040 which was to zero zero one, colon d b eight, 0:17:59.160 --> 0:18:03.920 colon three one, colon one, colon two zero A, colon 0:18:04.119 --> 0:18:08.520 nine five f f colon f e F five, colon 0:18:08.680 --> 0:18:12.280 two four six E. Now, when you can see formats 0:18:12.320 --> 0:18:14.240 like that, you can imagine, Yeah, there's gonna be a 0:18:14.320 --> 0:18:18.600 huge variety, which was pretty clear from my my my 0:18:19.680 --> 0:18:24.800 recitation of the number, and that certainly solves the problem 0:18:24.920 --> 0:18:28.119 of how many devices can connect to the Internet at 0:18:28.200 --> 0:18:30.960 a at a time, each with its own address. In fact, 0:18:31.000 --> 0:18:35.520 according to the ARS Technica article, uh, essentially our son 0:18:35.640 --> 0:18:40.280 will wither and die before we run out of addresses, 0:18:40.640 --> 0:18:44.600 even plotting the same or increased population growth that we're 0:18:44.600 --> 0:18:49.600 experiencing right now on and then assuming that the number 0:18:49.640 --> 0:18:53.320 of devices each person has increases as well. It's just 0:18:53.680 --> 0:18:58.680 it's such an enormous number that there's no conceivable way 0:18:58.680 --> 0:19:01.560 we could run out within the span of time that 0:19:01.600 --> 0:19:05.320 we the human race would be around. Another cool feature 0:19:05.400 --> 0:19:08.639 of the address, I'm just I'm trying to get my 0:19:08.680 --> 0:19:10.399 head around that, and I figured I should just move on. 0:19:10.600 --> 0:19:13.320 Another cool feature of I P. B. Six addresses is 0:19:13.359 --> 0:19:15.879 that if you have a section that has all zeros 0:19:15.880 --> 0:19:19.320 in it, you can skip it. Yeah, any any sequence 0:19:19.400 --> 0:19:21.479 as long as you can skip it once. So if 0:19:21.480 --> 0:19:24.080 you have if you had two sequences of zeros, like 0:19:24.119 --> 0:19:25.879 if you had a sequence of zeros and then a 0:19:25.960 --> 0:19:27.960 number and then another sequence of zeros, I'm not sure 0:19:28.040 --> 0:19:30.280 you can skip both of them. I believe you. Well, Okay, 0:19:30.400 --> 0:19:34.000 According to a paper I found from the University Hawaii 0:19:34.000 --> 0:19:37.479 by A. Wilson Chan, Um, you can, oh, okay, if 0:19:37.480 --> 0:19:40.800 there are no if there are no other characters in 0:19:40.840 --> 0:19:43.040 there besides zeros, you can. And you do this with 0:19:43.080 --> 0:19:45.879 a double colon. Yeah, so if you had if you 0:19:45.920 --> 0:19:50.000 had a section on your address, actually you could technically 0:19:50.040 --> 0:19:54.240 have zero colon, zero colon, zero colon, zero colon, zero 0:19:54.320 --> 0:19:56.400 colon all the way down to one and you could 0:19:56.440 --> 0:20:00.320 just change that to colon colon one. I don't know 0:20:00.359 --> 0:20:03.840 if that works, according to ours Technica does well, okay, 0:20:04.000 --> 0:20:06.840 So yeah, yeah, I mean multiple, multiple sections of zeros 0:20:06.880 --> 0:20:09.520 can be replaced with that double colon. So that's really 0:20:09.560 --> 0:20:13.520 cool too that you can use that as shorthand. Now, um, 0:20:13.600 --> 0:20:17.800 you were right though, Although people have been taking up 0:20:17.840 --> 0:20:20.679 i p v six. They're not not. Everybody is in 0:20:20.480 --> 0:20:22.440 a in a great big hurry to do this. Why 0:20:22.480 --> 0:20:25.480 because I would guess because it involves labor, and people 0:20:25.520 --> 0:20:28.280 are saying, well, the IPv for addresses are working just 0:20:28.320 --> 0:20:30.600 fine until I have to. I'm not gonna be exactly 0:20:30.720 --> 0:20:33.040 if it ain't broke, don't fix it now here. Here's 0:20:33.040 --> 0:20:34.720 the thing. In order to switch over to i p 0:20:34.840 --> 0:20:37.560 v six, you have to have support on multiple fronts. 0:20:38.000 --> 0:20:41.760 You have to have software support from the operating system front, 0:20:41.840 --> 0:20:44.840 which most I would say that. I think all modern 0:20:44.880 --> 0:20:47.439 operating systems, like all the most current operating systems support 0:20:47.480 --> 0:20:50.560 I p v six and I know that that uh 0:20:50.840 --> 0:20:55.399 Windows and the macOS, and I'm pretty darn sure that 0:20:55.640 --> 0:20:59.680 Lennox for a while now. They all have for several iterations. 0:20:59.680 --> 0:21:01.879 Window Vista was the first one to support it, and 0:21:01.880 --> 0:21:03.800 even Windows XP. I think there was a way where 0:21:03.800 --> 0:21:05.640 you could you could do it. It just wasn't doing 0:21:05.800 --> 0:21:08.960 It wasn't native to Windows XP. But Windows Vista and 0:21:09.000 --> 0:21:12.680 Windows seven both support it natively. Mac Os does as well, 0:21:12.760 --> 0:21:15.840 and I'm sure Lenox doesn't. I can't imagine considering and 0:21:16.160 --> 0:21:20.040 considering Google's role in advocating for I p v six. 0:21:20.119 --> 0:21:22.680 I bet chromos is as well. I would be. I 0:21:22.680 --> 0:21:26.439 would be surprised to find otherwise I would I would 0:21:26.480 --> 0:21:29.040 be about as shocked as I possibly could be. So 0:21:29.480 --> 0:21:31.200 you've got that. You have to have the support on 0:21:31.240 --> 0:21:34.760 the operating system and for the so that your computer 0:21:35.440 --> 0:21:39.560 can actually send information across I p v six protocols 0:21:39.600 --> 0:21:42.719 and then through the Internet. Okay, I got that. Well. 0:21:42.800 --> 0:21:44.880 Now you also have to make sure that all the 0:21:44.960 --> 0:21:49.159 other devices on the Internet are working on the I 0:21:49.280 --> 0:21:52.639 p v six protocols. So in some cases, with things 0:21:52.680 --> 0:21:54.800 like routers and nodes, you may have to have a 0:21:54.880 --> 0:21:59.560 firmware or software update so that you can either. Um, 0:22:00.359 --> 0:22:03.320 it's almost like teaching these machines how to handle a 0:22:03.359 --> 0:22:06.960 different format of information. Now, in some cases, you're gonna 0:22:06.960 --> 0:22:11.919 have devices that are truly physically incapable of transmitting I 0:22:12.080 --> 0:22:15.359 p v six UH data. They just they won't be 0:22:15.560 --> 0:22:18.919 because they're limited to I p v four. And in 0:22:18.920 --> 0:22:21.199 those cases, what would be required that you would have 0:22:21.200 --> 0:22:22.879 to go in and replace them. You would actually have 0:22:22.880 --> 0:22:25.800 to physically replace those machines with machines capable of running 0:22:25.800 --> 0:22:29.000 I p v six protocols. Okay, I'll be right back, 0:22:29.080 --> 0:22:30.440