Hacker News
RFC 2675: IPv6 Jumbograms
caminanteblanco
|next
[-]
The only place I could see the layman ever getting close to using this would be loopback. But at that point, you have IPC.
riffic
|root
|parent
|next
[-]
A 4 GB microSD card is well within the carrying capacity of a pigeon.
caminanteblanco
|root
|parent
[-]
Thank you riffic for sharing this, this reminds me of the SIGBOVIK papers :)
Pet_Ant
|root
|parent
|next
|previous
[-]
I mean inter-container communication on a host?
Also I assume it’s not a design goal to support 4GB but it is just a result of a power of 2. They are basically just doubling the size from 16 to 32 bits. Trimming it to 30 bit to cap it at something "reasonable" 1GB or something is more hassle then it’s worth.
I just cannot imagine the error correction on those packets. I mean if anything goes wrong that's a lot to toss away.
Palomides
|root
|parent
|next
|previous
[-]
bflesch
|next
|previous
[-]
theamk
|previous
[-]
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???)