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] RIPE Access Policy Change Request to allow allocations to critical infrastructure
- Previous message (by thread): [address-policy-wg] RIPE Access Policy Change Request to allow allocations to critical infrastructure
- Next message (by thread): [address-policy-wg] RIPE Access Policy Change Request to allow allocations to critical infrastructure
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Elmar K. Bins
ripe at detebe.org
Mon Jan 12 16:48:37 CET 2004
chapuis at ip-plus.net (Andre Chapuis) wrote: > Agreed, > And what about defining an address-range where every ISP opens its filter up to /29 (as an example) ? This would deal with both anycast and address-space conservation. > Let's show that we (as ISPs) are not bound to the /24 forever ! Nice idea. You try convincing the Tier-1s (and -wannabes). I second this thought, but I deem it impractical, since the "big players" will be hard to convince to change their filtering boundaries. I believe, some answers will be in the style of "who's RIPE anyway?". Yours, Elmar. -- Es gibt Luegen, verdammte Luegen und RIPE-141(-219)-Netzantraege. (mlelstv, dcii 2003) -----------------------------------------------------------[ ELMI-RIPE ]---
- Previous message (by thread): [address-policy-wg] RIPE Access Policy Change Request to allow allocations to critical infrastructure
- Next message (by thread): [address-policy-wg] RIPE Access Policy Change Request to allow allocations to critical infrastructure
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]