Hi, On Thu, Jan 08, 2004 at 11:08:01PM +0100, Hans Petter Holen wrote:
|That's why I'm in favour to have a policy that permits |allocations for specific, well-defined Anycast services. That |allocations would come from a well-known block, so people |would know to not filter /24s from there (and so on).
What should the cirteria to get "Anycast space" be ?
I had a proposal that nobody commented on :-) - it didn't mention "critical" anywhere, so maybe it wasn't sexy enough. I suggested: -------------------------- - Anycast deployment - multiple distributed servers bring benefits for the whole community - due to protocol limitations this cannot be done using other approaches (like "put up 100 servers at various ISP networks, using PA space from those ISPs") -------------------------- Now it's up to you people out there to come up with something better that a) solves the problem at hand (and not tries to solve everything else while at it - we're not going to save the world today, sorry) b) can be evaluated by a RIPE NCC hostmaster, so there must be clear and *easy* rules - it needs not be easy to get the space, but to say "you go - you don't" should be easy. Of course we could add something like - is accepted in a peer review (following this-and-that procedure) if that's what people want. Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 57882 (57753) SpaceNet AG Mail: netmaster@Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 80807 Muenchen Fax : +49-89-32356-299