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 ]
Florian Weimer
fweimer at bfk.de
Mon Jul 4 09:37:40 CEST 2011
* Sander Steffann: > Hi Masataka, > >> 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. And the IETF can define standards for that. The ISP vs end user distinction is very fuzzy. Even the RIPE policy documents don't use the terms consistently. And in most contexts, the term "ISP" includes companies mainly providing web and mail hosting services. -- Florian Weimer <fweimer at bfk.de> BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstraße 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99
- 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 ]