Re: [dns-privacy] Possible use case: Opportunistic encryption for recursive to authoritative

Ask Bjørn Hansen <ask@develooper.com> Sat, 08 August 2020 21:54 UTC

From: Ask Bjørn Hansen <ask@develooper.com>
Message-Id: <9856A472-1148-429A-844E-D561A1C808EB@develooper.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4BC4039D-9571-4866-A800-2D7C98192224"
Mime-Version: 1.0
Date: Sat, 08 Aug 2020 14:54:29 -0700
In-Reply-To: <17f6e4fd-e545-267f-f29e-01d5fb57d017@innovationslab.net>
Cc: dns-privacy@ietf.org
To: Brian Haberman <brian@innovationslab.net>
References: <3BA75997-3DE4-4DF5-B1F5-C57DBC423288@icann.org> <17f6e4fd-e545-267f-f29e-01d5fb57d017@innovationslab.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/SBhjYvOKDeysiRVAVIUSxcCcQiw>
Subject: Re: [dns-privacy] Possible use case: Opportunistic encryption for recursive to authoritative
Precedence: list

> On Aug 8, 2020, at 11:57 AM, Brian Haberman <brian@innovationslab.net> wrote:
> 
> Does anyone have numbers on how many authoritative servers use anycast
> for load balancing?

I don’t have data (and haven’t looked into it recently), but I think it’s a very safe assumption that

- most of the authoritative servers don’t use anycast
- most authoritative queries (for an average resolver) go to servers that use anycast

Ask

p.s. If you meant “for load balancing” to narrow which anycast deployments you are counting then it’s impossible to figure out unless you talk to each operator to find out what their motivations to use anycast were — performance, load balancing, resiliency, …

[dns-privacy] Possible use case: Opportunistic en… Paul Hoffman
Re: [dns-privacy] Possible use case: Opportunisti… Ben Schwartz
Re: [dns-privacy] [Ext] Possible use case: Opport… Paul Hoffman
Re: [dns-privacy] Possible use case: Opportunisti… John R. Levine
Re: [dns-privacy] Possible use case: Opportunisti… Tim Wicinski
Re: [dns-privacy] Possible use case: Opportunisti… Puneet Sood
Re: [dns-privacy] Possible use case: Opportunisti… Rob Sayre
Re: [dns-privacy] Possible use case: Opportunisti… Puneet Sood
Re: [dns-privacy] Possible use case: Opportunisti… Rob Sayre
Re: [dns-privacy] Possible use case: Opportunisti… Manu Bretelle
Re: [dns-privacy] Possible use case: Opportunisti… John Levine
Re: [dns-privacy] Possible use case: Opportunisti… Rob Sayre
Re: [dns-privacy] Possible use case: Opportunisti… Paul Wouters
Re: [dns-privacy] Possible use case: Opportunisti… Brian Haberman
Re: [dns-privacy] Possible use case: Opportunisti… Ask Bjørn Hansen
Re: [dns-privacy] Possible use case: Opportunisti… Paul Ebersman
Re: [dns-privacy] [Ext] Possible use case: Opport… Paul Hoffman
Re: [dns-privacy] Possible use case: Opportunisti… Peter van Dijk
Re: [dns-privacy] Possible use case: Opportunisti… Peter van Dijk
Re: [dns-privacy] [Ext] Possible use case: Opport… Brian Haberman
Re: [dns-privacy] Possible use case: Opportunisti… Tony Finch
Re: [dns-privacy] Possible use case: Opportunisti… Paul Wouters
[dns-privacy] TLSA for secure resolver-auth trans… Peter van Dijk
Re: [dns-privacy] Possible use case: Opportunisti… Vladimír Čunát
Re: [dns-privacy] [Ext] Possible use case: Opport… Paul Hoffman
Re: [dns-privacy] TLSA for secure resolver-auth t… Ilari Liusvaara
Re: [dns-privacy] TLSA for secure resolver-auth t… Paul Wouters
Re: [dns-privacy] [Ext] TLSA for secure resolver-… Paul Hoffman
Re: [dns-privacy] TLSA for secure resolver-auth t… Vladimír Čunát
Re: [dns-privacy] TLSA for secure resolver-auth t… Paul Wouters
Re: [dns-privacy] Possible use case: Opportunisti… Viktor Dukhovni
Re: [dns-privacy] TLSA for secure resolver-auth t… Peter van Dijk