[address-policy-wg] "too many" /64 or /48 assignments causing address space exhaustion
- Previous message (by thread): [address-policy-wg] getting second IPv6 PA as a LIR
- Next message (by thread): [address-policy-wg] "too many" /64 or /48 assignments causing address space exhaustion
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Tue May 3 09:53:28 CEST 2011
On 2 May 2011, at 21:45, Andrey Semenchuk wrote: > Yes, IPv6 provide much more address space but if this address space > will be wastefully allocated as IPv4, history will repeat itself This is just a statement of the bleedin' obvious Andrey. However you don't seem to have any data that shows how current IPv6 allocation policies could repeat those earlier mistakes. > So, the strong recommendation to give customers between a /48 and a / > 64 (and /64 even for a single machine) - is the right way to lay the > foundation of a new address space exhaustion If the Internet doles out a billion /64s every day -- several orders of magnitude more than any forseeable assignment rate -- it will take 50 million years to deplete the IPv6 address space. I'm happy to leave that problem to the next generation. :-)
- Previous message (by thread): [address-policy-wg] getting second IPv6 PA as a LIR
- Next message (by thread): [address-policy-wg] "too many" /64 or /48 assignments causing address space exhaustion
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]