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/[email protected]/
[address-policy-wg] Source of routing table growth
- Previous message (by thread): [address-policy-wg] Source of routing table growth
- Next message (by thread): [address-policy-wg] Re: Source of routing table growth
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jan Zorz @ go6.si
jan at go6.si
Sun Jul 3 20:44:08 CEST 2011
On 7/2/11 9:35 AM, Masataka Ohta wrote: > Sander Steffann wrote: > >> Getting a good solution for this is _very_ important to limit >> routing table growth. Many people/organizations probably >> don't want the hassle of BGP if they can get more redundancy >> and less dependencies on a single ISP (easier renumbering >> will help too) in a simpler way. But this is IETF territory, >> not RIPE :-) > > IETF can do nothing unless ISPs of RIPE and other RIRs accept > the restriction that only very large ISPs can have their own > global routing table entries and address spaces of other ISPs > must be delegated from those of the very large ISPs. RIPE is not a place to discuss this, as RIPE is all about resources allocation and policies around that, not how resources are used. IETF is not a place to discuss that, as if we understand what IETF stands for - that's engineering body that makes protocols and standards, not how resources are used. So we need new institution for that, let's call it "Internet Routing Police". Should I start filling in the registration papers for new not-for-profit institute with that name? :) Cheers, Jan Zorz
- Previous message (by thread): [address-policy-wg] Source of routing table growth
- Next message (by thread): [address-policy-wg] Re: Source of routing table growth
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]