IPv6’s standard 16-bit Payload Length field caps a packet’s payload at 65,535 bytes. RFC 2675 defines “jumbograms” for IPv6 links with MTUs large enough to carry bigger packets, allowing payloads up to 4,294,967,295 bytes. It introduces a Jumbo Payload option in the Hop-by-Hop Options header, immediately after the IPv6 header. The option carries a 32-bit payload length, which must exceed 65,535; the IPv6 Payload Length field is set to zero when it is used. Support is needed only on nodes that may use links with MTUs above 65,575 bytes, and such links must not expose unsupported nodes to jumbograms. Jumbograms cannot include an IPv6 Fragment header, and checksum calculations must use the jumbo length rather than the zero IPv6 length.
The specification also adapts UDP and TCP so they can use these packets. For UDP, a packet longer than 65,535 bytes uses zero in the UDP Length field; the receiver derives the actual UDP length from the Jumbo Payload Length, accounting for intervening extension headers. The actual UDP length - not zero - must be used in the checksum pseudo-header. TCP implementations supporting jumbograms must include the specified changes to accommodate existing 16-bit fields, including the MSS option and urgent pointer. Nodes that recognize the Jumbo Payload option must detect malformed combinations, such as a missing option when the IPv6 payload length is zero, an undersized jumbo length, or a Fragment header, and report errors with ICMP Parameter Problem messages. The RFC also notes that 16-bit TCP and UDP checksums become less reliable as the amount of data checked grows.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.