>> Is it fair to say that DNS would be the prime reason for anycast addresses
>> injected into the global BGP routing table ?

I would -guess- there are more DNS anycast than HTTP anycast nodes. But looking 
at the global table to figure that out is not likely to yield useful results.

> There is also a lot of anycast for HTTP servers. I don't know what its
> relative popularity is compared to DNS.

CDNs use HTTP anycast, such as Cloudflare & Cachefly. Cloudflare alone is 
supposedly 5% of "the web", so a non-trivial amount of HTTP is done on anycast.

In fact, one could argue that any HTTP anycast implementation is a CDN. There 
are companies that use HTTP anycast for their own web properties, for 
performance, to game metrics companies, as a method of redundancy, etc.

-- 
TTFN,
patrick

On Aug 06, 2014, at 09:18 , Tony Finch <[email protected]> wrote:

> Toerless Eckert <[email protected]> wrote:
>> 
>> Is it fair to say that DNS would be the prime reason for anycast addresses
>> injected into the global BGP routing table ?
> 
> There is also a lot of anycast for HTTP servers. I don't know what its
> relative popularity is compared to DNS.
> 
> Another example is 6to4, though it isn't a shining success story.
> 
>> The way i read RFC3258 it sounded as if every individual root server could
>> use its own anycast address across its own set of disperse DNS servers. But
>> i could see no indication that specific anycast addresses where assigned to 
>> be
>> used by root servers run in different organizations.
> 
> Correct. The closest it gets is the fairly liberal co-location done by
> L-root.
> 
> As I understand it, CommunityDNS does a similar thing, and they provide
> secondary service to a number of TLDs.
> http://www.communitydns.eu/pdf/Slave_Server_Spec.pdf
> 
> Tony.
> -- 
> f.anthony.n.finch  <[email protected]>  http://dotat.at/
> Irish Sea: West or southwest, veering northwest for a time, 4 or 5,
> occasionally 6 at first. Slight or moderate. Showers. Moderate or good.

_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to