3 ms·
This is wrong for a few reasons. It is common to try to fit TCP packets into 1500 bytes (minus the bytes for the IP and TCP headers) because 1500 bytes is a com
by eklitzke 5y ago
This is wrong for a few reasons. It is common to try to fit TCP packets into 1500 bytes (minus the bytes for the IP and TCP headers) because 1500 bytes is a common MTU for Ethernet, but this isn't a limitation of TCP, it's just something done to avoid fragmentation. Without extensions TCP packets can be sized up to 64KB. For example, in an environment with jumbo Ethernet frames you might have 9000 byte MTU at the link layer which is just fine. But it's also fine to send a 9000 byte or even 64KB TCP packet over a network with a 1500 byte MTU, the packet will just be split up at the IP layer using IP fragmentation. And as the article points out, RFC 2675 allows creating TCP packets whose payload is even larger than 64KB.
- bogomipz 5y agoNo it is not wrong. In fact you are supporting my point exactly. My question was about the terminology the author was using. Packets are TCP terminology. Frames are ethernet terminology and the 1500 byte limit is because this is the MTU of an Ethernet interface, again a layer 2 concern not layer 4. See also elsewhere in this thread where I also asked what the benefit of this over Jumbo frames.