75 ms·

If each RIR is limited to one /3, they can hand out 2^45 /48’s or over 8,000 entire IPV4 worth of addresses that can than be each subnetted 2^16 times and each

If each RIR is limited to one /3, they can hand out 2^45 /48’s or over 8,000 entire IPV4 worth of addresses that can than be each subnetted 2^16 times and each subnet support billions upon billions of hosts. And if we reserved a private address space at another single /3 like 10.0.0.0 is for IPV4 each one of those billions of hosts could have 2^45 addresses behind them as well. Even if there were 15 billion humans and 15 billion businesses and government entities and so on, a single /3 could provide enough /48s with over a billion of addresses to spare with everyone getting their own /48. IPV6 has no lack of addresses. Allowing for hosts to use a full /64 allow for additional features such as an “address TOTP” like this[0]. I will concede that they implemented this with just a /80. [0]: https://github.com/aidansteele/ipv6-ghost-ship https://github.com/aidansteele/ipv6-ghost-ship

withinboredom 4y ago
And yet many hosting companies are only handing out a /64 to hosts, which some software has issues dealing with less than /64 (if running a vm). Currently companies are buying/selling huge blocks of space, just like the early days of ipv4 (like Apple owning a whole /8 still). Yes, you logic of "there's plenty to go around" works, until the feast is over and everyone owns something because it is so cheap.
- bombcar 4y ago
  Mine gave me a 64 but I was able to set dhcpv6 or whatever it is to request a 56 and got it.
  - withinboredom 4y ago
    That works if you have dhcpv6, but in my experience, most hosting is static.
    - bombcar 4y ago
      Yeah, this is for a home connection.
- kemotep 4y ago
  Well that certainly is an issue I can agree with. Properly managed IPV6 has far and away enough addresses. I can see how failing to properly allocate address space can lead to the same issues as IPV4.
- pantalaimon 4y ago
  > many hosting companies are only handing out a /64 to hosts That's why variable SLAAC is about to become a thing https://datatracker.ietf.org/doc/draft-mishra-6man-variable-slaac/ https://datatracker.ietf.org/doc/draft-mishra-6man-variable-...

withinboredom 4y ago

And yet many hosting companies are only handing out a /64 to hosts, which some software has issues dealing with less than /64 (if running a vm). Currently companies are buying/selling huge blocks of space, just like the early days of ipv4 (like Apple owning a whole /8 still). Yes, you logic of "there's plenty to go around" works, until the feast is over and everyone owns something because it is so cheap.

bombcar 4y ago
Mine gave me a 64 but I was able to set dhcpv6 or whatever it is to request a 56 and got it.
- withinboredom 4y ago
  That works if you have dhcpv6, but in my experience, most hosting is static.
  - bombcar 4y ago
    Yeah, this is for a home connection.
kemotep 4y ago
Well that certainly is an issue I can agree with. Properly managed IPV6 has far and away enough addresses. I can see how failing to properly allocate address space can lead to the same issues as IPV4.
pantalaimon 4y ago
> many hosting companies are only handing out a /64 to hosts That's why variable SLAAC is about to become a thing https://datatracker.ietf.org/doc/draft-mishra-6man-variable-slaac/ https://datatracker.ietf.org/doc/draft-mishra-6man-variable-...