IETF Logo Mail Archive

Re: [DNSOP] Anycast and DNS questions

"William F. Maton Sotomayor" <wmaton@ottix.net> Wed, 06 August 2014 13:01 UTC

Return-Path: <wmaton@ottix.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 395E51B2D25 for <dnsop@ietfa.amsl.com>; Wed, 6 Aug 2014 06:01:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] 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 Cm8JJO7YALYp for <dnsop@ietfa.amsl.com>; Wed, 6 Aug 2014 06:01:03 -0700 (PDT)
Received: from iskra.ottix.net (iskra.ottix.net [IPv6:2001:410:90ff::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B70CC1A0AF6 for <dnsop@ietf.org>; Wed, 6 Aug 2014 06:01:02 -0700 (PDT)
Received: from iskra.ottix.net (localhost [127.0.0.1]) by iskra.ottix.net (8.14.9/8.14.9) with ESMTP id s76D10Ow020841 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <dnsop@ietf.org>; Wed, 6 Aug 2014 09:01:01 -0400
Received: from localhost (wmaton@localhost) by iskra.ottix.net (8.14.9/8.14.6/Submit) with ESMTP id s76D10qu020835 for <dnsop@ietf.org>; Wed, 6 Aug 2014 09:01:00 -0400
Date: Wed, 06 Aug 2014 09:01:00 -0400
From: "William F. Maton Sotomayor" <wmaton@ottix.net>
To: "dnsop@ietf.org" <dnsop@ietf.org>
In-Reply-To: <20140806123205.GG5546@cisco.com>
Message-ID: <alpine.DEB.2.03.1408060857100.19219@iskra.ottix.net>
References: <20140806114759.GF5546@cisco.com> <25907D96-0076-417A-8DB9-41A5A178D479@ianai.net> <20140806123205.GG5546@cisco.com>
User-Agent: Alpine 2.03 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/yy3XWtYqMEQEOt-G46v_Y-aN5wM
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 13:01:14 -0000

On Wed, 6 Aug 2014, Toerless Eckert wrote:

> Is it fair to say that DNS would be the prime reason for anycast addresses
> injected into the global BGP routing table ?  Has anyone tried to stat that ?
> Eg: counting how many global  BGP prefixes are "anycast" due to their properties,
> such as availability at widely disperse nework locations without actual transit
> indication in the AS path attributes (or the like, i am not a BGP expert, i am
> just guessing how they could be recognized).

It may be on the global Internet, but there miight be other uses.

>> Common? Ridiculously so, for at least 20 years.
>> Well known examples?  CDNs, as you already mentioned. E.g. LLNW.
>
> Thanks for the example. Any non-CDN examples  for localized information ?

An early paper:

https://www.usenix.org/legacy/event/lisa03/tech/full_papers/miller/miller_html/

>>> c) Any example in which the DNS servers utilizing a single shared
>>>   IP address (anycast address) are run by different operators ? Any
>>>   documents describing this ? (RFC3258 seems to focus on single operator
>>>   anycast group of DNS servers.
>>
>> How about the root servers?
>

Plus ISC has a tech note:

http://ftp.isc.org/isc/pubs/tn/isc-tn-2003-1.html

There might be something @ DNS-OARC that covers thisin their back catalog 
of presentations.

wfms

v2.29.0 | Report a Bug | By Email | System Status