Re: [icann-eu] Re: [ICANN-EU] Governmental Advisory Committee "invite[d] ICANN

["JIM FLEMING" <jfleming@anet.com>]

----- Original Message -----
From: Jefsey Morfin <jefsey@wanadoo.fr>
To: <icann-europe@fitug.de>
Cc: <icann-europe@fitug.de>
Sent: Saturday, November 18, 2000 7:07 PM
Subject: [icann-eu] Re: [ICANN-EU] Governmental Advisory Committee
"invite[d] ICANN


> At 17:45 12/11/00, JIM FLEMING wrote:
> >"c) Root server system improvements
> >
> >Mr Roberts clarified the role of ICANN in relation to the operation of
the
> >root server system. He noted that ICANN owes an enormous debt of
gratitude
> >to the operators of the root servers. The services provided by the root
> >server operators are voluntary services undertaken in the public
interest.
> >ICANN works with the root server operators, but does not operate the root
> >server system. Against this background, it is inappropriate for ICANN to
> >enter into contracts with the ccTLDs to provide root server system
> >services."
> >
> >@@@@@@@@@@@@@@@@@@@@@@@@@@
>
> Questions:
> 1. how many ccTLD cooperate freely as an operator of a root server?
> 2. where can I find the requirements to operate a root server
> 3. would it not be advisable that ccTLDs cooperate in operating a root
>      servers to achieve a better geographical distribution of the root
servers,
>      increase their number and achieve a better global reliability and
> stability?
> Jefsey
>
>

1. Each TLD has a "cluster of servers" for the TLD. Those are not root
servers.
One might call these TLDCs. (i.e. TLD Clusters)

The classic definition of a "root server" is one of the machines that sits
ABOVE
these TLDCs and tells other servers where to find a TLDC for a given
TLD. The collection of these root servers is referred to as a Root Server
Cluster
(or Confederation) (i.e. an RSC).

2. A true root server, which is generally part of a collection of servers
that
make up an RSC, has an easy task. It simply tells other servers where the
TLDCs are located. Over the years, various people have written documents
describing the requirements for runnung an RSC. In some cases, those
requirements were written to intentionally make it hard for other people to
participate, when companies stepped forward and met (or exceeded) all
of the requirements, then the control freaks that wrote the requirements
went
off to do other things. In summary, they had no intention of writing
requirements
to allow people to participate, they appeared to be shocked when people
MET or EXCEEDED the requirements, sort of like the way the ICANN
Board must have felt with 44 applicants who all could blow away the existing
TLD operators, some of whom operate TLDs with almost no infrastructure.
(ICANN does not check the existing TLDs...only those they want to prevent
from participating)

3. RSCs benefit from having a diverse collection of servers. TLDCs also
benefit from having a diverse collection of servers. Since you use the words
"root servers", one has to assume that you mean an RSC. Assuming that
TLDCs are diverse (which they are not), one could argue that the servers
ABOVE (the RSCs) could be localized into clusters, to help the real working
servers which are the ISPCs (ISP Clusters) which people are directed to
use. Since the ISPCs cache the info from the RSCs and then go directly to
the TLDCs, there may not be a huge pay-off in having a lot of RSCs. The
pay-off comes in not allowing one RSC to control the world's view, as is
the case with the legacy RSC, operated by the U.S. Government.

To summarize....

RSC - Root Server Cluster - Directs ISPCs to the TLDCs
TLDC - TLD Cluster
ISPC - ISP Cluster

...end-users are directed to ISPCs...some ISPCs now work "upwards"
and find the TLDCs without asking an RSC...that is the Floating Root...

Jim Fleming
http://www.unir.com/images/architech.gif
http://www.unir.com/images/address.gif
http://www.unir.com/images/headers.gif
http://www.ntia.doc.gov/ntiahome/domainname/130dftmail/unir.txt
http://msdn.microsoft.com/downloads/sdks/platform/tpipv6/start.asp