3 ms·
The statement about IPv6 [internet] having 2^128 addresses is completely and utterly untrue, in the same way as it would be untrue to claim that IPv4 [internet]
by aexaey 11y ago
The statement about IPv6 [internet] having 2^128 addresses is completely and utterly untrue, in the same way as it would be untrue to claim that IPv4 [internet] have 2^48 TCP ports.
What IPv6 have address-space-wise, is 2^64 subnets, out of which 2^61 is actually allocated to be routable over public internet.
Then comes granularity of /48 allocations (= 2^16 subnets) to end users and /32 allocations (= 2^32 subnets) to ISPs. That gives just 2^45 end users and 2^29 ISPs at best. In practice, if handing a user a /48 would become a common practice, all medium and large IPSs would start accumulating multiple /32s, then routing concerns would come back, and largest ISPs will start aggregating to /28s or /24s or whatnot.
That is still a whole lot of addresses (and IPv4 still looks laughably small in comparison), but actual, practical numbers are way, way lower then "340 undecillion" marketing figure being plastered all over the place.
- km3k 11y agoFrom what I've read, most end users will get /56 blocks and larger organizations will be the ones to get a /48, so the potential end users is much higher than you've estimated.
- aexaey 11y agoBlanket policy of /48 per end user comes from a (now obsolete) RFC3177. All RIRs now have less generous recommendations - both RIPE [0] and ARIN [1] seem to operate in /56 granularity nowadays, which is a very sensible step forward of course. [0] https://www.ripe.net/publications/docs/ripe-650 https://www.ripe.net/publications/docs/ripe-650 [1] https://www.arin.net/policy/nrpm.html#six7 https://www.arin.net/policy/nrpm.html#six7