IETF draft standard of IPv8: https://datatracker.ietf.org/doc/html/draft-pouwelse-trustch...
Bonus: "De-DSI" == LLM- based fuzzy search + IPv8
So besides the bad design ipv6 is also badly managed?
Capital One would never get a /16 in RIPE.
The IPv6 designers already thought of that and prepared for that eventuality. Only 1/8 of all available IPv6 addresses (the ones starting with the bits 001) is available for allocation under the current rules. If and when that gets exhausted, there will still be more than 5/8 of all IPv6 addresses available to be allocated under more strict rules. (See https://www.iana.org/assignments/ipv6-address-space/ipv6-add... and https://www.rfc-editor.org/rfc/rfc3513.html#section-4 for more details.)
[0] - https://blog.benjojo.co.uk/post/class-e-addresses-in-the-rea...
Yes yes yes, all sorts of really super serious policies were put in place to prevent abuse of IPv4 allocation rules too.
I have a /32 as an individual that I also got no questions asked.
It’s more IPv6 space than I could ever use.
However, IPv6 space has to be measured in /48s, and IPv4 in /24s, as those are the smallest possible BGP announcable blocks.
With IPv6 there's also an unwritten rule that RIRs will only assign blocks ending on a nibble boundary (with the exception of RIPE and their /29s that they expand by one bit every time you run out).
So a /44 is on the second smallest nibble boundary, making it the second smallest allocation possible.
Well, if the VPSes are in seperate sites, at least one per VPS, which means at least 2, which means that according to allocation policies, at least a /44. :)
We will never run out of IPv6, but I believe in my lifetime you won't be able to get new v6 allocations anymore because they will have all been handed out to the large corporations with deep pockets. Oops, no addresses left - but you can rent one from a cloud provider for a few dollars a month.