WEBVTT - This file was automatically generated by VIMEO

0
00:00:07.500 --> 00:00:10.500
Hello everyone in this video. We will be talking about

1
00:00:10.500 --> 00:00:13.600
 the networking fundamentals. Now, we

2
00:00:13.600 --> 00:00:17.000
 are getting started with OSI and tcp/ip models

3
00:00:16.000 --> 00:00:17.500
 information.

4
00:00:19.400 --> 00:00:22.900
The tcp/ip model is a framework for organizing and

5
00:00:22.900 --> 00:00:26.000
 communicating data across networks. It

6
00:00:25.600 --> 00:00:29.000
 consists of four layers. First one

7
00:00:28.300 --> 00:00:30.100
 is the link layer.

8
00:00:31.600 --> 00:00:34.500
This layer handles the physical connection between devices on

9
00:00:34.500 --> 00:00:38.100
 the same network these responsible for transmitting data

10
00:00:37.100 --> 00:00:40.500
 over the physical link between devices

11
00:00:40.500 --> 00:00:43.000
 and handles issues such as

12
00:00:43.200 --> 00:00:45.400
 error checking and floor control.

13
00:00:46.300 --> 00:00:50.000
And the second one is the internet layer. This

14
00:00:49.200 --> 00:00:52.800
 layer is responsible for routing data

15
00:00:52.800 --> 00:00:55.700
 between devices on different networks. It does

16
00:00:55.700 --> 00:00:58.700
 this by using IP addresses to

17
00:00:58.700 --> 00:01:01.800
 identify devices and reading data through

18
00:01:01.800 --> 00:01:04.300
 intermediate devices such as routers as

19
00:01:04.300 --> 00:01:04.800
 needed.

20
00:01:06.300 --> 00:01:09.700
And in the transport layer, this layer is responsible

21
00:01:09.700 --> 00:01:13.400
 for ensuring that data is delivered reliably from

22
00:01:12.400 --> 00:01:15.800
 one device to another it.

23
00:01:15.800 --> 00:01:18.300
 Does this by providing error checking

24
00:01:18.300 --> 00:01:21.800
 floor control and other mechanism to ensure

25
00:01:21.800 --> 00:01:23.800
 that the data is delivered correctly?

26
00:01:24.500 --> 00:01:27.700
And in the application layer, it is

27
00:01:27.700 --> 00:01:30.700
 responsible for providing the interface

28
00:01:30.700 --> 00:01:33.400
 between the network and the applications that

29
00:01:33.400 --> 00:01:36.500
 use it. It is responsible for defining how

30
00:01:36.500 --> 00:01:39.700
 applications communicate with the network and with

31
00:01:39.700 --> 00:01:40.000
 each other.

32
00:01:40.800 --> 00:01:43.500
The tcp/ip model is often referred to

33
00:01:43.500 --> 00:01:46.500
 as the Internet Protocol Suite because it

34
00:01:46.500 --> 00:01:50.300
 defines the protocols that are used to transmit data

35
00:01:50.300 --> 00:01:51.200
 over the internet.

36
00:01:52.600 --> 00:01:55.300
These protocols include TCP which means

37
00:01:55.300 --> 00:01:58.300
 transmission control protocol, which is

38
00:01:58.300 --> 00:02:02.100
 responsible for Reliable data transmission and

39
00:02:01.100 --> 00:02:05.300
 IP which means Internet Protocol.

40
00:02:05.900 --> 00:02:08.300
Which is responsible for routing data

41
00:02:08.300 --> 00:02:09.700
 between Networks.

42
00:02:11.300 --> 00:02:14.800
They also model is a framework for understanding how

43
00:02:14.800 --> 00:02:17.700
 communication occurs between different devices

44
00:02:17.700 --> 00:02:20.200
 on a network. It divides the process of

45
00:02:20.200 --> 00:02:23.900
 communication into seven layers Each of which performs

46
00:02:23.900 --> 00:02:25.500
 a specific set of functions.

47
00:02:26.500 --> 00:02:29.700
These are the layers first one physical

48
00:02:29.700 --> 00:02:30.200
 layer.

49
00:02:30.900 --> 00:02:33.500
The physical layer is responsible for the

50
00:02:33.500 --> 00:02:36.700
 transmission of row of data bits over a communication

51
00:02:36.700 --> 00:02:39.800
 Channel. It deals with the physical characteristics

52
00:02:39.800 --> 00:02:41.600
 of the transmission medium.

53
00:02:42.300 --> 00:02:45.500
such as the type of cable or wireless connection

54
00:02:45.500 --> 00:02:46.400
 being used

55
00:02:47.200 --> 00:02:51.400
It also defines the electrical mechanical and functional

56
00:02:50.400 --> 00:02:53.700
 characteristics of the interfaces between

57
00:02:53.700 --> 00:02:54.300
 the devices.

58
00:02:55.300 --> 00:02:59.100
And the second one data link layer, the

59
00:02:58.100 --> 00:03:01.200
 data link layer is responsible for

60
00:03:01.200 --> 00:03:04.500
 providing reliable communication between devices over

61
00:03:04.500 --> 00:03:05.900
 a single link of the network.

62
00:03:06.900 --> 00:03:09.600
Does despite dividing the data into frames

63
00:03:09.600 --> 00:03:12.700
 adding a header and a trailer

64
00:03:12.700 --> 00:03:15.400
 to each frame to identify the start

65
00:03:15.400 --> 00:03:18.900
 and end of the frame and providing

66
00:03:18.900 --> 00:03:21.100
 error detection and correction.

67
00:03:22.200 --> 00:03:25.800
The data link layer is also responsible for establishing

68
00:03:25.800 --> 00:03:28.300
 and maintaining a link between

69
00:03:28.300 --> 00:03:31.500
 devices known as a logical link control.

70
00:03:32.300 --> 00:03:34.400
and in the network layer

71
00:03:35.200 --> 00:03:38.500
It is responsible for routing data between devices on

72
00:03:38.500 --> 00:03:41.600
 the network. It does this by adding a heater

73
00:03:41.600 --> 00:03:44.400
 to each data packet that contains the

74
00:03:44.400 --> 00:03:47.600
 destination address and reading information.

75
00:03:47.600 --> 00:03:50.800
 The network layer is also responsible

76
00:03:50.800 --> 00:03:54.400
 for establishing and maintaining logical connections

77
00:03:53.400 --> 00:03:56.400
 between devices known as

78
00:03:56.400 --> 00:03:58.100
 virtual circuits.

79
00:03:59.600 --> 00:04:02.100
And in the transport layer, the

80
00:04:02.100 --> 00:04:05.700
 transport layer is responsible for providing and

81
00:04:05.700 --> 00:04:09.200
 to end communication between devices. It adds

82
00:04:08.200 --> 00:04:11.700
 a heater to each data packet that

83
00:04:11.700 --> 00:04:14.900
 contains information about the source and destination devices

84
00:04:14.900 --> 00:04:17.600
 and the seconds of the packets

85
00:04:17.600 --> 00:04:21.500
 the transport layer also provides error

86
00:04:20.500 --> 00:04:24.300
 recovery flow control and congestion

87
00:04:23.300 --> 00:04:26.400
 control to ensure that the data

88
00:04:26.400 --> 00:04:29.800
 is delivered reliably and efficiently and

89
00:04:29.800 --> 00:04:32.200
 in the session layer, the session layer

90
00:04:32.200 --> 00:04:36.000
 is responsible for establishing maintaining and

91
00:04:35.800 --> 00:04:39.000
 terminating sessions between devices.

92
00:04:40.600 --> 00:04:43.400
A session is a logical connection between two devices that

93
00:04:43.400 --> 00:04:46.800
 allows them to exchange data in a structured

94
00:04:46.800 --> 00:04:49.700
 manner. The session layer is also responsible

95
00:04:49.700 --> 00:04:53.400
 for providing synchronization and checkpointing

96
00:04:52.400 --> 00:04:55.600
 or services to hello for

97
00:04:55.600 --> 00:04:58.700
 recovery from failures decision layer

98
00:04:58.700 --> 00:05:01.700
 is also responsible for providing synchronization and

99
00:05:01.700 --> 00:05:04.400
 checkpointing services to allow for

100
00:05:04.400 --> 00:05:05.600
 recovery from failures.

101
00:05:07.100 --> 00:05:10.800
And the presentation layer is responsible for the representation

102
00:05:10.800 --> 00:05:13.700
 of data in a format that can

103
00:05:13.700 --> 00:05:16.100
 be understood by both the sender and

104
00:05:16.100 --> 00:05:16.900
 the receiver.

105
00:05:17.700 --> 00:05:20.800
It does this by providing encoding and decoding

106
00:05:20.800 --> 00:05:23.300
 of data as well as compression and

107
00:05:23.300 --> 00:05:24.600
 decompression of data.

108
00:05:25.200 --> 00:05:28.900
The presentation layer is also responsible for encryption and

109
00:05:28.900 --> 00:05:32.100
 decryption of data to provide secure

110
00:05:31.100 --> 00:05:32.500
 communication.

111
00:05:33.300 --> 00:05:36.100
In the application layer, the application layer is the

112
00:05:36.100 --> 00:05:39.700
 highest layer of the OSI model and is

113
00:05:39.700 --> 00:05:42.400
 responsible for providing the interface between

114
00:05:42.400 --> 00:05:45.200
 the network and the applications that use it.

115
00:05:45.200 --> 00:05:48.900
 It defines the protocols and standards that

116
00:05:48.900 --> 00:05:51.400
 applications use to communicate with

117
00:05:51.400 --> 00:05:53.400
 each other and with the network.

118
00:05:54.100 --> 00:05:57.900
It also provide services such as file transfer email

119
00:05:57.900 --> 00:06:00.100
 and virtual terminal access.

120
00:06:01.100 --> 00:06:04.400
The outside model is a useful way of understanding how

121
00:06:04.400 --> 00:06:07.300
 communication occurs between devices on a

122
00:06:07.300 --> 00:06:10.500
 network but it is important to note that it

123
00:06:10.500 --> 00:06:14.100
 is a logical model and doesn't necessarily correspond

124
00:06:13.100 --> 00:06:16.400
 to the physical implementation of a

125
00:06:16.400 --> 00:06:16.500
 network.

126
00:06:17.400 --> 00:06:21.000
In practice many devices and systems combine

127
00:06:20.400 --> 00:06:23.900
 the functions of multiple layers into

128
00:06:23.900 --> 00:06:26.600
 a single device or software component.

129
00:06:28.300 --> 00:06:31.300
If you wonder how a network packet travels in the

130
00:06:31.300 --> 00:06:34.600
 usai model, we can explain this in this

131
00:06:34.600 --> 00:06:37.200
 way. When a device on a network wants to send

132
00:06:37.200 --> 00:06:40.500
 data to another device. It breaks. The

133
00:06:40.500 --> 00:06:43.700
 data down into smaller units called packets.

134
00:06:44.400 --> 00:06:47.900
Each packet contains the data to be transmitted as

135
00:06:47.900 --> 00:06:50.800
 well as a heater that contains information about

136
00:06:50.800 --> 00:06:53.100
 the packet such as the source and

137
00:06:53.100 --> 00:06:56.100
 destination addresses and the sequence number of

138
00:06:56.100 --> 00:06:56.900
 the packet.

139
00:06:57.600 --> 00:07:00.700
As the packet there was through the network. It passes

140
00:07:00.700 --> 00:07:03.500
 through each of the seven layers of the YSI model

141
00:07:03.500 --> 00:07:04.200
 in turn.

142
00:07:04.900 --> 00:07:07.200
At each layer the packet is modified in

143
00:07:07.200 --> 00:07:10.400
 some way to enable it to be transmitted over

144
00:07:10.400 --> 00:07:10.800
 the network.

145
00:07:11.600 --> 00:07:14.300
Here is how a packet travels through the

146
00:07:14.300 --> 00:07:15.000
 OSI model.

147
00:07:15.800 --> 00:07:18.800
At the physical layer, the packet is transformed into

148
00:07:18.800 --> 00:07:21.400
 a series of bits that can

149
00:07:21.400 --> 00:07:24.100
 be transmitted over the physical medium of the network.

150
00:07:24.100 --> 00:07:27.200
 This may involve encoding the bits in

151
00:07:27.200 --> 00:07:30.800
 a particular way to ensure that they can be transmitted to

152
00:07:30.800 --> 00:07:31.200
 reliably

153
00:07:32.200 --> 00:07:34.500
such as using postcode modulation.

154
00:07:35.200 --> 00:07:38.600
Or PCM or such as type of cable

155
00:07:38.600 --> 00:07:40.900
 or wireless connection being used.

156
00:07:42.200 --> 00:07:45.600
And in the data link layer, the packet

157
00:07:45.600 --> 00:07:49.400
 is divided into smaller units called frames Each

158
00:07:48.400 --> 00:07:51.500
 of which contains a heater

159
00:07:51.500 --> 00:07:52.700
 and a trailer.

160
00:07:54.100 --> 00:07:57.500
The application layer is the topmost layer of the OSI model

161
00:07:57.500 --> 00:08:00.500
 and it represents the interface between the

162
00:08:00.500 --> 00:08:03.300
 application and network. Then an application

163
00:08:03.300 --> 00:08:06.600
 wants to send a network packet. It constructs the

164
00:08:06.600 --> 00:08:09.500
 packet and hands it off to the next layer

165
00:08:09.500 --> 00:08:10.800
 down in this stack.

166
00:08:11.500 --> 00:08:14.300
The presentation layer is responsible for

167
00:08:14.300 --> 00:08:17.800
 formatting and encoding the data being transmitted

168
00:08:17.800 --> 00:08:20.800
 as well as for providing that data

169
00:08:20.800 --> 00:08:23.200
 compression and encryption services.

170
00:08:24.100 --> 00:08:27.800
When I picked is handed down from the application layer the

171
00:08:27.800 --> 00:08:30.500
 presentation layer may add its own

172
00:08:30.500 --> 00:08:33.900
 Header information to the packet depending on

173
00:08:33.900 --> 00:08:37.400
 the protocol being used and the

174
00:08:36.400 --> 00:08:39.200
 session layer is responsible for

175
00:08:39.200 --> 00:08:43.000
 establishing maintaining and terminating connections

176
00:08:42.300 --> 00:08:43.900
 between devices.

177
00:08:44.800 --> 00:08:47.500
It does this by exchanging control messages

178
00:08:47.500 --> 00:08:50.500
 between devices to establish and terminate

179
00:08:50.500 --> 00:08:51.000
 sessions.

180
00:08:51.700 --> 00:08:55.200
As well as by providing floor control and error

181
00:08:54.200 --> 00:08:55.800
 Recovery Services.

182
00:08:57.400 --> 00:09:00.800
The transport layer is responsible for establishing and

183
00:09:00.800 --> 00:09:03.700
 maintaining and-to-end connections between devices

184
00:09:03.700 --> 00:09:07.000
 as well as for providing variable data

185
00:09:06.800 --> 00:09:09.200
 transfer services to the application

186
00:09:09.200 --> 00:09:12.100
 layer when I packet is handed down from

187
00:09:12.100 --> 00:09:15.500
 the session layer the transport layer may add its

188
00:09:15.500 --> 00:09:18.200
 own heater information to the packet depending on

189
00:09:18.200 --> 00:09:21.400
 the protocol being used and the network layer

190
00:09:21.400 --> 00:09:24.400
 is responsible for routing packets through the

191
00:09:24.400 --> 00:09:25.800
 network today your destination.

192
00:09:27.100 --> 00:09:30.200
Does this by adding a network layer heater to

193
00:09:30.200 --> 00:09:33.600
 the packet which contains information about source and destination

194
00:09:33.600 --> 00:09:34.900
 addresses of the packet?

195
00:09:36.400 --> 00:09:40.000
The data link layer is responsible for moving packets

196
00:09:39.300 --> 00:09:42.700
 between devices on the same network segment.

197
00:09:43.400 --> 00:09:46.600
It does this by adding a data link header to

198
00:09:46.600 --> 00:09:49.800
 the packet which contains information about source

199
00:09:49.800 --> 00:09:52.500
 and destination devices on the network segment.

200
00:09:53.300 --> 00:09:56.700
The physical layer is responsible for transmitting the

201
00:09:56.700 --> 00:10:00.500
 packet over the actual physical link between devices this

202
00:09:59.500 --> 00:10:02.600
 involves converting the packet

203
00:10:02.600 --> 00:10:05.900
 into a series of electrical sinus or pulses.

204
00:10:06.400 --> 00:10:08.500
Which are transmitted over the link?

205
00:10:09.400 --> 00:10:12.500
Once the packet has been transmitted over the physical link.

206
00:10:13.200 --> 00:10:16.600
It is received by the destination device and goes to

207
00:10:16.600 --> 00:10:18.500
 a similar process in reverse.

208
00:10:19.400 --> 00:10:22.600
Starting at the physical layer and working its way

209
00:10:22.600 --> 00:10:26.600
 up through the layers of the SI model until its

210
00:10:25.600 --> 00:10:28.300
 delivered to the destination application.

211
00:10:30.300 --> 00:10:33.800
Let's talk about encapsulation process based on OSI

212
00:10:33.800 --> 00:10:34.000
 model.

213
00:10:34.700 --> 00:10:38.000
Encapsulation is the process of adding heater

214
00:10:37.400 --> 00:10:40.400
 information to data as it travels to

215
00:10:40.400 --> 00:10:43.500
 a network and is an important aspect of

216
00:10:43.500 --> 00:10:46.500
 how data is transmitted and received over

217
00:10:46.500 --> 00:10:49.000
 a network according to the other side model.

218
00:10:50.100 --> 00:10:53.500
There are some model is a framework for understanding how

219
00:10:53.500 --> 00:10:56.900
 data is transmitted over a network and consists of

220
00:10:56.900 --> 00:10:59.300
 seven layers each with its

221
00:10:59.300 --> 00:11:02.400
 own specific role and function here is a

222
00:11:02.400 --> 00:11:05.600
 step-by-step description of the encapsulation process

223
00:11:05.600 --> 00:11:07.800
 on each layer of the assign model.

224
00:11:08.400 --> 00:11:11.700
First one is the application layer and a

225
00:11:11.700 --> 00:11:14.500
 device sends data over a network it first adds

226
00:11:14.500 --> 00:11:18.300
 an application layer header to the data this header

227
00:11:17.300 --> 00:11:20.200
 contains information about the source and

228
00:11:20.200 --> 00:11:23.500
 destination devices as well as error checking

229
00:11:23.500 --> 00:11:23.800
 data.

230
00:11:24.600 --> 00:11:27.600
And in the presentation layers, the device

231
00:11:27.600 --> 00:11:30.300
 adds a presentation layer header to

232
00:11:30.300 --> 00:11:33.500
 the data this heater contains information about

233
00:11:33.500 --> 00:11:36.100
 the formatting and encoding of the

234
00:11:36.100 --> 00:11:39.000
 data as well as error checking data.

235
00:11:40.500 --> 00:11:43.600
In decision layer the device then adds a

236
00:11:43.600 --> 00:11:46.800
 session layer header to the data this heater

237
00:11:46.800 --> 00:11:49.400
 contains information about the connection between the

238
00:11:49.400 --> 00:11:52.200
 source and destination devices as well

239
00:11:52.200 --> 00:11:53.800
 as error checking data.

240
00:11:54.600 --> 00:11:57.600
And in the transport layer after the

241
00:11:57.600 --> 00:12:00.900
 session layer heater is added the device adds a

242
00:12:00.900 --> 00:12:02.900
 transport layer header to the data.

243
00:12:03.500 --> 00:12:07.100
Is hey there contains information about the reliability and

244
00:12:06.100 --> 00:12:09.100
 Order of the data as well as

245
00:12:09.100 --> 00:12:12.400
 error checking data in the network layer. The

246
00:12:12.400 --> 00:12:15.400
 device adds a network layer header to

247
00:12:15.400 --> 00:12:18.700
 the data which contains the address of destination device

248
00:12:18.700 --> 00:12:20.500
 as well as error checking data.

249
00:12:21.900 --> 00:12:24.900
And in the data link layer after

250
00:12:24.900 --> 00:12:27.700
 the network layer heater is added the device

251
00:12:27.700 --> 00:12:31.600
 adds a data link layer header and filter

252
00:12:30.600 --> 00:12:33.900
 due to the data this contain

253
00:12:33.900 --> 00:12:36.300
 information about source and destination devices

254
00:12:36.300 --> 00:12:38.800
 as well as error checking data.

255
00:12:40.100 --> 00:12:43.800
In physical layer, finally the device adds a

256
00:12:43.800 --> 00:12:46.200
 physical layer heater and footer to the data

257
00:12:46.200 --> 00:12:49.700
 and this information is about physical

258
00:12:49.700 --> 00:12:52.400
 transmission of the data such as the type of

259
00:12:52.400 --> 00:12:55.800
 cables or connectors use it the data rate

260
00:12:55.800 --> 00:12:57.600
 and to signalic method.

261
00:12:58.200 --> 00:13:01.800
Once all of the headers have been added the data

262
00:13:01.800 --> 00:13:04.100
 is fully encapsulated and ready to be

263
00:13:04.100 --> 00:13:07.300
 transmitted over the network when the

264
00:13:07.300 --> 00:13:10.300
 data reach its destination the capsulation process

265
00:13:10.300 --> 00:13:13.400
 begins and the heaters are stripped of

266
00:13:13.400 --> 00:13:16.300
 one layer at a time starting with the

267
00:13:16.300 --> 00:13:19.600
 top layer which means that the application layer

268
00:13:19.600 --> 00:13:22.600
 and working it's way down to the physical layer.

269
00:13:24.100 --> 00:13:27.700
Now we will explain the capsulation process based

270
00:13:27.700 --> 00:13:30.700
 on OSI model the capsulation also

271
00:13:30.700 --> 00:13:33.400
 known as the process of unwrapping or

272
00:13:33.400 --> 00:13:35.900
 stripping of the layers of a packet.

273
00:13:36.400 --> 00:13:39.500
As it travels through a network is an

274
00:13:39.500 --> 00:13:42.300
 important aspect of how data is transmitted and

275
00:13:42.300 --> 00:13:45.600
 received over a network according to the OSI model

276
00:13:45.600 --> 00:13:49.300
 to understand the decapsulation process. It's

277
00:13:48.300 --> 00:13:51.100
 helpful to consider. How data is

278
00:13:51.100 --> 00:13:54.600
 transmitted over the network when a device sends

279
00:13:54.600 --> 00:13:57.300
 data or a network. It wraps the data

280
00:13:57.300 --> 00:14:00.500
 in a series of eaters and Footers that

281
00:14:00.500 --> 00:14:03.900
 contain information about source and destination devices.

282
00:14:04.900 --> 00:14:08.200
As well as error checking data each layer

283
00:14:07.200 --> 00:14:10.400
 of the RSI model adds its

284
00:14:10.400 --> 00:14:13.400
 own header or footer to the data as

285
00:14:13.400 --> 00:14:16.400
 it travels through the network when the data

286
00:14:16.400 --> 00:14:19.500
 reach its destination the capsulation process begins

287
00:14:19.500 --> 00:14:22.500
 the device receiving the data strips of

288
00:14:22.500 --> 00:14:26.000
 the headers and Footers one

289
00:14:25.400 --> 00:14:26.800
 layer at a time.

290
00:14:27.500 --> 00:14:30.900
This process allows the receiving device to extracted

291
00:14:30.900 --> 00:14:33.200
 original data and pass it on to the

292
00:14:33.200 --> 00:14:35.400
 appropriate application for processing.

293
00:14:36.300 --> 00:14:39.400
Here is a detailed step by step description of

294
00:14:39.400 --> 00:14:42.300
 the decoupcellation process on each layer of

295
00:14:42.300 --> 00:14:45.300
 the website model and we will begin with the

296
00:14:45.300 --> 00:14:46.000
 physical layer.

297
00:14:46.800 --> 00:14:49.200
In the physical layer when the data reach

298
00:14:49.200 --> 00:14:52.600
 the physical layer the device receiving the data

299
00:14:52.600 --> 00:14:55.900
 removes on the physical layer header and footer

300
00:14:55.900 --> 00:14:58.400
 which contain information about the

301
00:14:58.400 --> 00:15:01.100
 physical transmission of the data such as the

302
00:15:01.100 --> 00:15:04.600
 type of cables or connectors use it the

303
00:15:04.600 --> 00:15:07.000
 data rate and the signaling method.

304
00:15:07.700 --> 00:15:09.100
In the data link layer.

305
00:15:09.900 --> 00:15:12.800
After the physical layer heater and footer are

306
00:15:12.800 --> 00:15:15.100
 remote the device removes the data link

307
00:15:15.100 --> 00:15:16.800
 layer and footer.

308
00:15:17.300 --> 00:15:20.400
Which contain information about source and destination devices

309
00:15:20.400 --> 00:15:23.100
 as well as error checking data?

310
00:15:24.400 --> 00:15:27.400
In the network layer the device that removes the network

311
00:15:27.400 --> 00:15:28.500
 layer header.

312
00:15:29.100 --> 00:15:31.800
Which contains the address of the destination device?

313
00:15:32.800 --> 00:15:35.600
In the transport layer after the network

314
00:15:35.600 --> 00:15:38.600
 layer is removed the device you're most

315
00:15:38.600 --> 00:15:41.700
 transport layer heater which contains information

316
00:15:41.700 --> 00:15:44.800
 about reliability and Order of

317
00:15:44.800 --> 00:15:47.300
 the data as well as error checking

318
00:15:47.300 --> 00:15:47.500
 data.

319
00:15:48.800 --> 00:15:51.700
And when it comes to session layers

320
00:15:51.700 --> 00:15:54.400
 the device then removes the session layer

321
00:15:54.400 --> 00:15:55.100
 header.

322
00:15:56.500 --> 00:15:59.500
Next the device you most presentation layer

323
00:15:59.500 --> 00:16:02.800
 header contains information about the formatting

324
00:16:02.800 --> 00:16:04.900
 and encoding of the data.

325
00:16:05.900 --> 00:16:08.800
In the application layer, finally the device

326
00:16:08.800 --> 00:16:11.700
 removes the application layer header which

327
00:16:11.700 --> 00:16:14.900
 contains information about the source and destination

328
00:16:14.900 --> 00:16:15.400
 devices.

329
00:16:17.300 --> 00:16:20.600
Now, let me tell you about some common protocols and

330
00:16:20.600 --> 00:16:21.400
 ports.

331
00:16:22.500 --> 00:16:25.300
In a typical network data flows between devices such as

332
00:16:25.300 --> 00:16:28.500
 computer servers and routers using a

333
00:16:28.500 --> 00:16:30.600
 set of protocols and ports.

334
00:16:31.500 --> 00:16:34.600
Protocols are the sets of rules that Define how

335
00:16:34.600 --> 00:16:37.300
 devices communicate with each other over a

336
00:16:37.300 --> 00:16:40.800
 network. They specify the format and structure

337
00:16:40.800 --> 00:16:43.400
 of the data being transmitted as well

338
00:16:43.400 --> 00:16:47.300
 as procedures and rules for exchanging data.

339
00:16:47.900 --> 00:16:50.500
Ports are logical connections on a

340
00:16:50.500 --> 00:16:53.300
 device that allow it to communicate with other

341
00:16:53.300 --> 00:16:56.800
 devices on the network. There are many different protocols

342
00:16:56.800 --> 00:16:59.800
 and port numbers that are commonly used

343
00:16:59.800 --> 00:17:00.900
 in Networks.

344
00:17:01.500 --> 00:17:03.100
Some examples are here.

345
00:17:04.300 --> 00:17:08.100
First one is the TCP which means transmission control

346
00:17:07.100 --> 00:17:08.900
 protocol.

347
00:17:09.800 --> 00:17:12.400
This is a transport layer protocol that

348
00:17:12.400 --> 00:17:15.700
 provides reliable and to end communication

349
00:17:15.700 --> 00:17:16.800
 between devices.

350
00:17:17.700 --> 00:17:20.600
It is commonly used for applications that require

351
00:17:20.600 --> 00:17:23.600
 guaranteed delivery of data such as

352
00:17:23.600 --> 00:17:26.100
 web processing and file transfer.

353
00:17:26.800 --> 00:17:29.200
And the second one is UDP,

354
00:17:29.200 --> 00:17:31.900
 which means user datagram protocol.

355
00:17:32.700 --> 00:17:35.500
This is also a transport layer protocol, but

356
00:17:35.500 --> 00:17:38.800
 it is connectionless and doesn't guarantee

357
00:17:38.800 --> 00:17:40.500
 the delivery of data.

358
00:17:41.300 --> 00:17:44.600
It is often used for real-time applications such

359
00:17:44.600 --> 00:17:47.800
 as video streaming and online gaming

360
00:17:47.800 --> 00:17:51.200
 where it is important more where

361
00:17:50.200 --> 00:17:53.500
 it is more important to receive

362
00:17:53.500 --> 00:17:56.600
 data in a timely manner than to

363
00:17:56.600 --> 00:17:58.700
 ensure that all data is delivered.

364
00:18:00.300 --> 00:18:02.700
At the next one is http.

365
00:18:03.200 --> 00:18:06.800
Which means hypertext transfer protocol this is

366
00:18:06.800 --> 00:18:09.300
 an application layer protocol that is

367
00:18:09.300 --> 00:18:12.500
 used to transmit hypertext documents such as

368
00:18:12.500 --> 00:18:14.500
 web page over the internet.

369
00:18:15.100 --> 00:18:18.200
Is commonly used on Port 80. The other

370
00:18:18.200 --> 00:18:22.500
 one is https, which means HTTP

371
00:18:21.500 --> 00:18:23.100
 secure.

372
00:18:23.500 --> 00:18:26.700
This is a secure version of HTTP that is

373
00:18:26.700 --> 00:18:29.000
 used to transmit data over a secure connection.

374
00:18:29.700 --> 00:18:32.400
And it is commonly used on Port for

375
00:18:32.400 --> 00:18:33.500
 three.

376
00:18:34.900 --> 00:18:37.500
And the next one is FTP, which means

377
00:18:37.500 --> 00:18:39.200
 file transfer protocol.

378
00:18:39.800 --> 00:18:42.300
This is an application layer protocol. Also

379
00:18:42.300 --> 00:18:45.600
 that is used to transfer files between

380
00:18:45.600 --> 00:18:48.200
 devices or network. It is commonly used

381
00:18:48.200 --> 00:18:49.800
 on Port 21.

382
00:18:50.600 --> 00:18:53.700
And the last one is SSH which means

383
00:18:53.700 --> 00:18:55.000
 secure shaft.

384
00:18:55.500 --> 00:18:58.400
This is a network protocol that is used to set

385
00:18:58.400 --> 00:19:01.900
 your remote command line login sessions and other

386
00:19:01.900 --> 00:19:04.600
 types of network connections and it

387
00:19:04.600 --> 00:19:08.000
 is commonly used on Port 22. These

388
00:19:07.300 --> 00:19:10.700
 are just a few examples of the many

389
00:19:10.700 --> 00:19:13.400
 protocols and port numbers that are used in

390
00:19:13.400 --> 00:19:14.200
 Networks.

391
00:19:15.100 --> 00:19:18.800
There are many others and specific protocols and ports

392
00:19:18.800 --> 00:19:21.700
 that are used can depend on the specific

393
00:19:21.700 --> 00:19:24.300
 needs and requirements of the network.

394
00:19:26.300 --> 00:19:29.200
Now I will talk about the three-way handshake.

395
00:19:29.800 --> 00:19:32.300
Three way handshake is a process that is used

396
00:19:32.300 --> 00:19:35.300
 to establish a transport connection between the two

397
00:19:35.300 --> 00:19:36.500
 devices on a network.

398
00:19:37.400 --> 00:19:40.500
It involves the exchange of three messages between

399
00:19:40.500 --> 00:19:42.100
 the devices as follows.

400
00:19:43.100 --> 00:19:46.400
Here is device a sense a scene

401
00:19:46.400 --> 00:19:49.300
 message to device P indicating that it

402
00:19:49.300 --> 00:19:50.700
 wants to establish a connection.

403
00:19:51.500 --> 00:19:54.500
Then device P receives the scene message and

404
00:19:54.500 --> 00:19:58.400
 sends a thin egg synchronize acknowledge

405
00:19:57.400 --> 00:20:00.500
 message back to the device a

406
00:20:00.500 --> 00:20:03.800
 acknowledging the request and indicating

407
00:20:03.800 --> 00:20:06.500
 that it is also ready to establish a

408
00:20:06.500 --> 00:20:06.700
 connection.

409
00:20:07.800 --> 00:20:10.800
Device a receives the syntax

410
00:20:10.800 --> 00:20:13.700
 message and sends an egg message

411
00:20:13.700 --> 00:20:16.400
 which means acknowledge message back to

412
00:20:16.400 --> 00:20:19.400
 the device B acknowledging result of

413
00:20:19.400 --> 00:20:22.600
 the syntax message and completing the three

414
00:20:22.600 --> 00:20:23.500
 way handshake.

415
00:20:24.200 --> 00:20:27.600
Once the trivia handshake is completed. The devices can

416
00:20:27.600 --> 00:20:30.400
 begin exchanging data over the established connection.

417
00:20:31.300 --> 00:20:34.900
The connection remains open until one of the devices sends

418
00:20:34.900 --> 00:20:37.400
 a fin message which means punish message

419
00:20:37.400 --> 00:20:40.500
 to the other indicating that it wants

420
00:20:40.500 --> 00:20:41.500
 to close the connection.

421
00:20:42.600 --> 00:20:45.700
The other device responds with an act

422
00:20:45.700 --> 00:20:47.600
 message and the connection is closed.

423
00:20:49.400 --> 00:20:52.600
here is a sample of network traffic that shows the

424
00:20:52.600 --> 00:20:56.200
 TCP three way handshake in this example device

425
00:20:55.200 --> 00:20:59.200
 a with the IP address 1

426
00:20:58.200 --> 00:21:01.600
 9 2 1 6

427
00:21:01.600 --> 00:21:03.100
 8 1 10

428
00:21:04.100 --> 00:21:08.000
initiates the three-way handshake by sanding message

429
00:21:07.100 --> 00:21:08.900
 to device p

430
00:21:09.800 --> 00:21:12.500
the message includes a sequence number.

431
00:21:13.200 --> 00:21:17.400
A sequence number of hundred 100 which

432
00:21:16.400 --> 00:21:19.900
 is a value that is used to track track.

433
00:21:19.900 --> 00:21:23.000
 The order of the data being transmitted. The

434
00:21:22.600 --> 00:21:26.200
 ACT field is set to zero since this

435
00:21:25.200 --> 00:21:28.500
 is the first message in the three way handshake.

436
00:21:29.100 --> 00:21:33.000
Then device be response with a synec message acknowledging

437
00:21:32.400 --> 00:21:35.500
 the request and indicating that it

438
00:21:35.500 --> 00:21:37.400
 is also ready to establish a connection.

439
00:21:38.200 --> 00:21:43.100
The message includes a sequence number of 200 and

440
00:21:42.100 --> 00:21:46.800
 the Egg field is set to 101

441
00:21:45.800 --> 00:21:48.400
 acknowledging the

442
00:21:48.400 --> 00:21:52.100
 same message from device a and lastly device

443
00:21:51.100 --> 00:21:54.700
 a response with an X message

444
00:21:54.700 --> 00:21:57.700
 acknowledging recite of the scene act

445
00:21:57.700 --> 00:22:00.800
 message and completing the three way

446
00:22:00.800 --> 00:22:03.700
 handshake the message includes a sequence

447
00:22:03.700 --> 00:22:06.800
 number of 101 and

448
00:22:06.800 --> 00:22:10.700
 the heck field is set to 201.

449
00:22:11.500 --> 00:22:14.400
Acknowledging the sin act message from device B

450
00:22:14.400 --> 00:22:17.700
 wants the three way handshake is complete the

451
00:22:17.700 --> 00:22:20.200
 devices can begin exchanging data

452
00:22:20.200 --> 00:22:23.800
 over the established connection the connection remains open

453
00:22:23.800 --> 00:22:26.400
 until one of the devices sends a

454
00:22:26.400 --> 00:22:27.500
 thin message to the other.

455
00:22:29.100 --> 00:22:32.000
Now we have finished the section 1 move on to the next

456
00:22:32.100 --> 00:22:35.700
 we will talk about basics of Wireshark. See you

457
00:22:35.700 --> 00:22:36.100
 on the next video.
