Re: Shared vs. Exclusive

[Simon Higgs <simon@higgs.com>]

At 10:50 AM +0200 11/21/96, Hank Nussbacher wrote:

> > Is there anyone on this list who supports the idea of exclusive
> > registries who doesn't have money on the line?  Not to imply that
> > financial incentives are amoral, but, if there is anyone out there
> > unencumbered by financial considerations, I'd like to here their reasons
> > for supporting exclusive registries.
>
> I support the idea and have no money on the line.  Reasons:
>
> a) The Shared Top Level Domain Working at Higgs is about a year away from
> completing its draft RFC, having it accepted as an RFC and having
> all the software up and running to have an operational shared TLD.  In
> order to eliminate "exclusive' TLDs, Higgs and crew have to complete
> their work.  In the interim, we need exclusive TLDs.
>
> b) This list as well as others has shown to me at least, that certain
> companies and individuals cannot live in peace and harmony in any sort
> of shared system, let alone a shared TLD.  How long do you think a shared
> TLD would last if it is shared by say 4-5 of the more common posters
> to this forum?  No amount of rules and guidelines would save it.
> Therefore, we need exclusive TLDs.
>

If anyone hasn't seen it yet, I have an existing draft in the internet
drafts archive that redefines the top level domain name environment
that, in the meantime, will hopefully keep everybody happy:

http://ds.internic.net/internet-drafts/draft-higgs-tld-cat-02.txt
ftp://ds.internic.net/internet-drafts/draft-higgs-tld-cat-02.txt

I'm revising it for submission to the IAHC, and it is intended to
replace RFC1591.

There are two parts essentially:

1. The introduction of three classes of TLD. Shared, Specialized, and
   Privately-held. Shared TLDs are exactly that - competing registries sharing
   delegation duties. Specialized TLDs are operated by a single registry for
   operational reasons (such as .INT), where closer supervision of the
   delegation is required. Privately held TLDs are those wholly owned and
   operated by large organizations (.MIL & .GOV).

2. Addressing the trademark issues by creating a pool of TLDs (possibly
   eventually shared) that map to the international trademark schedule of goods
   and services. It's purpose is to reduce naming conflicts by opening up the
   .COM namespace (.COM becomes Cat 42 - Misc.). It WILL NOT eliminate
   conflicts completely. The major flaws are documented. I have yet to find any
   other model that will limit conflicts as well as this model.

Feedback is most welcome, as I'm rewriting it for the Dec 1st
submission deadline. Comments to me ASAP so I can review them in time.

Thanks for your input,


Simon

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