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 ]
Turchanyi Geza
turchanyi.geza at gmail.com
Tue May 3 10:48:01 CEST 2011
> > One thing that does worry me is the use of very long prefixes for v6 "to > save address space" which then causes the size of DFZ to explode. > ??? If an ISP receive max 2 IPv6 blocks, this is just two entries in the (current BGP) routing table. The use of long prefixes in the costumer's network means more costumers served from the same block. Is there a point where we disagree? Géza -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/address-policy-wg/attachments/20110503/3d0e5f48/attachment.html>
- 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 ]