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/dns-wg@ripe.net/
[dns-wg] Global Vs local node data in www.root-servers.org
- Previous message (by thread): [dns-wg] Global Vs local node data in www.root-servers.org
- Next message (by thread): [dns-wg] Relative response time graph
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
bmanning at vacation.karoshi.com
bmanning at vacation.karoshi.com
Mon Mar 17 16:51:03 CET 2014
On Mon, Mar 17, 2014 at 11:11:40AM -0400, Joe Abley wrote: > > On 17 Mar 2014, at 10:27, manning bill <bmanning at isi.edu> wrote: > > > alas, our service predates Joe’s marvelous text. > > > > “B” provides its services locally to its upstream ISPs. > > We don’t play routing tricks, impose routing policy, or attempt to > > influence prefix announcement. > > In the taxonomy I just shared, that makes the origin nodes of B all "global nodes". > > To clarify though, I certainly wasn't trying to suggest that the things I described were new or original when I was writing in 2003. Anycast had already been in use for quite some time by a variety of people at that time. > > It's specifically the terms "local" and "global" in a DNS anycast context that I was apologising for :-) > > > Joe No apology needed. I was clarifying why "B" is listed as a local node. That it doesn't fit you taxonomy is fine - but it does need an explaination. /bill
- Previous message (by thread): [dns-wg] Global Vs local node data in www.root-servers.org
- Next message (by thread): [dns-wg] Relative response time graph
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]