[12384] in Commercialization & Privatization of the Internet

home help back first fref pref prev next nref lref last post

Re: About the creation of new 3-letter domain(s)

daemon@ATHENA.MIT.EDU (Masataka Ohta)
Tue May 17 10:56:12 1994

From: Masataka Ohta <mohta@necom830.cc.titech.ac.jp>
To: dcrocker@mordor.stanford.edu (Dave Crocker)
Date: Tue, 17 May 94 13:19:18 JST
Cc: klensin@infoods.unu.edu, PAUL@tdr.com, PVM@isi.edu, bigz@rice.edu,
        com-priv@psi.com, hostmaster@internic.net, hostmaster@nic.ddn.mil,
        ja@ess.cs.ucl.ac.uk, namedroppers@rs.internic.net, pullen@darpa.mil,
        postel@isi.edu
In-Reply-To: <199405162047.NAA09604@Mordor.Stanford.EDU>; from "Dave Crocker" at May 16, 94 1:47 pm

Dave,

It's me who suggested to use postal or phone code to partition big zones
in bigz mailing list. I still think that 3 or 5 digits are much more human
friendly than 20 or 30 letters of alphabets for geographical domain
names.

People are familiar with their phone numbers and postal codes.

>     > [apt/ste.]number.street.city.region.postal-code.country
>     >
>     reasons that range from privacy to security to local custom and general
> 
> We have a dilemma.

As postal or phone code partitions areas small enough and the partition
tends to evenly divide population, not the size of area, you don't need a
lot more sub domains.

	name.postal-code.country

or

	name.phone-code.country

with first come first served base is practically enough, I think.

Anyway, most of the contries in the world do not have the address structure of

	[apt/ste.]number.street.city.region.postal-code.country

> I.e., for those with particularly extreme privacy concerns, yes we need
> to put in a special mechanism.

For the privacy purpose, registration authority should not check the actual
location of registees. You don't have to register yourself under the
postal-code domain of your real address. That's all.

> My primary point is that we have a global addressing scheme, as defined
> for postal recpients.  I'm suggesting we use it.  I was not really
> believing that my terse representation of it was complete.  (For
> example, real postal codes go in different places depending on
> country.

Some contry have national standard to number various regions, which could
also be useful. But, in general, people are much familiar with their
postal codes or phone codes.

> For our purposes, I'd hope we standardize the format more
> that that, but do assume that things are more elaborate than I
> represented.)

You don't have to investigate all the contries in the world. There
are a lot of variations and how it should be used should be determined
by the person who is delegated 2 letter contry code from IANA.
For your purpose, dividing "US" domain in some US-specific standard
manner is enough.

Otherwise, the result will be quite lengthy and reversed domain name
such as tpc.int.

> Let me emphasize that I am very much NOT suggesting 'turning
> registration over' to the postal system in the sense of creating a new
> registration system.  I am suggesting that we re-use the EXISTING
> registrations.  They're there.  They works.  It can be used with no
> additional assignment activity.

It will be good if we can delegate the management job to post offices
in the future.

							Masataka Ohta

home help back first fref pref prev next nref lref last post