This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

[dns-wg] New on RIPE Labs: Researching F-root Anycast Placement Using RIPE Atlas

• Previous message (by thread): [dns-wg] New on RIPE Labs: Researching F-root Anycast Placement Using RIPE Atlas
• Next message (by thread): [dns-wg] New on RIPE Labs: Researching F-root Anycast Placement Using RIPE Atlas

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Shane Kerr shane at time-travellers.org
Wed Oct 14 16:28:04 CEST 2015

Randy,

On Wed, 14 Oct 2015 15:20:57 +0200
Randy Bush <randy at psg.com> wrote:

> from a discussion in montréal
> 
> q: why do we anycast dns?
> a: for attack resistance, latency is a secondary effect
> 
> q: what are the majority of queries?
> a: trash
> 
> q: where should we place instances?
> a: near folk who need queries answered.  bzzzt!  no!
> a: near the sources of the rubbish so it can be absorbed quickly

Interesting point. This suggests a better (new?) metric is needed. I'm
not exactly sure what this would be though. :)

Cheers,

--
Shane

• Previous message (by thread): [dns-wg] New on RIPE Labs: Researching F-root Anycast Placement Using RIPE Atlas
• Next message (by thread): [dns-wg] New on RIPE Labs: Researching F-root Anycast Placement Using RIPE Atlas

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ dns-wg Archives ]