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] Re: Source of routing table growth
- Previous message (by thread): [address-policy-wg] Re: Source of routing table growth
- Next message (by thread): [address-policy-wg] Source of routing table growth
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jan Zorz @ go6.si
jan at go6.si
Sun Jul 3 23:49:24 CEST 2011
On 7/3/11 10:01 PM, Daniel Roesen wrote: > On Sun, Jul 03, 2011 at 08:44:08PM +0200, Jan Zorz @ go6.si wrote: >> RIPE is not a place to discuss this, as RIPE is all about resources >> allocation and policies around that, not how resources are used. > > RIPE has a long history of dealing with things outside of the resource > allocation and policy matters. With the IPv6 equipment requirement > document (RIPE-501) - authored partly by yourself - being the most > "offtopic" one I'm aware of. Hi, I agree :) But there is difference between BCP and policy. If we can fix routing table growth with BCP, then let's try :) What I'm afraid here is that we need stronger means than BCP for this matter. Cheers, Jan
- Previous message (by thread): [address-policy-wg] Re: Source of routing table growth
- Next message (by thread): [address-policy-wg] Source of routing table growth
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]