1
00:00:04,120 --> 00:00:07,160
Speaker 1: Get in touch with technology with tech Stuff from how

2
00:00:07,200 --> 00:00:13,680
Speaker 1: stuff Works dot com. Hey there, and welcome to tech Stuff.

3
00:00:13,680 --> 00:00:16,880
Speaker 1: I'm your host, Jonathan Strickland. I'm an executive producer at

4
00:00:16,920 --> 00:00:20,560
Speaker 1: iHeart Radio and how Stuff Works in I love all

5
00:00:20,800 --> 00:00:25,680
Speaker 1: things tech, and recently, as I was looking over tech news,

6
00:00:25,760 --> 00:00:30,520
Speaker 1: I saw that the Venerable Transmission Control Protocol a a

7
00:00:30,680 --> 00:00:33,680
Speaker 1: t c P is getting ready to take its bow

8
00:00:33,920 --> 00:00:37,560
Speaker 1: upon the release of the next version of Hypertext Transfer

9
00:00:37,600 --> 00:00:40,920
Speaker 1: Protocol or h t t P. In other words, it

10
00:00:40,960 --> 00:00:44,960
Speaker 1: will no longer be part of how ht t P works.

11
00:00:44,960 --> 00:00:47,000
Speaker 1: So wait, what does all that mean? That's a whole

12
00:00:47,040 --> 00:00:50,680
Speaker 1: lot of initialisms, and why does it matter. Where did

13
00:00:50,720 --> 00:00:54,520
Speaker 1: TCP come from? Anyway? Well, most of the time we

14
00:00:54,680 --> 00:00:59,120
Speaker 1: group TCP together with Internet Protocol or i P, so

15
00:00:59,480 --> 00:01:03,000
Speaker 1: it's pretty comedy here. People talk about the TCP slash

16
00:01:03,120 --> 00:01:07,080
Speaker 1: i P protocol, but that name is misleading as generally

17
00:01:07,160 --> 00:01:10,000
Speaker 1: what is meant by that is a suite of protocols,

18
00:01:10,040 --> 00:01:13,320
Speaker 1: not just those two. Though. To be fair, when Robert

19
00:01:13,360 --> 00:01:16,600
Speaker 1: Khan invinced SURF we're first working on the transport rules

20
00:01:16,680 --> 00:01:19,520
Speaker 1: of the Internet, they lumped it all together in one

21
00:01:19,600 --> 00:01:24,160
Speaker 1: protocol called t c P, So just a reminder. Let's

22
00:01:24,160 --> 00:01:28,280
Speaker 1: start on the very basic definitions here. A protocol is

23
00:01:28,360 --> 00:01:32,200
Speaker 1: essentially a set of rules or directions. So it's the

24
00:01:32,200 --> 00:01:35,360
Speaker 1: parameters that we create so that computers know what to

25
00:01:35,440 --> 00:01:38,120
Speaker 1: do when we tell them to do stuff. And a

26
00:01:38,160 --> 00:01:41,520
Speaker 1: good protocol should be functional and consistent. You should be

27
00:01:41,520 --> 00:01:44,639
Speaker 1: able to get the same result every time you follow

28
00:01:44,640 --> 00:01:47,840
Speaker 1: those rules if you give the same inputs. Now, while

29
00:01:47,880 --> 00:01:51,640
Speaker 1: there are several protocols in the TCP I P suite,

30
00:01:51,880 --> 00:01:55,480
Speaker 1: the t c P and i P ones are particularly important.

31
00:01:55,600 --> 00:01:59,360
Speaker 1: No big surprise, since that's the ones we use whenever

32
00:01:59,400 --> 00:02:03,200
Speaker 1: we refer to these protocols. So a quick reminder about

33
00:02:03,320 --> 00:02:08,000
Speaker 1: how computers send data over the Internet. Computers do not

34
00:02:08,320 --> 00:02:11,640
Speaker 1: send enormous files all in one go, because that would

35
00:02:11,639 --> 00:02:14,960
Speaker 1: be difficult to scale as the network of computers got

36
00:02:15,040 --> 00:02:18,760
Speaker 1: larger and the file sizes got bigger as well, and

37
00:02:18,760 --> 00:02:20,640
Speaker 1: it would mean that if something were to go wrong

38
00:02:20,919 --> 00:02:23,799
Speaker 1: during the transmission of a file, you would at best

39
00:02:24,080 --> 00:02:26,680
Speaker 1: end up with a corrupt file and you'd have to

40
00:02:26,720 --> 00:02:29,040
Speaker 1: start all over again. At worst, you wouldn't end up

41
00:02:29,080 --> 00:02:31,840
Speaker 1: with anything at all. So either way, you would have

42
00:02:31,880 --> 00:02:34,360
Speaker 1: to figure out how to start up the process so

43
00:02:34,440 --> 00:02:38,000
Speaker 1: to facilitate sending this information across the network so that

44
00:02:38,080 --> 00:02:42,560
Speaker 1: it's not unmanageable. This protocol suite divvies up the file

45
00:02:42,680 --> 00:02:48,320
Speaker 1: into smaller packets of data. Each packet has information associated

46
00:02:48,360 --> 00:02:51,640
Speaker 1: with it that identifies where it is coming from, where

47
00:02:51,639 --> 00:02:55,000
Speaker 1: it is headed on the Internet, and how the information

48
00:02:55,040 --> 00:02:58,560
Speaker 1: contained within the packet fits in with all the other

49
00:02:58,639 --> 00:03:02,000
Speaker 1: packets of information for that same file, so that the

50
00:03:02,000 --> 00:03:05,239
Speaker 1: computer on the other end of the communication channel can

51
00:03:05,280 --> 00:03:07,200
Speaker 1: get all those packets and then put it all back

52
00:03:07,240 --> 00:03:09,560
Speaker 1: together so that you get the file that was sent

53
00:03:09,800 --> 00:03:15,960
Speaker 1: by the first computer. TCP defines how applications can create

54
00:03:16,080 --> 00:03:21,000
Speaker 1: channels of communication across a network. It also manages how

55
00:03:21,040 --> 00:03:25,120
Speaker 1: a message is assembled into those smaller packets before they

56
00:03:25,160 --> 00:03:28,960
Speaker 1: are then transmitted over the Internet and then reassembled at

57
00:03:28,960 --> 00:03:32,600
Speaker 1: the destination address, and it makes sure that the recipient

58
00:03:32,639 --> 00:03:37,440
Speaker 1: computer has actually received each packet in sequence to verify

59
00:03:37,440 --> 00:03:40,200
Speaker 1: that the entire file has made it across. So it's

60
00:03:40,280 --> 00:03:44,080
Speaker 1: kind of an error checking mechanism, or a way of

61
00:03:44,240 --> 00:03:48,000
Speaker 1: ensuring that the information computer A is sending to computer

62
00:03:48,080 --> 00:03:52,240
Speaker 1: B gets to where it's going. Without these rules, you

63
00:03:52,240 --> 00:03:55,480
Speaker 1: would never really be sure if you send something from

64
00:03:55,480 --> 00:03:58,600
Speaker 1: computer A. If computer B got it. This is a

65
00:03:58,640 --> 00:04:01,120
Speaker 1: set of rules that tells computer or be to say, hey,

66
00:04:01,160 --> 00:04:03,600
Speaker 1: by the way, once you get all these, let computer

67
00:04:03,680 --> 00:04:08,480
Speaker 1: A know so that everyone knows that the transmission is complete.

68
00:04:09,160 --> 00:04:12,080
Speaker 1: I P, by the way, defines how to address and

69
00:04:12,200 --> 00:04:16,240
Speaker 1: route each packet to make sure it reaches the right destination.

70
00:04:16,520 --> 00:04:22,560
Speaker 1: It's technically on a layer lower than the TCP protocol. Now,

71
00:04:22,600 --> 00:04:26,560
Speaker 1: way back in the early nineteen seventies, you had a

72
00:04:26,600 --> 00:04:30,839
Speaker 1: team working on a project called ARPA net. This is

73
00:04:30,839 --> 00:04:33,600
Speaker 1: going to go back to DARPA, which I covered in

74
00:04:33,640 --> 00:04:36,839
Speaker 1: a series of episodes recently, so this kind of ties

75
00:04:36,880 --> 00:04:40,320
Speaker 1: in with that more than a little bit. Ar Ponett

76
00:04:40,480 --> 00:04:43,520
Speaker 1: was an early computer network, and in a way it

77
00:04:43,560 --> 00:04:46,599
Speaker 1: was a precursor to the Internet. Remember the Internet is

78
00:04:46,640 --> 00:04:51,480
Speaker 1: a network of networks. Ar Ponnett was a network, period

79
00:04:52,480 --> 00:04:55,320
Speaker 1: and while the team was working on this, they realized

80
00:04:55,360 --> 00:04:58,320
Speaker 1: that the protocols they had been using for our bonnet

81
00:04:58,560 --> 00:05:02,000
Speaker 1: were functional but not scalable. If you were to go

82
00:05:02,080 --> 00:05:05,960
Speaker 1: beyond just one network, if you wanted to connect two

83
00:05:06,040 --> 00:05:09,560
Speaker 1: networks together, you really needed a different solution. And as

84
00:05:09,600 --> 00:05:13,200
Speaker 1: this network would get bigger, the situation would become untenable

85
00:05:13,640 --> 00:05:15,800
Speaker 1: and so some of the team got to work designing

86
00:05:15,839 --> 00:05:19,839
Speaker 1: new sets of rules for networked communication that could keep

87
00:05:19,880 --> 00:05:23,119
Speaker 1: things running smoothly even as the network would get bigger

88
00:05:23,120 --> 00:05:26,520
Speaker 1: and bigger, something that was truly scalable. One of the

89
00:05:26,560 --> 00:05:29,719
Speaker 1: people working on this was a guy named Robert Kahn,

90
00:05:29,880 --> 00:05:32,520
Speaker 1: one of the fathers of the Internet. You often hear

91
00:05:32,560 --> 00:05:36,360
Speaker 1: about him and his buddy Vents Surf, who together would

92
00:05:36,600 --> 00:05:40,680
Speaker 1: create TCP. So Robert Kahn comes on over to DARPA

93
00:05:40,720 --> 00:05:43,680
Speaker 1: and he's part of the I P. T O Department.

94
00:05:43,880 --> 00:05:48,160
Speaker 1: That's the department that's in charge of creating networks and

95
00:05:48,200 --> 00:05:51,240
Speaker 1: that sort of thing. He specifically wanted to replace an

96
00:05:51,279 --> 00:05:55,120
Speaker 1: earlier set of rules, an earlier protocol called the Network

97
00:05:55,240 --> 00:05:58,719
Speaker 1: Control Program or in c P. And the reason for

98
00:05:58,800 --> 00:06:01,400
Speaker 1: that gets a little technical, but I figure we can

99
00:06:01,440 --> 00:06:04,719
Speaker 1: go a bit further than just it doesn't scale well,

100
00:06:04,800 --> 00:06:07,120
Speaker 1: because that doesn't really tell you much. So for just

101
00:06:07,200 --> 00:06:10,200
Speaker 1: a second, let's talk about what con was envisioning back

102
00:06:10,240 --> 00:06:13,719
Speaker 1: in the early nineteen seventies. He wanted a protocol that

103
00:06:13,839 --> 00:06:16,200
Speaker 1: was going to do certain things. He felt that a

104
00:06:16,200 --> 00:06:19,880
Speaker 1: computer scientists had connected these distant computers together using the

105
00:06:19,920 --> 00:06:22,760
Speaker 1: telephone system that created the first wide area network, but

106
00:06:22,880 --> 00:06:26,799
Speaker 1: that was not going to be sustainable on a broader scale.

107
00:06:27,400 --> 00:06:30,120
Speaker 1: He knew that the key component of the network technology

108
00:06:30,120 --> 00:06:34,080
Speaker 1: at our ponet was the Interface Message Processor or i

109
00:06:34,320 --> 00:06:38,200
Speaker 1: MP and MP and an MP is kind of like

110
00:06:38,360 --> 00:06:41,920
Speaker 1: a router. It was a packet switching node that would

111
00:06:41,920 --> 00:06:45,799
Speaker 1: serve as a connection between different computers on our bonnet.

112
00:06:46,520 --> 00:06:49,880
Speaker 1: In addition to imps, the team on our Bonnet was

113
00:06:50,240 --> 00:06:52,920
Speaker 1: working on a host to host protocol which would become

114
00:06:52,960 --> 00:06:57,159
Speaker 1: the network control protocol, and developers began to create applications

115
00:06:57,440 --> 00:07:00,400
Speaker 1: to run on those networks like email and con would

116
00:07:00,440 --> 00:07:05,120
Speaker 1: demonstrate even a twenty node large network in nineteen seventy two,

117
00:07:05,160 --> 00:07:08,760
Speaker 1: so a network consisting of twenty computers. Khan was also

118
00:07:08,839 --> 00:07:14,000
Speaker 1: working on technology for a packet radio network that would

119
00:07:14,040 --> 00:07:17,440
Speaker 1: actually use radio waves to send data back and forth

120
00:07:17,440 --> 00:07:20,720
Speaker 1: across different computers, and that was going to use packet

121
00:07:20,760 --> 00:07:26,080
Speaker 1: switching specifically because radio is tricky stuff. If a signal

122
00:07:26,320 --> 00:07:30,360
Speaker 1: were lost or jammed, then the information that was being

123
00:07:30,400 --> 00:07:32,800
Speaker 1: sent across the network would be lost and you'd end

124
00:07:32,840 --> 00:07:35,600
Speaker 1: up with miscommunications and failures, so you had to have

125
00:07:35,640 --> 00:07:39,320
Speaker 1: a way to deal with this. Originally, Khan had intended

126
00:07:39,360 --> 00:07:43,440
Speaker 1: to develop a protocol specifically for radio packet networks to

127
00:07:44,040 --> 00:07:47,520
Speaker 1: have the sort of error correction mechanism in there, a

128
00:07:47,560 --> 00:07:51,600
Speaker 1: way of guaranteeing that the information from one system would

129
00:07:51,640 --> 00:07:55,720
Speaker 1: get to another, and then this network would be able

130
00:07:55,760 --> 00:08:00,400
Speaker 1: to interface with other networks like arpanet, using the already

131
00:08:00,520 --> 00:08:04,720
Speaker 1: established in CP as a transport layer. But there was

132
00:08:04,760 --> 00:08:08,120
Speaker 1: a big problem. N c P could only address networks

133
00:08:08,120 --> 00:08:12,000
Speaker 1: and machines down to the imp level. N CP would

134
00:08:12,000 --> 00:08:16,040
Speaker 1: rely upon our bonnet itself for end to end reliability,

135
00:08:16,120 --> 00:08:18,760
Speaker 1: so it worked just fine if you were in our

136
00:08:18,840 --> 00:08:22,680
Speaker 1: pannet if your machine was directly connected into that network,

137
00:08:23,040 --> 00:08:27,600
Speaker 1: But if you wanted to interconnect the arpanet network with

138
00:08:27,720 --> 00:08:31,760
Speaker 1: another network, something had to change because n c P

139
00:08:32,000 --> 00:08:36,280
Speaker 1: could not handle identifying and responding to errors and delivering

140
00:08:36,800 --> 00:08:40,120
Speaker 1: information to the computers that were outside of our bannet.

141
00:08:40,480 --> 00:08:43,800
Speaker 1: N CP just didn't have that capability. Arpanet handled everything

142
00:08:43,800 --> 00:08:46,600
Speaker 1: within the network, but it didn't have anything designed to

143
00:08:46,960 --> 00:08:51,160
Speaker 1: handle stuff from outside that network. So at first Kahn

144
00:08:51,320 --> 00:08:54,800
Speaker 1: had planned to only work on the packet radio networks

145
00:08:54,800 --> 00:08:57,760
Speaker 1: and just concentrate on that, but ultimately his quest to

146
00:08:57,800 --> 00:09:01,439
Speaker 1: create a protocol that could ensure message is were arriving

147
00:09:01,520 --> 00:09:07,200
Speaker 1: at their destinations across different networks, expanded beyond just the

148
00:09:07,200 --> 00:09:12,800
Speaker 1: packet radio application. So Cohn wanted an open network architecture,

149
00:09:13,160 --> 00:09:16,920
Speaker 1: something that would allow any sort of networked system to

150
00:09:17,120 --> 00:09:20,560
Speaker 1: interconnect with another and still have rules in place to

151
00:09:20,800 --> 00:09:24,040
Speaker 1: ensure that the data was getting to where it needed

152
00:09:24,080 --> 00:09:27,760
Speaker 1: to go. So Robert Kahn and vent Surf were two

153
00:09:27,800 --> 00:09:30,720
Speaker 1: computer scientists who were working on this. They were the

154
00:09:30,800 --> 00:09:34,720
Speaker 1: authors of these protocols. Vent Surf had been one of

155
00:09:34,720 --> 00:09:37,880
Speaker 1: the people to create in CP well fun fact, by

156
00:09:37,920 --> 00:09:41,880
Speaker 1: the way, TCP did not originally stand for Transmission control

157
00:09:41,960 --> 00:09:46,040
Speaker 1: Protocol back when con and Surf first proposed it. Instead,

158
00:09:46,559 --> 00:09:50,800
Speaker 1: it stood for Transmission Control Program, and that's a subtle difference,

159
00:09:50,840 --> 00:09:54,199
Speaker 1: to be sure. They wrote the first version of TCP

160
00:09:54,480 --> 00:09:58,280
Speaker 1: in ninety three, and they published a fully documented and

161
00:09:58,360 --> 00:10:04,760
Speaker 1: revised version in four under RFC six. It was specifically

162
00:10:04,760 --> 00:10:10,360
Speaker 1: titled Specification of Internet Transmission Control Program. Not long after

163
00:10:10,400 --> 00:10:13,280
Speaker 1: the initial creation, other folks began to realize that it

164
00:10:13,360 --> 00:10:16,280
Speaker 1: might be a better idea to break out the functions

165
00:10:16,320 --> 00:10:19,520
Speaker 1: of t c P into two sets of protocols, and

166
00:10:19,559 --> 00:10:22,760
Speaker 1: that's where we get t c P I P. Because, again,

167
00:10:22,800 --> 00:10:25,360
Speaker 1: before it was all lumped together, and then they figured

168
00:10:25,440 --> 00:10:28,800
Speaker 1: this would make more sense if we separated them out

169
00:10:28,880 --> 00:10:32,319
Speaker 1: into two sets of rules. The creation of t C

170
00:10:32,520 --> 00:10:37,040
Speaker 1: P I P predates the Open Systems Interconnection or O

171
00:10:37,280 --> 00:10:39,599
Speaker 1: S I layer model. And I've talked about the O

172
00:10:39,760 --> 00:10:42,600
Speaker 1: SI model in a past episode of tech Stuff. But

173
00:10:42,720 --> 00:10:45,800
Speaker 1: the O SI model describes how different parts of a

174
00:10:45,800 --> 00:10:50,600
Speaker 1: telecommunications or computer system communicate with one another. They have

175
00:10:50,880 --> 00:10:54,760
Speaker 1: layers to describe the different functions. But T C P

176
00:10:54,960 --> 00:10:57,959
Speaker 1: I P layers are are pretty similar to O SI layers,

177
00:10:58,160 --> 00:11:00,160
Speaker 1: so we can we can talk about the two as

178
00:11:00,200 --> 00:11:04,960
Speaker 1: being at least somewhat analogous. It's an abstract idea that's

179
00:11:05,000 --> 00:11:09,160
Speaker 1: meant to describe how each layer fits within a grand scheme.

180
00:11:09,400 --> 00:11:12,240
Speaker 1: So layers that are near the bottom of the stack

181
00:11:12,760 --> 00:11:15,319
Speaker 1: support all the layers that are on top of it.

182
00:11:15,720 --> 00:11:19,720
Speaker 1: Layers at the top do not necessarily support any other layers.

183
00:11:19,760 --> 00:11:22,600
Speaker 1: They rely on the ones below them, but they don't

184
00:11:22,640 --> 00:11:26,120
Speaker 1: support anything any layers above them. And again this is

185
00:11:26,160 --> 00:11:31,160
Speaker 1: an abstraction. There are not actual literal layers in these systems,

186
00:11:31,200 --> 00:11:34,840
Speaker 1: but within this framework, you could say TCP would be

187
00:11:34,920 --> 00:11:38,280
Speaker 1: on layer four. That would be the transport layer. The

188
00:11:38,320 --> 00:11:42,360
Speaker 1: Internet protocol is one layer further down. It's on layer three,

189
00:11:42,840 --> 00:11:46,640
Speaker 1: meaning it is a little closer to the basic hardware

190
00:11:46,760 --> 00:11:50,480
Speaker 1: layer of the system. That's the lowest layer is the hardware,

191
00:11:51,080 --> 00:11:55,080
Speaker 1: and that uh means that the i P protocol supports

192
00:11:55,120 --> 00:11:59,880
Speaker 1: the TCP protocols above it and above TCP are the

193
00:12:00,080 --> 00:12:03,880
Speaker 1: application layers where you have stuff like file Transfer Protocol,

194
00:12:04,360 --> 00:12:07,520
Speaker 1: email and h T t P. Those are all on

195
00:12:07,600 --> 00:12:10,400
Speaker 1: top of it. I've got more to say about what

196
00:12:10,520 --> 00:12:13,240
Speaker 1: TCP is and what it does in just a moment,

197
00:12:13,240 --> 00:12:16,440
Speaker 1: but first let's take a quick break to thank our sponsor.

198
00:12:23,960 --> 00:12:27,720
Speaker 1: So when laying out the rules for TCP, bob con

199
00:12:27,760 --> 00:12:31,160
Speaker 1: had a few requirements and this is from the Internet

200
00:12:31,160 --> 00:12:34,800
Speaker 1: Society's page on the History of the Internet, and they

201
00:12:34,800 --> 00:12:38,080
Speaker 1: were each distinct network would have to stand on its

202
00:12:38,080 --> 00:12:42,240
Speaker 1: own and no internal changes should be required to any

203
00:12:42,280 --> 00:12:47,320
Speaker 1: such network to connect it to the Internet. Next, communications

204
00:12:47,480 --> 00:12:50,600
Speaker 1: would be on a best effort basis, so if a

205
00:12:50,640 --> 00:12:53,920
Speaker 1: packet did not make it to the final destination, it

206
00:12:53,960 --> 00:12:57,920
Speaker 1: would shortly be retransmitted from the source. So this is

207
00:12:58,000 --> 00:13:02,640
Speaker 1: the error correction part. A packet on its way to

208
00:13:03,360 --> 00:13:07,240
Speaker 1: computer B never makes it, then computer A will retransmit

209
00:13:07,320 --> 00:13:10,720
Speaker 1: that same packet black boxes would be used to connect

210
00:13:10,760 --> 00:13:14,240
Speaker 1: these networks. These would later be called gateways and routers,

211
00:13:14,720 --> 00:13:18,160
Speaker 1: and there would be no information retained by the gateways

212
00:13:18,240 --> 00:13:22,120
Speaker 1: about the individual flows of packets passing through them, thereby

213
00:13:22,240 --> 00:13:25,640
Speaker 1: just keeping them very simple and avoiding complicated adaptation and

214
00:13:25,679 --> 00:13:28,880
Speaker 1: recovery from various failure modes. So they were really just

215
00:13:29,679 --> 00:13:35,480
Speaker 1: a means of controlling traffic flow, but not monitoring traffic flow,

216
00:13:35,920 --> 00:13:39,240
Speaker 1: and there would be no global control at the operations level.

217
00:13:39,400 --> 00:13:42,680
Speaker 1: Those were his requirements. Those would develop into more granular

218
00:13:42,760 --> 00:13:46,920
Speaker 1: requirements as the work would continue on the protocols. And

219
00:13:47,040 --> 00:13:51,240
Speaker 1: Vince Surf did a really really good explanation about how

220
00:13:51,320 --> 00:13:54,679
Speaker 1: TCP works in a short video, and he used a

221
00:13:54,720 --> 00:13:58,360
Speaker 1: postcard analogy, and I highly recommend checking it out because

222
00:13:59,040 --> 00:14:01,680
Speaker 1: he just puts it very simply. I'm gonna kind of

223
00:14:01,720 --> 00:14:06,000
Speaker 1: paraphrase what he said here. He compared TCP to sending

224
00:14:06,240 --> 00:14:09,080
Speaker 1: a book to a friend, and you're using the postal service,

225
00:14:10,080 --> 00:14:13,200
Speaker 1: except your postal service is very peculiar. They will not

226
00:14:13,400 --> 00:14:17,240
Speaker 1: carry anything other than postcards. So you cannot actually send

227
00:14:17,240 --> 00:14:20,720
Speaker 1: the physical book as is to your friend because the

228
00:14:20,800 --> 00:14:23,320
Speaker 1: post office is not gonna carry that. So what you

229
00:14:23,400 --> 00:14:27,040
Speaker 1: have to do is cut your book up so that

230
00:14:27,080 --> 00:14:31,920
Speaker 1: you can fit maybe about half a page on a postcard,

231
00:14:32,240 --> 00:14:34,280
Speaker 1: and then you can send that postcard through the mail,

232
00:14:34,680 --> 00:14:37,240
Speaker 1: and then you have to send all of the book

233
00:14:37,560 --> 00:14:39,520
Speaker 1: in a series of postcards to your friend. But then

234
00:14:39,600 --> 00:14:42,040
Speaker 1: you realize, hey, wait, because of the way I have

235
00:14:42,120 --> 00:14:46,000
Speaker 1: to cut up this book, sometimes there's no indication there

236
00:14:46,040 --> 00:14:48,760
Speaker 1: about a page number, so there's no way of knowing

237
00:14:48,920 --> 00:14:52,440
Speaker 1: just on the page where this page fits in relation

238
00:14:52,480 --> 00:14:55,080
Speaker 1: to the rest of the book. So then you number

239
00:14:55,480 --> 00:14:58,840
Speaker 1: every single postcard, and that way your friend knows what

240
00:14:59,120 --> 00:15:01,960
Speaker 1: order they go in, they know the sequence, so there's

241
00:15:02,320 --> 00:15:05,760
Speaker 1: no guarantee that any one postcard will actually make it

242
00:15:05,760 --> 00:15:08,240
Speaker 1: all the way through. There's also no guarantee your friend

243
00:15:08,280 --> 00:15:10,880
Speaker 1: will receive the postcards in the same order that you

244
00:15:11,000 --> 00:15:14,360
Speaker 1: sent them. But by numbering, your friend will know which

245
00:15:14,400 --> 00:15:17,800
Speaker 1: postcards they have received. So if they get postcard number

246
00:15:17,840 --> 00:15:21,080
Speaker 1: eighty three but they didn't get postcard number A D two,

247
00:15:21,360 --> 00:15:23,960
Speaker 1: they can send you a message alerting you that they

248
00:15:24,000 --> 00:15:27,200
Speaker 1: are missing one, and you can read, transmit or re send,

249
00:15:27,640 --> 00:15:29,840
Speaker 1: so your friend can send a postcard back to you.

250
00:15:30,040 --> 00:15:32,680
Speaker 1: Essentially says, hey, I got all the postcards up to

251
00:15:32,760 --> 00:15:35,560
Speaker 1: number eighty two or whatever. But that's it, and this

252
00:15:35,560 --> 00:15:38,160
Speaker 1: would let you know that you need to resend those postcards,

253
00:15:38,240 --> 00:15:40,280
Speaker 1: which means you have to keep a copy of the

254
00:15:40,320 --> 00:15:43,560
Speaker 1: postcards you've submitted. You can't just send your only copy

255
00:15:43,720 --> 00:15:48,200
Speaker 1: because you'd be up the creek if your buddy says, hey,

256
00:15:48,240 --> 00:15:51,160
Speaker 1: I didn't get that, and if nothing comes back to you,

257
00:15:51,200 --> 00:15:55,120
Speaker 1: if your friend never says, oh, I received everything, then

258
00:15:55,160 --> 00:15:58,200
Speaker 1: you would have to start re sending postcards until you

259
00:15:58,320 --> 00:16:00,800
Speaker 1: finally got a message that says, hey, a toad, scut

260
00:16:00,800 --> 00:16:02,480
Speaker 1: all the postcards, thank you, I'm going to read the

261
00:16:02,520 --> 00:16:04,720
Speaker 1: book now, or whatever it might be. But that's how

262
00:16:04,760 --> 00:16:08,280
Speaker 1: TCP works. But instead of it being you know, physical postcards,

263
00:16:08,320 --> 00:16:12,320
Speaker 1: we're talking digital information. There's never a guarantee that the

264
00:16:12,360 --> 00:16:14,880
Speaker 1: information you send is actually going to get to your

265
00:16:14,920 --> 00:16:19,160
Speaker 1: destination or that will all arrive sequentially. But these safeguards

266
00:16:19,200 --> 00:16:21,920
Speaker 1: mean that your computer will know when to send stuff

267
00:16:21,960 --> 00:16:26,280
Speaker 1: again to guarantee transmission. The United States Department of Defense

268
00:16:26,360 --> 00:16:31,080
Speaker 1: adopted TCP i P as a standard in nineteen eighty.

269
00:16:31,280 --> 00:16:35,200
Speaker 1: DARPA was able to change over in advance of everyone else,

270
00:16:35,480 --> 00:16:39,240
Speaker 1: which allowed for partitioning of the military networks from non

271
00:16:39,320 --> 00:16:42,120
Speaker 1: military networks, and that would carry forward, so you have

272
00:16:42,240 --> 00:16:44,920
Speaker 1: mill net that's its own separate network that's based on

273
00:16:45,440 --> 00:16:49,120
Speaker 1: essentially the same architecture as the general Internet. T c

274
00:16:49,320 --> 00:16:52,880
Speaker 1: P i P would become the official transport layer for

275
00:16:53,080 --> 00:16:57,680
Speaker 1: ar PONNETT on January one, nine three. This was called

276
00:16:57,760 --> 00:17:00,720
Speaker 1: a flag day. Now, that is an event that involves

277
00:17:00,920 --> 00:17:06,040
Speaker 1: incorporating a critical change in a very large system UH

278
00:17:06,040 --> 00:17:08,800
Speaker 1: in a simultaneous way, like it has to change throughout

279
00:17:08,840 --> 00:17:12,160
Speaker 1: the system the same time, UH, and that is really

280
00:17:12,200 --> 00:17:14,480
Speaker 1: tricky to do. The bigger the system, obviously, the harder

281
00:17:14,520 --> 00:17:17,400
Speaker 1: it is for you to make a global change all

282
00:17:17,440 --> 00:17:20,400
Speaker 1: at the same time. The transition had been planned out

283
00:17:20,400 --> 00:17:24,400
Speaker 1: for years in advance because this would require network administrators

284
00:17:24,400 --> 00:17:26,400
Speaker 1: to change over to the t c P i P

285
00:17:26,400 --> 00:17:29,920
Speaker 1: protocol all at the same time, and surprisingly it went

286
00:17:29,960 --> 00:17:33,359
Speaker 1: off without any really major problems, So that's pretty cool.

287
00:17:34,000 --> 00:17:38,359
Speaker 1: By the mid nineteen eighties, the Internet was an established thing,

288
00:17:38,680 --> 00:17:41,480
Speaker 1: though really only a relatively small number of people were

289
00:17:41,520 --> 00:17:44,280
Speaker 1: aware of it. If you worked at DARPA, or if

290
00:17:44,320 --> 00:17:46,880
Speaker 1: you were at a university with a really good computer

291
00:17:46,960 --> 00:17:50,280
Speaker 1: science curriculum, or maybe you worked in a research facility,

292
00:17:51,200 --> 00:17:54,400
Speaker 1: or maybe you were in the military, then you might

293
00:17:54,720 --> 00:17:57,640
Speaker 1: know about it. A few other government offices also were

294
00:17:57,720 --> 00:18:02,560
Speaker 1: on the early Internet, but apart from that and a

295
00:18:02,600 --> 00:18:06,080
Speaker 1: few major businesses, it was largely a thing of mystery.

296
00:18:06,440 --> 00:18:09,480
Speaker 1: The general public was pretty much ignorant of the Internet

297
00:18:09,560 --> 00:18:12,520
Speaker 1: for almost a decade. It wouldn't be until the emergence

298
00:18:12,520 --> 00:18:14,960
Speaker 1: of the World Wide Web that more people would become

299
00:18:15,000 --> 00:18:18,000
Speaker 1: aware of the Internet, and in fact, at that point,

300
00:18:18,080 --> 00:18:21,320
Speaker 1: the Worldwide Web and the Internet would often be confused

301
00:18:21,320 --> 00:18:24,160
Speaker 1: as meaning the same thing for a lot of people.

302
00:18:24,200 --> 00:18:26,880
Speaker 1: A lot of people would refer to the Worldwide Web

303
00:18:26,920 --> 00:18:30,240
Speaker 1: as the Internet, not realizing that really the world Wide

304
00:18:30,240 --> 00:18:34,560
Speaker 1: Web is one application built on top of the Internet,

305
00:18:35,040 --> 00:18:38,800
Speaker 1: it is not itself the Internet. In the early nineties, uh,

306
00:18:38,840 --> 00:18:42,120
Speaker 1: speaking of the Web, a guy named Tim berners Lee,

307
00:18:42,400 --> 00:18:46,000
Speaker 1: he was working for a little scientific research organization called CERN,

308
00:18:46,400 --> 00:18:48,600
Speaker 1: had a bright idea. And his idea was for an

309
00:18:48,640 --> 00:18:52,800
Speaker 1: application protocol on top of the Internet that would facilitate

310
00:18:52,840 --> 00:18:58,520
Speaker 1: communications between client computers and server computers, including file transfers

311
00:18:58,640 --> 00:19:00,879
Speaker 1: and the ability for a sir her to refer a

312
00:19:00,960 --> 00:19:03,879
Speaker 1: client to a different server. And that would be the

313
00:19:03,920 --> 00:19:07,119
Speaker 1: foundation for the Worldwide Web. And just in case you

314
00:19:07,119 --> 00:19:10,080
Speaker 1: didn't pick up on my stupid joke. CERN is not

315
00:19:10,320 --> 00:19:14,720
Speaker 1: a little scientific research organization. It's the European Organization for

316
00:19:14,840 --> 00:19:19,479
Speaker 1: Nuclear Research and it is a huge, huge deal. Among

317
00:19:19,800 --> 00:19:24,120
Speaker 1: the many things it does is oversee the large Hadron collider,

318
00:19:24,520 --> 00:19:29,920
Speaker 1: so big, big organization. Ultimately, the purpose of h t

319
00:19:30,119 --> 00:19:33,639
Speaker 1: t P, which was created by Tim berners Lee, was

320
00:19:33,800 --> 00:19:37,760
Speaker 1: to create a means of linking different documents together through

321
00:19:37,880 --> 00:19:40,640
Speaker 1: what is called hypertext. And you've seen these. These are

322
00:19:40,640 --> 00:19:43,480
Speaker 1: those highlighted words and web pages, and when you click

323
00:19:43,520 --> 00:19:45,959
Speaker 1: on it, you go to a different web page. And

324
00:19:46,000 --> 00:19:48,679
Speaker 1: that's the whole point is clicking on hypertext sends a

325
00:19:48,680 --> 00:19:52,119
Speaker 1: command to navigate to a new page. And because the

326
00:19:52,240 --> 00:19:55,639
Speaker 1: rules for h T t P allow for one server

327
00:19:56,080 --> 00:19:59,240
Speaker 1: to refer a client to another server, those two web

328
00:19:59,240 --> 00:20:02,320
Speaker 1: pages don't have a quote unquote live on the same

329
00:20:02,359 --> 00:20:06,520
Speaker 1: server together. So we're talking about the very basic foundation

330
00:20:06,560 --> 00:20:10,919
Speaker 1: of how the Worldwide Web works with the interlinking documents

331
00:20:10,960 --> 00:20:13,720
Speaker 1: that allow you to hop from one page or one

332
00:20:13,800 --> 00:20:19,680
Speaker 1: site to another. The features of HTTP version zero point nine,

333
00:20:19,920 --> 00:20:23,000
Speaker 1: which was the first one released to the public, included

334
00:20:23,119 --> 00:20:29,200
Speaker 1: the following clients Server Request Response Protocol as key protocol

335
00:20:29,320 --> 00:20:32,600
Speaker 1: running over a t C p I P link. It

336
00:20:32,720 --> 00:20:36,000
Speaker 1: was designed to transfer hypertext documents or h t m

337
00:20:36,160 --> 00:20:39,600
Speaker 1: L and the connection between server and client is closed

338
00:20:39,680 --> 00:20:43,439
Speaker 1: after every request. And that's it. It was bare bones stuff,

339
00:20:43,720 --> 00:20:47,520
Speaker 1: but this was the beginning of something truly transformational. In fact,

340
00:20:48,280 --> 00:20:50,919
Speaker 1: I could honestly say I would not have the career

341
00:20:51,000 --> 00:20:58,480
Speaker 1: I have without this invention. So from the h t

342
00:20:58,480 --> 00:21:02,520
Speaker 1: t P standard of pretty quickly, Tim burns Lee had

343
00:21:02,520 --> 00:21:05,040
Speaker 1: set the stage, and then a team at the National

344
00:21:05,119 --> 00:21:09,359
Speaker 1: Center of Supercomputing Applications or in c s A made

345
00:21:09,400 --> 00:21:13,359
Speaker 1: the first popular web browser called Mosaic. One of the

346
00:21:13,400 --> 00:21:16,880
Speaker 1: programmers on that team was a guy named Mark Andreason,

347
00:21:17,240 --> 00:21:20,359
Speaker 1: who went on to co found the Mosaic Corporation and

348
00:21:20,400 --> 00:21:25,119
Speaker 1: eventually publish a new browser called Netscape. Now, at that

349
00:21:25,240 --> 00:21:29,480
Speaker 1: same time, the Internet Engineering Task Force was organizing a

350
00:21:29,480 --> 00:21:33,720
Speaker 1: team called the ht t P Working Group dedicated to

351
00:21:33,840 --> 00:21:39,240
Speaker 1: improving this HTTP protocol, and it was quickly developing in

352
00:21:39,440 --> 00:21:42,360
Speaker 1: several different directions. And by that I mean a lot

353
00:21:42,359 --> 00:21:46,200
Speaker 1: of different people had started by taking the version zero

354
00:21:46,280 --> 00:21:49,800
Speaker 1: point nine h t t P and then tweaking it

355
00:21:50,200 --> 00:21:55,560
Speaker 1: independently of each other. So it's evolving in different directions simultaneously.

356
00:21:56,560 --> 00:22:00,359
Speaker 1: So while there's a shorthand that refers to h t

357
00:22:00,359 --> 00:22:04,000
Speaker 1: t P one point oh. There is not an actual

358
00:22:04,359 --> 00:22:09,040
Speaker 1: standard one point oh. There were many quote unquote flavors

359
00:22:09,040 --> 00:22:11,320
Speaker 1: of one point oh because there were so many different

360
00:22:11,880 --> 00:22:15,480
Speaker 1: variations on that, the I E. T F Working Group

361
00:22:15,760 --> 00:22:20,399
Speaker 1: would publish a standard for HTTP Protocol version one point

362
00:22:20,520 --> 00:22:25,800
Speaker 1: one under RFC two zero six eight if you want

363
00:22:25,800 --> 00:22:29,560
Speaker 1: to read it. It's a little technical, but this version

364
00:22:29,600 --> 00:22:32,720
Speaker 1: would be tweaked and updated before it was officially released.

365
00:22:32,760 --> 00:22:37,960
Speaker 1: In Version two point oh of h T t P

366
00:22:38,480 --> 00:22:42,959
Speaker 1: wouldn't come out until two thousand fifteen. That is a

367
00:22:43,040 --> 00:22:46,080
Speaker 1: long time between versions one point one came out in

368
00:22:47,080 --> 00:22:51,480
Speaker 1: two point oh and two thousand fifteen, and only about

369
00:22:51,480 --> 00:22:55,080
Speaker 1: a third of all websites in the world today support

370
00:22:55,680 --> 00:22:59,240
Speaker 1: version two point oh as the standard. Most websites are

371
00:22:59,240 --> 00:23:02,920
Speaker 1: still using one point oh or one point one, So

372
00:23:03,200 --> 00:23:06,440
Speaker 1: it may come as something of a surprise to hear

373
00:23:06,800 --> 00:23:09,600
Speaker 1: that h T t P three point oh is right

374
00:23:09,640 --> 00:23:12,359
Speaker 1: around the corner when not even a majority of sites

375
00:23:12,680 --> 00:23:15,240
Speaker 1: are on the most recent version of two point oh,

376
00:23:15,359 --> 00:23:19,320
Speaker 1: and perhaps an even bigger surprises that, unlike the earlier versions,

377
00:23:19,920 --> 00:23:24,600
Speaker 1: this h T t P protocol will not rely upon

378
00:23:24,720 --> 00:23:27,320
Speaker 1: t c P. I'll explain more in just a second,

379
00:23:27,320 --> 00:23:39,080
Speaker 1: but first let's take another quick break to thank our sponsor. Okay,

380
00:23:39,760 --> 00:23:44,160
Speaker 1: So why would h T t P three point oh

381
00:23:44,560 --> 00:23:47,480
Speaker 1: ditch TCP, which has been a part of the framework

382
00:23:47,680 --> 00:23:51,640
Speaker 1: of the Internet since the very beginning, since before there

383
00:23:51,960 --> 00:23:55,560
Speaker 1: was an Internet. Well, it mostly comes down to two

384
00:23:55,600 --> 00:24:00,240
Speaker 1: big things, speed and efficiency. So when Robert Cohn and

385
00:24:00,280 --> 00:24:03,280
Speaker 1: when vent surf we're working on TCP, they were building

386
00:24:03,280 --> 00:24:07,240
Speaker 1: out a protocol to handle any sort of application that

387
00:24:07,280 --> 00:24:10,280
Speaker 1: would be built on top of what was to become

388
00:24:10,280 --> 00:24:13,520
Speaker 1: the Internet. So and it has a very much a

389
00:24:13,600 --> 00:24:17,399
Speaker 1: one size fits all kind of approach to that it

390
00:24:17,480 --> 00:24:20,280
Speaker 1: provided useful or really I mean, at this point I

391
00:24:20,280 --> 00:24:25,440
Speaker 1: should just say necessary set of features to facilitate communication.

392
00:24:25,960 --> 00:24:30,880
Speaker 1: But some of those are excessive or not as pertinent

393
00:24:31,080 --> 00:24:33,560
Speaker 1: to the types of traffic that happened over h T

394
00:24:33,760 --> 00:24:38,320
Speaker 1: t P, or they impede some of the functions that

395
00:24:38,600 --> 00:24:42,520
Speaker 1: htt P handles. For example, in an effort to establish

396
00:24:42,880 --> 00:24:47,360
Speaker 1: a connection between a client and a server, TCP requires

397
00:24:47,400 --> 00:24:51,880
Speaker 1: a number of back and forth messages, essentially saying, hey

398
00:24:51,920 --> 00:24:55,840
Speaker 1: over there, services, Yeah, what is it? Client says, I

399
00:24:55,840 --> 00:24:57,880
Speaker 1: want to talk to you? The services all right? Hang

400
00:24:57,920 --> 00:25:00,760
Speaker 1: on a second, and the computer says now, good time,

401
00:25:00,800 --> 00:25:02,639
Speaker 1: and the services yeah, yeah, let's go ahead and do that.

402
00:25:03,640 --> 00:25:06,199
Speaker 1: It's far more technical than that, but there's this series

403
00:25:06,240 --> 00:25:09,280
Speaker 1: that goes back and forth in order for a communication

404
00:25:09,359 --> 00:25:13,480
Speaker 1: channel to be established between client and server. That gets

405
00:25:13,520 --> 00:25:17,040
Speaker 1: even more complicated if you want to have an encrypted

406
00:25:17,160 --> 00:25:21,840
Speaker 1: connection over Secure socket Layer or s s L using

407
00:25:21,920 --> 00:25:24,879
Speaker 1: a website. So you know the little lock that you

408
00:25:24,960 --> 00:25:28,000
Speaker 1: see in the address bar when you visit a secure website,

409
00:25:28,240 --> 00:25:31,800
Speaker 1: that's part of s SL. Well, to establish that kind

410
00:25:31,840 --> 00:25:35,400
Speaker 1: of connection between your computer or your computer's browser, which

411
00:25:35,440 --> 00:25:39,160
Speaker 1: is the client, and the server which houses the website

412
00:25:39,160 --> 00:25:42,680
Speaker 1: you're visiting to, it requires even more round trips between

413
00:25:42,800 --> 00:25:46,560
Speaker 1: the two to first establish the connectivity and then established

414
00:25:46,640 --> 00:25:50,879
Speaker 1: the encrypted communications. So the process is good for making

415
00:25:50,920 --> 00:25:54,280
Speaker 1: sure that there is an actual route for data to follow,

416
00:25:54,480 --> 00:25:57,520
Speaker 1: but it's not the most straightforward approach if you want

417
00:25:57,520 --> 00:26:03,040
Speaker 1: to use HTTP, particularly if you want to use encrypted connections.

418
00:26:03,720 --> 00:26:08,879
Speaker 1: There is another protocol, however, called User Data Gram Protocol

419
00:26:09,400 --> 00:26:12,399
Speaker 1: or u d P, and that can serve as the

420
00:26:12,480 --> 00:26:16,119
Speaker 1: foundation for a new transport layer for h T t

421
00:26:16,280 --> 00:26:19,960
Speaker 1: P three point oh. U d P has a big

422
00:26:20,000 --> 00:26:23,919
Speaker 1: advantage over TCP. It is incredibly simple and it is

423
00:26:23,960 --> 00:26:28,360
Speaker 1: incredibly fast. It is a transport layer protocol just like TCP,

424
00:26:28,800 --> 00:26:33,640
Speaker 1: but unlike TCP, u DP does not have the same

425
00:26:33,680 --> 00:26:38,480
Speaker 1: features to ensure communications are established or successful, so that

426
00:26:38,560 --> 00:26:42,600
Speaker 1: could be a big drawback. Right. U DP transmissions are unordered,

427
00:26:43,040 --> 00:26:47,200
Speaker 1: so a later message can arrive ahead of an earlier one,

428
00:26:47,520 --> 00:26:49,679
Speaker 1: and that can be very confusing if you haven't built

429
00:26:49,680 --> 00:26:52,680
Speaker 1: in a way of dealing with that. There's also no

430
00:26:52,800 --> 00:26:55,880
Speaker 1: means for the receiving computer to know if something has

431
00:26:55,920 --> 00:26:59,200
Speaker 1: gone wrong, if packets go missing, like it doesn't know

432
00:26:59,680 --> 00:27:02,600
Speaker 1: if doesn't have all the different pieces, if it's just

433
00:27:02,680 --> 00:27:05,680
Speaker 1: over pure U d P. But U d P can

434
00:27:05,720 --> 00:27:08,280
Speaker 1: act as a base to build upon. It doesn't have

435
00:27:08,440 --> 00:27:10,919
Speaker 1: to be uh. The protocols don't have to be the

436
00:27:11,000 --> 00:27:14,240
Speaker 1: end all be all. That's your starting point. So Google

437
00:27:14,600 --> 00:27:17,040
Speaker 1: has taken you U d P as its starting point

438
00:27:17,520 --> 00:27:20,919
Speaker 1: and built upon it to create an experimental network protocol

439
00:27:21,520 --> 00:27:25,320
Speaker 1: called q U I C for Quick U d P

440
00:27:25,960 --> 00:27:29,959
Speaker 1: Internet Connections. The I E t F has taken this

441
00:27:30,040 --> 00:27:34,359
Speaker 1: experimental protocol and worked on creating a standardized version, which

442
00:27:34,560 --> 00:27:38,080
Speaker 1: in some ways has moved away from what Google's initial

443
00:27:38,160 --> 00:27:40,760
Speaker 1: design was all about, But the writing is on the

444
00:27:40,800 --> 00:27:43,520
Speaker 1: wall for t c P as far as the h

445
00:27:43,680 --> 00:27:47,760
Speaker 1: t t P standard is concerned. Moving forward, the transport

446
00:27:47,840 --> 00:27:51,240
Speaker 1: layer that was initially published in the nineteen seventies is

447
00:27:51,280 --> 00:27:54,840
Speaker 1: going to have to make way for a lighter, more agile,

448
00:27:55,000 --> 00:27:58,760
Speaker 1: and less cumbersome standard. In addition to the move away

449
00:27:58,840 --> 00:28:01,600
Speaker 1: from t c P, the new version of h T

450
00:28:01,760 --> 00:28:06,080
Speaker 1: t P will be more secure. QUICK, as designed by Google,

451
00:28:06,280 --> 00:28:11,040
Speaker 1: transports data by encrypting it by default, is not the

452
00:28:11,119 --> 00:28:14,760
Speaker 1: added layer on top of everything. It is the default layer.

453
00:28:15,200 --> 00:28:18,159
Speaker 1: Google's build, which is sometimes called h t t P

454
00:28:18,600 --> 00:28:23,119
Speaker 1: over QUICK, is supported in the latest versions of Google

455
00:28:23,200 --> 00:28:27,040
Speaker 1: Chrome and in the Opera web browser. Right now, only

456
00:28:27,080 --> 00:28:29,520
Speaker 1: a few websites actually make use of it, most of

457
00:28:29,520 --> 00:28:33,520
Speaker 1: them belong to Google, though Facebook has also been incorporating it.

458
00:28:33,520 --> 00:28:35,920
Speaker 1: It's going to be a really long path to travel

459
00:28:36,320 --> 00:28:40,640
Speaker 1: to get widespread adoption because right now less than two

460
00:28:40,640 --> 00:28:46,640
Speaker 1: percent of all websites support QUICK. Meanwhile, TCP will still

461
00:28:46,680 --> 00:28:49,400
Speaker 1: be in use. Just because it's being phased out of

462
00:28:49,440 --> 00:28:52,840
Speaker 1: future versions of h T t P does not mean

463
00:28:52,840 --> 00:28:56,600
Speaker 1: that this protocol is completely obsolete. As I mentioned earlier

464
00:28:56,600 --> 00:29:00,480
Speaker 1: in this episode, the Worldwide Web is just one implication

465
00:29:00,560 --> 00:29:03,040
Speaker 1: on top of the Internet, there are lots of others

466
00:29:03,280 --> 00:29:06,960
Speaker 1: that will still make use of that venerable set of rules,

467
00:29:07,240 --> 00:29:10,680
Speaker 1: and some websites may never move off of it, since

468
00:29:10,720 --> 00:29:15,040
Speaker 1: it requires work to make the transition, and let's be honest,

469
00:29:15,120 --> 00:29:18,480
Speaker 1: it's not always the highest priority for some businesses that

470
00:29:18,600 --> 00:29:22,200
Speaker 1: maintain websites out there. But it is interesting to me

471
00:29:22,280 --> 00:29:25,560
Speaker 1: to see this move away from TCP. I have always

472
00:29:25,600 --> 00:29:30,240
Speaker 1: associated TCP as being a truly integral part of the Internet,

473
00:29:30,320 --> 00:29:33,400
Speaker 1: and it still will be. It just won't necessarily be

474
00:29:33,800 --> 00:29:38,120
Speaker 1: as integral to web browsing as it used to be.

475
00:29:38,640 --> 00:29:41,960
Speaker 1: Fascinating stuff to me. I hope you guys enjoyed this episode.

476
00:29:41,960 --> 00:29:44,600
Speaker 1: I know it got a little more uh techie with

477
00:29:44,720 --> 00:29:48,080
Speaker 1: the protocols than usual, but I thought this was a

478
00:29:48,080 --> 00:29:51,240
Speaker 1: big deal and one that maybe, probably I'm guessing, is

479
00:29:51,280 --> 00:29:54,760
Speaker 1: not going to get widely reported outside of tech news circles.

480
00:29:55,160 --> 00:29:57,720
Speaker 1: I doubt that you're gonna, you know, turn on the

481
00:29:57,760 --> 00:30:00,960
Speaker 1: local news and some anchor is going to say and

482
00:30:01,160 --> 00:30:05,120
Speaker 1: another news, the Worldwide Web is moving away from this

483
00:30:06,760 --> 00:30:10,600
Speaker 1: ancient set of rules. I just don't see that making

484
00:30:10,640 --> 00:30:14,200
Speaker 1: the news, but it is important anyway. If you guys

485
00:30:14,200 --> 00:30:17,280
Speaker 1: have any suggestions for future episodes of tech Stuff. Maybe

486
00:30:17,320 --> 00:30:20,600
Speaker 1: it's a technology, a company, a person in tech. Maybe

487
00:30:20,800 --> 00:30:24,520
Speaker 1: there's someone you would want me to talk with about technology.

488
00:30:24,680 --> 00:30:27,760
Speaker 1: You should send me those thoughts. You can email the

489
00:30:27,760 --> 00:30:30,800
Speaker 1: show it is tech Stuff at how stuff works dot com,

490
00:30:30,920 --> 00:30:33,280
Speaker 1: or you can go to our website that's text Stuff

491
00:30:33,360 --> 00:30:36,680
Speaker 1: podcast dot com and you can find other ways to

492
00:30:36,720 --> 00:30:39,400
Speaker 1: contact me there. Don't forget to head on over to

493
00:30:39,600 --> 00:30:43,120
Speaker 1: our merchandise store that's at t public dot com slash

494
00:30:43,160 --> 00:30:46,600
Speaker 1: tech Stuff. Everything you purchased there goes to benefit the show.

495
00:30:46,680 --> 00:30:50,040
Speaker 1: We greatly appreciate that, and there's some pretty cool things

496
00:30:50,120 --> 00:30:52,320
Speaker 1: over there. If you haven't checked it out, go see

497
00:30:52,360 --> 00:30:55,680
Speaker 1: if there are any designs that you particularly like. And oh,

498
00:30:56,000 --> 00:31:00,280
Speaker 1: remember we've been nominated in the Science and Technology category

499
00:31:00,320 --> 00:31:03,920
Speaker 1: of the I Heart Radio Podcast Awards. You can head

500
00:31:04,000 --> 00:31:06,440
Speaker 1: on over to the website for the I Heart Radio

501
00:31:06,520 --> 00:31:09,640
Speaker 1: Podcast Awards and vote up to five times a day.

502
00:31:09,880 --> 00:31:12,040
Speaker 1: You can dedicate all five of those votes to tech

503
00:31:12,120 --> 00:31:16,600
Speaker 1: Stuff if that is your desire. But whatever you want

504
00:31:16,600 --> 00:31:18,560
Speaker 1: to do, you should go check out all of those

505
00:31:18,560 --> 00:31:21,080
Speaker 1: different categories see if there are any other shows you

506
00:31:21,120 --> 00:31:23,840
Speaker 1: really like. Maybe you can discover some shows you didn't

507
00:31:23,840 --> 00:31:27,120
Speaker 1: even know existed. I always love finding new podcasts. This

508
00:31:27,200 --> 00:31:29,600
Speaker 1: is a great way of finding some really high quality ones,

509
00:31:30,440 --> 00:31:39,480
Speaker 1: and I'll talk to you again really soon for more

510
00:31:39,560 --> 00:31:41,840
Speaker 1: on this and thousands of other topics, because it how

511
00:31:41,880 --> 00:31:52,760
Speaker 1: stuff works. Dot com