Hi Greg,
I would say IPv4 anycast /24 PI must be allocated for anycasting DNS service only. You simply can't add more nameservers if you hit the max limit...
That is an incorrect assumption no matter how you look at it. To me, the biggest problem seems to be that people either doesn't know better or actually don't want to know better regarding this topic. I have probably written this before, and some people have probably answered, but: You can add as many anycast nameservers as you want without any prefix at all. They obviously have to be in the same asn/ip-network if you want to anycast without using your own prefix in dfz. You can also use other similar techniques than ancyast, for example network load balancing. The NS limit in a response is what, 13 entries? If you need more than 13 nameservers spread around 13 different networks, and they are all anycasted for each network, then you really need to start thinking about running some other nameserver software because it is obviously not designed to scale anyway. If you actually have 13 NS entries and 10 anycast servers per entry, you should be able to handle more than 7 billion requests per second with cheap hardware. DDoS is not a problem with decent hardware. With 7 billion requests per second I am sure you can afford it. j -----Original Message----- From: address-policy-wg-admin@ripe.net [mailto:address-policy-wg-admin@ripe.net] On Behalf Of Greg L. Sent: 8. august 2007 21:39 To: Gert Doering Cc: address-policy-wg@ripe.net Subject: Re: [address-policy-wg] PI for Not-DNS Anycast. I would say IPv4 anycast /24 PI must be allocated for anycasting DNS service only. You simply can't add more nameservers if you hit the max limit... The rules for IPv6 anycast allocations must be not that strict in the future... why? The address space will be more than enough, the router HW will be more powerful to handle large routing tables ... Sincerely, Greg L.
On Tue, Aug 07, 2007 at 08:36:06PM -0700, Greg L. wrote:
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 ;)
So what's your message? Do you support handing out /24 PI for "these" applications, or do you oppose it, due to address space / routing table slots usage?
Your e-mail was a bit unclear in that respect...
Gert Doering -- APWG chair -- Total number of prefixes smaller than registry allocations: 113403
SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279