RFC 2675 defines IPv6 Jumbo Payload option for packets over 65,535 bytes
RFC 2675, published by the Network Working Group in August 1999, specifies an IPv6 hop-by-hop option called Jumbo Payload that uses a 32-bit length field to support packet payloads between 65,536 and 4,294,967,295 octets, called 'jumbograms.' It also details necessary modifications to TCP and UDP so they can handle these oversized payloads, and it obsoletes the earlier RFC 2147.
GoKawiil's interpretation of the reporting above, not reported fact.
The standard only applies to IPv6 nodes connected to links with an MTU greater than 65,575 octets, meaning most networks need not implement it, which suggests the option targets specialized high-bandwidth or research networking environments rather than general internet use. By formalizing how transport protocols handle such large payloads, the RFC could help future networks exceeding standard packet-size limits interoperate consistently.
- RFC 2675 introduces the IPv6 Jumbo Payload option, enabling payloads up to about 4.29 billion octets via a 32-bit length field.
- The option is only relevant to IPv6 nodes on links with MTU greater than 65,575 octets and need not be implemented elsewhere.
- The document also specifies required changes to TCP and UDP to support these jumbogram packets, and it supersedes RFC 2147.
Source: rfc-editor.org — D. Borman, 2026-11-18
Published there as: “RFC 2675: IPv6 Jumbograms”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.