4 ms·
I'm not sure I agree with Geoff's concern on fragmentation of the IPv4 internet due to growth and lack of v6 migration. I absolutely agree the increased cost of
by zamadatix 5y ago
I'm not sure I agree with Geoff's concern on fragmentation of the IPv4 internet due to growth and lack of v6 migration. I absolutely agree the increased cost of maintaining ever more complex and larger scaled NATs is going to continue to drive IPv6 migration but that these are possible is exactly why fragmentation won't happen in my mind.
The cost of fragmentation (due to growth, not other factors like national politics) is far greater than the cost of running even multiple levels of NAT (e.g. CG-NAT) and, apart from already being done in many places today, this scales to nearly the same level as IPv6. Yes, IPv6 has 128 bit addresses but over half of this address space will be "wasted" for ease of use like /64s and/or ease of allocation like allocating enormous blocks that will be sparsely filled with /64s for decades to come. Meanwhile GC-NAT allows nearly 100% utilization of any public IPs via dynamic assignment. Suddenly adding nearly 32 bits (there will be inefficiencies so it won't be the theoretical 32) of address pool on top of the nearly 32 bits address pool isn't all that far from the "128" bits of IPv6. It is however god awful complicated, slower/more latent due to needing to go to NAT points, and needs more centralized care and feeding to keep running, but not really at risk of being to limiting to drive a fragmented internet in anyone's lifetime due to "running out of NAT" or such.
Hopefully however these pressures from the burden of NATs and the ability to do more than just client+server model on TCP/UDP like the article points out and continues driving IPv6 to the point NAT64 becomes cheaper/easier to run and use than dual stack with v4 NAT.
Obligatory off topic plug (sorry dang) about this tech hacker site still being v4 only.
- immibis 5y agoNote although half the bits in IPv6 are wasted under current schemes, almost 7/8 of the IPv6 space is unused, precisely so that if we screw up the public allocation we have many more chances to start over. And there is no fundamental technical limitation on subnets smaller than /64, either. Should 45 bits not be enough (and it won't be, not forever!) we could start using DHCPv6 on smaller subnets, instead of using SLAAC.
- jandrese 5y agoThere is a lot of assumptions that are broken if you try to allocate something smaller than /64. It would be like trying to re-assign the multicast address space for unicast. But running out of space on IPv6 is seriously not a concern. Even a "paltry" 64 bits of address space is an absurdly large number of addresses. Humans need to have colonized the entire galaxy before it becomes an issue.
- mortenlarsen 5y agoYes, 64 bits is the same amount of space as an entire IPv4 Internet NAT'ed behind every IPv4 address on the current Internet. Actually more if you take multicast and reserved addresses into account.
- immibis 5y agoI believe the current allocation plan allows for 2^45 "customers" getting a /48 each. While we don't have 2^45 humans get, it's not too hard to imagine having more than one "customer" per human especially due to corporations and multi-homing, and there will be unused space due to hierarchical allocations, and I'd say that with 128 bits available, probably more than 10 of them should be devoted to future-proofing. If each customer were to get a /64 or a /60 or perhaps a /56 by default, that would leave plenty of room for inefficient hierarchical allocation and future-proofing. But that doesn't leave many bits for subnetting. To my knowledge, the only thing that breaks in subnets smaller than /64 is automatic address assignment, i.e. SLAAC and privacy addresses, which are in no way required, merely convenient.
- Arnavion 5y agoNothing breaks irrevocably in subnets smaller than /64, including SLAAC and privacy addresses. You just need NDP proxies between them.
- jandrese 5y agoThere are plenty of second order effects though. Like IPv6 blacklists operating at the /64 level or higher. Sharing a /64 is like being behind the same natted IPv4 address as a bad guy.