1 00:00:00,470 --> 00:00:09,440 A Tsipi segment consists of a segment header and a data section, the TCP header contains 10 mandatory 2 00:00:09,440 --> 00:00:12,380 fields and an optional extension field. 3 00:00:13,420 --> 00:00:18,190 The optional field is the options field, which is the last field seen on the sly. 4 00:00:19,300 --> 00:00:25,500 The TCP header includes a source port and destination port each 16 bits in like. 5 00:00:26,630 --> 00:00:31,340 The source port is the port on the originating machine that emitted the packet. 6 00:00:32,840 --> 00:00:36,360 The destination port indicates the port on the target machine. 7 00:00:36,560 --> 00:00:38,150 The package should be delivered to. 8 00:00:39,670 --> 00:00:46,210 The sequence number and an acknowledgement number allows Tsipi to track a series of packets to make 9 00:00:46,210 --> 00:00:49,500 sure they arrive reliably and pretty much in order. 10 00:00:49,870 --> 00:00:51,420 No, absolutely in order. 11 00:00:52,360 --> 00:00:56,110 If a packet is lost, TCP will retransmit it. 12 00:00:56,980 --> 00:01:03,340 If packets arrive out of order, TCP will adjust them to make sure that they are delivered to the destination 13 00:01:03,340 --> 00:01:05,230 services in the proper order. 14 00:01:07,480 --> 00:01:13,150 Data asset specifies the size of the TCP header in 32 bit words. 15 00:01:14,530 --> 00:01:19,330 The minimum size header is five words and the maximum is 15 words. 16 00:01:20,520 --> 00:01:27,210 There's also TCP control bit space, also known as Flagg's, which are incredibly important for tracking 17 00:01:27,210 --> 00:01:29,610 the state of a given TCP connection. 18 00:01:30,300 --> 00:01:33,150 As you know, we talked about them a few minutes ago. 19 00:01:34,160 --> 00:01:37,230 Of course, if you didn't take a break, it was a few minutes ago. 20 00:01:37,470 --> 00:01:39,800 But whatever you do, just don't spill in the keyboard. 21 00:01:40,590 --> 00:01:46,290 Now, TCP senders use a number called window size, which isn't byte by default. 22 00:01:47,280 --> 00:01:52,830 To regulate how much data they send to a receiver before requiring an acknowledgement in return. 23 00:01:53,890 --> 00:02:00,990 So if the window size becomes too small, network data transfer will be unnecessarily slow, while if 24 00:02:01,000 --> 00:02:07,720 the window size becomes too large, the network link can become saturated or the receiver may not be 25 00:02:07,720 --> 00:02:12,610 able to process incoming data quickly enough, also resulting in slow performance. 26 00:02:14,600 --> 00:02:21,650 Windowing algorithms built into the protocol dynamically calculate size values and use this field of 27 00:02:21,650 --> 00:02:25,820 the TCP headers to coordinate changes between senders and receivers.