[address-policy-wg] PI for Not-DNS Anycast.

Hi,

I think Anycast should be just an extra issue for getting a "regular"
PI, and that PI should be not less than /24.

Why not less than /24? Because of less size networks not routed in
global Internet. Of course, we can do policies whatever we want,
thinking about conservation, but people will have to lie to RIPE NCC to
get really useful block (or even got less size block, spend money and
time, and have to drop it because of unable to provide service).

By the way, what is current anycast projects' behavior now? Getting a
"regular" PI? Getting more specific from somebody?

Andy Davidson wrote:
> 
> Hi,
> 
> Can I get the community's thoughts on this, please ..
> 
> I think we have a well defined policy on what to do when someone needs
> some PI in order to run an Anycasted DNS service.  We set out a family
> of requirements based on geographic diversity, for instance, that
> clearly states what should be in place when a request for PI for DNS use
> is made.
> 
> What if a company wants to try to deploy an anycasted production service
> for something which is not DNS ?  It could be a proprietary protocol, or
> something standard like http.  Is the community view that they should
> just deaggregate some of their PA - which I don't like the sound of - or
> apply for PI in the normal way, and pretend anycast isn't necessarily
> involved ?
> 
> Many thanks
> Andy
> 


-- 
WBR,
Max Tulyev (MT6561-RIPE, 2:463/253 at FIDO)