User:The Monster/TCPHeader
Appearance
TCP segment structure
[edit]A TCP segment consists of a segment header and a data section. The TCP header contains 10 mandatory fields, and an optional extension field (Options, pink background in table). The data section follows the header. Its contents is the payload data carried for the application.
Bit offset | 0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
1 0 |
1 1 |
1 2 |
1 3 |
1 4 |
1 5 |
1 6 |
1 7 |
1 8 |
1 9 |
2 0 |
2 1 |
2 2 |
2 3 |
2 4 |
2 5 |
2 6 |
2 7 |
2 8 |
2 9 |
3 0 |
3 1 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0 | Source port | Destination port | ||||||||||||||||||||||||||||||
32 | Sequence number | |||||||||||||||||||||||||||||||
64 | Acknowledgment number | |||||||||||||||||||||||||||||||
96 | Data offset |
Reserved | Flags | Window Size | ||||||||||||||||||||||||||||
0 | 0 | 0 | 0 | C W R |
E C E |
U R G |
A C K |
P S H |
R S T |
S Y N |
F I N | |||||||||||||||||||||
128 | Checksum | Urgent pointer | ||||||||||||||||||||||||||||||
160 ... |
Options (if Data Offset > 5) ... |
- Source port (16 bits) – identifies the sending port
- Destination port (16 bits) – identifies the receiving port
- Sequence number (32 bits) – has a dual role
- If the SYN flag is set, then this is the initial sequence number. The sequence number of the actual first data byte will then be this sequence number plus 1.
- If the SYN flag is clear, then this is the sequence number of the first data byte
- Acknowledgment number (32 bits) – if the ACK flag is set then the value of this field is the next sequence number that the receiver is expecting. This acknowledges receipt of all prior bytes (if any). The first ACK sent by each end acknowledges the other end's initial sequence number itself, but no data.
- Data offset (4 bits) – specifies the size of the TCP header in 32-bit words. The minimum size header is 5 words and the maximum is 15 words thus giving the minimum size of 20 bytes and maximum of 60 bytes, allowing for up to 40 bytes of options in the header. This field gets its name from the fact that it is also the offset from the start of the TCP segment to the actual data.
- Reserved (4 bits) – for future use and should be set to zero
- Flags (8 bits) (aka Control bits) – contains 8 1-bit flags
- CWR (1 bit) – Congestion Window Reduced (CWR) flag is set by the sending host to indicate that it received a TCP segment with the ECE flag set and had responded in congestion control mechansim (added to header by RFC 3168).
- ECE (1 bit) – ECN-Echo indicates
- If the SYN flag is set, that the TCP peer is ECN capable.
- If the SYN flag is clear, that a packet with Congestion Experienced flag in IP header set is received during normal transmission(added to header by RFC 3168).
- URG (1 bit) – indicates that the Urgent pointer field is significant
- ACK (1 bit) – indicates that the Acknowledgment field is significant. All packets after the initial SYN packet sent by the client should have this flag set.
- PSH (1 bit) – Push function
- RST (1 bit) – Reset the connection
- SYN (1 bit) – Synchronize sequence numbers. Only the first packet sent from each end should have this flag set. Some other flags change meaning based on this flag, and some are only valid for when it is set, and others when it is clear.
- FIN (1 bit) – No more data from sender
- Window (16 bits) – the size of the receive window, which specifies the number of bytes (beyond the sequence number in the acknowledgment field) that the receiver is currently willing to receive (see Flow control)
- Checksum (16 bits) – The 16-bit checksum field is used for error-checking of the header and data
- Urgent pointer (16 bits) – if the URG flag is set, then this 16-bit field is an offset from the sequence number indicating the last urgent data byte
- Options (Variable 0-320 bits, divisible by 32) – The length of this field is determined by the data offset field. Options 0 and 1 are a single byte (8 bits) in length. The remaining options indicate the total length of the option (expressed in bytes) in the second byte.[1] Some options may only be sent when SYN is set; they are indicated below as [SYN].
- 0 (8 bits) - End of options list
- 1 (8 bits) - No operation (NOP, Padding) This may be used to align option fields on 32-bit boundaries for better performance.
- 2,4,SS (32 bits) - Maximum segment size (see maximum segment size)
- 3,3,S (24 bits) - Window scale (see window scaling for details) [SYN][2]
- 4,2 (16 bits) - Selective Acknowledgement supported. [SYN] (See selective acknowledgments for details) [3]
- 5,N,BBBB,EEEE,... (variable bits, N is either 10, 18, 26, or 34)- Selective ACKnowlegement (SACK) [4] These first two bytes are followed by a list of 1-4 blocks being selectively acknowledged, specified as 32-bit begin/end pointers.
- 8,10,TTTT,EEEE (80 bits)- Timestamp and echo of previous timestamp (see TCP Timestamps for details)[5]
- 14,3,S (24 bits) - TCP Alternate Checksum Request. [SYN][6]
- 15,N,... (variable bits) - TCP Alternate Checksum Data.
- (The remaining options are obsolete, experimental, not yet standardized, or unassigned)
- ^ http://www.iana.org/assignments/tcp-parameters/
- ^ RFC 1323, TCP Extensions for High Performance, Section 2.2
- ^ RFC 2018, TCP Selective Acknowledgement Options, Section 2
- ^ RFC 2018, TCP Selective Acknowledgement Options, Section 3
- ^ RFC 1323, TCP Extensions for High Performance, Section 3.2
- ^ RFC 1146, TCP Alternate Checksum Options