Hi, On Tue, Jun 15, 2004 at 04:10:57PM +0200, Wilfried Woeber, UniVie/ACOnet wrote:

...

...

If you qualify for at least /24 of v4 address space, there shouldn't be a problem with current v4 policy?

There is. People don't want to use part of their PA block for the anycast announcement (due to "allocation boundary" filters) and you won't qualify for a /24 PI with just a single IP address used inside the block.

This, together with the fact that (if I remeber correctly!) there is no longer a minimum usage restriction for becoming an LIR should help to solve this problem?!

I can't fully follow you here. I described the problem, but you seem to interpret this as a solution? Take, for example, DENIC. They are a LIR, and have "their" LIR PA /20 address block (81.91.160.0/20). People "know" that inside 81/8, only /20 or larger sized blocks have been allocated, and might filter out everything more specific than a /20. So using a /24 out of the PA /20 allocation for anycasting might not work reliably "enough" to warrant the effort, due to non-reachability in those networks that have filters set up (this might be debatable, and indeed is the key issue whether an independent address block - and policy - is "necessary" or not). DENIC cannot get another "independent" PA block (because the first one is not at 80% utilization), and a single IP address doesn't qualify for a /24 PI. So they can get neither PA nor PI for this specific purpose. Now *DENIC* has enough /24 PI networks lying around from de.zz times :-), but the idea is to have a generic-enough policy that will permit similar deployments for other "DNS providers" as well. Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 60210 (58081) SpaceNet AG Mail: netmaster@Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 80807 Muenchen Fax : +49-89-32356-299