| ▲ | caminanteblanco 2 hours ago |
| 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. |
|
| ▲ | tosti 32 minutes ago | parent | next [-] |
| IPv6 is designed to last. Just because we can't fathom a use case today doesn't mean we'll never have one. |
|
| ▲ | Pet_Ant 2 hours ago | parent | prev | next [-] |
| > loopback 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. |
| |
| ▲ | wahern 16 minutes ago | parent | next [-] | | > I just cannot imagine the error correction on those packets. I mean if anything goes wrong that's a lot to toss away. I think the original jumbogram work occurred back when alot of people were still convinced end-to-end IP alone wasn't suitable for many uses. This was the era when, e.g., people were still pitching ATM or exploring bespoke solutions for linking research centers. So basically jumbograms were presumed to be delivered atop another long-haul, multi-link protocol that would provide reliability. Jumbograms were a way to improve the throughput and latency between IP peers with minimal but high-impact changes to application and kernel network stacks (presuming IPv6 adoption), placing most of the complexity in the network transit layers. What we ended up with, ironically, was the reverse, everything IP and below largely ossified from software perspective, some minor evolution at the TCP layer, but most progress happening above TCP/UDP, and alot of work invested in local hardware link layers that remains opaque to IP or even the ethernet software stack, effectively placing a ceiling on dividends. | |
| ▲ | caminanteblanco 2 hours ago | parent | prev [-] | | I hadn't thought of that, that would be a potential use case for sure. And I agree that literal 4GB packets probably aren't what's in mind here, but I think it is an oddity that a confluence of other factors has it allowed by the RFC. |
|
|
| ▲ | riffic 2 hours ago | parent | prev | next [-] |
| Transit media was addressed by RFC 6214 - avian carrier! Section 3.1 states that "an adult carrier can carry jumbograms [RFC2675]". A 4 GB microSD card is well within the carrying capacity of a pigeon. https://www.rfc-editor.org/rfc/rfc6214.html |
| |
| ▲ | caminanteblanco an hour ago | parent [-] | | https://www.rfc-editor.org/info/rfc1149/ has more specific information in regard to the benefits of avian carriers. Particularly "because of the 3D ether space available to the carriers, in contrast to the 1D ether used by IEEE802.3." Thank you riffic for sharing this, this reminds me of the SIGBOVIK papers :) |
|
|
| ▲ | Palomides 2 hours ago | parent | prev | next [-] |
| I dunno, we've got 800Gb/s NICs with TCP offload now, you could send dozens of gigabyte jumbograms a second |
| |
| ▲ | andrewstuart2 2 hours ago | parent [-] | | Is there really that much room for improvement by changing packet size? You're avoiding a little bit of overhead for the 40 byte packet header and you're also increasing the risk of that packet failing CRC and getting discarded which is a lot more expensive. | | |
| ▲ | pixl97 an hour ago | parent [-] | | I mean over the standard 1500 byte packet, for sure. I'd assume that you'd probably find an optimal spot at 1 to 8Mb on super fast networks. Also networks at these speeds tend to have very low retry rates. It's the buffer sizes that start to get crazy though. |
|
|
|
| ▲ | warkdarrior 2 hours ago | parent | prev [-] |
| My prompts to Claude will finally fit in one packet. |