1
00:00:04,160 --> 00:00:07,480
Speaker 1: Get in tech with technology with tech Stuff from stuff

2
00:00:07,520 --> 00:00:14,000
Speaker 1: works dot com. Hey there, and welcome to tex Stuff.

3
00:00:14,040 --> 00:00:17,680
Speaker 1: I'm your host, Jonathan Strickland. I'm an executive producer over

4
00:00:17,760 --> 00:00:20,160
Speaker 1: at how Stuff Works and I love all things tech,

5
00:00:20,640 --> 00:00:24,520
Speaker 1: and today we're going to talk about a pretty technical subject.

6
00:00:24,600 --> 00:00:26,440
Speaker 1: And just to get this out of the way, I

7
00:00:26,520 --> 00:00:30,600
Speaker 1: am getting over a cold and it's pollen season here

8
00:00:30,640 --> 00:00:35,640
Speaker 1: in Atlanta already, so I might sound a little extra

9
00:00:35,720 --> 00:00:39,440
Speaker 1: grungy today. Uh just just blame that on on my

10
00:00:39,520 --> 00:00:43,839
Speaker 1: health and Nirvana. But recently a listener asked me to

11
00:00:43,920 --> 00:00:47,760
Speaker 1: give an update on the switchover to I p V six,

12
00:00:47,760 --> 00:00:50,320
Speaker 1: which I thought presented a great opportunity to talk about

13
00:00:50,400 --> 00:00:53,800
Speaker 1: what that actually means, why it's important, as well as

14
00:00:54,200 --> 00:00:57,520
Speaker 1: what progress has been made in this switchover. Now. It

15
00:00:57,560 --> 00:01:01,320
Speaker 1: all boils down to solving April saying problem, which is

16
00:01:01,400 --> 00:01:04,040
Speaker 1: that the old set of rules we relied upon for

17
00:01:04,080 --> 00:01:07,679
Speaker 1: the Internet just aren't quite sufficient to keep up with

18
00:01:07,760 --> 00:01:11,640
Speaker 1: the way we're using the Internet. So first we need

19
00:01:11,680 --> 00:01:15,520
Speaker 1: to define what is i P. It stands for Internet Protocol,

20
00:01:15,720 --> 00:01:19,560
Speaker 1: which sounds a little daunting, but really that just means

21
00:01:19,640 --> 00:01:22,440
Speaker 1: it's the method or set of rules that the Internet

22
00:01:22,480 --> 00:01:26,280
Speaker 1: follows in order to send data between computers or other

23
00:01:26,319 --> 00:01:30,399
Speaker 1: devices that are interconnected within this network of networks. In

24
00:01:30,480 --> 00:01:34,600
Speaker 1: protocol speak, we typically refer to these devices as hosts,

25
00:01:35,319 --> 00:01:38,040
Speaker 1: and from a high level, the rules are pretty straightforward,

26
00:01:38,120 --> 00:01:41,360
Speaker 1: but they are absolutely necessary. Without these rules, it would

27
00:01:41,360 --> 00:01:44,640
Speaker 1: be pretty challenging to find what you're looking for when

28
00:01:44,680 --> 00:01:47,040
Speaker 1: you connect to the Internet. So let's take a very

29
00:01:47,120 --> 00:01:50,240
Speaker 1: simple connection and that way we can build on that

30
00:01:50,280 --> 00:01:53,240
Speaker 1: to understand what the challenges are. Back in the good

31
00:01:53,240 --> 00:01:56,840
Speaker 1: old Bolton Board System days, the BBS days, you would

32
00:01:56,880 --> 00:02:00,800
Speaker 1: typically have one machine acting like a server. Everything would

33
00:02:01,080 --> 00:02:05,160
Speaker 1: live on that machine and it would serve data to

34
00:02:05,280 --> 00:02:08,280
Speaker 1: a single client at a time. So that meant you

35
00:02:08,320 --> 00:02:12,240
Speaker 1: add one computer or host in the terminology of the Internet,

36
00:02:12,639 --> 00:02:15,680
Speaker 1: and this one is the server that has all the

37
00:02:15,720 --> 00:02:19,680
Speaker 1: message boards, files, games, whatever the Bolton Board System might have.

38
00:02:20,520 --> 00:02:24,200
Speaker 1: The people who want to visit the BBS would use

39
00:02:24,240 --> 00:02:27,240
Speaker 1: a dial up modem on their personal computer. This is

40
00:02:27,240 --> 00:02:30,600
Speaker 1: another host in Internet parlance, but we also would call

41
00:02:30,639 --> 00:02:33,080
Speaker 1: it a client and they would use that to call

42
00:02:33,320 --> 00:02:37,280
Speaker 1: up the server computer over a normal phone line. So

43
00:02:37,360 --> 00:02:39,160
Speaker 1: it's just like if you were to make a phone

44
00:02:39,160 --> 00:02:43,079
Speaker 1: call to somebody else. The connection was direct, or at

45
00:02:43,200 --> 00:02:45,520
Speaker 1: least as direct as a connection can be when it

46
00:02:45,520 --> 00:02:49,840
Speaker 1: crosses over telecommunications infrastructure like phone lines. The point is

47
00:02:50,280 --> 00:02:54,720
Speaker 1: the client and server communicated directly with one another. The

48
00:02:54,800 --> 00:02:57,880
Speaker 1: data didn't need to pass through any third party hosts.

49
00:02:58,240 --> 00:03:02,000
Speaker 1: A good analogy is the old two cans and a

50
00:03:02,120 --> 00:03:04,920
Speaker 1: string method of communication. You know, you got a can

51
00:03:04,919 --> 00:03:06,440
Speaker 1: on one side and a can on the other, string

52
00:03:06,480 --> 00:03:08,720
Speaker 1: connecting the two, and you speak, and the vibrations go

53
00:03:08,800 --> 00:03:11,160
Speaker 1: through the string and are amplified on the other side,

54
00:03:11,200 --> 00:03:14,000
Speaker 1: and thus you can talk well. The two computers in

55
00:03:14,000 --> 00:03:17,600
Speaker 1: this example are those cans, and the phone infrastructure would

56
00:03:17,639 --> 00:03:22,960
Speaker 1: be the string. But the Internet consists of millions of computers,

57
00:03:22,960 --> 00:03:26,799
Speaker 1: plus routers and switches and other devices that are all

58
00:03:26,880 --> 00:03:30,720
Speaker 1: interconnected in various ways. Whenever you visit a website or

59
00:03:30,800 --> 00:03:33,359
Speaker 1: you send an email, you're sending and receiving data to

60
00:03:33,680 --> 00:03:36,560
Speaker 1: and from other devices connected to that network, and some

61
00:03:36,680 --> 00:03:39,520
Speaker 1: of them might be across the world from each other,

62
00:03:39,800 --> 00:03:42,280
Speaker 1: which means there have to be rules in place for

63
00:03:42,320 --> 00:03:45,880
Speaker 1: your messages to get to the right computers, and those

64
00:03:45,880 --> 00:03:48,280
Speaker 1: computers have to know where to send the data back

65
00:03:48,440 --> 00:03:52,720
Speaker 1: to you in response to your requests. Part of the

66
00:03:52,760 --> 00:03:56,840
Speaker 1: Internet protocol addresses this very issue, and yes, that is

67
00:03:56,960 --> 00:04:00,560
Speaker 1: kind of a pun. It's called IP addresses. An IP

68
00:04:00,720 --> 00:04:05,320
Speaker 1: address is a unique identifier for every computer or connected

69
00:04:05,360 --> 00:04:10,120
Speaker 1: device on the Internet. Uh, anything that's directly communicating with

70
00:04:10,240 --> 00:04:13,000
Speaker 1: the Internet has to have an IP address, and it's

71
00:04:13,040 --> 00:04:15,880
Speaker 1: similar to a physical address that we would use for

72
00:04:16,040 --> 00:04:19,600
Speaker 1: mailing things in that it provides a means for computers

73
00:04:19,640 --> 00:04:23,320
Speaker 1: to locate the right destination for data. But unlike a

74
00:04:23,400 --> 00:04:27,360
Speaker 1: physical address, a machine's IP address doesn't necessarily always stay

75
00:04:27,440 --> 00:04:30,760
Speaker 1: the same. It can it can be a static IP address,

76
00:04:30,800 --> 00:04:34,560
Speaker 1: but it's pretty common to run into dynamic IP addresses,

77
00:04:34,720 --> 00:04:37,479
Speaker 1: which means they can change depending upon the local network

78
00:04:37,600 --> 00:04:41,200
Speaker 1: that it connects to the router that's in charge. Lots

79
00:04:41,200 --> 00:04:45,080
Speaker 1: of different things can determine what a machine's IP address

80
00:04:45,240 --> 00:04:48,320
Speaker 1: is at any given time. Now, the idea for IP

81
00:04:48,400 --> 00:04:52,159
Speaker 1: addresses goes back much further than most people's experience with

82
00:04:52,279 --> 00:04:55,640
Speaker 1: the Internet, unless you were a researcher or an engineer.

83
00:04:56,000 --> 00:04:58,640
Speaker 1: The debut of the Worldwide Web in the early nineties

84
00:04:58,720 --> 00:05:01,880
Speaker 1: kind of helped usher in a new era of computer users,

85
00:05:01,920 --> 00:05:05,159
Speaker 1: but the Internet itself had been around for a decade

86
00:05:05,360 --> 00:05:08,440
Speaker 1: before the Web was a thing. Those rules had to

87
00:05:08,480 --> 00:05:10,640
Speaker 1: be in place for the Internet to work, and they were,

88
00:05:10,720 --> 00:05:13,480
Speaker 1: in fact an evolution of the rules that engineers were

89
00:05:13,520 --> 00:05:17,400
Speaker 1: creating when they built the predecessor to the Internet, called

90
00:05:17,400 --> 00:05:21,480
Speaker 1: our Bonnet. Our Bonnet was a Department of Defense project.

91
00:05:21,680 --> 00:05:24,200
Speaker 1: Those working on the project, we're creating the framework and

92
00:05:24,320 --> 00:05:29,440
Speaker 1: rules within which different computers built on different architectures could

93
00:05:29,520 --> 00:05:34,200
Speaker 1: meaningfully communicate across a network. This was a pretty hefty undertaking,

94
00:05:34,279 --> 00:05:37,119
Speaker 1: but I've talked about it in other episodes of Tech Stuff,

95
00:05:37,120 --> 00:05:39,320
Speaker 1: so I'm not gonna go all the way through that

96
00:05:39,400 --> 00:05:42,080
Speaker 1: again right here and right now. You can find the

97
00:05:42,080 --> 00:05:44,440
Speaker 1: episodes on our Bonnet and listen to those. But in

98
00:05:44,520 --> 00:05:48,960
Speaker 1: a Request for Comments document and r FC document dating

99
00:05:49,000 --> 00:05:52,800
Speaker 1: from nineteen eighty, the team working on Internet protocols detailed

100
00:05:52,839 --> 00:05:56,719
Speaker 1: the necessity for addresses and helped clarify their role. Part

101
00:05:56,720 --> 00:05:59,880
Speaker 1: of that meant explaining what an address is and is not.

102
00:06:00,400 --> 00:06:03,440
Speaker 1: So here's a quote, a direct quote from RFC seven

103
00:06:03,520 --> 00:06:08,640
Speaker 1: sixty and yes, fasten your seat belts because it's really

104
00:06:08,680 --> 00:06:13,400
Speaker 1: exciting speech. A distinction is made between names, addresses, and routes.

105
00:06:13,800 --> 00:06:18,000
Speaker 1: A name indicates what we seek, an address indicates where

106
00:06:18,080 --> 00:06:21,919
Speaker 1: it is. A route indicates how to get there. The

107
00:06:21,960 --> 00:06:26,080
Speaker 1: Internet protocol deals primarily with addresses. Is the task of

108
00:06:26,240 --> 00:06:30,440
Speaker 1: higher level i e. Host to host or application protocols

109
00:06:30,760 --> 00:06:34,760
Speaker 1: to make the mapping from names to addresses, and so

110
00:06:34,800 --> 00:06:37,039
Speaker 1: a device would need a name and an address. The

111
00:06:37,120 --> 00:06:39,520
Speaker 1: route would be the pathway the data would take between

112
00:06:39,520 --> 00:06:42,400
Speaker 1: the hosts. Now, this isn't all that different from sending

113
00:06:42,480 --> 00:06:45,480
Speaker 1: snail mail in the real world. You can't just put

114
00:06:45,520 --> 00:06:47,760
Speaker 1: an envelope in a mailbox with a person's name on

115
00:06:47,800 --> 00:06:50,080
Speaker 1: it and expect the postal service to be able to

116
00:06:50,120 --> 00:06:53,320
Speaker 1: deliver it, unless I guess the name is Santa clause

117
00:06:53,839 --> 00:06:56,440
Speaker 1: you need to include an address on the envelope. The

118
00:06:56,480 --> 00:06:59,760
Speaker 1: postal service then takes the collected outgoing mail and to

119
00:06:59,800 --> 00:07:02,200
Speaker 1: turn emens how to deliver it, which is not that

120
00:07:02,320 --> 00:07:06,360
Speaker 1: different from how computers send data across the Internet. Now,

121
00:07:06,400 --> 00:07:08,920
Speaker 1: one thing that is a little different is how devices

122
00:07:08,920 --> 00:07:11,720
Speaker 1: on the Internet package data when they send it across

123
00:07:11,760 --> 00:07:14,920
Speaker 1: the Internet. Devices on the Internet send data in small

124
00:07:15,040 --> 00:07:19,480
Speaker 1: batches called packets. These packets are sort of like puzzle pieces.

125
00:07:19,520 --> 00:07:21,960
Speaker 1: They don't all have to take the same pathway to

126
00:07:22,000 --> 00:07:26,200
Speaker 1: get to their destination, where they are then reassembled into

127
00:07:26,240 --> 00:07:28,480
Speaker 1: whatever it is that you were sending. It's a pretty

128
00:07:28,600 --> 00:07:31,360
Speaker 1: ingenious design that helps avoid problems when a particular machine

129
00:07:31,360 --> 00:07:34,520
Speaker 1: on the network goes down. But let's get back to addresses,

130
00:07:34,560 --> 00:07:37,800
Speaker 1: because that's kind of a separate topic. In this request

131
00:07:37,840 --> 00:07:41,000
Speaker 1: for comments, the group also mentioned that addresses were a

132
00:07:41,080 --> 00:07:46,160
Speaker 1: fixed length of four octets or thirty two bits. Now,

133
00:07:46,200 --> 00:07:50,240
Speaker 1: a bit is a single unit of information. It can

134
00:07:50,280 --> 00:07:53,200
Speaker 1: take the form of a zero or a one. So

135
00:07:53,280 --> 00:07:57,120
Speaker 1: the team would refine this a bit in future RFC documents,

136
00:07:57,160 --> 00:08:02,200
Speaker 1: but for the time being four octets or four uh

137
00:08:02,240 --> 00:08:06,360
Speaker 1: eight bits four bytes. In other words, the thirty two

138
00:08:06,360 --> 00:08:09,480
Speaker 1: bits gave the team a lot of potential addresses to

139
00:08:09,520 --> 00:08:12,960
Speaker 1: play with. So each bit can have one of two states,

140
00:08:13,000 --> 00:08:15,040
Speaker 1: that being a zero or a one, and there are

141
00:08:15,120 --> 00:08:17,040
Speaker 1: thirty two of them total. So what you would do

142
00:08:17,120 --> 00:08:20,320
Speaker 1: is you take to the states and raise it to

143
00:08:20,320 --> 00:08:22,440
Speaker 1: the power of thirty two the number of bits. That

144
00:08:22,560 --> 00:08:26,840
Speaker 1: gives you a grand total of four billion, two hundred

145
00:08:27,000 --> 00:08:31,040
Speaker 1: ninety four million, nine hundred sixty seven thousand, two hundred

146
00:08:31,120 --> 00:08:36,000
Speaker 1: ninety six addresses. Almost Now why do I say almost,

147
00:08:36,320 --> 00:08:39,400
Speaker 1: because not all of those addresses are actually available to

148
00:08:39,520 --> 00:08:43,160
Speaker 1: the general world. The protocol reserves nearly two hundred ninety

149
00:08:43,200 --> 00:08:46,800
Speaker 1: million addresses for specialized purposes, but still more than four

150
00:08:46,840 --> 00:08:49,280
Speaker 1: billion addresses. Seemed like they were going to be plenty

151
00:08:49,520 --> 00:08:52,520
Speaker 1: way back in nineteen eighty. Now, the way we typically

152
00:08:52,559 --> 00:08:55,040
Speaker 1: see those addresses written out is in a series of

153
00:08:55,080 --> 00:08:59,080
Speaker 1: decimal numbers separated by periods. For example, you might see

154
00:08:59,080 --> 00:09:04,520
Speaker 1: an address like this two hundred sixteen dot dot sixty

155
00:09:04,600 --> 00:09:09,080
Speaker 1: one dot seven. Those are your four octets, except they're

156
00:09:09,080 --> 00:09:13,840
Speaker 1: being represented as decimal numbers, not as bits. So you'll

157
00:09:13,840 --> 00:09:16,600
Speaker 1: never see a number higher than two hundred fifty five

158
00:09:16,760 --> 00:09:19,880
Speaker 1: in any of those four spots. And why is that, Well,

159
00:09:19,880 --> 00:09:24,480
Speaker 1: it's because the highest number eight bets can represent would

160
00:09:24,480 --> 00:09:30,120
Speaker 1: be two fifty six. So you start with zero, you

161
00:09:30,160 --> 00:09:32,480
Speaker 1: can go up to two five. If we started with

162
00:09:32,559 --> 00:09:34,120
Speaker 1: just one and built up, we could go all the

163
00:09:34,120 --> 00:09:35,760
Speaker 1: way up to two fifty six. But we start with

164
00:09:35,880 --> 00:09:38,559
Speaker 1: zero because we're talking about base ten, so once you

165
00:09:38,640 --> 00:09:40,280
Speaker 1: hit nine, you need to be able to flip back

166
00:09:40,280 --> 00:09:43,520
Speaker 1: over to zero. So two five is the largest number

167
00:09:43,600 --> 00:09:46,320
Speaker 1: that can occupy any of those four spots. If we

168
00:09:46,360 --> 00:09:48,760
Speaker 1: wrote out that same IP address I just mentioned the

169
00:09:48,920 --> 00:09:52,720
Speaker 1: to sixteen dot seven dot sixty one dot one seven,

170
00:09:52,880 --> 00:09:55,480
Speaker 1: it would look like this in binary code, and I

171
00:09:55,520 --> 00:09:57,800
Speaker 1: apologize ahead of time because you're gonna hear a lot

172
00:09:57,840 --> 00:10:00,760
Speaker 1: of ones and zeros, guys. But this is why they

173
00:10:00,800 --> 00:10:03,920
Speaker 1: decided to switch over to a decimal based system for notation.

174
00:10:04,160 --> 00:10:08,200
Speaker 1: The binary address would be one one zero one one

175
00:10:08,559 --> 00:10:13,960
Speaker 1: zero zero zero, dot zero zero zero one one zero

176
00:10:14,040 --> 00:10:19,160
Speaker 1: one one dot zero zero one one one one zero

177
00:10:19,240 --> 00:10:24,040
Speaker 1: one dot one zero zero zero one zero zero one.

178
00:10:24,440 --> 00:10:26,600
Speaker 1: And yes, it sounds like I just did the binary

179
00:10:26,679 --> 00:10:29,800
Speaker 1: solo from the humans are dead by fly of the concords.

180
00:10:30,320 --> 00:10:32,960
Speaker 1: It doesn't exactly roll off the tongue, so you can

181
00:10:33,000 --> 00:10:35,320
Speaker 1: see why the team decided to go with that decimal

182
00:10:35,360 --> 00:10:39,079
Speaker 1: based system. Now, at a higher level than the Internet protocol,

183
00:10:39,360 --> 00:10:41,319
Speaker 1: there are rules in place that allow us to use

184
00:10:41,360 --> 00:10:44,480
Speaker 1: stuff like domain names and file pathways to make it

185
00:10:44,559 --> 00:10:48,000
Speaker 1: easier to direct emails or go web browsing to where

186
00:10:48,040 --> 00:10:51,559
Speaker 1: we want to go. In tim Burners, Lee introduced the

187
00:10:51,600 --> 00:10:54,719
Speaker 1: concept of uniform resource locators or u r l s.

188
00:10:55,200 --> 00:10:56,760
Speaker 1: But all of that is just a way to make

189
00:10:56,760 --> 00:11:00,120
Speaker 1: it easier for us humans to navigate the Internet and

190
00:11:00,160 --> 00:11:03,000
Speaker 1: the Web. On the machine level, it's all about the bits,

191
00:11:03,440 --> 00:11:06,200
Speaker 1: all right. So we have our four octets of bits,

192
00:11:06,280 --> 00:11:10,360
Speaker 1: each representing a decimal number in that series of four numbers.

193
00:11:10,400 --> 00:11:13,200
Speaker 1: This set of rules was part of the fourth version

194
00:11:13,360 --> 00:11:16,600
Speaker 1: of the Internet Protocol, so we tend to call these

195
00:11:16,720 --> 00:11:21,760
Speaker 1: i p v four addresses or just IP address for short. Typically,

196
00:11:21,800 --> 00:11:24,400
Speaker 1: if someone says IP address, they're talking about i p

197
00:11:24,640 --> 00:11:27,839
Speaker 1: v four. So what happened to versions one through three, Well,

198
00:11:27,840 --> 00:11:31,199
Speaker 1: those were all experimental versions of Internet Protocol that were

199
00:11:31,200 --> 00:11:35,400
Speaker 1: never rolled out for general public use. Now, originally IPv

200
00:11:35,559 --> 00:11:38,520
Speaker 1: four divided up the octets to designate networks and hosts.

201
00:11:38,960 --> 00:11:41,760
Speaker 1: In other words, part of the address would tell the

202
00:11:41,800 --> 00:11:46,160
Speaker 1: system which network your computer was on, and the rest

203
00:11:46,200 --> 00:11:49,120
Speaker 1: of the address would be specific to your actual computer

204
00:11:49,320 --> 00:11:53,079
Speaker 1: on that network. Because remember, the Internet is a network

205
00:11:53,320 --> 00:11:57,320
Speaker 1: of networks. It's not like each computer is just independently

206
00:11:57,880 --> 00:12:03,240
Speaker 1: plugging into a giant web of data. These are hierarchies

207
00:12:03,280 --> 00:12:05,920
Speaker 1: that we're looking at. So this is not again that

208
00:12:06,080 --> 00:12:09,040
Speaker 1: different from an address on an envelope, because on an

209
00:12:09,040 --> 00:12:12,600
Speaker 1: address and an envelope you'll have general information such as

210
00:12:12,679 --> 00:12:15,560
Speaker 1: a country, a state, a city, that kind of thing,

211
00:12:16,040 --> 00:12:19,679
Speaker 1: and then more specific information like a house number and

212
00:12:19,760 --> 00:12:22,880
Speaker 1: a street that sort of thing. So again, very similar

213
00:12:22,920 --> 00:12:25,800
Speaker 1: to the way physical mail works. But even early on

214
00:12:25,880 --> 00:12:29,120
Speaker 1: while before the Web. The team working on Internet Protocol

215
00:12:29,240 --> 00:12:31,760
Speaker 1: realized that this was going to limit the useful number

216
00:12:31,760 --> 00:12:34,280
Speaker 1: of addresses a bit too much, and so in nine

217
00:12:34,960 --> 00:12:39,040
Speaker 1: they redefined the approach by creating five classes of networks.

218
00:12:39,040 --> 00:12:43,360
Speaker 1: They designated the classes from A to E. This became

219
00:12:43,400 --> 00:12:47,120
Speaker 1: known as class full networking. Now, classes D and E

220
00:12:47,360 --> 00:12:50,240
Speaker 1: contained the reserved addresses I talked about before. Some of

221
00:12:50,240 --> 00:12:53,640
Speaker 1: them were for uh experimental purposes and some of them

222
00:12:53,679 --> 00:12:57,319
Speaker 1: were reserved for other reasons. Classes A through C use

223
00:12:57,400 --> 00:13:01,439
Speaker 1: different bit lengths to designate specific networks. This removed the

224
00:13:01,480 --> 00:13:03,520
Speaker 1: tight restriction on the number of networks that could join

225
00:13:03,520 --> 00:13:06,199
Speaker 1: the Internet using IPD four, which up to that point

226
00:13:06,200 --> 00:13:09,080
Speaker 1: had been a measly two fifty six networks. If the

227
00:13:09,120 --> 00:13:11,920
Speaker 1: Internet only consisted of two ft six networks, we never

228
00:13:11,960 --> 00:13:15,600
Speaker 1: would have had to worry about adding this change. But

229
00:13:15,920 --> 00:13:18,640
Speaker 1: clearly that was not going to stay the same now.

230
00:13:18,800 --> 00:13:22,160
Speaker 1: If you connect your computer directly to your Internet service provider,

231
00:13:22,440 --> 00:13:25,120
Speaker 1: also known as your I s P, your computer would

232
00:13:25,120 --> 00:13:27,880
Speaker 1: get an IP address from that I s P. It

233
00:13:27,880 --> 00:13:32,040
Speaker 1: would have some sort of designation for this, but many

234
00:13:32,120 --> 00:13:35,679
Speaker 1: people are using routers or connecting to the network through

235
00:13:35,920 --> 00:13:38,880
Speaker 1: another network that has its own router, and in these cases,

236
00:13:39,200 --> 00:13:42,720
Speaker 1: the router has an IP address specific to it and

237
00:13:42,760 --> 00:13:46,240
Speaker 1: typically creates a subnetwork for all the devices or nodes

238
00:13:46,280 --> 00:13:50,120
Speaker 1: that connect through that router. So let's take our little

239
00:13:50,160 --> 00:13:53,640
Speaker 1: example again. So let's say your computer's IP address is

240
00:13:53,679 --> 00:13:57,360
Speaker 1: currently set to to sixty seven dot sixty one dot

241
00:13:57,400 --> 00:14:00,440
Speaker 1: one seven, and in this example, we'll say your network's

242
00:14:00,480 --> 00:14:04,400
Speaker 1: identity is represented in the first three octets, so that

243
00:14:04,440 --> 00:14:09,920
Speaker 1: means your network's identity is to sixteen dot dot sixty one.

244
00:14:10,400 --> 00:14:14,360
Speaker 1: The final octet designates the node on that network, in

245
00:14:14,400 --> 00:14:17,840
Speaker 1: other words, your computer, So you could theoretically have any

246
00:14:17,920 --> 00:14:22,320
Speaker 1: value from dot zero as the final one to dot to.

247
00:14:23,200 --> 00:14:25,680
Speaker 1: Now I say theoretically because this is a Class C

248
00:14:26,000 --> 00:14:28,960
Speaker 1: network and as such may not have an ending in

249
00:14:29,080 --> 00:14:31,240
Speaker 1: zero or two fifty five. But that gets a little

250
00:14:31,240 --> 00:14:33,880
Speaker 1: too technical. The computers on the network use a set

251
00:14:33,880 --> 00:14:37,359
Speaker 1: of rules called a subnet mask to separate the octets

252
00:14:37,400 --> 00:14:41,920
Speaker 1: that indicate networks versus nodes. Uh sub net masks in

253
00:14:42,320 --> 00:14:44,720
Speaker 1: I p V four follow up patterns. So the first

254
00:14:44,720 --> 00:14:47,960
Speaker 1: such mask is two five five dot zero dot zero

255
00:14:48,080 --> 00:14:53,000
Speaker 1: dot zero. This mask reserves eight bits to designate the networks.

256
00:14:53,040 --> 00:14:55,920
Speaker 1: That eight bits is in that first octet, the number

257
00:14:55,960 --> 00:14:59,520
Speaker 1: that's represented in there is two five, and then it

258
00:14:59,600 --> 00:15:03,040
Speaker 1: reserves the other twenty four bits to designate nodes, So

259
00:15:03,080 --> 00:15:05,640
Speaker 1: that would be a Class A network. On the flip side,

260
00:15:06,000 --> 00:15:08,440
Speaker 1: you have two five five dot two five five dot

261
00:15:08,480 --> 00:15:11,240
Speaker 1: two five five dot zero. That would mean you would

262
00:15:11,240 --> 00:15:15,480
Speaker 1: have twenty four bits the first three octets to designate

263
00:15:15,560 --> 00:15:19,480
Speaker 1: the network and only eight bits to designate the various nodes.

264
00:15:19,520 --> 00:15:22,280
Speaker 1: This would be a Class C network. These are called

265
00:15:22,320 --> 00:15:25,320
Speaker 1: masks because they guide routers to look at specific numbers

266
00:15:25,360 --> 00:15:28,400
Speaker 1: within the addresses, and by looking only at the numbers

267
00:15:28,440 --> 00:15:31,200
Speaker 1: that are pertinent to the network, the routers can save

268
00:15:31,240 --> 00:15:33,560
Speaker 1: some time. They don't have to process an entire thirty

269
00:15:33,560 --> 00:15:35,120
Speaker 1: two bit address. They just look at the bit of

270
00:15:35,160 --> 00:15:38,240
Speaker 1: the address that's important. Again, going back to the postal service,

271
00:15:38,520 --> 00:15:41,200
Speaker 1: this would be like if you had UH two major

272
00:15:41,240 --> 00:15:43,360
Speaker 1: piles and one of them is for local mail and

273
00:15:43,400 --> 00:15:46,040
Speaker 1: the other is for non local mail, and you look

274
00:15:46,040 --> 00:15:48,360
Speaker 1: at the address and just by looking at the bottom

275
00:15:48,400 --> 00:15:51,160
Speaker 1: line where you look at the the state, you know

276
00:15:51,400 --> 00:15:53,280
Speaker 1: is it local or nonlocal, and so you just do

277
00:15:53,360 --> 00:15:55,960
Speaker 1: a quick sorting that way. It's kind of similar to that.

278
00:15:56,160 --> 00:15:58,640
Speaker 1: But why would we have all these different classes. Anyway,

279
00:15:58,720 --> 00:16:01,200
Speaker 1: let's all in how a network work gets set up.

280
00:16:01,240 --> 00:16:04,640
Speaker 1: So a network administrator would make these sort of determinations. Uh,

281
00:16:04,680 --> 00:16:06,920
Speaker 1: if a network is going to have a lot of subnets,

282
00:16:06,960 --> 00:16:10,800
Speaker 1: you need more bits to designate networks. If the subnets

283
00:16:10,840 --> 00:16:12,840
Speaker 1: are going to have a lot of nodes, that is,

284
00:16:13,080 --> 00:16:15,880
Speaker 1: computers connected to those subnets, then you would need to

285
00:16:15,880 --> 00:16:19,720
Speaker 1: dedicate more bits for the node or a computer side

286
00:16:19,720 --> 00:16:22,400
Speaker 1: of things. It's all dependent upon the infrastructure of the network.

287
00:16:22,840 --> 00:16:25,240
Speaker 1: I'll explain a little bit more, but first, why don't

288
00:16:25,240 --> 00:16:35,120
Speaker 1: we take a quick break to thank our sponsor. All Right,

289
00:16:35,200 --> 00:16:38,560
Speaker 1: on the Internet itself, only the network part of an

290
00:16:38,560 --> 00:16:43,200
Speaker 1: IP address is important. Uh, the the Internet machines don't

291
00:16:43,280 --> 00:16:47,040
Speaker 1: care about your specific computers address. They just need to

292
00:16:47,040 --> 00:16:49,400
Speaker 1: know what network it needs to go to. Data will

293
00:16:49,440 --> 00:16:52,480
Speaker 1: move toward that appropriate network, and once it's there, the

294
00:16:52,520 --> 00:16:55,600
Speaker 1: host part of the address then becomes important. It's it's

295
00:16:55,640 --> 00:16:57,360
Speaker 1: kind of like once you get the mail to the

296
00:16:57,440 --> 00:17:00,000
Speaker 1: right state, then you need to start dividing it up

297
00:17:00,000 --> 00:17:03,000
Speaker 1: by a city and thus neighborhood and that kind of thing.

298
00:17:03,760 --> 00:17:07,320
Speaker 1: IP addresses can be static, which means they don't change,

299
00:17:07,600 --> 00:17:09,960
Speaker 1: or they can be dynamic, meaning they get assigned every

300
00:17:09,960 --> 00:17:12,840
Speaker 1: time the device connects to the Internet. Most devices in

301
00:17:12,880 --> 00:17:16,040
Speaker 1: the hands of consumers use dynamic IP addresses, and many

302
00:17:16,080 --> 00:17:19,680
Speaker 1: are connected to sub networks or subnets, which are networks

303
00:17:19,680 --> 00:17:23,399
Speaker 1: that share a common network address. A single company might

304
00:17:23,520 --> 00:17:28,560
Speaker 1: use subnets to share a single network address across all subnets,

305
00:17:28,560 --> 00:17:31,480
Speaker 1: even if they are geographically distant from one another, and

306
00:17:31,520 --> 00:17:34,200
Speaker 1: that helps conserve the number of network addresses that are

307
00:17:34,240 --> 00:17:38,280
Speaker 1: generally available. Even so, it didn't take very long for

308
00:17:38,359 --> 00:17:40,679
Speaker 1: the engineering team to realize that thirty two bits was

309
00:17:40,680 --> 00:17:42,879
Speaker 1: a big limiting factor, and so they set about to

310
00:17:42,920 --> 00:17:45,480
Speaker 1: solve this problem. Otherwise, the world would reach a limit

311
00:17:45,520 --> 00:17:48,320
Speaker 1: on the number of useful addresses, and no new networks

312
00:17:48,320 --> 00:17:50,480
Speaker 1: would be able to join the Internet. It would have

313
00:17:50,600 --> 00:17:55,000
Speaker 1: hit capacity. So with IPv four addresses again, we have

314
00:17:55,119 --> 00:17:58,320
Speaker 1: a little bit more than four billion available ones once

315
00:17:58,359 --> 00:18:01,280
Speaker 1: you take away the ones that have been reserved for

316
00:18:01,320 --> 00:18:04,680
Speaker 1: other purposes. A billion is admittedly a very large number,

317
00:18:04,720 --> 00:18:07,200
Speaker 1: but not nearly large enough. Even in the late eighties

318
00:18:07,200 --> 00:18:10,359
Speaker 1: and early nineties, engineers were saying this is gonna be

319
00:18:10,359 --> 00:18:13,320
Speaker 1: a problem. Things were changing quickly, and it soon became

320
00:18:13,359 --> 00:18:16,040
Speaker 1: clear that we'd hit a real crunch with IP addresses.

321
00:18:16,080 --> 00:18:18,800
Speaker 1: For one thing, there was an emerging trend of moving

322
00:18:18,840 --> 00:18:23,000
Speaker 1: from an on demand connection to the Internet to pervasive connections.

323
00:18:23,560 --> 00:18:25,320
Speaker 1: Now by that I mean in the early days, you

324
00:18:25,320 --> 00:18:27,960
Speaker 1: would typically use a dial up modem to connect to

325
00:18:28,000 --> 00:18:30,639
Speaker 1: the Internet, and frequently this meant that you were engaging

326
00:18:30,720 --> 00:18:34,400
Speaker 1: your homes one phone line so that you could call

327
00:18:34,560 --> 00:18:37,879
Speaker 1: up an Internet server and browse the Internet. So you

328
00:18:37,880 --> 00:18:40,800
Speaker 1: wouldn't stay on it forever because you need that phone

329
00:18:40,840 --> 00:18:44,400
Speaker 1: line for other things, and frankly, you could end up

330
00:18:44,560 --> 00:18:46,399
Speaker 1: racking up big charges if you were on for a

331
00:18:46,400 --> 00:18:50,120
Speaker 1: really long time, so you would typically hang up when

332
00:18:50,119 --> 00:18:52,880
Speaker 1: you were done. Now hanging up meant that you were

333
00:18:53,040 --> 00:18:55,240
Speaker 1: you had just freed up an IP address. You didn't

334
00:18:55,240 --> 00:18:58,320
Speaker 1: need that IP address anymore because you were no longer

335
00:18:58,320 --> 00:19:01,560
Speaker 1: connected to the Internet. So even if you had more

336
00:19:01,600 --> 00:19:03,760
Speaker 1: people than you had I P addresses, not everyone was

337
00:19:03,800 --> 00:19:05,480
Speaker 1: going to be connected at the same time, and so

338
00:19:05,520 --> 00:19:08,119
Speaker 1: you can kind of fudge things a little bit. But

339
00:19:08,200 --> 00:19:11,280
Speaker 1: then we gradually began to move toward more broadband connections

340
00:19:11,400 --> 00:19:14,600
Speaker 1: using things besides just dial up modems, and we also

341
00:19:14,640 --> 00:19:17,480
Speaker 1: started to make a move towards always connected devices. Now

342
00:19:17,520 --> 00:19:20,360
Speaker 1: this is even more true today when you have everything

343
00:19:20,400 --> 00:19:23,480
Speaker 1: from set top boxes like video game consoles, to wireless

344
00:19:23,520 --> 00:19:26,320
Speaker 1: devices like smart thrum, the stats and home security devices

345
00:19:26,320 --> 00:19:29,080
Speaker 1: to add in. Then there's an added problem that any

346
00:19:29,119 --> 00:19:31,679
Speaker 1: device that has multiple ways to connect to the Internet

347
00:19:31,800 --> 00:19:36,080
Speaker 1: needs a different i p address for each of those methods. So,

348
00:19:36,200 --> 00:19:39,159
Speaker 1: for example, if you have a smartphone that connects to

349
00:19:39,200 --> 00:19:43,879
Speaker 1: an LTE network as well as to a WiFi router UH,

350
00:19:43,920 --> 00:19:46,200
Speaker 1: it has to have an IP address for each of those,

351
00:19:46,359 --> 00:19:47,919
Speaker 1: Or if you have a laptop that has both a

352
00:19:47,920 --> 00:19:50,920
Speaker 1: wired and a wireless connection, has to have an IP

353
00:19:50,960 --> 00:19:53,560
Speaker 1: address for each of those, So a single device can

354
00:19:53,600 --> 00:19:56,760
Speaker 1: take up more than one IP address. And of course

355
00:19:56,800 --> 00:19:59,080
Speaker 1: the other big challenge was that more of the world

356
00:19:59,160 --> 00:20:02,760
Speaker 1: was going online. The Internet when it first got started

357
00:20:02,840 --> 00:20:08,600
Speaker 1: was kind of an exclusive club, really nerdy exclusive club,

358
00:20:08,640 --> 00:20:11,840
Speaker 1: but still exclusive. But now it was going global, so

359
00:20:11,880 --> 00:20:13,720
Speaker 1: there were just a lot more people trying to connect

360
00:20:13,720 --> 00:20:18,199
Speaker 1: and a new method of addressing was needed. In the

361
00:20:18,200 --> 00:20:21,760
Speaker 1: Internet Engineering Task Force developed the successor to i p

362
00:20:21,920 --> 00:20:24,840
Speaker 1: V four. This one was called i p V six,

363
00:20:25,240 --> 00:20:28,400
Speaker 1: So that immediately raises a question, why the heck did

364
00:20:28,400 --> 00:20:31,800
Speaker 1: we jump from four to six. Well, what would have

365
00:20:31,880 --> 00:20:35,359
Speaker 1: been Internet Protocol five was an Internet stream protocol that

366
00:20:35,440 --> 00:20:38,800
Speaker 1: was in development as far back as the late seventies. Ultimately,

367
00:20:38,840 --> 00:20:41,479
Speaker 1: that protocol never rolled out for public use, and it

368
00:20:41,520 --> 00:20:45,520
Speaker 1: also was never adopted as i p V five officially.

369
00:20:45,600 --> 00:20:47,640
Speaker 1: But back then no one was really sure how things

370
00:20:47,640 --> 00:20:49,080
Speaker 1: were going to turn out, and so they went with

371
00:20:49,119 --> 00:20:51,560
Speaker 1: i p V six to be safe. It expanded that

372
00:20:51,640 --> 00:20:55,879
Speaker 1: bit number for addresses from thirty two to one twenty eight,

373
00:20:56,480 --> 00:20:59,160
Speaker 1: and they don't look like i p V four addresses either,

374
00:20:59,600 --> 00:21:03,159
Speaker 1: and I V six address consists of eight groups of

375
00:21:03,280 --> 00:21:10,280
Speaker 1: four hexadecimal digits. The hexadecimal system is a base sixteen system.

376
00:21:10,640 --> 00:21:12,760
Speaker 1: So with a base ten system, you start at zero,

377
00:21:12,840 --> 00:21:15,400
Speaker 1: you go up to nine, and then you start over right,

378
00:21:15,640 --> 00:21:18,320
Speaker 1: ten is just one zero, and then you can go

379
00:21:18,400 --> 00:21:21,080
Speaker 1: up to nineteen, which is just one nine, and then

380
00:21:21,080 --> 00:21:23,280
Speaker 1: you start over again. Now you go to twenty, which

381
00:21:23,320 --> 00:21:27,080
Speaker 1: is to zero, and over and over again. Now hexadecimal

382
00:21:27,720 --> 00:21:30,199
Speaker 1: goes up to sixteen, but you really can't show that

383
00:21:30,280 --> 00:21:33,959
Speaker 1: using just decimal numerals. It doesn't work that way. So

384
00:21:34,000 --> 00:21:37,560
Speaker 1: with hexadecimal, you start at zero, you go up to nine,

385
00:21:37,760 --> 00:21:41,560
Speaker 1: and then to fill in the additional digits you use

386
00:21:41,600 --> 00:21:45,639
Speaker 1: a sequence like a B C d, E and F, so,

387
00:21:45,680 --> 00:21:48,600
Speaker 1: in other words, and hexadecimal it goes zero to f

388
00:21:49,200 --> 00:21:53,480
Speaker 1: before repeating. Each hexadecimal digit in this sequence of thirty

389
00:21:53,520 --> 00:21:58,160
Speaker 1: two represents four bits, also known as a nibble. So

390
00:21:58,280 --> 00:22:01,679
Speaker 1: while each decimal is and I p v for in

391
00:22:01,720 --> 00:22:05,800
Speaker 1: an IPv for address represents an octet, each digit and

392
00:22:05,840 --> 00:22:09,600
Speaker 1: a hexadecimal address represents a nibble. And now I'm not

393
00:22:09,640 --> 00:22:12,000
Speaker 1: making any of that up. Four times thirty two is

394
00:22:12,080 --> 00:22:16,560
Speaker 1: one eight, So that's where you get the one eight bits.

395
00:22:18,119 --> 00:22:20,920
Speaker 1: What this means is that the effective number of addresses

396
00:22:21,400 --> 00:22:25,159
Speaker 1: sky rockets. If none of the addresses were reserved for

397
00:22:25,240 --> 00:22:28,320
Speaker 1: special use, you would have three point four times ten

398
00:22:28,400 --> 00:22:32,240
Speaker 1: to the thirty eight power of addresses. So what is

399
00:22:32,280 --> 00:22:35,879
Speaker 1: that in real numbers? I'd love to tell you, but

400
00:22:36,000 --> 00:22:39,080
Speaker 1: the closest I can really get is three hundred forty

401
00:22:39,200 --> 00:22:43,000
Speaker 1: trillion two d eighty two billion, three hundred six million,

402
00:22:43,160 --> 00:22:50,320
Speaker 1: nine thousand eight followed by twenty four zeros. It's more

403
00:22:50,359 --> 00:22:53,040
Speaker 1: than enough for the foreseeable future. Even with such developments

404
00:22:53,119 --> 00:22:56,800
Speaker 1: as the Internet of Things, an IPv six address might

405
00:22:56,880 --> 00:22:59,639
Speaker 1: look something like this. And bear with me, because again,

406
00:22:59,680 --> 00:23:03,720
Speaker 1: this is a long and somewhat confusing one f e

407
00:23:03,720 --> 00:23:09,320
Speaker 1: eight zero, colon zero zero zero zero, colon zero zero

408
00:23:09,440 --> 00:23:13,960
Speaker 1: zero zero, colon zero zero zero zero, colon zero two

409
00:23:14,240 --> 00:23:18,399
Speaker 1: zero to colon b three f f, colon f e

410
00:23:18,480 --> 00:23:22,639
Speaker 1: one e, colon eight three to nine. Each sequence of

411
00:23:22,680 --> 00:23:25,199
Speaker 1: four digits has a colon separating it from its neighbors,

412
00:23:25,280 --> 00:23:27,760
Speaker 1: so it's essentially the same sort of purpose as the

413
00:23:27,800 --> 00:23:31,640
Speaker 1: dot in the I p v four addresses. In addition,

414
00:23:31,880 --> 00:23:33,840
Speaker 1: there are some nice tricks that you can use to

415
00:23:33,880 --> 00:23:37,800
Speaker 1: abbreviate those long addresses. If you have a leading zero,

416
00:23:38,080 --> 00:23:40,399
Speaker 1: in other words, you've just gotten past the colon, or

417
00:23:40,440 --> 00:23:44,560
Speaker 1: maybe you're even in the very first uh octet um,

418
00:23:44,680 --> 00:23:47,560
Speaker 1: then you get not octete. I'm sorry, you're in the

419
00:23:47,600 --> 00:23:51,080
Speaker 1: first section. Any leading zeros you can drop, you can

420
00:23:51,119 --> 00:23:54,320
Speaker 1: just go to the first number that is not a zero. Also,

421
00:23:54,320 --> 00:23:57,400
Speaker 1: if you have a single range of zeros, you can

422
00:23:57,560 --> 00:24:00,199
Speaker 1: drop those and replace it with a double colon. If

423
00:24:00,200 --> 00:24:04,080
Speaker 1: you have several series of four zeros, you can drop

424
00:24:04,080 --> 00:24:07,600
Speaker 1: all of those if they're all consecutive, and replace them

425
00:24:07,600 --> 00:24:10,520
Speaker 1: with a double colon. So you might remember that when

426
00:24:10,520 --> 00:24:12,879
Speaker 1: I was reading off that very long I p v

427
00:24:13,040 --> 00:24:16,720
Speaker 1: six address, there were a few uh segments that went

428
00:24:16,880 --> 00:24:19,520
Speaker 1: zero zero zero zero, Well, that means we could drop

429
00:24:19,600 --> 00:24:22,119
Speaker 1: those and just put a double colon in there. So

430
00:24:22,160 --> 00:24:24,840
Speaker 1: that last address I read a minute ago, if we

431
00:24:24,880 --> 00:24:28,600
Speaker 1: abbreviated it, we could say was F E eight zero

432
00:24:28,720 --> 00:24:32,760
Speaker 1: double colon two zero two colon B three f f

433
00:24:32,960 --> 00:24:35,960
Speaker 1: colon f e one e colon eight three to nine.

434
00:24:36,040 --> 00:24:40,040
Speaker 1: Simple as pie, or at least easier than what the

435
00:24:40,040 --> 00:24:42,760
Speaker 1: previous one was. Now, I mentioned that the Engineering Task

436
00:24:42,840 --> 00:24:46,840
Speaker 1: Force developed the strategy in but it wasn't until two

437
00:24:46,920 --> 00:24:50,480
Speaker 1: thousand seventeen that I p v six was officially adopted

438
00:24:50,520 --> 00:24:53,280
Speaker 1: as a standard. And I p v four and I

439
00:24:53,359 --> 00:24:56,720
Speaker 1: p v six are not fully compatible on their own,

440
00:24:57,240 --> 00:25:00,520
Speaker 1: and I p v six address can contain an embedded

441
00:25:00,560 --> 00:25:03,480
Speaker 1: I p v four address, but the I p v

442
00:25:03,720 --> 00:25:07,560
Speaker 1: four format is not forward compatible with I p v

443
00:25:07,720 --> 00:25:11,320
Speaker 1: six because well, that's the way time works. When you

444
00:25:11,359 --> 00:25:14,440
Speaker 1: think of something first, you don't necessarily make it where

445
00:25:14,440 --> 00:25:17,160
Speaker 1: it's automatically compatible with the next thing, because you haven't

446
00:25:17,200 --> 00:25:20,640
Speaker 1: thought of the next thing yet. Sadly enough, it also

447
00:25:20,640 --> 00:25:24,320
Speaker 1: takes a lot of time to switch an established infrastructure

448
00:25:24,359 --> 00:25:27,960
Speaker 1: over into a new set of protocols, So that has

449
00:25:28,359 --> 00:25:29,960
Speaker 1: what's one of the other reasons why it took so

450
00:25:30,000 --> 00:25:32,480
Speaker 1: long to adopt as a standard and to even make

451
00:25:32,560 --> 00:25:34,879
Speaker 1: some progress on this. Add to that the fact that

452
00:25:34,880 --> 00:25:37,800
Speaker 1: the Internet is not a single entity. It's not like

453
00:25:38,160 --> 00:25:40,800
Speaker 1: there's one big building where the Internet is. It's not

454
00:25:40,880 --> 00:25:42,960
Speaker 1: like the I T crowd where they put it on

455
00:25:43,040 --> 00:25:46,440
Speaker 1: top of big ben The Internet is a distributed network

456
00:25:46,600 --> 00:25:51,320
Speaker 1: across lots of different machines. So rolling out a comprehensive

457
00:25:51,480 --> 00:25:55,960
Speaker 1: change to the protocol is a colossal task, and it's

458
00:25:55,960 --> 00:25:59,240
Speaker 1: a big complicated mess, and there's no one entity in

459
00:25:59,359 --> 00:26:02,360
Speaker 1: charge to say, hey, go out there and do this.

460
00:26:02,880 --> 00:26:05,600
Speaker 1: Everyone agrees that we need to deploy i p v

461
00:26:05,760 --> 00:26:08,760
Speaker 1: six across all networks and adopt it moving forward, but

462
00:26:08,880 --> 00:26:12,720
Speaker 1: actually doing it isn't that easy. According to the website

463
00:26:13,040 --> 00:26:16,600
Speaker 1: World i p v six launch dot org, the percentage

464
00:26:16,600 --> 00:26:19,120
Speaker 1: of i p v six adoption among the top one

465
00:26:19,160 --> 00:26:22,520
Speaker 1: thousand sites as measured by Alexa Internet, which is a

466
00:26:22,560 --> 00:26:27,359
Speaker 1: subsidiary company owned by Amazon uh the numbers just below,

467
00:26:28,240 --> 00:26:31,280
Speaker 1: So all the traffic going to the one thousand top

468
00:26:31,320 --> 00:26:35,000
Speaker 1: websites of those top websites support i p v six,

469
00:26:35,359 --> 00:26:38,080
Speaker 1: which means that more than sevent of the most popular

470
00:26:38,080 --> 00:26:41,720
Speaker 1: websites are not yet reachable via i p v six,

471
00:26:42,440 --> 00:26:45,200
Speaker 1: and that is a bit of an issue. I will

472
00:26:45,240 --> 00:26:47,440
Speaker 1: say that a lot of the I s p s,

473
00:26:47,480 --> 00:26:50,440
Speaker 1: particularly the big ones in the United States, are pretty

474
00:26:50,480 --> 00:26:53,639
Speaker 1: well prepared. They have done a fairly decent job at

475
00:26:53,680 --> 00:26:57,040
Speaker 1: switching over their infrastructures to support I p v six.

476
00:26:57,119 --> 00:26:59,840
Speaker 1: But we still have a long ways to go. Speaking

477
00:26:59,880 --> 00:27:01,920
Speaker 1: of a long ways to go, let's take another quick

478
00:27:01,920 --> 00:27:05,040
Speaker 1: break and then we'll conclude our discussion about I p

479
00:27:05,200 --> 00:27:16,560
Speaker 1: v six. So every day we're adding more devices, including routers,

480
00:27:16,640 --> 00:27:19,640
Speaker 1: to the Internet, and we've established that even in the nineties,

481
00:27:19,680 --> 00:27:22,200
Speaker 1: engineers recognized that the number of addresses that I p

482
00:27:22,320 --> 00:27:25,359
Speaker 1: v four could handle was not up to snuff. How

483
00:27:26,440 --> 00:27:29,919
Speaker 1: in the blue blazes have we managed to avoid a

484
00:27:29,960 --> 00:27:34,120
Speaker 1: catastrophe for so many decades? So does that just mean

485
00:27:34,160 --> 00:27:36,320
Speaker 1: the problem wasn't as bad as we thought it was.

486
00:27:36,680 --> 00:27:38,920
Speaker 1: Because if we haven't switched completely over to I p

487
00:27:39,040 --> 00:27:41,280
Speaker 1: V six, and we knew that I p v four

488
00:27:41,320 --> 00:27:47,760
Speaker 1: addresses running out, why haven't we hit a massive crash? Well,

489
00:27:47,960 --> 00:27:52,000
Speaker 1: the problem is evident. The four plus billion IP addresses

490
00:27:52,040 --> 00:27:55,320
Speaker 1: are actually all gone now. That is, they've all been

491
00:27:55,359 --> 00:27:59,640
Speaker 1: snagged by various companies and institutions like Internet service providers

492
00:27:59,720 --> 00:28:03,840
Speaker 1: or unversities. Now those entities can assign out dynamic IP

493
00:28:03,960 --> 00:28:07,760
Speaker 1: addresses on their own respective networks, but no new network

494
00:28:07,800 --> 00:28:10,800
Speaker 1: could pop up and request a spectrum of addresses from

495
00:28:11,359 --> 00:28:14,480
Speaker 1: the Internet Assigned Numbers Authority or I A n A.

496
00:28:14,680 --> 00:28:17,520
Speaker 1: That's the authority that oversees the stuff. You couldn't request

497
00:28:17,560 --> 00:28:19,720
Speaker 1: any new ones from I A n A because there

498
00:28:19,760 --> 00:28:22,320
Speaker 1: are no new ones left. What you might be able

499
00:28:22,320 --> 00:28:25,760
Speaker 1: to do is negotiate with some other entity that actually

500
00:28:25,840 --> 00:28:30,199
Speaker 1: has unused IP addresses and purchase them that way. But

501
00:28:30,600 --> 00:28:32,760
Speaker 1: there aren't any new ones coming out because i P

502
00:28:32,840 --> 00:28:36,560
Speaker 1: V four is all dried up. Below the I A

503
00:28:36,880 --> 00:28:41,080
Speaker 1: n A R five Regional Internet Registries UH they are

504
00:28:41,200 --> 00:28:44,240
Speaker 1: called r I R s. These, as the name suggests,

505
00:28:44,280 --> 00:28:47,920
Speaker 1: oversee I P address assignments over specific regions in the world.

506
00:28:48,360 --> 00:28:51,600
Speaker 1: Those five entities, in turn can assign banks of IP

507
00:28:51,760 --> 00:28:55,680
Speaker 1: addresses to local Internet registries, which can include stuff like

508
00:28:55,720 --> 00:28:59,440
Speaker 1: the aforementioned I s p s and universities and other institutions.

509
00:28:59,680 --> 00:29:02,240
Speaker 1: And I'll so just to clarify, while an I s

510
00:29:02,280 --> 00:29:05,760
Speaker 1: P might be a local Internet registry, not all I

511
00:29:06,000 --> 00:29:08,520
Speaker 1: s p s fall into that category. Some I s

512
00:29:08,560 --> 00:29:11,520
Speaker 1: p s belonged to a larger entity, which in turn

513
00:29:11,640 --> 00:29:14,760
Speaker 1: is the actual local Internet registry. So this stuff gets

514
00:29:14,800 --> 00:29:19,000
Speaker 1: pretty complicated. Back in January two thleven, the Asia Pacific

515
00:29:19,080 --> 00:29:22,600
Speaker 1: Network Information Center better known as ap NICK, A P

516
00:29:22,880 --> 00:29:25,920
Speaker 1: and I C, which is one of those five regional

517
00:29:25,960 --> 00:29:30,200
Speaker 1: Internet Address registries I talked about, requested and received the

518
00:29:30,280 --> 00:29:35,040
Speaker 1: last two unreserved blocks of IP addresses. There were only

519
00:29:35,200 --> 00:29:38,520
Speaker 1: five reserved blocks remaining, and so the I A n

520
00:29:38,560 --> 00:29:42,680
Speaker 1: A ceremoniously granted one block to each of the regional

521
00:29:42,720 --> 00:29:47,920
Speaker 1: Internet Address registries, and then all of those IP addresses

522
00:29:48,120 --> 00:29:51,000
Speaker 1: were technically out in the wild. There were none left

523
00:29:51,000 --> 00:29:54,440
Speaker 1: in reserve. By April two thousand eleven, app NICK ran

524
00:29:54,520 --> 00:29:58,080
Speaker 1: out of freely allocated IPv VOORA addresses, which means that

525
00:29:58,160 --> 00:30:00,840
Speaker 1: sometimes in that region you can't get an IPv for

526
00:30:01,000 --> 00:30:03,400
Speaker 1: address when you need one, I mean, you can't connect

527
00:30:03,400 --> 00:30:06,520
Speaker 1: to the Internet. So why hasn't that happened everywhere? Well,

528
00:30:06,520 --> 00:30:09,000
Speaker 1: it's largely because engineers are very clever at figuring out

529
00:30:09,080 --> 00:30:12,280
Speaker 1: workarounds or problems. There have been a few temporary measures

530
00:30:12,320 --> 00:30:14,880
Speaker 1: that have extended the useful life of ip V four

531
00:30:15,040 --> 00:30:18,880
Speaker 1: despite the growing number of connected devices. So remember when

532
00:30:18,880 --> 00:30:21,360
Speaker 1: I mentioned that IP addresses could be divided up by

533
00:30:21,400 --> 00:30:24,720
Speaker 1: classes based on how many bits are dedicated to the

534
00:30:24,840 --> 00:30:28,920
Speaker 1: network address versus the host address. Well, there's also something

535
00:30:28,960 --> 00:30:33,280
Speaker 1: called classless inter domain routing or c I d R

536
00:30:33,520 --> 00:30:38,400
Speaker 1: or CIDER. The Internet Engineering Task Force introduced c I

537
00:30:38,520 --> 00:30:42,960
Speaker 1: d R in as a way to simplify how data

538
00:30:43,000 --> 00:30:45,400
Speaker 1: moved through routers on the Internet and to extend the

539
00:30:45,480 --> 00:30:48,280
Speaker 1: useful life of IP v four, and it mostly has

540
00:30:48,280 --> 00:30:52,360
Speaker 1: to do with the big drawback of the class full system.

541
00:30:52,680 --> 00:30:57,280
Speaker 1: So the smallest allocation of addresses using the class full

542
00:30:57,320 --> 00:31:01,400
Speaker 1: system is two hundred fifty six addresses, which is a

543
00:31:01,400 --> 00:31:04,120
Speaker 1: pretty small number when you remember how many devices need

544
00:31:04,200 --> 00:31:09,200
Speaker 1: more than one IP address. So that's the most addresses

545
00:31:09,200 --> 00:31:12,360
Speaker 1: that eight bits can support. If you were in that class,

546
00:31:12,360 --> 00:31:15,600
Speaker 1: if you moved up a class, suddenly the number of

547
00:31:15,680 --> 00:31:20,440
Speaker 1: IP addresses you would get or for this particular class

548
00:31:20,440 --> 00:31:23,240
Speaker 1: would go from two fifty six to sixty five thousand,

549
00:31:23,360 --> 00:31:26,720
Speaker 1: five hundred thirty six. There's no in between there. You

550
00:31:26,760 --> 00:31:29,760
Speaker 1: go to fifty six to sixty thirty six. That's a

551
00:31:29,840 --> 00:31:33,600
Speaker 1: huge number. That's more than what most organizations need for

552
00:31:33,840 --> 00:31:37,760
Speaker 1: the devices that are connecting through their networks. So there

553
00:31:37,800 --> 00:31:40,280
Speaker 1: was no way to step between those two. From a

554
00:31:40,280 --> 00:31:43,800
Speaker 1: protocol standpoint, you either ended up with too few addresses

555
00:31:44,000 --> 00:31:46,840
Speaker 1: where people were not going to be able to connect

556
00:31:46,960 --> 00:31:50,000
Speaker 1: their machines properly to too many addresses where a whole

557
00:31:50,000 --> 00:31:53,720
Speaker 1: bunch we're just gonna go unused and wasted. Um, And

558
00:31:54,480 --> 00:31:56,760
Speaker 1: that was a real issue. That's when c I d

559
00:31:57,080 --> 00:31:59,360
Speaker 1: R was able to solve this problem. It was a

560
00:31:59,360 --> 00:32:02,160
Speaker 1: new method to step around it. Rather than define networks

561
00:32:02,160 --> 00:32:06,520
Speaker 1: and hosts by octets for bites, you know, sequences of

562
00:32:06,560 --> 00:32:11,000
Speaker 1: eight bits, it divides networks into variously sized subnets. So

563
00:32:11,040 --> 00:32:13,600
Speaker 1: when setting up a network, engineers can aim for a

564
00:32:13,800 --> 00:32:17,600
Speaker 1: range of addresses that best suits the organization's needs and

565
00:32:17,680 --> 00:32:20,080
Speaker 1: not go beyond that. Now you have to go for

566
00:32:20,120 --> 00:32:24,360
Speaker 1: a consecutive addresses if you're using c I DR notation.

567
00:32:24,960 --> 00:32:27,720
Speaker 1: Otherwise you have to keep using the notation repeatedly. Think

568
00:32:27,720 --> 00:32:30,600
Speaker 1: it's pretty messy. We use c I DR notation to

569
00:32:30,640 --> 00:32:33,200
Speaker 1: represent IP addresses in this way. If you've ever seen

570
00:32:33,240 --> 00:32:35,120
Speaker 1: what looks like an I P address followed by a

571
00:32:35,160 --> 00:32:38,080
Speaker 1: slash and then a decimal number, you've likely seen an

572
00:32:38,080 --> 00:32:41,400
Speaker 1: example of c I d R notation. The decimal number

573
00:32:41,440 --> 00:32:46,160
Speaker 1: represents the number of leading one bits in the routing mask. Essentially,

574
00:32:46,160 --> 00:32:49,040
Speaker 1: it's a shorthand notation to express the range of addresses

575
00:32:49,120 --> 00:32:52,040
Speaker 1: represented in a network, and it's not limited to octets

576
00:32:52,080 --> 00:32:55,240
Speaker 1: the way class full representation was. One big benefit of

577
00:32:55,240 --> 00:32:57,880
Speaker 1: c I d R was that fewer IP addresses would

578
00:32:57,880 --> 00:33:00,760
Speaker 1: go to waste unused. If you were up a large

579
00:33:00,840 --> 00:33:03,840
Speaker 1: but not ginormous network, you can set up a range

580
00:33:03,840 --> 00:33:06,640
Speaker 1: of IP addresses sufficient to meet your needs without going

581
00:33:06,640 --> 00:33:10,600
Speaker 1: overboard by tens of thousands of excess addresses, which in

582
00:33:10,680 --> 00:33:13,640
Speaker 1: turn meant that those unused addresses could be freed up

583
00:33:13,680 --> 00:33:16,640
Speaker 1: for other networks, and it allowed for a better distribution

584
00:33:16,880 --> 00:33:21,040
Speaker 1: of IP addresses. In other words, Another solution is network

585
00:33:21,160 --> 00:33:24,960
Speaker 1: address translation or in a t net. It's a set

586
00:33:24,960 --> 00:33:27,360
Speaker 1: of rules that allows a single device to act a

587
00:33:27,440 --> 00:33:31,000
Speaker 1: sort of a liaison between a specific network and the Internet.

588
00:33:31,240 --> 00:33:33,480
Speaker 1: So remember the Internet is a network of networks, so

589
00:33:33,600 --> 00:33:37,080
Speaker 1: a device like a router could act as the gateway

590
00:33:37,120 --> 00:33:40,000
Speaker 1: between your local network, the one that just has a

591
00:33:40,000 --> 00:33:43,240
Speaker 1: bunch of computers directly communicating with one another, and then

592
00:33:43,320 --> 00:33:45,720
Speaker 1: everything else out there on the Internet. So I'll use

593
00:33:45,800 --> 00:33:48,600
Speaker 1: my office as an example. When I log in from

594
00:33:48,640 --> 00:33:51,720
Speaker 1: how stuff works, all traffic between the Internet, and my

595
00:33:51,800 --> 00:33:55,520
Speaker 1: computer passes through our company's neat router. First, the router

596
00:33:55,600 --> 00:33:59,080
Speaker 1: has a range of IP addresses that ultimately come from I, A,

597
00:33:59,280 --> 00:34:01,680
Speaker 1: N A. You have to go up a couple of levels,

598
00:34:01,880 --> 00:34:03,760
Speaker 1: several levels, as it turns out, but I A and

599
00:34:03,840 --> 00:34:08,600
Speaker 1: A ultimately was the agency that granted this. My computer,

600
00:34:08,680 --> 00:34:11,600
Speaker 1: on the other hand, has a non unique and therefore

601
00:34:11,800 --> 00:34:15,560
Speaker 1: non routable address that works fine for communicating with other

602
00:34:15,600 --> 00:34:19,040
Speaker 1: computers on my network, but wouldn't work if I could

603
00:34:19,040 --> 00:34:21,799
Speaker 1: somehow bypass the router and try to communicate directly with

604
00:34:21,800 --> 00:34:23,560
Speaker 1: the Internet. So what do I mean by that? Well,

605
00:34:23,880 --> 00:34:28,000
Speaker 1: within a network, you need unique addresses, otherwise data is

606
00:34:28,000 --> 00:34:29,799
Speaker 1: not going to know where to go to get to

607
00:34:29,840 --> 00:34:34,120
Speaker 1: the right destination. But network A could have a series

608
00:34:34,120 --> 00:34:36,879
Speaker 1: of addresses, and network B could have the exact same

609
00:34:36,920 --> 00:34:39,200
Speaker 1: series of addresses, And as long as A and B

610
00:34:39,440 --> 00:34:43,440
Speaker 1: are completely self contained, it doesn't matter. Right, all the

611
00:34:43,440 --> 00:34:46,319
Speaker 1: computers on B know what it means to go to

612
00:34:46,400 --> 00:34:49,360
Speaker 1: this particular address, and all the computers on A know

613
00:34:49,480 --> 00:34:51,640
Speaker 1: what it means to go to that exact same address,

614
00:34:51,760 --> 00:34:55,799
Speaker 1: because they only belong to their respective networks. When you

615
00:34:55,840 --> 00:34:58,640
Speaker 1: connect through the Internet, you then have to have another

616
00:34:58,760 --> 00:35:03,480
Speaker 1: layer something else to actually uniquely identify the machine. Otherwise

617
00:35:03,800 --> 00:35:06,440
Speaker 1: it would be as if the house I live in

618
00:35:06,560 --> 00:35:09,120
Speaker 1: and the house you live in have exactly the same

619
00:35:09,160 --> 00:35:11,839
Speaker 1: physical address, but are in two different parts of town.

620
00:35:12,640 --> 00:35:15,799
Speaker 1: That would be incredibly confusing, and we would constantly be

621
00:35:15,880 --> 00:35:18,720
Speaker 1: receiving each other's mail. I think you have my socks,

622
00:35:19,040 --> 00:35:21,840
Speaker 1: but my computer is behind the router. From the perspective

623
00:35:21,880 --> 00:35:24,920
Speaker 1: of the Internet, so my computer is not communicating directly

624
00:35:24,960 --> 00:35:27,879
Speaker 1: with the rest of the Internet. It's communicating through the router.

625
00:35:27,960 --> 00:35:30,439
Speaker 1: It sends data to the router, and then the router

626
00:35:30,480 --> 00:35:33,359
Speaker 1: in turn routes that out to the Internet. So on

627
00:35:33,400 --> 00:35:36,160
Speaker 1: my side of the router, on the company side, I

628
00:35:36,200 --> 00:35:39,040
Speaker 1: don't have a need for a unique IP address. Whenever

629
00:35:39,040 --> 00:35:41,120
Speaker 1: I try to communicate with a machine that is not

630
00:35:41,520 --> 00:35:44,880
Speaker 1: on my private network, non the house stuff works network,

631
00:35:45,320 --> 00:35:48,480
Speaker 1: that message passes through the router, which uses an available

632
00:35:48,520 --> 00:35:52,080
Speaker 1: IP address that it has assigned to it, and then

633
00:35:52,120 --> 00:35:54,560
Speaker 1: sends that message out into the world. The router then

634
00:35:54,640 --> 00:35:57,880
Speaker 1: has to consult what is called an address translation table

635
00:35:57,920 --> 00:36:01,439
Speaker 1: whenever data is coming back to determine which machine on

636
00:36:01,800 --> 00:36:05,120
Speaker 1: our network is the intended recipient. So if I go

637
00:36:05,200 --> 00:36:08,120
Speaker 1: out to say look at a web page. That message

638
00:36:08,120 --> 00:36:10,920
Speaker 1: will go out to the router, which then will assign

639
00:36:11,120 --> 00:36:14,480
Speaker 1: an available IP address to send that out to the Internet.

640
00:36:14,560 --> 00:36:17,640
Speaker 1: The response will come back, the router will look at

641
00:36:17,680 --> 00:36:21,680
Speaker 1: the IP address on that that you know, the intended recipient.

642
00:36:22,640 --> 00:36:25,839
Speaker 1: Use a trend a network translation table to say, all right,

643
00:36:25,880 --> 00:36:28,560
Speaker 1: well who did I give this to? Again? Which which

644
00:36:28,600 --> 00:36:32,200
Speaker 1: computer has this temporary IP address? Oh, it's Jonathan's machine.

645
00:36:32,440 --> 00:36:37,120
Speaker 1: He's the one going to red versus Blue dot com

646
00:36:37,200 --> 00:36:41,120
Speaker 1: and watching cartoons. That's typical, And then it would get

647
00:36:41,160 --> 00:36:45,480
Speaker 1: to me, probably without the actual commentary. Network address translation

648
00:36:45,520 --> 00:36:47,520
Speaker 1: has a lot of other uses, but for the purposes

649
00:36:47,520 --> 00:36:49,759
Speaker 1: of this episode, it really kind of sums up what

650
00:36:49,880 --> 00:36:54,440
Speaker 1: it does via visa the the IPv for shortage. So

651
00:36:54,880 --> 00:37:00,360
Speaker 1: this is a lot of of useful treading a water,

652
00:37:00,440 --> 00:37:02,879
Speaker 1: you might say. In fact, a lot of engineers said

653
00:37:02,920 --> 00:37:05,399
Speaker 1: that the development of stuff like c I, d R

654
00:37:05,400 --> 00:37:08,360
Speaker 1: and n A T extended the useful life of I

655
00:37:08,520 --> 00:37:12,040
Speaker 1: p V four by about twenty years. That's pretty cool,

656
00:37:12,360 --> 00:37:15,480
Speaker 1: but we still clearly have a need to move to

657
00:37:15,520 --> 00:37:17,319
Speaker 1: I p V six, which is going to create so

658
00:37:17,360 --> 00:37:21,439
Speaker 1: many addresses that is very difficult to imagine a time

659
00:37:21,480 --> 00:37:24,719
Speaker 1: when we will run out of them anytime soon. It

660
00:37:24,800 --> 00:37:29,880
Speaker 1: may one day happen, but we're talking trillions upon trillions

661
00:37:29,880 --> 00:37:33,960
Speaker 1: of addresses here, so the deployment is going pretty well.

662
00:37:34,120 --> 00:37:37,319
Speaker 1: It's been a slow process when you consider that it

663
00:37:37,360 --> 00:37:40,960
Speaker 1: was back in that they were first proposing I p

664
00:37:41,120 --> 00:37:45,200
Speaker 1: V six, But it's largely because, at least in the

665
00:37:45,200 --> 00:37:47,839
Speaker 1: commercial world, a lot of entities don't make a move

666
00:37:47,920 --> 00:37:53,200
Speaker 1: until it's absolutely necessary. So once I A and A

667
00:37:53,200 --> 00:37:56,919
Speaker 1: allocated all those remaining I p v four addresses, that's

668
00:37:56,920 --> 00:38:00,920
Speaker 1: when companies said, WHOA, we might need to start working

669
00:38:00,920 --> 00:38:02,520
Speaker 1: on this I p v six thing. We might need

670
00:38:02,560 --> 00:38:05,480
Speaker 1: to start rolling that out and making sure our websites

671
00:38:05,520 --> 00:38:09,080
Speaker 1: are accessible, that our machines can communicate through I p

672
00:38:09,200 --> 00:38:12,279
Speaker 1: V six, because otherwise we're going to run into some

673
00:38:12,360 --> 00:38:17,120
Speaker 1: pretty tough situations. The migration requires software and firmware updates,

674
00:38:17,160 --> 00:38:20,760
Speaker 1: sometimes hardware updates to stuff like routers across the Internet,

675
00:38:21,080 --> 00:38:23,360
Speaker 1: but many I s p s, particularly those big ones

676
00:38:23,440 --> 00:38:25,360
Speaker 1: like the ones that we have here in the United States,

677
00:38:25,360 --> 00:38:28,040
Speaker 1: have largely addressed this. That no one's at a percent

678
00:38:28,080 --> 00:38:30,040
Speaker 1: as far as I can tell, but uh, there are

679
00:38:30,040 --> 00:38:33,480
Speaker 1: a lot of of companies that have gotten to you know,

680
00:38:33,520 --> 00:38:37,239
Speaker 1: the eighties and ninety percentiles of deployment, which is pretty impressive.

681
00:38:37,719 --> 00:38:40,520
Speaker 1: On the consumer side, smartphones pretty much are on the

682
00:38:40,560 --> 00:38:43,560
Speaker 1: i p v six train already, and all current versions

683
00:38:43,600 --> 00:38:46,480
Speaker 1: of operating systems support the i p v six protocol,

684
00:38:46,960 --> 00:38:49,239
Speaker 1: so we're mostly waiting on web servers at this point,

685
00:38:49,239 --> 00:38:51,800
Speaker 1: if I'm being honest. Now. Back in two thousands thirteen,

686
00:38:52,080 --> 00:38:56,400
Speaker 1: cloud Flare CEO Matthew Prince projected that based on the

687
00:38:56,400 --> 00:38:59,280
Speaker 1: adoption rate of i p v six at that time,

688
00:39:00,200 --> 00:39:03,239
Speaker 1: we could celebrate a full migration to i p v

689
00:39:03,400 --> 00:39:10,560
Speaker 1: six on May tenth of so market calendars. Also, I

690
00:39:10,600 --> 00:39:13,120
Speaker 1: should point out it's quite quite likely we're never gonna

691
00:39:13,160 --> 00:39:16,600
Speaker 1: see I p v four abandoned entirely. It's more likely

692
00:39:16,920 --> 00:39:19,800
Speaker 1: that we're gonna see both sets of protocols continue side

693
00:39:19,800 --> 00:39:22,880
Speaker 1: by side. It's just that I p v four addresses

694
00:39:23,080 --> 00:39:26,000
Speaker 1: will eventually be more or less completely locked down. But

695
00:39:26,040 --> 00:39:30,319
Speaker 1: it's very rare to abandon completely a legacy infrastructure, and

696
00:39:30,360 --> 00:39:33,359
Speaker 1: the i p v four framework as a particularly large one.

697
00:39:34,120 --> 00:39:36,919
Speaker 1: So we will continue to see this deployment, will see

698
00:39:37,200 --> 00:39:39,440
Speaker 1: more development on the side of i p v six,

699
00:39:40,040 --> 00:39:43,439
Speaker 1: and uh maybe in a few years it'll we'll see

700
00:39:43,440 --> 00:39:47,080
Speaker 1: that percentage for the top one thousand sites go up

701
00:39:47,120 --> 00:39:51,640
Speaker 1: to above the mark. But it's gonna take some time.

702
00:39:51,920 --> 00:39:55,920
Speaker 1: And honestly, the the measures that have been put in

703
00:39:55,960 --> 00:40:01,720
Speaker 1: place have created enough slack that a lot of people

704
00:40:01,760 --> 00:40:04,759
Speaker 1: who obviously should be thinking hard about the future have

705
00:40:04,880 --> 00:40:08,279
Speaker 1: kind of put it off a bit. They procrastinated. Uh,

706
00:40:08,320 --> 00:40:11,560
Speaker 1: that's not great for all of us, But the bright

707
00:40:11,600 --> 00:40:15,040
Speaker 1: side is we're not going to see the Internet fail.

708
00:40:15,719 --> 00:40:19,520
Speaker 1: I p V six will be more than enough to

709
00:40:19,680 --> 00:40:23,640
Speaker 1: solve this problem. It's just a question of when the

710
00:40:23,719 --> 00:40:27,160
Speaker 1: various entities involved get motivated enough to switch over to

711
00:40:27,239 --> 00:40:30,319
Speaker 1: I p V six. So I don't think that they

712
00:40:30,400 --> 00:40:33,640
Speaker 1: were headed toward a catastrophe at this stage, at least

713
00:40:33,719 --> 00:40:36,880
Speaker 1: not collectively. There might be individual companies out there that

714
00:40:36,960 --> 00:40:40,560
Speaker 1: find themselves scrambling once it gets to a certain point,

715
00:40:40,920 --> 00:40:44,040
Speaker 1: but maybe that'll just mean they'll learn a valuable lesson

716
00:40:44,640 --> 00:40:46,680
Speaker 1: and then the board of directors will change the CEO

717
00:40:46,800 --> 00:40:49,240
Speaker 1: and then the whole thing will start over again. That's cynical.

718
00:40:49,320 --> 00:40:52,280
Speaker 1: We're not gonna talk about that. Let's wrap this up, Hey, guys,

719
00:40:52,440 --> 00:40:55,600
Speaker 1: if you have any suggestions for future episodes of tech Stuff,

720
00:40:55,640 --> 00:40:59,000
Speaker 1: I have a solution for you send me an email

721
00:40:59,400 --> 00:41:01,960
Speaker 1: address is tech stuff at how stuff works dot com,

722
00:41:02,040 --> 00:41:04,160
Speaker 1: or you can drop you a line on Facebook or Twitter.

723
00:41:04,200 --> 00:41:06,600
Speaker 1: The hand over both of those is tech Stuff hs W.

724
00:41:07,200 --> 00:41:10,480
Speaker 1: You can watch me live on twitch dot tv slash

725
00:41:10,480 --> 00:41:14,480
Speaker 1: tech stuff most Wednesdays and Fridays. I'm recording episodes. I'm

726
00:41:14,520 --> 00:41:17,160
Speaker 1: glad to have you guys watch me as I stumble

727
00:41:17,280 --> 00:41:19,680
Speaker 1: through this. I'm so glad that right now I don't

728
00:41:19,680 --> 00:41:22,600
Speaker 1: have anyone watching me because cold medication makes me do

729
00:41:22,680 --> 00:41:25,840
Speaker 1: weird things. Oh and uh, make sure you follow our

730
00:41:25,880 --> 00:41:29,120
Speaker 1: Instagram account. All right, that's it for this episode. Join

731
00:41:29,239 --> 00:41:32,560
Speaker 1: us next time when we talk about something completely unrelated

732
00:41:32,680 --> 00:41:36,720
Speaker 1: to Internet protocols, and I'll talk to you again really soon.

733
00:41:42,280 --> 00:41:44,960
Speaker 1: For more on this and thousands of other topics, how

734
00:41:45,000 --> 00:41:55,760
Speaker 1: stuff works dot com