3 ms·
I 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 m
by immibis 5y ago
I 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.
- Arnavion 5y agoRight, I wasn't saying that giving end-users something smaller than a /64 should actually be done. Not only does it require more effort but also it breaks higher-level things as you said. I was just saying that there's no technical breakage that would occur, especially not SLAAC or privacy addresses.
- oarsinsync 5y ago> Like IPv6 blacklists operating at the /64 level or higher Several blocklists I'm aware of block at /48s, not at /64s, on the basis that customer allocations (per the spec) are supposed to be /48s. Not enough people use IPv6 right now, so the level of complaints from this is low->zero.
- Arnavion 5y agoRFC6177 (2011) obsoleted the recommendation (which is all it was to begin with, not a "supposed to") that end users should get /48s.