Re: What is a shared registry?

[Simon Higgs <simon@higgs.com>]

At 9:46 AM -0500 11/22/96, Vince Wolodkin wrote:

> We all seem to view shared registries just a little bit differently so I
> though I might try and put into words how I see them, and would invite
> others to do the same:
>
> I see the shared registry system as encompassing all domains.  If a
> registry were granted license to share in one TLD it should be very
> simple for them to become permitted for all domains.  I see in the
> future a host of registries that are able to register customers in any
> domain (including .com, but maybe not ISO domains).
>

First we need to put the horse before the cart. The registry serves the
TLD, not the other way around. The TLD only exists if there is
justification for it. It is not appropriate for all TLDs to be shared.
Consequently, I've proposed three TLD classes in draft-higgs-tld-cat
(the following is current and not exactly the same as what is in the
internet draft archive):

   3.4 TLD Classes

   Top level domains can be divided into three groups. There are those
   which are Shared (non-exclusive), and which can be served by multiple
   competing registries. There are those that may need to be served by a
   single, registry that has the necessary expertize to address specific
   industry issues, and there are a very small number of TLDs which
   are required to serve single large organizations.

      3.4.1. Shared TLD Class

      The Shared TLD Class contains TLD's in which all second level
      domain name registrations are performed by multiple competing
      registries. Unless specifically documented otherwise in the TLD's
      charter, it is expected that all newly delegated TLDs will be in
      this class. Existing TLDs may be delegated by IANA into this class
      as well.

      3.4.2. Specialized TLD Class

      The Specialized TLD Class describes TLDs that are industry-
      specific, or where a high-level of domain name control is needed.
      These TLD's are operated by a single registry. Registration is
      only open to organizations within the specific areas defined in
      the TLDs charter. These TLD's could represent specific industries,
      other closely defined market niches, or top level country domains.
      A registry must be able to constructively address industry
      specific issues in the context of running a TLD registry.

      An example of an existing TLD in this class is .INT which is
      closely controlled and is only open to International Treaty
      Organizations. Registry duties for .INT are handled by the ITU in
      accordance with a policy authorized by IANA.

      3.4.3. Private TLD

      In certain rare instances, it may be possible for a qualifying
      internationally known organization to be identified on the
      Internet by it's own exclusive TLD. All second and third level
      domain name registrations are performed within the organization.
      The organization is the sole trustee of the TLD, and all disputes
      arising from domain name delegation are the organizations
      responsibility.

      An example of an existing TLD in this class is .MIL., which is
      exclusively operated by, and for, the United States military.


Now, if the registries are applied to this model, some will be sharing
TLDs with others, some will have sole operation of a TLD, and some will
run their own TLD as a private entity. This eliminates the problems of
whether a TLD is shared/non-shared, because each TLD is chartered and
identified right from it's creation. The only thing left is to create a
policy for the registries to follow to delegate TLDs within the shared
TLD class.




Simon

--
It may be that your sole purpose in life is simply to serve as a
warning to others.