RFC 2675: IPv6 Jumbograms
caminanteblanco
29 points
47 comments
November 18, 2026
Related Discussions
Found 5 related stories in 533.9ms across 13,334 title embeddings via pgvector HNSW
- RFC8950: Announce IPv4 with an IPv6 next-hop porridgeraisin · 102 pts · October 16, 2026 · 52% similar
- Closing the IPv6 first-packet gap with GRAND m_montazeri · 26 pts · September 15, 2026 · 49% similar
- A Farewell to ARPs: IPv4 Service on IPv6-Only Networks speckx · 46 pts · July 13, 2026 · 47% similar
- CVE-2026-98432: Linux IPv4 UAF Shank · 24 pts · October 31, 2026 · 46% similar
- UTF-8000: Unlimited UTF-8 vismit2000 · 129 pts · September 20, 2026 · 46% similar
Discussion Highlights (6 comments)
theamk
maybe not everything needs to be IPv6? No standard equipment can do 64K+ frames, so you are not going to be connecting to global internet soon. Plus, why are you doing this at all? If you are super-concerned with the overhead, you don't want IP stack anyway, with all its layers and tunables - you want something like RDMA which can work very close to metal. And if you are OK with overhead, then why go with huge frames? Go with small ones and reassemble, your life would be much easier. (Normally reassembling is a pain because of possibility of lost or reordered packets, but if you are willing to go with such huge packet size, it must not be a concern with you) (this reminds of the opposite direction: people stuffing IPv6 into sensor networks.. your frames are 32/64 _bytes_ and you want IPv6 headers in there???)
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.
bflesch
(1999) is missing. Crazy how far ahead these folks were planning, I wonder what they work on today.
lwarfield
I crashed my college campus's routing infrastructure once by sending a 4GB packet!
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.
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?