[12480] in Commercialization & Privatization of the Internet
Re: About the creation of new 3-letter domain(s)
daemon@ATHENA.MIT.EDU (Masataka Ohta)
Thu May 19 00:31:09 1994
From: Masataka Ohta <mohta@necom830.cc.titech.ac.jp>
To: dcrocker@mordor.stanford.edu (Dave Crocker)
Date: Thu, 19 May 94 12:20:59 JST
Cc: bigz@rice.edu, namedroppers@rs.internic.net, com-priv@psi.com
In-Reply-To: <a9fff81a06021011f39a@[128.102.17.23]>; from "Dave Crocker" at May 18, 94 9:55 am
> >If you have a father named "Dave Crocker" living with you, you, anyway
> >have a name conflict. So, location is no good anyway. To resolve it,
> >use diferent name with first come first served base or register the
> >same name under different place.
>
> As I said in the discussion of the postal address proposal, the goal is to
> create a sub-domain with a small enough granularity so that it will be easy
> to resolve naming conflicts.
In that sense, current "com" with first-come-first-served policy is
still small enough.
> In my view, resolving them within my
> household is easy.
Your father might have dfferent opinion.
> Resolving them in a larger scope gets into various
> administrative and even legal complexities.
If you want to avoid legal complexities with geographical naming
scheme, you must confirm that a new request is really from a person or
company with the name and address in the request, which perhaps means
exchhanging of registered material mails (you can't use e-mail to confirm
geographical identity), which is, IMHO, administrativeely impossible.
The better way is to provide a lot of spaces with not-so-meaningful
names and let requesters choose the ones they prefer.
> >For example, Jon's proposal:
> >
> > <simple-name>.<low>.<high>.PID
> >
> >allows a lot of different places. People can choose thier favourite numbers
>
> All of this whimsy is, of course, great fun. But how will this be
> administered? What will it take to register?
Didn't you read my mail? I wrote:
:So, instead, all the new reqest should be processed by automatic
:mechanisms through e-mail to some address, say "namemaster.<high>.pid".
:Somee authentication is desirable for mails requesting modification.
:
:For the time being, we need 10 or 100 voluntary machines to serve
:as name servers of 1000 zones: <high>.pid. The machines should also
:run automatic registration mechanisms.
So, a person or a company who want a new domain name under <low>.<high>.PID
send (or ask someone else to send) an e-mail to "namemaster@<high>.PID".
If "<high>.PID" is operated outside US with a brain dead patent system,
the requester can add his public key in the request, which will be used
later to authenticate modification request. Otherwise, the namemaster
program may send back pass words to weakly protect future modification
transaction. It may be worthwhile to request registees renew registration
at least once a year to reclaim unused domains.
The e-mail registration form should have rigid syntax containing
information on MX or NS (and glue A's) records. For privacy, it may
be better not to request the real names or addresses of registees.
All requests are accepted automatically as long as it does not
contain syntax error and the requested domain does not exist yet.
All such operation can be done completely automatically without human
intervention.
How a person can find friendly IP connected site to direct MX and NS
is not a problem of "PID" domain.
So, I believe there is no administration problems.
Masataka Ohta
