1
00:00:04,440 --> 00:00:12,319
Speaker 1: Welcome to tech Stuff, a production from iHeartRadio. Hey there,

2
00:00:12,360 --> 00:00:15,920
Speaker 1: and welcome to tech Stuff. I'm your host, Jonathan Strickland.

3
00:00:15,920 --> 00:00:19,599
Speaker 1: I'm an executive producer with iHeart Podcasts and how the

4
00:00:19,720 --> 00:00:24,079
Speaker 1: tech are you. Recently here in the United States, Senator

5
00:00:24,160 --> 00:00:28,560
Speaker 1: Elizabeth Warren and Congressman Jerry Nadler have called for an

6
00:00:28,560 --> 00:00:33,239
Speaker 1: investigation into a company called VeriSign. So why did they

7
00:00:33,320 --> 00:00:36,239
Speaker 1: do that? Well, they say that VeriSign has engaged in

8
00:00:36,640 --> 00:00:42,760
Speaker 1: predatory pricing their words. And what is VeriSign's business, Well,

9
00:00:42,840 --> 00:00:46,440
Speaker 1: among other things, vera sign is the one and only

10
00:00:46,760 --> 00:00:52,760
Speaker 1: entity acting as a registry for some top level domain names,

11
00:00:53,000 --> 00:00:55,200
Speaker 1: and we're going to break all that down so that

12
00:00:55,280 --> 00:00:58,240
Speaker 1: it's easier to parse. But let me preface this by

13
00:00:58,280 --> 00:01:03,840
Speaker 1: saying this is complicated stuff, not just technically, but from

14
00:01:03,920 --> 00:01:09,800
Speaker 1: like an organizational perspective. This is really complex and there's

15
00:01:09,840 --> 00:01:13,480
Speaker 1: gonna be a lot of talk about the responsibilities of

16
00:01:14,000 --> 00:01:18,280
Speaker 1: a registry in this episode and how things have kind

17
00:01:18,319 --> 00:01:24,000
Speaker 1: of shifted around since the days of arpenet into the Internet.

18
00:01:24,319 --> 00:01:26,880
Speaker 1: So what I'm saying is that there's a lot more

19
00:01:26,920 --> 00:01:29,160
Speaker 1: to this than what I'm going to cover. In fact,

20
00:01:29,200 --> 00:01:31,160
Speaker 1: I'm not even going to get into things like the

21
00:01:31,280 --> 00:01:35,560
Speaker 1: DNS wars or the Root Registry wars, or any of

22
00:01:35,560 --> 00:01:39,040
Speaker 1: that stuff, because it would require a full series of

23
00:01:39,040 --> 00:01:42,840
Speaker 1: episodes all by themselves. So if what I'm talking about

24
00:01:42,880 --> 00:01:45,880
Speaker 1: today is interesting to you and you want to learn more,

25
00:01:46,120 --> 00:01:49,400
Speaker 1: let me tell you there is a wealth of information online.

26
00:01:49,440 --> 00:01:52,360
Speaker 1: You can just do some searching around for things like

27
00:01:52,720 --> 00:01:56,440
Speaker 1: DNS wars, for example, and learn all about how people

28
00:01:56,480 --> 00:02:00,720
Speaker 1: were trying to establish standards in price. This is, you know,

29
00:02:00,800 --> 00:02:04,560
Speaker 1: before you actually arrive at standards and practices, it can

30
00:02:04,600 --> 00:02:07,640
Speaker 1: be a little bit like the wild West out there,

31
00:02:07,720 --> 00:02:12,160
Speaker 1: and that was certainly the case with early organization of

32
00:02:12,240 --> 00:02:17,800
Speaker 1: information on the Internet infrastructure. But let's talk about devices

33
00:02:18,040 --> 00:02:21,840
Speaker 1: and names now. The naming of computers is a difficult matter.

34
00:02:21,960 --> 00:02:24,320
Speaker 1: It isn't just one of your holiday games. You may

35
00:02:24,360 --> 00:02:26,160
Speaker 1: think at first, I'm as mad as a hatter when

36
00:02:26,160 --> 00:02:28,600
Speaker 1: I tell you a computer as a name that's really

37
00:02:28,639 --> 00:02:30,200
Speaker 1: a bunch of numbers. You know. I was really going

38
00:02:30,240 --> 00:02:33,119
Speaker 1: to try and channel ts Elliott through the whole episode,

39
00:02:33,440 --> 00:02:35,800
Speaker 1: but it kind of fell off quickly there, So I

40
00:02:35,800 --> 00:02:38,640
Speaker 1: guess there goes my chance of having this episode be

41
00:02:38,720 --> 00:02:41,720
Speaker 1: turned into a musical by Androloid Weber. But yeah, in

42
00:02:41,800 --> 00:02:45,000
Speaker 1: the early days of arpinnet, when a bunch of computer

43
00:02:45,080 --> 00:02:48,000
Speaker 1: scientists were kind of sussing out how to create a

44
00:02:48,040 --> 00:02:51,000
Speaker 1: system in which different computers would be able to communicate

45
00:02:51,040 --> 00:02:54,240
Speaker 1: with one another and send and receive files and all

46
00:02:54,240 --> 00:02:58,760
Speaker 1: that kind of stuff. One of the many challenges required

47
00:02:58,760 --> 00:03:03,280
Speaker 1: that each computer have a unique name or address assigned

48
00:03:03,400 --> 00:03:06,760
Speaker 1: to it. Otherwise you would have to rely on maybe

49
00:03:06,800 --> 00:03:10,079
Speaker 1: a direct computer to computer connection to send information from

50
00:03:10,120 --> 00:03:12,959
Speaker 1: computer A to computer B. And that works if you're

51
00:03:13,000 --> 00:03:15,359
Speaker 1: just talking about two computers. Right, If you just need

52
00:03:15,400 --> 00:03:19,320
Speaker 1: to directly connect two machines together, no big deal. I mean,

53
00:03:19,360 --> 00:03:22,200
Speaker 1: it is a big deal. But you could do that.

54
00:03:22,440 --> 00:03:25,880
Speaker 1: You could create a physical connection and create standards that

55
00:03:25,919 --> 00:03:28,600
Speaker 1: would allow one computer to talk to another. Keep in mind,

56
00:03:28,960 --> 00:03:31,920
Speaker 1: different computers communicate in very different ways, so you'd have

57
00:03:31,960 --> 00:03:35,840
Speaker 1: to kind of build a translator in on either side

58
00:03:35,920 --> 00:03:39,160
Speaker 1: so that the computers could understand the information being sent

59
00:03:39,240 --> 00:03:42,280
Speaker 1: back and forth. But more than that, if you add

60
00:03:42,280 --> 00:03:44,520
Speaker 1: more computers to this, so that you don't just have

61
00:03:44,560 --> 00:03:47,080
Speaker 1: computer A and B, but you have C through Z

62
00:03:47,280 --> 00:03:49,720
Speaker 1: and then all the numbers, well you get into a

63
00:03:49,720 --> 00:03:52,680
Speaker 1: system that's far more complicated. Right. You can't just directly

64
00:03:52,720 --> 00:03:57,520
Speaker 1: connect Computer A to all five thousand other machines that

65
00:03:57,520 --> 00:04:00,760
Speaker 1: are on the network. That would be impossible. You would

66
00:04:00,840 --> 00:04:03,520
Speaker 1: just have a massive cables that would be a real

67
00:04:03,600 --> 00:04:06,600
Speaker 1: tripping hazard if nothing else, Plus where would you plug

68
00:04:06,600 --> 00:04:08,960
Speaker 1: them all into. So sooner or later, you're going to

69
00:04:09,040 --> 00:04:11,920
Speaker 1: have a huge mess on your hands that needs to

70
00:04:11,920 --> 00:04:15,880
Speaker 1: be solved through some other means. And thus it makes

71
00:04:16,120 --> 00:04:19,680
Speaker 1: more sense to create an infrastructure in which each computer

72
00:04:19,960 --> 00:04:23,600
Speaker 1: has a unique name or address. So if Computer one

73
00:04:23,680 --> 00:04:26,800
Speaker 1: wants to talk to Computer five hundred, will both computers

74
00:04:26,800 --> 00:04:30,080
Speaker 1: have their own unique addresses, and that facilitates this connection

75
00:04:30,200 --> 00:04:33,040
Speaker 1: between the two, so that Computer one is communicating only

76
00:04:33,080 --> 00:04:36,240
Speaker 1: with Computer five hundred and not just blasting out information

77
00:04:36,600 --> 00:04:40,559
Speaker 1: to four hundred ninety nine machines only one of which

78
00:04:40,960 --> 00:04:43,440
Speaker 1: actually is relevant. You don't want it to be a

79
00:04:43,560 --> 00:04:47,920
Speaker 1: party line. So those unique addresses would allow this to happen.

80
00:04:48,040 --> 00:04:51,200
Speaker 1: And computers two through four hundred ninety nine plus anything

81
00:04:51,240 --> 00:04:54,200
Speaker 1: above five hundred one or five oh one. And further,

82
00:04:54,720 --> 00:04:56,799
Speaker 1: none of those are going to accidentally get the information

83
00:04:56,960 --> 00:05:00,000
Speaker 1: meant to just go between these other two computers one

84
00:05:00,120 --> 00:05:02,400
Speaker 1: in five hundred. So I'm not going to dwell too

85
00:05:02,480 --> 00:05:07,839
Speaker 1: much on the old NCP days. NCP stands for Network

86
00:05:07,960 --> 00:05:11,919
Speaker 1: Control Protocol. That is a topic that will require a

87
00:05:11,960 --> 00:05:15,839
Speaker 1: deeper dive in itself in order to talk about network infrastructure.

88
00:05:16,240 --> 00:05:19,800
Speaker 1: But it's a predecessor to what we have today. So instead,

89
00:05:20,000 --> 00:05:24,520
Speaker 1: let's turn our attention to an approach that would succeed

90
00:05:24,920 --> 00:05:29,440
Speaker 1: the old NCP rules, and that would be TCP IP.

91
00:05:29,920 --> 00:05:33,720
Speaker 1: We usually write that as TCP slash IP. These are

92
00:05:33,720 --> 00:05:38,400
Speaker 1: two sets of rules that are the Transmission Control Protocol

93
00:05:38,680 --> 00:05:42,159
Speaker 1: and the Internet protocol. Remember, protocol is really just a

94
00:05:42,160 --> 00:05:45,840
Speaker 1: fancy word to say rule set. This is the process,

95
00:05:46,080 --> 00:05:49,400
Speaker 1: the rules that you follow in order to achieve whatever

96
00:05:49,440 --> 00:05:52,440
Speaker 1: the thing is you're trying to achieve. Now, the transmission

97
00:05:52,440 --> 00:05:56,719
Speaker 1: control protocol is incredibly important. This is where we get

98
00:05:56,760 --> 00:06:00,719
Speaker 1: into stuff like packet switching with you know, headers and

99
00:06:00,920 --> 00:06:03,480
Speaker 1: error checking and all that kind of stuff. The basic

100
00:06:03,839 --> 00:06:07,359
Speaker 1: functionality that allows Internet traffic to work as it does.

101
00:06:07,480 --> 00:06:11,719
Speaker 1: So instead of sending, say an enormous file all in

102
00:06:11,920 --> 00:06:15,120
Speaker 1: one big chunk, you divide it up into packets, which

103
00:06:15,160 --> 00:06:19,440
Speaker 1: makes it far easier to deliver to your destination even

104
00:06:19,560 --> 00:06:22,840
Speaker 1: if a pathway shuts down. So, like let's say that

105
00:06:22,880 --> 00:06:27,320
Speaker 1: you have a route planned where the information is going

106
00:06:27,360 --> 00:06:29,640
Speaker 1: from computer one to computer five hundred, but then one

107
00:06:29,680 --> 00:06:32,200
Speaker 1: of the computers along that route shuts off. Well, if

108
00:06:32,240 --> 00:06:35,760
Speaker 1: you're sending one big file and it hasn't finished transferring yet,

109
00:06:35,800 --> 00:06:38,520
Speaker 1: then you've got errors, you've got an incomplete file. You're

110
00:06:38,560 --> 00:06:40,560
Speaker 1: gonna have to start all over again. If you divide

111
00:06:40,560 --> 00:06:42,919
Speaker 1: that file into lots of teeny tiny little packets and

112
00:06:42,960 --> 00:06:45,520
Speaker 1: you send all those packets across the network, and not

113
00:06:45,560 --> 00:06:47,599
Speaker 1: all of them are taking the same path. They're all

114
00:06:47,600 --> 00:06:49,920
Speaker 1: going to the same destination, but they're taking different ways

115
00:06:49,960 --> 00:06:53,320
Speaker 1: to get there, then it's far more likely that all

116
00:06:53,320 --> 00:06:56,039
Speaker 1: that information is going to arrive at its destination and

117
00:06:56,080 --> 00:07:01,640
Speaker 1: get reassembled into whatever the original fileile was. That's the

118
00:07:01,680 --> 00:07:07,960
Speaker 1: basics of how internet transfers work. But we're more interested

119
00:07:08,240 --> 00:07:11,880
Speaker 1: in focusing on the other set of rules, the IP,

120
00:07:12,160 --> 00:07:15,480
Speaker 1: the Internet protocol. These are the rules that involve attaching

121
00:07:15,640 --> 00:07:19,160
Speaker 1: addresses to information so that the system can tell where

122
00:07:19,200 --> 00:07:22,760
Speaker 1: the information is coming from and where it is going to.

123
00:07:23,600 --> 00:07:26,360
Speaker 1: It's kind of like the physical postal address that you

124
00:07:26,400 --> 00:07:28,040
Speaker 1: would put on a piece of mail so that the

125
00:07:28,080 --> 00:07:31,320
Speaker 1: post service could accurately deliver your letter, or in the

126
00:07:31,320 --> 00:07:35,120
Speaker 1: event that it's undeliverable could return the letter to you.

127
00:07:35,120 --> 00:07:37,200
Speaker 1: You know, like, if it turns out the address your

128
00:07:37,240 --> 00:07:39,480
Speaker 1: grandma gave you was fake and she's currently on the

129
00:07:39,560 --> 00:07:42,720
Speaker 1: run from the authorities, I might be projecting a little here.

130
00:07:42,760 --> 00:07:46,720
Speaker 1: Stay safe, Grandma. While the first part of tcp IP

131
00:07:47,000 --> 00:07:50,920
Speaker 1: published way back in nineteen seventy four, the IP address

132
00:07:50,920 --> 00:07:54,080
Speaker 1: stuff doesn't really come into play for another decade, mostly

133
00:07:54,120 --> 00:07:57,080
Speaker 1: because it took years to establish a stable version of

134
00:07:57,120 --> 00:08:02,360
Speaker 1: TCPIP that was reliable enough to reply the older NCP rules.

135
00:08:02,400 --> 00:08:06,000
Speaker 1: These things aren't like an overnight switch. As it turns out,

136
00:08:06,480 --> 00:08:09,480
Speaker 1: this included the creation of IP addresses, something that I'm

137
00:08:09,520 --> 00:08:12,440
Speaker 1: sure you have heard about. The original set of rules

138
00:08:12,440 --> 00:08:16,720
Speaker 1: for addresses came about with IPv four, and those involved

139
00:08:16,760 --> 00:08:20,280
Speaker 1: a thirty two bit address. That means that the IPv

140
00:08:20,400 --> 00:08:25,600
Speaker 1: four could represent nearly four point three billion different addresses,

141
00:08:25,640 --> 00:08:28,720
Speaker 1: but I should add that lots of addresses were withheld

142
00:08:29,040 --> 00:08:33,160
Speaker 1: for various reasons. Also, four point three billion wouldn't be

143
00:08:33,320 --> 00:08:36,040
Speaker 1: enough addresses. It was clear that while it was more

144
00:08:36,040 --> 00:08:39,600
Speaker 1: than sufficient for the arpinet days and the early Internet days,

145
00:08:39,840 --> 00:08:43,040
Speaker 1: over time we would eventually run out of addresses to

146
00:08:43,120 --> 00:08:46,160
Speaker 1: assign to devices, and we would need a different solution

147
00:08:46,720 --> 00:08:49,679
Speaker 1: that ultimately would arrive with IPv six, but again, that's

148
00:08:49,679 --> 00:08:53,520
Speaker 1: another topic for a different time. The IPv four address

149
00:08:53,520 --> 00:08:57,720
Speaker 1: format consists of four numbers, and each number is separated

150
00:08:57,760 --> 00:09:00,920
Speaker 1: from the others by a period. Each number could range

151
00:09:00,920 --> 00:09:04,480
Speaker 1: between zero and two hundred and fifty five. Each set

152
00:09:04,480 --> 00:09:08,040
Speaker 1: of numbers is an octet, which means it is made

153
00:09:08,120 --> 00:09:11,680
Speaker 1: up of eight bits or a byte of information, so

154
00:09:11,720 --> 00:09:15,960
Speaker 1: you get four bytes or thirty two bits total. Viola,

155
00:09:16,480 --> 00:09:19,800
Speaker 1: I'm sorry, voila. Gotta just refer to that in my

156
00:09:19,960 --> 00:09:22,760
Speaker 1: notes here. The address can also be thought of as

157
00:09:23,000 --> 00:09:27,240
Speaker 1: two parts. One part represents the network prefix and the

158
00:09:27,280 --> 00:09:30,680
Speaker 1: other part is the host number. So the network prefix

159
00:09:30,720 --> 00:09:33,080
Speaker 1: would be the same for all devices connected to the

160
00:09:33,120 --> 00:09:36,800
Speaker 1: Internet through that same network. The host numbers would be

161
00:09:36,880 --> 00:09:41,680
Speaker 1: unique to the individual devices connected to that network. Also,

162
00:09:41,760 --> 00:09:44,160
Speaker 1: if the device is only visible to the local network,

163
00:09:44,360 --> 00:09:48,000
Speaker 1: it could have a locally unique number that potentially isn't

164
00:09:48,080 --> 00:09:51,480
Speaker 1: globally unique. That means some other device somewhere else on

165
00:09:51,520 --> 00:09:54,520
Speaker 1: the Internet could have that same address. Now, if the

166
00:09:54,559 --> 00:09:58,480
Speaker 1: device is visible to the world at large, then it

167
00:09:58,520 --> 00:10:01,280
Speaker 1: needs its own unique number or else than there's confusion

168
00:10:01,320 --> 00:10:03,560
Speaker 1: because you would have more than one device with the

169
00:10:03,640 --> 00:10:06,280
Speaker 1: same address, which would be kind of like if someone

170
00:10:06,320 --> 00:10:08,800
Speaker 1: in your town somehow has the same address as you,

171
00:10:09,160 --> 00:10:11,200
Speaker 1: but lives in a different part of town entirely. Like

172
00:10:11,280 --> 00:10:14,200
Speaker 1: let's say there's for some reason, two different Oak Streets

173
00:10:14,240 --> 00:10:18,720
Speaker 1: and they have similar numbering conventions for the houses, and

174
00:10:18,800 --> 00:10:22,360
Speaker 1: you live in one twenty three Oak Street on one

175
00:10:22,400 --> 00:10:24,400
Speaker 1: side of town, and someone else lives in one twenty

176
00:10:24,400 --> 00:10:26,280
Speaker 1: three Oak Street on the other side of town, and

177
00:10:26,320 --> 00:10:28,680
Speaker 1: you both would end up getting mail for each other

178
00:10:29,040 --> 00:10:31,959
Speaker 1: on a pretty frequent basis. That would be the same issue.

179
00:10:32,000 --> 00:10:35,560
Speaker 1: So you have to have unique addresses otherwise the whole

180
00:10:35,920 --> 00:10:39,040
Speaker 1: function of the Internet starts to break down. Now, the

181
00:10:39,080 --> 00:10:41,600
Speaker 1: IPv four approach was great and that it made it

182
00:10:41,679 --> 00:10:45,040
Speaker 1: possible for machines to connect to other specific machines across

183
00:10:45,120 --> 00:10:48,040
Speaker 1: a network of networks, which is what the Internet is.

184
00:10:48,440 --> 00:10:51,559
Speaker 1: But while machines could do this fairly simply, it was

185
00:10:51,559 --> 00:10:54,600
Speaker 1: a real bear for human beings because you know, remembering

186
00:10:54,640 --> 00:10:58,120
Speaker 1: a sequence of four numbers for everything that you want

187
00:10:58,200 --> 00:11:01,240
Speaker 1: to send mail to or you want to go visit

188
00:11:01,280 --> 00:11:03,920
Speaker 1: a website on the World Wide Web, that would be

189
00:11:03,920 --> 00:11:07,880
Speaker 1: a huge headache, right, Like, what was this one, two, seven,

190
00:11:08,040 --> 00:11:11,200
Speaker 1: dot like it would just be a nightmare. So what

191
00:11:11,360 --> 00:11:14,920
Speaker 1: was needed was a means to translate those numbers into

192
00:11:14,960 --> 00:11:18,360
Speaker 1: some other format, a format that would be much easier

193
00:11:18,360 --> 00:11:21,079
Speaker 1: for human beings to work with. And thus we enter

194
00:11:21,320 --> 00:11:25,320
Speaker 1: the concept of domain names, which were created as part

195
00:11:25,320 --> 00:11:29,400
Speaker 1: of the Domain Name System, which came into being around

196
00:11:29,440 --> 00:11:33,600
Speaker 1: nineteen eighty three or so. The domain name system would

197
00:11:33,720 --> 00:11:37,240
Speaker 1: allow users to rely on addresses made up of words

198
00:11:37,280 --> 00:11:41,000
Speaker 1: and letters instead of seemingly random numbers. The machines are

199
00:11:41,000 --> 00:11:44,560
Speaker 1: still communicating through numbers. The domain names and addresses are

200
00:11:44,600 --> 00:11:47,160
Speaker 1: just a layer that's easier for humans to work with,

201
00:11:47,280 --> 00:11:49,840
Speaker 1: kind of like programming languages, same sort of thing. It's

202
00:11:49,880 --> 00:11:53,160
Speaker 1: a level of abstraction that's easier for us to handle

203
00:11:53,280 --> 00:11:55,960
Speaker 1: than if we get down to the actual machine code.

204
00:11:56,360 --> 00:11:59,360
Speaker 1: And so there was already precedents for this kind of

205
00:11:59,400 --> 00:12:02,880
Speaker 1: approach using something that humans can work with. Machines can't

206
00:12:02,960 --> 00:12:06,360
Speaker 1: natively work with that format, but you can have it

207
00:12:07,720 --> 00:12:12,840
Speaker 1: interact or relate to machine code or in this case,

208
00:12:12,960 --> 00:12:17,000
Speaker 1: IP addresses that would allow for machines to be able

209
00:12:17,000 --> 00:12:21,280
Speaker 1: to actually make sense of the information. So those domain

210
00:12:21,360 --> 00:12:24,560
Speaker 1: names and addresses, it's just a layer, and each of

211
00:12:24,600 --> 00:12:29,280
Speaker 1: those corresponds to a numeric address. The domains themselves have

212
00:12:29,440 --> 00:12:31,840
Speaker 1: multiple parts. Now, one of those parts is what we

213
00:12:31,960 --> 00:12:36,400
Speaker 1: call the top level domain or TLD. This is what

214
00:12:36,720 --> 00:12:40,480
Speaker 1: we're concerned with when it comes to VeriSign. The TLD

215
00:12:40,679 --> 00:12:43,400
Speaker 1: is the extension that follows the dot at the end

216
00:12:43,440 --> 00:12:46,480
Speaker 1: of a basic URL. So, for example, years ago, I

217
00:12:46,559 --> 00:12:51,280
Speaker 1: wrote for the website HowStuffWorks dot Com. Well, that dot

218
00:12:51,360 --> 00:12:55,240
Speaker 1: com part is the top level domain. The comm stands

219
00:12:55,240 --> 00:12:58,720
Speaker 1: for commercial, and the dot com domain was meant for

220
00:12:58,760 --> 00:13:03,359
Speaker 1: commercial organization. It's also far and away the most popular

221
00:13:03,960 --> 00:13:07,440
Speaker 1: of the top level domains. The house stuff Works bit

222
00:13:07,760 --> 00:13:10,360
Speaker 1: of the address would be what we would call a

223
00:13:10,520 --> 00:13:14,199
Speaker 1: second level domain. The www bit at the beginning of

224
00:13:14,240 --> 00:13:17,760
Speaker 1: the web URL would be a subdomain. But it's the

225
00:13:17,800 --> 00:13:20,920
Speaker 1: top level domains we're really concerned about when we're talking

226
00:13:21,040 --> 00:13:26,040
Speaker 1: about vera sign. So we'll talk more about what that

227
00:13:26,160 --> 00:13:28,280
Speaker 1: means in just a moment, But first let's take a

228
00:13:28,360 --> 00:13:40,960
Speaker 1: quick break to thank our sponsors. All right, So, in

229
00:13:41,080 --> 00:13:43,920
Speaker 1: order to get a domain for a website, you have

230
00:13:43,960 --> 00:13:49,200
Speaker 1: to purchase your domain from a registrar. Registrars are the

231
00:13:49,559 --> 00:13:55,160
Speaker 1: companies responsible for selling and assigning a domain to a customer.

232
00:13:55,360 --> 00:13:59,079
Speaker 1: So if you want a top level domain where your

233
00:13:59,080 --> 00:14:03,800
Speaker 1: top level domain is, well, ultimately your registrar has to

234
00:14:03,800 --> 00:14:07,800
Speaker 1: get that from a registry. These are two different services,

235
00:14:08,080 --> 00:14:13,280
Speaker 1: they're similar, and in fact VeriSign itself historically has operated

236
00:14:13,320 --> 00:14:17,800
Speaker 1: as both, though that changed many years ago. At this point,

237
00:14:17,840 --> 00:14:22,960
Speaker 1: we'll get to that. So if you wanta dot com domain, ultimately,

238
00:14:23,200 --> 00:14:26,360
Speaker 1: once you go up the chain, the supply chain for

239
00:14:26,760 --> 00:14:30,560
Speaker 1: domain names, VeriSign is the stopping point for that. VeriSign

240
00:14:30,680 --> 00:14:37,440
Speaker 1: is the only company that ultimately oversees the registration of

241
00:14:37,560 --> 00:14:41,200
Speaker 1: dot com domains. So how did that happen? How is

242
00:14:41,240 --> 00:14:45,480
Speaker 1: it that a single company became the gatekeeper for the

243
00:14:45,640 --> 00:14:48,760
Speaker 1: dot com TLD. Well, we've got a lot more history

244
00:14:48,800 --> 00:14:51,080
Speaker 1: to get through before we can actually answer that, because

245
00:14:51,120 --> 00:14:54,600
Speaker 1: this is complicated stuff, and this history also gets a

246
00:14:54,600 --> 00:14:57,000
Speaker 1: bit fuzzy because in real life it could be hard

247
00:14:57,040 --> 00:15:00,040
Speaker 1: to point out a firm date and say definitively this

248
00:15:00,240 --> 00:15:04,680
Speaker 1: is when it began. But let's try and muddle our

249
00:15:04,720 --> 00:15:08,320
Speaker 1: way through this. So the DNS, the domain name system,

250
00:15:08,600 --> 00:15:12,520
Speaker 1: becomes a thing around nineteen eighty three, a decade before

251
00:15:12,560 --> 00:15:14,840
Speaker 1: most folks would even have heard of the Internet at

252
00:15:14,840 --> 00:15:17,320
Speaker 1: that point, Because I would argue it was the World

253
00:15:17,360 --> 00:15:19,800
Speaker 1: Wide Web that introduced a lot of people to the

254
00:15:19,840 --> 00:15:22,400
Speaker 1: concept of the Internet, so much so that for a

255
00:15:22,400 --> 00:15:25,720
Speaker 1: lot of folks the two are synonymous, although the World

256
00:15:25,720 --> 00:15:28,480
Speaker 1: Wide Web is just one set of services that exists

257
00:15:28,600 --> 00:15:32,840
Speaker 1: on top of the Internet. Before the DNS, engineers working

258
00:15:32,920 --> 00:15:36,120
Speaker 1: on ARPINET had established a sort of catalog to keep

259
00:15:36,160 --> 00:15:40,800
Speaker 1: track of network infrastructure, sockets, addresses, and other words. John

260
00:15:40,880 --> 00:15:44,680
Speaker 1: Postel and Joyce K Reynolds were chiefly responsible for keeping

261
00:15:44,720 --> 00:15:49,160
Speaker 1: track of IP addresses from the earliest days, which is

262
00:15:49,240 --> 00:15:51,760
Speaker 1: pretty wild because this was just kind of a side

263
00:15:51,880 --> 00:15:56,120
Speaker 1: quest to their main responsibilities. It wasn't their job to

264
00:15:56,200 --> 00:15:58,800
Speaker 1: do this, they did it in addition to their jobs.

265
00:15:59,200 --> 00:16:03,800
Speaker 1: Somewhat orally, a department that ultimately became known as the

266
00:16:03,840 --> 00:16:09,040
Speaker 1: Internet Assigned Numbers Authority or IANA would start to take

267
00:16:09,160 --> 00:16:13,600
Speaker 1: form now according to various RFCs, which stands for Request

268
00:16:13,640 --> 00:16:17,640
Speaker 1: for Comments. RFCs are in large part the documentation the

269
00:16:17,760 --> 00:16:21,880
Speaker 1: historical documents that help us keep track of how the

270
00:16:22,360 --> 00:16:26,840
Speaker 1: Internet gradually took shape, and they are hard to follow

271
00:16:27,280 --> 00:16:30,400
Speaker 1: if you're not an engineer, and I'm not. They are

272
00:16:30,840 --> 00:16:33,920
Speaker 1: a challenge to follow because they weren't necessarily written to

273
00:16:34,040 --> 00:16:39,600
Speaker 1: be like a historical documentation, they were an ongoing discussion

274
00:16:39,680 --> 00:16:43,080
Speaker 1: among the various people working on the systems to keep

275
00:16:43,200 --> 00:16:47,840
Speaker 1: up with what's going on and to share developments. Anyway,

276
00:16:48,320 --> 00:16:51,720
Speaker 1: the first appearance of ia in A in an RFC

277
00:16:51,840 --> 00:16:55,280
Speaker 1: documentation was somewhere in the late nineteen eighties. But those

278
00:16:55,400 --> 00:16:59,480
Speaker 1: very same documents that mention ia in a by name

279
00:16:59,640 --> 00:17:03,400
Speaker 1: for the time say essentially that the department, or the

280
00:17:03,400 --> 00:17:07,000
Speaker 1: functions at least were as old as arpinnet itself. The

281
00:17:07,040 --> 00:17:10,000
Speaker 1: engineers just hadn't documented an official name for it for

282
00:17:10,080 --> 00:17:13,800
Speaker 1: a couple of decades now. In addition to Postel's work,

283
00:17:14,600 --> 00:17:19,000
Speaker 1: an engineer named Elizabeth Feinler developed a directory of numerical

284
00:17:19,080 --> 00:17:21,760
Speaker 1: addresses reference through a list of host names and a

285
00:17:21,800 --> 00:17:27,720
Speaker 1: document titled hosts dot txt. Feindler would manually add host

286
00:17:27,800 --> 00:17:32,439
Speaker 1: names and their assigned numeric addresses to the directory, and

287
00:17:32,920 --> 00:17:35,879
Speaker 1: it was Feinler's department that gradually developed the idea for

288
00:17:35,960 --> 00:17:38,400
Speaker 1: domain names to make it easier for humans to work

289
00:17:38,440 --> 00:17:41,879
Speaker 1: with the system instead of having to do this cross referencing,

290
00:17:42,040 --> 00:17:44,840
Speaker 1: where you know, you look up a host name, like

291
00:17:44,920 --> 00:17:48,040
Speaker 1: you know what host name you want to send information to,

292
00:17:48,320 --> 00:17:49,879
Speaker 1: so you look it up in this directory so you

293
00:17:49,880 --> 00:17:52,359
Speaker 1: can find the IP address you need to use in

294
00:17:52,440 --> 00:17:56,000
Speaker 1: order to send the information there. Well, that's already complicated

295
00:17:56,119 --> 00:17:58,400
Speaker 1: enough just on its own, but it was getting far

296
00:17:58,480 --> 00:18:03,199
Speaker 1: more complicated as more machines were joining the network. You know,

297
00:18:03,280 --> 00:18:05,959
Speaker 1: each time a new machine joins the network, it adds

298
00:18:06,000 --> 00:18:09,879
Speaker 1: to the complexity of the overall system. That complexity would

299
00:18:09,920 --> 00:18:14,120
Speaker 1: grow considerably throughout the nineteen eighties and nineteen nineties. Now,

300
00:18:14,160 --> 00:18:18,439
Speaker 1: for a long time, those machines joining the networks were

301
00:18:18,560 --> 00:18:25,240
Speaker 1: either from research institutions, universities and colleges, or government agencies,

302
00:18:25,240 --> 00:18:28,080
Speaker 1: including the military, And in fact, the military and large

303
00:18:28,119 --> 00:18:31,399
Speaker 1: part was funding a lot of the work going into this.

304
00:18:31,800 --> 00:18:36,000
Speaker 1: Keep in mind, you know, ARPINET started as a defense project,

305
00:18:36,200 --> 00:18:39,320
Speaker 1: right DARPA what is today called DARPA. Back in the day,

306
00:18:39,359 --> 00:18:41,760
Speaker 1: it was called ARPA. So it all started as a

307
00:18:41,800 --> 00:18:45,520
Speaker 1: defense thing, and for the longest time, the government oversaw stuff.

308
00:18:45,600 --> 00:18:50,040
Speaker 1: But gradually that would start to shift as more, you know,

309
00:18:50,440 --> 00:18:54,040
Speaker 1: non government folks were starting to get involved in the network.

310
00:18:54,359 --> 00:18:58,439
Speaker 1: John Postel continued to oversee the process of assigning names

311
00:18:58,480 --> 00:19:02,119
Speaker 1: and addresses up to the late nineteen nineties, which is

312
00:19:02,119 --> 00:19:04,720
Speaker 1: pretty phenomenal because by then you're getting into the dot

313
00:19:04,760 --> 00:19:09,240
Speaker 1: com days. But around ninety seven, the United States government

314
00:19:09,320 --> 00:19:15,200
Speaker 1: stepped in. The National Telecommunications and Information Administration or NTIA

315
00:19:15,280 --> 00:19:17,760
Speaker 1: we'll talk about them later, which itself is part of

316
00:19:17,760 --> 00:19:20,720
Speaker 1: the US Department of Commerce, sought to create a new

317
00:19:20,840 --> 00:19:25,280
Speaker 1: nonprofit organization that would oversee functions such as assigning DNS

318
00:19:25,320 --> 00:19:28,640
Speaker 1: addresses and that kind of thing. In late nineteen ninety eight,

319
00:19:28,920 --> 00:19:33,200
Speaker 1: it created the Internet Corporation for Assigned Names and Numbers

320
00:19:33,320 --> 00:19:37,680
Speaker 1: or ICON i CAN if you prefer ICA n N.

321
00:19:38,080 --> 00:19:44,800
Speaker 1: Now i CAN assumed the responsibility of overseeing the DNS

322
00:19:45,119 --> 00:19:49,600
Speaker 1: functions of IANA IAANA. So lots of acronyms in this too.

323
00:19:49,600 --> 00:19:52,119
Speaker 1: I'm apologizing for that, but you know I wasn't the

324
00:19:52,119 --> 00:19:54,720
Speaker 1: one who came up with him. So John Postel was

325
00:19:55,200 --> 00:19:58,119
Speaker 1: meant to be the chief technology officer for i CAN,

326
00:19:58,359 --> 00:20:01,720
Speaker 1: but sadly he passed away following a surgical procedure and

327
00:20:01,800 --> 00:20:06,240
Speaker 1: he died about a month after i CAN was first incorporated. Okay,

328
00:20:06,320 --> 00:20:09,359
Speaker 1: but now we have to talk about another organization that

329
00:20:09,520 --> 00:20:11,920
Speaker 1: was operating at the same time as all the stuff

330
00:20:11,960 --> 00:20:14,800
Speaker 1: I just mentioned. This is where Elizabeth Feindler comes back

331
00:20:14,800 --> 00:20:18,280
Speaker 1: into it, and this would be the Network Information Center

332
00:20:18,800 --> 00:20:23,840
Speaker 1: the NIC or NICK, later known as INTERNICK. This organization

333
00:20:23,920 --> 00:20:27,080
Speaker 1: grew out of the Stanford Research Institute, which is now

334
00:20:27,119 --> 00:20:30,879
Speaker 1: known as SRI International. And I'm just going to refer

335
00:20:30,960 --> 00:20:33,800
Speaker 1: to it as INTERNICK as a matter of convenience, but

336
00:20:33,840 --> 00:20:37,000
Speaker 1: it actually didn't get that name until like the nineteen nineties.

337
00:20:37,160 --> 00:20:39,119
Speaker 1: I'm just going to use that name rather than switching

338
00:20:39,160 --> 00:20:40,960
Speaker 1: back and forth because we're already going to have so

339
00:20:41,000 --> 00:20:44,280
Speaker 1: many different names and acronyms in this and initialisms. So

340
00:20:44,680 --> 00:20:47,880
Speaker 1: internick was kind of like a reference library. It maintained

341
00:20:47,880 --> 00:20:50,760
Speaker 1: a directory of address numbers and published them to the

342
00:20:50,800 --> 00:20:55,359
Speaker 1: network at large, and it handled actual registration requests. So

343
00:20:55,600 --> 00:20:59,880
Speaker 1: this was Elizabeth Feindler's group. Stanford oversaw Internet until night

344
00:20:59,840 --> 00:21:04,720
Speaker 1: teen ninety one, and at that point the department changed hands.

345
00:21:05,119 --> 00:21:08,680
Speaker 1: And this is bringing us ever closer to VERI sign.

346
00:21:08,720 --> 00:21:12,080
Speaker 1: We're not there yet, but we're getting closer. So the

347
00:21:12,160 --> 00:21:16,520
Speaker 1: company that would take over Internet in nineteen ninety one

348
00:21:16,720 --> 00:21:21,040
Speaker 1: was called Network Solutions. Now, technically the US government gave

349
00:21:21,080 --> 00:21:24,800
Speaker 1: the job of overseeing Internet to another company called Government

350
00:21:24,840 --> 00:21:29,000
Speaker 1: Systems Incorporated, But then Government Systems turned around and subcontracted

351
00:21:29,040 --> 00:21:32,440
Speaker 1: the work to Network Solutions. This is a great business

352
00:21:32,440 --> 00:21:34,080
Speaker 1: to get in. By the way, if you can be

353
00:21:34,119 --> 00:21:38,520
Speaker 1: a business that lands huge contracts and then you subcontract

354
00:21:38,600 --> 00:21:42,320
Speaker 1: that work to someone else and you just keep the difference, man,

355
00:21:42,480 --> 00:21:46,040
Speaker 1: what a racket. Not saying that government systems was a racket,

356
00:21:46,040 --> 00:21:50,000
Speaker 1: but golly sure, I sure could get into that biz anyway.

357
00:21:50,040 --> 00:21:53,160
Speaker 1: So Network Solutions got its start in nineteen seventy nine

358
00:21:53,280 --> 00:21:56,000
Speaker 1: as a consulting company in the tech sector, and in

359
00:21:56,080 --> 00:21:58,919
Speaker 1: nineteen ninety three it won a bid to become the

360
00:21:59,040 --> 00:22:04,400
Speaker 1: exclusive register nation services provider for non military entities wishing

361
00:22:04,440 --> 00:22:07,800
Speaker 1: to register a domain on the Internet. It won this

362
00:22:07,920 --> 00:22:12,400
Speaker 1: bid by being using by following a very very sound strategy,

363
00:22:12,520 --> 00:22:15,800
Speaker 1: being the only company that actually bid for the gig. Now,

364
00:22:15,840 --> 00:22:18,480
Speaker 1: this meant that Network Solutions was the one and only

365
00:22:18,640 --> 00:22:21,160
Speaker 1: place someone could go to if they wanted to register

366
00:22:21,359 --> 00:22:25,040
Speaker 1: a TLD that was in the dot org, dot net

367
00:22:25,080 --> 00:22:30,280
Speaker 1: and dot com categories. Network Solutions had a monopoly on

368
00:22:30,359 --> 00:22:33,520
Speaker 1: that business. Now, I call it a business, but in truth,

369
00:22:33,600 --> 00:22:37,000
Speaker 1: at the time it wasn't really a business because Network

370
00:22:37,040 --> 00:22:41,159
Speaker 1: Solutions was not allowed to charge for domain name registrations.

371
00:22:41,840 --> 00:22:46,080
Speaker 1: Yet it was still a free service ultimately provided by

372
00:22:46,080 --> 00:22:51,000
Speaker 1: the government, so the government was essentially paying this company

373
00:22:51,040 --> 00:22:54,439
Speaker 1: Government Systems, which in turn was paying Network Solutions to

374
00:22:54,600 --> 00:22:59,680
Speaker 1: oversee this process. But they weren't turning people into customers.

375
00:22:59,720 --> 00:23:03,680
Speaker 1: They were providing a service for free that was government funded.

376
00:23:04,119 --> 00:23:09,240
Speaker 1: In nineteen ninety five, another company called Science Applications International

377
00:23:09,280 --> 00:23:13,760
Speaker 1: Corporation or SAIC, or as I prefer to call them, PSYCH,

378
00:23:14,680 --> 00:23:18,840
Speaker 1: they acquired Network Solutions for four point seven million dollars.

379
00:23:19,440 --> 00:23:23,600
Speaker 1: Keep that number in mind, because holy cats, will that

380
00:23:24,080 --> 00:23:27,919
Speaker 1: be a world of difference in just five years. Further

381
00:23:28,000 --> 00:23:32,280
Speaker 1: into this history, not long after PSYCH took over control

382
00:23:32,440 --> 00:23:38,400
Speaker 1: of Network Solutions, the National Science Foundation or NSF, gave

383
00:23:38,560 --> 00:23:42,399
Speaker 1: PSYCH and therefore Network Solutions, the power to charge a

384
00:23:42,520 --> 00:23:47,080
Speaker 1: fee for registering domain names. This is where things start

385
00:23:47,119 --> 00:23:50,479
Speaker 1: to shift, where now it is a business. Before it

386
00:23:50,520 --> 00:23:52,840
Speaker 1: was a service that was government funded. Now it's a

387
00:23:52,880 --> 00:23:56,560
Speaker 1: business where Network Solutions can charge a fee in order

388
00:23:56,600 --> 00:23:59,920
Speaker 1: to register a domain name to customers. Not at that point,

389
00:24:00,160 --> 00:24:03,520
Speaker 1: Network Solutions began to charge applicants a one hundred dollars

390
00:24:03,760 --> 00:24:06,439
Speaker 1: and for one hundred dollars you could register a domain

391
00:24:06,520 --> 00:24:09,520
Speaker 1: name for a period of two years, and after two

392
00:24:09,600 --> 00:24:12,879
Speaker 1: years you would need to renew your registration. Thirty percent

393
00:24:13,000 --> 00:24:16,200
Speaker 1: of the fee that Network Solutions charged would end up

394
00:24:16,240 --> 00:24:19,800
Speaker 1: going to the National Science Foundation in SF to help

395
00:24:20,040 --> 00:24:24,200
Speaker 1: fund other services. But this rubbed people the wrong way

396
00:24:24,680 --> 00:24:28,679
Speaker 1: because it was a single service provider. Here there was

397
00:24:28,720 --> 00:24:32,200
Speaker 1: no competition. You couldn't go anywhere else to register a

398
00:24:32,320 --> 00:24:37,520
Speaker 1: top level domain URL or address. So in nineteen ninety

399
00:24:37,560 --> 00:24:40,880
Speaker 1: seven a lawsuit argued that Network Solutions was in fact

400
00:24:41,000 --> 00:24:45,440
Speaker 1: a monopoly and because thirty percent of the fees being

401
00:24:45,480 --> 00:24:48,480
Speaker 1: paid to Network Solutions were going to a government agency,

402
00:24:48,520 --> 00:24:53,080
Speaker 1: that amounted to illegal taxation. So Network Solutions ended up

403
00:24:53,400 --> 00:24:56,280
Speaker 1: ending its payments out to the NSF. It could still

404
00:24:56,400 --> 00:25:01,639
Speaker 1: charge for registration, but that thirty percent would go to NSF. Thankfully,

405
00:25:02,000 --> 00:25:05,240
Speaker 1: that also meant that at least initially, the cost for

406
00:25:05,440 --> 00:25:08,399
Speaker 1: registering a domain dropped by thirty percent, so it became

407
00:25:08,440 --> 00:25:12,520
Speaker 1: seventy dollars for two years before you needed to renew.

408
00:25:12,960 --> 00:25:16,600
Speaker 1: So in nineteen ninety eight, i CAN was given the

409
00:25:16,640 --> 00:25:21,240
Speaker 1: authority to oversee the dns, and i CAN chose Surprise

410
00:25:21,280 --> 00:25:25,480
Speaker 1: Surprise Network Solutions to continue to have this exclusive holdover

411
00:25:25,600 --> 00:25:29,920
Speaker 1: dot net, dot Oregon, dot Com TLDs. So for Network Solutions,

412
00:25:29,920 --> 00:25:33,440
Speaker 1: nothing really changed other than i CAN became the new

413
00:25:33,520 --> 00:25:38,199
Speaker 1: authority overseeing this rather than specifically the NSF. Not that

414
00:25:38,280 --> 00:25:41,960
Speaker 1: the NSF would be uninvolved, but you get the point,

415
00:25:42,200 --> 00:25:44,840
Speaker 1: all right. So this holds true for a couple of years.

416
00:25:44,840 --> 00:25:47,639
Speaker 1: We skip ahead to two thousand. It's the heady days

417
00:25:47,680 --> 00:25:51,520
Speaker 1: of the dot com boom, before the bubble had actually burst,

418
00:25:51,720 --> 00:25:54,880
Speaker 1: and numerous companies would find themselves struggling to stay in business.

419
00:25:55,080 --> 00:25:59,159
Speaker 1: But that's when Network Solutions got a new owner, and

420
00:25:59,240 --> 00:26:03,159
Speaker 1: this is where or VeriSign finally comes into play. So

421
00:26:04,000 --> 00:26:07,560
Speaker 1: VeriSign got its start back in nineteen ninety five, so

422
00:26:07,640 --> 00:26:09,840
Speaker 1: it was a relatively young company. It was only five

423
00:26:09,920 --> 00:26:12,280
Speaker 1: years old when it made this move, and it had

424
00:26:12,320 --> 00:26:16,120
Speaker 1: started off as a provider of certification services, and by

425
00:26:16,119 --> 00:26:20,520
Speaker 1: that I mean Internet certification services. So you know that

426
00:26:20,680 --> 00:26:23,880
Speaker 1: when you sign on to a website and you see

427
00:26:23,880 --> 00:26:28,639
Speaker 1: that little padlock symbol up in your urlbar, that padlock

428
00:26:28,680 --> 00:26:32,600
Speaker 1: symbol indicates that the site you're visiting is protecting the

429
00:26:32,760 --> 00:26:36,880
Speaker 1: data traffic between you and that website through encryption, meaning

430
00:26:36,920 --> 00:26:40,520
Speaker 1: that if anyone else snooped in on your data transfers

431
00:26:40,600 --> 00:26:43,400
Speaker 1: to that website, all they would get was encrypted data,

432
00:26:43,440 --> 00:26:46,199
Speaker 1: which wouldn't mean anything to them, at least assuming the

433
00:26:46,280 --> 00:26:50,800
Speaker 1: encryption is really good. The padlock shows that the protection

434
00:26:50,960 --> 00:26:56,880
Speaker 1: is certified, meaning some other authority has analyzed and certified

435
00:26:57,160 --> 00:27:00,920
Speaker 1: that the process is secure. VeriSign one of the companies

436
00:27:00,920 --> 00:27:04,840
Speaker 1: that provided that kind of certification, thus ensuring that digital

437
00:27:04,960 --> 00:27:08,159
Speaker 1: commerce could occur safely over the internet. Keep in mind,

438
00:27:08,520 --> 00:27:12,040
Speaker 1: back in nineteen ninety five, commerce online was a new

439
00:27:12,200 --> 00:27:16,840
Speaker 1: and scary idea. People were understandably reticent to just plug

440
00:27:16,880 --> 00:27:19,520
Speaker 1: their credit card numbers into a computer. You never knew

441
00:27:19,560 --> 00:27:22,480
Speaker 1: who might get hold of that information. So companies like

442
00:27:22,600 --> 00:27:25,639
Speaker 1: VeriSign would end up playing a really important part in

443
00:27:25,760 --> 00:27:30,160
Speaker 1: establishing a safe and secure infrastructure to allow online commerce

444
00:27:30,240 --> 00:27:33,680
Speaker 1: to actually become a thing. And business must have been

445
00:27:33,920 --> 00:27:38,960
Speaker 1: pretty darn good, because in two thousand, VeriSign made a

446
00:27:39,160 --> 00:27:44,680
Speaker 1: huge move and acquired Network Solutions from Psych for the

447
00:27:44,880 --> 00:27:50,400
Speaker 1: princely sum of twenty one billion with a B dollars. Now,

448
00:27:50,440 --> 00:27:55,480
Speaker 1: remember Psych Saic had purchased Network Solutions for less than

449
00:27:55,600 --> 00:28:00,280
Speaker 1: five million with an M dollars back in nineteen ninety five,

450
00:28:00,480 --> 00:28:04,440
Speaker 1: then sold it five years later for twenty one billion dollars. That,

451
00:28:04,680 --> 00:28:07,240
Speaker 1: my friends, is a heck of a return on investment.

452
00:28:07,680 --> 00:28:11,040
Speaker 1: But it's not as clear as all that it's not

453
00:28:11,440 --> 00:28:14,159
Speaker 1: as amazing a turnaround as that. I mean, it is

454
00:28:14,160 --> 00:28:18,280
Speaker 1: an amazing turnaround, But to be honest, SAIC had actually

455
00:28:18,280 --> 00:28:21,080
Speaker 1: been selling off portions of its ownership, like it had

456
00:28:21,119 --> 00:28:24,440
Speaker 1: been selling off percentages of its stake in Network Solutions

457
00:28:24,480 --> 00:28:27,920
Speaker 1: to other parties since it had acquired the company in

458
00:28:28,000 --> 00:28:33,000
Speaker 1: nineteen ninety five. So while SAIC saw an enormous payout

459
00:28:33,440 --> 00:28:36,200
Speaker 1: due to this acquisition, it wasn't as impressive as it

460
00:28:36,240 --> 00:28:39,200
Speaker 1: would have been if, in fact, it held full ownership

461
00:28:39,240 --> 00:28:42,000
Speaker 1: of Network Solutions at that point. But you get the idea,

462
00:28:42,320 --> 00:28:45,600
Speaker 1: you know, four point seven million to twenty one billion

463
00:28:45,720 --> 00:28:49,840
Speaker 1: in five years phenomenal. It also says a lot that

464
00:28:50,080 --> 00:28:55,320
Speaker 1: the original version of Network Solutions was essentially a government

465
00:28:55,440 --> 00:28:59,960
Speaker 1: funded and thus government restricted business, So it was also

466
00:29:00,120 --> 00:29:03,000
Speaker 1: a very different world in ninety five than it was

467
00:29:03,000 --> 00:29:05,320
Speaker 1: in two thousand. All Right, we're going to take another

468
00:29:05,400 --> 00:29:07,960
Speaker 1: quick break. When we come back, we'll talk more about

469
00:29:08,400 --> 00:29:22,600
Speaker 1: VeriSign and the current concerns surrounding the company. All right,

470
00:29:22,640 --> 00:29:25,160
Speaker 1: we're back. So before the break, we talked about how

471
00:29:25,440 --> 00:29:28,640
Speaker 1: VeriSign comes in and buys Network Solutions, and by the

472
00:29:28,680 --> 00:29:32,960
Speaker 1: transitive property of ownership, VeriSign becomes the new exclusive keeper

473
00:29:33,200 --> 00:29:37,000
Speaker 1: of the dot com, dot net and dot org TLD's

474
00:29:37,120 --> 00:29:40,160
Speaker 1: top level domains. That's when the Security is in Exchange

475
00:29:40,200 --> 00:29:44,239
Speaker 1: Commission where SEC took an interest in VeriSign. So for

476
00:29:44,280 --> 00:29:49,280
Speaker 1: a while, Network Solutions had been operating two distinct but

477
00:29:49,440 --> 00:29:54,080
Speaker 1: related businesses. Business number one was to serve as a registry.

478
00:29:54,240 --> 00:29:58,240
Speaker 1: Now essentially, a registry serves as a database, and it

479
00:29:58,280 --> 00:30:04,800
Speaker 1: could sell top level main addresses wholesale to registrars. Registrars

480
00:30:05,120 --> 00:30:10,720
Speaker 1: could then sell domain names or domain name registrations to customers. However,

481
00:30:11,200 --> 00:30:15,360
Speaker 1: Network Solutions was also acting as a registrar itself, so

482
00:30:15,400 --> 00:30:19,680
Speaker 1: it's both a registry and a registrar. The SEC felt

483
00:30:20,000 --> 00:30:23,600
Speaker 1: this was way too much power concentrated into a single organization,

484
00:30:23,680 --> 00:30:27,720
Speaker 1: and it could use its monopolistic holdover the dot com,

485
00:30:27,760 --> 00:30:32,880
Speaker 1: dot net and dot org TLDs to create predatory pricing.

486
00:30:33,400 --> 00:30:38,600
Speaker 1: So VeriSign sold off its registrar business and held onto

487
00:30:38,640 --> 00:30:42,680
Speaker 1: the registry part. Now, VeriSign could sell top level domains

488
00:30:42,680 --> 00:30:46,080
Speaker 1: wholesale to registrars, and the registrars in turn could sell

489
00:30:46,120 --> 00:30:49,720
Speaker 1: those two customers. So effectively, this meant VeriSign sold off

490
00:30:49,880 --> 00:30:54,160
Speaker 1: part of Network Solutions to another company called Pivotal Equity Groups.

491
00:30:54,200 --> 00:30:56,880
Speaker 1: So we'll say by by to Network Solutions from this

492
00:30:56,960 --> 00:31:01,520
Speaker 1: point forward. Just know that the services that Networkstions provided,

493
00:31:02,080 --> 00:31:06,840
Speaker 1: at least regarding being a registry, are now verisigns. So

494
00:31:07,040 --> 00:31:10,200
Speaker 1: VeriSign would remain the sole organization ultimately in charge of

495
00:31:10,240 --> 00:31:13,680
Speaker 1: those dot com TLDs. And that's where the current situation

496
00:31:13,840 --> 00:31:16,760
Speaker 1: comes back into play. So at the heart of the

497
00:31:16,800 --> 00:31:20,480
Speaker 1: issue is a change in the rules that VeriSign has

498
00:31:20,520 --> 00:31:22,920
Speaker 1: to follow when it comes to how much it can

499
00:31:23,000 --> 00:31:26,840
Speaker 1: charge customers for registering TLDs. Keep in mind this is

500
00:31:26,880 --> 00:31:30,560
Speaker 1: because the government, the US government, has been heavily involved

501
00:31:30,560 --> 00:31:34,840
Speaker 1: in this from the beginning. Initially, the predecessor to averisign

502
00:31:35,040 --> 00:31:40,440
Speaker 1: was not allowed to charge for registering top level domain names.

503
00:31:40,560 --> 00:31:44,120
Speaker 1: You couldn't do it. It was all government provided. But the

504
00:31:44,360 --> 00:31:48,480
Speaker 1: slow transition from the Internet being a government owned and

505
00:31:48,640 --> 00:31:55,400
Speaker 1: operated entity to a global market entity unto itself meant

506
00:31:55,440 --> 00:31:59,040
Speaker 1: that things had to change. So there were still rules

507
00:31:59,200 --> 00:32:04,080
Speaker 1: in place to keep VeriSign or its predecessor from charging

508
00:32:04,080 --> 00:32:08,520
Speaker 1: out the wazoo. Because being a single company in charge

509
00:32:08,560 --> 00:32:13,880
Speaker 1: of this this particular commodity, the dot com TLDs, there

510
00:32:13,920 --> 00:32:17,960
Speaker 1: needed to be some restrictions otherwise, because the dot com

511
00:32:18,000 --> 00:32:21,720
Speaker 1: domain names are so valuable, you would end up getting

512
00:32:21,800 --> 00:32:25,760
Speaker 1: charged ridiculous amounts of money in order to register your

513
00:32:25,840 --> 00:32:28,960
Speaker 1: domain name. You might still get that, but that's because

514
00:32:29,000 --> 00:32:33,400
Speaker 1: the registrar, not the registry. So at the heart of

515
00:32:33,440 --> 00:32:36,960
Speaker 1: the current matter is a change in the rules that

516
00:32:37,080 --> 00:32:39,880
Speaker 1: VeriSign has to follow when it comes to how much

517
00:32:39,880 --> 00:32:43,680
Speaker 1: it charges its customers for registering TLDs. Now, according to

518
00:32:43,760 --> 00:32:49,560
Speaker 1: a letter from Senator Warren and Representative Nadler, quote, VeriSign

519
00:32:49,760 --> 00:32:53,479
Speaker 1: is exploiting its monopoly power to charge millions of users

520
00:32:53,640 --> 00:32:57,440
Speaker 1: excessive prices for registering a dot Com top level domain.

521
00:32:57,800 --> 00:33:01,760
Speaker 1: VeriSign hasn't changed or in improved its services. It has

522
00:33:01,760 --> 00:33:06,280
Speaker 1: simply raised prices because it holds a government insured monopoly

523
00:33:06,560 --> 00:33:11,360
Speaker 1: end quote now. Essentially, during the previous Trump administration, the

524
00:33:11,440 --> 00:33:14,880
Speaker 1: government eased off a little bit on the restrictions it

525
00:33:14,960 --> 00:33:18,680
Speaker 1: had placed over how much VeriSign was allowed to charge customers.

526
00:33:18,960 --> 00:33:23,680
Speaker 1: So the company, once these restrictions were gone, increased its prices. Now,

527
00:33:23,720 --> 00:33:27,440
Speaker 1: according to the letter from the politicians I mentioned earlier,

528
00:33:27,680 --> 00:33:31,040
Speaker 1: that increase was around thirty percent, So the prices went

529
00:33:31,120 --> 00:33:35,080
Speaker 1: up by thirty percent but the services provided hadn't changed

530
00:33:35,120 --> 00:33:38,600
Speaker 1: in any material way, So you're paying thirty percent more

531
00:33:38,880 --> 00:33:42,480
Speaker 1: for the exact same service you had earlier. Nothing else

532
00:33:42,560 --> 00:33:46,480
Speaker 1: has improved or been fleshed out further. Again, this is

533
00:33:46,520 --> 00:33:50,000
Speaker 1: according to their letter, So essentially, Warren and Nadler are saying,

534
00:33:50,040 --> 00:33:52,440
Speaker 1: you're charging more for the same services, and because you

535
00:33:52,440 --> 00:33:55,280
Speaker 1: have a monopoly, there's nowhere else for customers to go,

536
00:33:55,720 --> 00:33:59,440
Speaker 1: so this amounts to price gouging. Now, as you might imagine,

537
00:33:59,640 --> 00:34:03,040
Speaker 1: various design objects to the way that this has been framed.

538
00:34:03,120 --> 00:34:07,040
Speaker 1: The company claims that a quote small, self interested group

539
00:34:07,080 --> 00:34:11,200
Speaker 1: of domain name investors end quote are behind all this.

540
00:34:11,719 --> 00:34:14,839
Speaker 1: That you know, this isn't a real public issue. It's

541
00:34:14,840 --> 00:34:18,080
Speaker 1: something that some people who have a vested interest in

542
00:34:18,120 --> 00:34:22,400
Speaker 1: the matter are pursuing because they have the potential to

543
00:34:22,440 --> 00:34:25,160
Speaker 1: make a lot of money if things change. But things

544
00:34:25,200 --> 00:34:29,040
Speaker 1: shouldn't change because they're not inherently unfair, according to VeriSign,

545
00:34:29,480 --> 00:34:33,480
Speaker 1: and also says that the complaints the politicians are raising

546
00:34:33,560 --> 00:34:39,640
Speaker 1: echo some so called inaccuracies around the TLD registry business. Also,

547
00:34:39,800 --> 00:34:43,600
Speaker 1: VeriSign says there are alternatives to dot com in the

548
00:34:43,600 --> 00:34:47,040
Speaker 1: TLD space, so that means that VeriSign's not operating a monopoly,

549
00:34:47,360 --> 00:34:49,799
Speaker 1: and I guess that's an argument. I mean, you could

550
00:34:49,800 --> 00:34:54,120
Speaker 1: say VeriSign does have a monopolistic holdover dot com domains.

551
00:34:54,440 --> 00:34:59,680
Speaker 1: That's indisputable. They do. They're the soul registry for dot com.

552
00:35:00,080 --> 00:35:03,439
Speaker 1: But it's also true that there are other registries out

553
00:35:03,480 --> 00:35:07,839
Speaker 1: there for other kinds of TLDs. So, for example, if

554
00:35:07,880 --> 00:35:11,160
Speaker 1: you wanted to register a domain that had a dot

555
00:35:11,280 --> 00:35:14,680
Speaker 1: tv as its top level domain, well then you would

556
00:35:14,719 --> 00:35:17,600
Speaker 1: have to go through go Daddy registry. By the way,

557
00:35:17,680 --> 00:35:21,799
Speaker 1: technically dot tv is an Internet country Code top level

558
00:35:21,800 --> 00:35:25,480
Speaker 1: domain and it's for TAVALU, but a lot of sites

559
00:35:25,560 --> 00:35:29,160
Speaker 1: use dot TV because TV can also mean television. Thus

560
00:35:29,239 --> 00:35:33,960
Speaker 1: you have things like dropout TV. Complicating matters is the

561
00:35:33,960 --> 00:35:37,480
Speaker 1: fact that I can ultimately has the authority to reject

562
00:35:37,520 --> 00:35:41,279
Speaker 1: price hikes in the Domain Name Registry Services space, and

563
00:35:41,760 --> 00:35:45,680
Speaker 1: this comes from the NTIA. So hang on, if I

564
00:35:45,880 --> 00:35:51,480
Speaker 1: can is able to reject price hikes, then where's the problem?

565
00:35:51,800 --> 00:35:55,120
Speaker 1: Because yes, you do have VeriSign as an entity that

566
00:35:55,160 --> 00:35:59,680
Speaker 1: has exclusive rights to the dot Com registry business. However,

567
00:36:00,360 --> 00:36:03,919
Speaker 1: if a nonprofit organization that's closely associated with the US

568
00:36:04,000 --> 00:36:08,560
Speaker 1: government ultimately has authority to reject price increases. Doesn't that

569
00:36:08,680 --> 00:36:12,920
Speaker 1: solve things? Well, not so fast, because back in twenty twenty,

570
00:36:13,400 --> 00:36:16,920
Speaker 1: VeriSign and i CAN signed an agreement in which VeriSign

571
00:36:17,040 --> 00:36:20,520
Speaker 1: was allowed to increase prices to a certain maximum and

572
00:36:20,640 --> 00:36:24,399
Speaker 1: in return, i CAN would receive twenty million dollars over

573
00:36:24,440 --> 00:36:27,200
Speaker 1: the course of five years. Now, Warren and Nadler are

574
00:36:27,239 --> 00:36:30,040
Speaker 1: saying this appears to be a case of collusion, where

575
00:36:30,040 --> 00:36:35,200
Speaker 1: these two organizations have colluded and created a mutually beneficial

576
00:36:35,520 --> 00:36:42,120
Speaker 1: relationship that is ultimately predating upon customers. So the customers

577
00:36:42,160 --> 00:36:45,960
Speaker 1: are unfairly burdened with price increases and they have no recourse,

578
00:36:46,360 --> 00:36:49,120
Speaker 1: they have no competing service they can go to to

579
00:36:49,160 --> 00:36:51,840
Speaker 1: get a dot com top level domain, and they're not

580
00:36:51,960 --> 00:36:55,880
Speaker 1: getting an improvement in their services now. As wireds Joel

581
00:36:56,080 --> 00:36:58,719
Speaker 1: khalely reported back in late November, I think it was

582
00:36:58,800 --> 00:37:03,759
Speaker 1: November twenty second, the National Telecommunications and Information Administration or

583
00:37:03,880 --> 00:37:08,800
Speaker 1: NTIA was set to renew this agreement with VeriSign after

584
00:37:08,920 --> 00:37:13,160
Speaker 1: a review on November thirty, and that meant with this

585
00:37:13,239 --> 00:37:16,600
Speaker 1: review that there would actually be a chance that new

586
00:37:16,719 --> 00:37:20,200
Speaker 1: pricing rules could come into play and that VeriSign would

587
00:37:20,200 --> 00:37:23,640
Speaker 1: be forced to lower prices, and that these rules would

588
00:37:23,640 --> 00:37:26,200
Speaker 1: actually be in effect for six years, which means they'd

589
00:37:26,239 --> 00:37:29,600
Speaker 1: actually remain in place for the entirety of the second

590
00:37:29,800 --> 00:37:34,960
Speaker 1: Trump administration, because that lasts four years. But nothing really

591
00:37:35,000 --> 00:37:38,359
Speaker 1: turned out that way, and why was that? Well, the

592
00:37:38,480 --> 00:37:43,160
Speaker 1: NTIA renewed the agreement with VeriSign and did nothing to

593
00:37:43,200 --> 00:37:46,920
Speaker 1: address the price issues, and in a release, the NTIA

594
00:37:47,000 --> 00:37:50,440
Speaker 1: said it really wished it could have done something. Cush gosh,

595
00:37:50,520 --> 00:37:53,120
Speaker 1: darn it, what a sticky wicket, which is not a

596
00:37:53,200 --> 00:37:57,279
Speaker 1: very satisfying conclusion to this story. As Andrew Allmann of

597
00:37:57,440 --> 00:38:03,320
Speaker 1: Domain name Wire put it, the nt IA essentially said, golly,

598
00:38:03,719 --> 00:38:06,279
Speaker 1: we really wish we could do something, but sadly, we

599
00:38:06,400 --> 00:38:09,920
Speaker 1: just don't have the authority to set dot com domain prices.

600
00:38:10,200 --> 00:38:14,440
Speaker 1: And here's the kicker, according to Aliman, quote, this statement

601
00:38:14,560 --> 00:38:18,920
Speaker 1: is strange because it is the NTIA that literally sets

602
00:38:18,920 --> 00:38:22,440
Speaker 1: a cap on dot com prices end quote. So yeah,

603
00:38:22,520 --> 00:38:25,480
Speaker 1: the government organization is saying we don't have the authority

604
00:38:25,520 --> 00:38:28,480
Speaker 1: to do the thing we're authorized to do. Now, Aliman

605
00:38:28,719 --> 00:38:32,840
Speaker 1: actually extends some understanding toward the NTIA. It's just that

606
00:38:32,920 --> 00:38:35,880
Speaker 1: perhaps the issue is really that because of the twenty

607
00:38:36,000 --> 00:38:40,160
Speaker 1: twenty agreement between VeriSign and I can the NTIA is

608
00:38:40,400 --> 00:38:43,600
Speaker 1: not able to set a cap on prices without actual

609
00:38:43,640 --> 00:38:48,760
Speaker 1: cooperation from VeriSign itself, and obviously VeriSign has a vested

610
00:38:48,800 --> 00:38:52,200
Speaker 1: interest in not creating lower price caps for its services.

611
00:38:52,520 --> 00:38:56,080
Speaker 1: Like a business is not gonna sit there and say, oh, yeah, yeah,

612
00:38:56,120 --> 00:38:59,440
Speaker 1: you're right, I should charge less for this thing that

613
00:38:59,520 --> 00:39:02,719
Speaker 1: you can own only get from me, and I have

614
00:39:02,800 --> 00:39:06,120
Speaker 1: all the leverage here, so obviously I should lower my prices.

615
00:39:06,280 --> 00:39:08,080
Speaker 1: So vera Sign said, you know what, we're going to

616
00:39:08,200 --> 00:39:13,319
Speaker 1: decline that at least that's that's the assumption that that's

617
00:39:13,360 --> 00:39:18,120
Speaker 1: why the NTIA was unable to put in new price

618
00:39:18,280 --> 00:39:23,239
Speaker 1: caps on the TLD registration business or registry business. The

619
00:39:23,320 --> 00:39:26,560
Speaker 1: NTIA did lament that the whole pricing situation is pretty

620
00:39:26,640 --> 00:39:29,880
Speaker 1: darn messed up from the wholesale side of the registry

621
00:39:29,920 --> 00:39:32,960
Speaker 1: business all the way downstream to the customer, and that

622
00:39:33,320 --> 00:39:35,600
Speaker 1: ultimately customers are kind of at the mercy of the

623
00:39:35,640 --> 00:39:38,520
Speaker 1: various companies within the industry. You know, gosh darn it,

624
00:39:38,560 --> 00:39:40,960
Speaker 1: if only the government had the authority to actually address

625
00:39:40,960 --> 00:39:45,160
Speaker 1: potentially unfair business practices. Anyway, that's where we stand now

626
00:39:45,239 --> 00:39:48,920
Speaker 1: with one company ultimately sitting on a vault of dot

627
00:39:48,960 --> 00:39:52,680
Speaker 1: com TLDs and considering it was Trump's first administration that

628
00:39:52,760 --> 00:39:56,200
Speaker 1: gave VeriSign more freedom to increase prices in the first place,

629
00:39:56,360 --> 00:39:58,400
Speaker 1: I imagine we're not going to see any efforts to

630
00:39:58,480 --> 00:40:01,960
Speaker 1: curb costs in the near future. So this is kind

631
00:40:02,000 --> 00:40:04,800
Speaker 1: of where we're at. And I thought it was interesting

632
00:40:05,120 --> 00:40:08,239
Speaker 1: that there was this move against verisigns so late in

633
00:40:08,280 --> 00:40:12,480
Speaker 1: the game, especially since ultimately you can trace the whole

634
00:40:12,920 --> 00:40:16,360
Speaker 1: history of this back to how the government handled the

635
00:40:16,400 --> 00:40:19,960
Speaker 1: Internet in the early days, Like this wasn't a private

636
00:40:20,040 --> 00:40:24,440
Speaker 1: company or even a publicly traded company that created the situation.

637
00:40:24,600 --> 00:40:27,400
Speaker 1: This was a situation created by the US government that

638
00:40:27,480 --> 00:40:30,920
Speaker 1: now the US government is like, h this isn't ideal.

639
00:40:31,360 --> 00:40:35,000
Speaker 1: Some might have seen this as a way for Democrat

640
00:40:35,200 --> 00:40:38,680
Speaker 1: leaders to try and stick it to the Trump administration

641
00:40:39,000 --> 00:40:42,760
Speaker 1: by getting some policy changes in at the last minute,

642
00:40:42,960 --> 00:40:45,439
Speaker 1: changes that would last six years, so that it would

643
00:40:45,520 --> 00:40:47,680
Speaker 1: kind of be a thorn in the side, or at

644
00:40:47,719 --> 00:40:50,840
Speaker 1: least a little thumb of the nose at Republican leaders

645
00:40:50,880 --> 00:40:53,000
Speaker 1: because they're going to be in charge for the next

646
00:40:53,200 --> 00:40:56,040
Speaker 1: several years. But it didn't work. Like that didn't that's

647
00:40:56,040 --> 00:40:59,560
Speaker 1: not how it turned out. So if that was an attempt,

648
00:40:59,640 --> 00:41:02,520
Speaker 1: it failed, and it just means that I think it's

649
00:41:02,560 --> 00:41:05,759
Speaker 1: going to be business as usual for the near future. Heck,

650
00:41:05,800 --> 00:41:08,560
Speaker 1: it might end up meaning that ultimately we have to

651
00:41:08,560 --> 00:41:12,920
Speaker 1: pay even more for the whole registration process, because if

652
00:41:13,000 --> 00:41:16,680
Speaker 1: varsign can increase prices again I'm sure it will, that

653
00:41:16,760 --> 00:41:20,560
Speaker 1: will pass costs down to the registrars, who will then

654
00:41:20,680 --> 00:41:24,640
Speaker 1: pass those costs down to customers because everyone needs to

655
00:41:24,680 --> 00:41:28,759
Speaker 1: make some scratch off of those transactions. And ultimately it

656
00:41:28,840 --> 00:41:31,440
Speaker 1: means that the consumer at the end of the line

657
00:41:31,600 --> 00:41:36,480
Speaker 1: ends up bearing the expense. So fun times. But that's it.

658
00:41:36,880 --> 00:41:40,960
Speaker 1: That's a quick explanation and a very very high level

659
00:41:41,040 --> 00:41:44,640
Speaker 1: explanation of what's going on on the business side of

660
00:41:45,040 --> 00:41:48,759
Speaker 1: domain names. As I said, it is far more complicated

661
00:41:48,800 --> 00:41:51,200
Speaker 1: than what I've talked about here, both on a technical

662
00:41:51,280 --> 00:41:55,120
Speaker 1: level and from a corporate level or an administration level,

663
00:41:55,280 --> 00:41:59,200
Speaker 1: And if you are interested, there are numerous resources out

664
00:41:59,239 --> 00:42:02,680
Speaker 1: there that go into far more detail about how the

665
00:42:02,719 --> 00:42:08,120
Speaker 1: domain name system took shape over years of tweaking and experimentation,

666
00:42:08,600 --> 00:42:13,399
Speaker 1: how the administration of the dns changed over time, and

667
00:42:13,800 --> 00:42:18,480
Speaker 1: the competing ideas that ultimately didn't make it, whereas the

668
00:42:18,560 --> 00:42:22,320
Speaker 1: DNS did. All of that is documented in different places online.

669
00:42:22,360 --> 00:42:25,200
Speaker 1: It is fascinating, but it's a huge amount of information

670
00:42:25,280 --> 00:42:27,920
Speaker 1: and far too much for me to tackle on an

671
00:42:27,960 --> 00:42:30,400
Speaker 1: episode of tech Stuff. But I hope you found this interesting.

672
00:42:30,680 --> 00:42:33,440
Speaker 1: I hope you're all doing well, and I'll talk to

673
00:42:33,440 --> 00:42:43,120
Speaker 1: you again really soon. Tech Stuff is an iHeartRadio production.

674
00:42:43,440 --> 00:42:48,440
Speaker 1: For more podcasts from iHeartRadio, visit the iHeartRadio app, Apple Podcasts,

675
00:42:48,560 --> 00:42:53,959
Speaker 1: or wherever you listen to your favorite shows.