A closer look at TCP Maximum Segment Sizes in the wild
A TCP connection always starts with the three-way handshake. The client sends a SYN packet contains several TCP options including the Maximum Segment Size (MSS) that announces the largest segment that the client agrees to receive. The server provides its own MSS in the SYN+ACK.
The MSS is usually derived from the Maximum Transmission Unit (MTU), i.e. the largest packet that the host can send on its Local Area Network. In a post on the tcpm mailing list, Matt Mathis provided very interesting data on the MSS sizes observed on the Measurement Lab servers.
With IPv4, the most frequent values are :
- 1448 bytes
- 1460 bytes
- 1440 bytes
With IPv6, the most frequent values are :
- 1428 bytes
- 1440 bytes
- 1288 bytes
In both cases, the measurements indicate that there are many other values of the MSS option that the measurement lab servers receive. The full data is available as a csv file. If you have free time, you can try to infer in which scenario a given host would send a given value of the MSS. Note however that there are middleboxes (such as CPE routers, enterprise firewalls, …) that will happily change the MSS option in all SYN segments that they forward to prevent some types of fragmentation problems. You can use tracebox to detect this type of interference.