ietf
[Top] [All Lists]

Re: IS THERE A CONTACT LIST OF ROOT SERVER OPERATORS - was Re: anyone remember when the root servers were hi-jacked? (fwd)

2002-11-03 21:26:14
A list of who operates each server, as well as their geographical location
can be found at:
http://root-servers.org/


Quoting from a statement by ICANN:

     "In addition, each root name server operator has contact information
(in hard copy) for all other operators, thus should an issue be detected,
the root name server operators can get in contact with each other (assuming
the telephone system is operational). "

The entire statement can be found at:
http://www.icann.org/committees/dns-root/y2k-statement.htm
although it deals with an unrelated topic, the relevant portion can be found
in the administration section.

I also came across a powerpoint presentation by Paul Vixie and a few others
which states:

    "each root name server operator has contact information (digitally
secured and hardcopy) for all other operators"

The entire version (in HTML courtesy of googles cache) can be found at:
http://216.239.53.100/search?q=cache:MU55Q5m9DggC:www.wwtld.org/~wwtld/lives
cribe/JunMurai2.ppt+root+server+operator+contact+information&hl=en&ie=UTF-8

I believe the only people able to provide a list are the operators
themselves and ICANN.  Is anybody certain of this?

-Daniel Pelstring


----- Original Message -----
From: "Joe Baptista" <baptista(_at_)dot-god(_dot_)com>
To: "Daniel Pelstring" <culsu(_at_)CULSU(_dot_)NET>
Cc: <ietf(_at_)ietf(_dot_)org>
Sent: Sunday, November 03, 2002 9:49 PM
Subject: IS THERE A CONTACT LIST OF ROOT SERVER OPERATORS - was Re: anyone
remember when the root servers were hi-jacked? (fwd)



Does anyone know of such a list?

Cheers
Joe Baptista

--
Planet Communications & Computing Facility
a division of The dot.GOD Registry, Limited

On Sun, 3 Nov 2002, Daniel Pelstring wrote:

Since NSI has gone rogue and, many would argue that ICANN has too, I
wish he
was around to run another "test".  Is anybody able to do this again?

-Daniel Pelstring

----- Original Message -----
From: "Dave Crocker" <dave(_at_)tribalwise(_dot_)com>
To: <owner-ietf(_at_)ietf(_dot_)org>; "Michael Froomkin - U.Miami School of 
Law"
<froomkin(_at_)law(_dot_)miami(_dot_)edu>
Cc: <lordb(_at_)nomad(_dot_)tallship(_dot_)net>; <ietf(_at_)ietf(_dot_)org>
Sent: Thursday, October 31, 2002 10:25 PM
Subject: Re: anyone remember when the root servers were hi-jacked? (fwd)


Michael,


Thursday, October 31, 2002, 6:28:08 PM, you wrote:
Michael>
http://www.law.miami.edu/~froomkin/articles/icann-body.htm#B170
Michael> tells the story as best I could reconstruct it.  There are
footnotes to
Michael> the documents I could find.

Notice that Professor Froomkin's "To his detractors" text does not
attempt any balance by offering any other explanation.

As even Prof. Froomkin notes, things were fragile back then. That
included concern over the possibility that NSI would go rogue. NSI
controlled the master root. The one that all others took their data
from. Jon needed to test the ability to switch to a different master
DNS root, to make sure that there were ways to "route around" this
concern over NSI.

That's all the test was.  Jon was clear about the need for this, weeks
before the test.  All anyone needed to do was ask him, rather than
engage in unfounded, inflammatory speculation.

The other point that folks keep forgetting is that Jon had been
issuing operation directives for the root servers since the inception
of the DNS.  How can one "take over" something that one has been
responsible for over its entire existence?

All of the storm and fury has been from people who have had nothing to
do with the running of the DNS, but instead have focused strictly on
the politics of it. (In fact, it was quite interesting to see that a
year of federal inter-agency task force meetings -- including
Magaziner's participation -- took place with most participants having
almost no understanding of DNS technical basics. We had to arrange a
tutorial for them.)

d/
--
 Dave Crocker  <mailto:dave(_at_)tribalwise(_dot_)com>
 TribalWise <http://www.tribalwise.com>
 t +1.408.246.8253; f +1.408.850.1850