This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/address-policy-wg@ripe.net/
[address-policy-wg] getting second IPv6 PA as a LIR
- 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 ]
Mikael Abrahamsson
swmike at swm.pp.se
Tue May 3 09:46:32 CEST 2011
On Mon, 2 May 2011, Andrey Semenchuk wrote: > 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 10 billion people on earth has 10 devices with a /48 for each device, you will have spent approximately one 1/2800th of the IPv6 address space. There are 281 thousand billion /48s. Let's use this current allocation policy until the first /3 is used up, then we have 7 more tries to "get it right" if we decide we need to change something. -- Mikael Abrahamsson email: swmike at swm.pp.se
- 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 ]