[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Thread 5: Defining the namespace (was Re: Thread 1:
- Date: Tue, 31 Dec 1996 10:53:09 -0800 (PST)
- From: davidk@ISI.EDU
- Subject: Re: Thread 5: Defining the namespace (was Re: Thread 1:
Hank,
> Hank Nussbacher writes :
>
> I would assume some sort of gTLD charter would have to be written so that
> everyone knows what belongs in each gTLD. But how do you enforce it? What
> is to stop a news agency from wanting to register a .net SLD? Or should we
> ignore that entirely and just hope that everyone opens a SLD in the proper
> place? By using very generic gTLDs like .inet and .iway we eliminate that
> problem. Which is better? I'd like to hear opinions on this matter.
The trick is to use meaningfull names. .SEX is a nice example of such a
name. You can be sure that many people don't want to be associated which
such an gTLD while others do want to be associated with it.
The problem with .COM and .NET was that they are *not* meaningfull so
nobody gets a feeling that they are registering at the wrong place. This
leads to the conclusion that names are preferable short, not a
(relatively unknown) abbreviation and are accepted in many languages as a
known word (again .SEX is a perfect match ..., but also .RADIO). A pure
English word (note: I am not a native English speaker) that can be
assumed to be known and meaningfull for most of the world population
could also be acceptable (example .LAW, .NEWS, .SOFTWARE). Of course
naming is always a compromise. We will never be able to find a name that
suites all, but I am sure that we can find names that most of us
understand.
Also, there is initially no real need to create a lot of new gTLDs that
have a meaning that is quite the same as already existing domain names.
Shared registries already provide for immediate competition. The only
exception is of course a .COM like domain ... Of course, when the system
is working we can decide to add domains with comparable meaning (.LEGAL
or a French/Spanish equivalent word) to broaden the name space and to
give people a second chance when their preferred name is already gone.
Note that it is no problem if domain categories have some (but not total)
overlap, this will again give people more name space to choose an
alternative name.
And then as my last sentence for the opinion polls:
I do like the draft in general. I also do have some problems with
specific parts but I already posted my questions/problems. I am sure that
the IAHC and list members can read and don't need to get a second copy as
some of the Top 3 posters on this mail list think is needed in order to
endorse their own drafts or private interests,
David K.
---