Re: Shared domain correctness/quality considerations (was C

["Rick H. Wesson" <wessorh@ar.com>]

On Nov 23, 10:26am, Marty Modell wrote:
> Subject: Re: Shared domain correctness/quality considerations (was C
> Shared TLDs have in common the same problems that distributed
> replicated databases have in the commercial world.  Fine if they are
> read only, but a bear of a problem if multiple site updates are
> involved.

I think what we have been discussing as far as shared TLDs are conserned,
is a modle where a central repository is maintained by a third party.
All the 'domain allocators' then connect to the central database
and minipulate the database.

> Most resolutions I know of rely on some central rbitartor site to
> carry the official update version which then replicates out to the
> field... barring that they rely on shadow updating.. the update is
> good until it is processed by some central site whcih resolves
> (somehow and how varies and is not relevent) duplications
>
> Registries can perhaps work like state license plate agencies, I will
> sell you the special plate you want, subject to verification of
> availability) or you can have one from my assigned pool.

If you think people will buy random names, then maybe
this would work. Histroy shows us that all the NIC sells are
vanity names. If we were just allocation random strings, one TLD woould
do us fine because there are something like 6 billion billion random
names in each of the iTLDs we have now.


-Rick

-- 
Rick H. Wesson