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] "too many" /64 or /48 assignments causing address space exhaustion
- Next message (by thread): [address-policy-wg] getting second IPv6 PA as a LIR
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sascha Lenz
slz at baycix.de
Tue May 3 10:08:05 CEST 2011
Hay, Am 02.05.2011 um 22:45 schrieb Andrey Semenchuk: [...] > 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 That's not the case. PLEASE use your favorite search engine to find the last thousand discussions about this and do the math yourself. -- Mit freundlichen Grüßen / Kind Regards Sascha Lenz [SLZ-RIPE] Senior System- & Network Architect
- Previous message (by thread): [address-policy-wg] "too many" /64 or /48 assignments causing address space exhaustion
- Next message (by thread): [address-policy-wg] getting second IPv6 PA as a LIR
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]