IPv6 Jumbograms let a single packet carry up to 4 GB of payload
RFC 2675: IPv6 Jumbograms
RFC 2675 defines the IPv6 Jumbo Payload option, a hop-by-hop header that extends the 16-bit Payload Length field to 32 bits, allowing packets with payloads from 65,536 to 4,294,967,295 octets. It also specifies TCP and UDP changes: UDP sets its Length field to zero for jumbograms, while TCP treats an MSS of 65,535 as infinity and handles urgent pointers beyond 65,535 bytes. The option only matters on links with MTU greater than 65,575 octets.
A "jumbogram" is an IPv6 packet containing a payload longer than 65,535 octets.
- darksim905
Speaking out loud in case anyone sees this, but regarding jumbo frames:
why aren't they the default since, I don't know, fiber ISP rollouts? Outside of a slight increase in latency and maybe loss of value with small webpages/fragments, surely ISPs can handle it and you could upgrade fiber ONTs to easily handle 2.5, 5, 10 GigE or fiber directly to your internal network. There's almost no excuse. Other than I guess resource starvation of the end device processing data. Am I not understanding something?
- caminanteblanco
To summarize for the uninitiated, I learned today that IPv6 supports packets of up to 4GB! Why you would ever need a packet within even an order of magnitude of that size is beyond my ken. (Also, I don't know what transit media even support packet sizes anywhere close to that size).
The only place I could see the layman ever getting close to using this would be loopback. But at that point, you have IPC.
- lwarfield
I crashed my college campus's routing infrastructure once by sending a 4GB packet!
- bflesch
(1999) is missing. Crazy how far ahead these folks were planning, I wonder what they work on today.
- cyberax
Sigh. IPv6 again, the tale of bad design and stupidity. IPv6 is forever stuck with 1462 MTU now because they neglected the PMTU discovery.
For larger packets to work, the MTU size signal has to be baked into _each_ packet. ICMP on truncation is NOT a good design.
Of course, there's a belated RFC to fix it: https://www.rfc-editor.org/info/rfc9268/ But it'll never get implemented and deployed, as we're deep in the "ossification" stage for IPv6.