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

I think that the PI /24 block should be assigned only to UDP related 
services as RFC suggests, however, I have yet to see the successful 
implementation of TCP data, state... replication in case one router 
withdraws BGP announcement of the /24 prefix.

IPv4 anycast is a perfect way to distribute load and hopefully with lowest 
latency (not always true) for the following UDP related services:

-syslog
-dns
-ddos mitigation

The PI /24 anycast block should be assigned only when the applicant can 
demonstrate:

at least 5 physically disperse locations (verification done by traceroute 
and checking the hop before the last hop in the traceroute). Traceroute's 
can be performed from open traceroute gateways (over the web etc - there 
are hundreds) or public ISP BGP route servers.

to manage the server you will need a non anycast address(es), however, 
customers may keep this info secret if they do not want it to be public....

all anycast nodes must speak BGP to the upstream and in case the server 
goes down, the BGP router withdraws the BGP anycast /24 route

Ps. If Ripe will allow anycast /24 PI allocation for syslog and ddos, and 
other UDP based services, then expect all free /24 blocks taken in a year 
or less for sure ;)

My $0.02 cents...

Greg
http://www.LinuxAdmin.org