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] "too many" /64 or /48 assignments causing address space exhaustion
- Previous message (by thread): [address-policy-wg] "too many" /64 or /48 assignments causing address space exhaustion
- Next message (by thread): [address-policy-wg] "too many" /64 or /48 assignments causing address space exhaustion
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Florian Weimer
fweimer at bfk.de
Tue May 3 10:10:21 CEST 2011
* Jim Reid: > 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. :-) There have been suggestions to use multiple /24s for each ISP using certain IPv6 deployment strategies. Exhaustion isn't so remote anymore if such efforts become widespread. -- Florian Weimer <fweimer at bfk.de> BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstraße 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99
- Previous message (by thread): [address-policy-wg] "too many" /64 or /48 assignments causing address space exhaustion
- Next message (by thread): [address-policy-wg] "too many" /64 or /48 assignments causing address space exhaustion
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]