Re: [DNSOP] Anycast and DNS questions

"Patrick W. Gilmore" <patrick@ianai.net> Wed, 06 August 2014 14:53 UTC

Return-Path: <patrick@ianai.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E900C1B2D69 for <dnsop@ietfa.amsl.com>; Wed, 6 Aug 2014 07:53:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 431bGZ3fiYOe for <dnsop@ietfa.amsl.com>; Wed, 6 Aug 2014 07:53:57 -0700 (PDT)
Received: from ianai.priori.net (bos2.priori.net [140.186.190.105]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EE931B2D55 for <dnsop@ietf.org>; Wed, 6 Aug 2014 07:53:47 -0700 (PDT)
Received: from [10.128.24.37] (inet-perimeter-nat.bos.markleygroup.com [208.118.225.28]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: patrick) by ianai.priori.net (Postfix) with ESMTPSA id 3CC0864594; Wed, 6 Aug 2014 10:54:59 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: "Patrick W. Gilmore" <patrick@ianai.net>
In-Reply-To: <alpine.LSU.2.00.1408061409540.13901@hermes-1.csi.cam.ac.uk>
Date: Wed, 06 Aug 2014 10:53:46 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <348AC130-BD20-4CC2-9740-109C2A4E8BEF@ianai.net>
References: <20140806114759.GF5546@cisco.com> <25907D96-0076-417A-8DB9-41A5A178D479@ianai.net> <20140806123205.GG5546@cisco.com> <alpine.LSU.2.00.1408061409540.13901@hermes-1.csi.cam.ac.uk>
To: "dnsop@ietf.org" <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/kd7pEUiWUISZ5NVebWKz0n-eIUE
Subject: Re: [DNSOP] Anycast and DNS questions
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Aug 2014 14:54:00 -0000

>> 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 <dot@dotat.at> wrote:

> Toerless Eckert <eckert@cisco.com> 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  <dot@dotat.at>  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.