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] Source of routing table growth
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Masataka Ohta
mohta at necom830.hpcl.titech.ac.jp
Sat Jul 2 13:44:06 CEST 2011
Sander Steffann wrote: >> 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. > > You don't make sense. We're not talking about ISPs here, we're talking > about end users. Considering that end users won't not directly suffer from nor complain about routing table explosions, but some clever ISPs may, we should be talking about ISPs, a collection of which is RIPE. Yes, ISPs through RIRs are the source of problems. > And the IETF can define standards for that. The distance between IETF and end users is, mostly, infinite. 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 ]