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] Source of routing table growth
- Previous message (by thread): [address-policy-wg] Source of routing table growth
- Next message (by thread): [address-policy-wg] Source of routing table growth
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Masataka Ohta
mohta at necom830.hpcl.titech.ac.jp
Sat Jul 2 09:35:02 CEST 2011
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. Is it time to ressurect RFC2374? Masataka Ohta
- Previous message (by thread): [address-policy-wg] Source of routing table growth
- Next message (by thread): [address-policy-wg] Source of routing table growth
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]