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 ]
Jim Reid
jim at rfc1035.com
Tue May 3 10:31:34 CEST 2011
On 3 May 2011, at 09:26, Turchanyi Geza wrote: > Jim, probably you are better expert in this field than me I very much doubt that. > - what do you > foresee about scaling of routing and the possibilities of chosing > between > different backbone service providers in the future? If I knew the answers to your question, I would have a much more lucrative career as a commodities trader or buying lottery tickets. :-) 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.
- 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 ]