From: timk@tdkcs.waterloo.on.ca (Tim Kuehn)
Subject: Re: Domain naming conventions
Organization: TDK Consulting Services
Date: Tue, 5 Jan 1993 03:00:14 GMT

In article <C0CMB4.34p@wimsey.bc.ca> sl@wimsey.bc.ca (Stuart Lynne) writes:
>I'm led to believe (inside sources and all that) that there are 
>suggestions to make addresses like org.municp.prov.ca the norm. Currently
>they are being suggested only for organizations with limited scope of
>operation.s.
>
>If we look at the US domain they use the same convention. But apply it
>uniformly. I.e. they would require IBM.Armonk.NY.US not IBM.US. This is
>probably a better and fairer way to do things. It leads to less debates
>about whether a particular organization is privileged enough to be at 
>a higher level.
>
>I'll go out on the limb and guess that some of the sour grapes over the 
>current convention is that everyone would like to be org.ca, but only a
>few organizations qualify. Leaving those that don't a bit envious. 
>
>The US Domain eliminates this by requiring everyone to use the same 
>notation: org.city.state.US.

In all actuality I'd prefer to follow that naming convention. While Greg 
Woods and Ed Hew correctly pointed out that the organization I'm working 
with would quite easily qualify to register as org.ca or org.org and they
could manage the *.org.[org/ca] domain underneath as they saw fit, it 
doesn't make much sense when the org.munic.prov.ca naming convention is 
already consistent with the naming convention used by a large number of 
other sites/domains.  Going under .ca/.org would also lead to having to 
use contra-convention naming schemes -- such as country.prov.munic.org.org
instead of org.munic.prov.country. 

Now admittedly the client could register under org.* and then cross-
register under org.munic.prov.ca later on, but if, at that time, someone 
else has taken the "org" name for that munic.prov.ca domain, then what?

There is a place for registrations under .ca and .org, particularly for
multi-provincial/national business enterprises, but given the nature and 
type of work my client does, I think they would be much better served as 
org.munic.prov.ca provided they could reserve the "org" name across Canada, 
and not have to go through the application process to impliment a site under 
a given munic.prov.ca domain as org.munic.prov.ca, except where munic.prov.ca 
doesn't previously exist and needs to be created.

Registering under *.org.ca/org could be done later on for certain 
specialized departments of the organization, but I don't see that 
happening for a couple of years now.

>BTW I received a note from Jon Postel (co-author of RFC1886) this morning 
>re: making reservations in .US. He basically said it "is not appropriate". 
>
>>From: postel@ISI.EDU (Jon Postel)
>>In the US domain, a subdomain can either be delegated (NS records) or
>>registered directly (MX or A records), but not both.  It is not appropriate
>>to register simply to reserve a name for future use.

Which is a mistake and going to be a royal pain in the glut-max. Doubtless
there'll be a time when you have a large company wanting to register a name 
that they have over the rest of the states/world in some municipality, but 
some other person has absconded with it before them and holds the name 
ransom for $$$.  Or plain refuses to let it go.

>Stuart Lynne <sl@wimsey.com> ......................... UNIX Facsimile Software

 +-----------+-----------------------------------+---------------------------+
 | Tim Kuehn | TDK Consulting Services           | timk@tdkcs.waterloo.on.ca |
 | <><       | Ask me about news and mail in KW! | (519)-888-0766            |
 +-----------+-----------------------------------+---------------------------+
Newsgroups: can.domain