From: lawrence@combdyn.com (Lawrence Chen)
Subject: Re: Domain naming conventions
Organization: Combustion Dynamics Ltd.
Date: Mon, 4 Jan 1993 19:17:42 GMT

In article <1993Jan2.195509.27735@tdkcs.waterloo.on.ca> timk@tdkcs.waterloo.on.ca (Tim Kuehn) writes:
>In article <C082x8.GCt@wimsey.bc.ca> sl@wimsey.bc.ca (Stuart Lynne) writes:
>>Anyone interested in domain name topics should probably look at the new
>>RFC-1386 titled "The US Domain" by A. Cooper and J. Postel. 
>>The current approach to use of the US domain is similiar to what the CA-domain
>>committee is moving too. Assigning names based on political geography. It is
>>implemented a bit differently and possibly a bit more consistently. For example
>>it does not appear to allow ibm.us but would require ibm.armonk.ny.us. 
>
>This is an interesting question, since I have a client that presently
>has no email-prescence on the net, but will hopefully be getting in 
>sometime soon. I'll address this in a seperate message though.
>
Several months ago, I hooked this company into the wide world of networking.

I was drawing on my experiences in setting up a domain for the area UNIX
usersgroup.

As you can see we ended up in the .COM domain....since they wanted to be up
and running as fast as possible...and it was taking too long to get going
in .CA.

>>CA guidelines allow xxx.ca, xxx.prov.ca or xxx.municp.prov.ca depending on
>>the size and scope of your business/organization etc.
>
>>My personal opinion is that this approach leads to domain names that are
>>too long. Which leads to problems with use due to being incorrectly 
>>transcribed.
>
>I'd rather have a domain name that's a little verbose and longer than 
>cryptic and shorter since such names are *much* easier to remember. People 
>already remember much longer names for snail-mail postal addresses, so 
>remembering email address domains, particularly ones based on easily- 
>deduced naming rules based on geography are much easier to deal with.
>
>"Problems due to transcription errors" is a smoke screen since any such 
>errors will be caught the first time a message is sent to an ill-transcribed
>address when it bounces.
>

I prefer short and easy to remember.  Our users group is known as UUMH.

So, our domain name is .uumh.ab.ca....even though the mh stands for Medicine
Hat, we have membership outside of Medicine Hat so all was okay.....

The company on the other hand....(at the time was only in Medicine Hat) so
following the guidelines that came with the application-form....

We came up with a domain name of .CombDynLtd.MedicineHat.AB.CA, along the
way we needed to exchange mail with DRES...and I had to try to tell the
person what our email address was going to be.  I told him that my address
was 'lawrence@combdyn.CombDynLtd.MedicineHat.AB.CA'....now its just
'lawrence@combdyn.com'.  I wonder which is easier to tell people, remember,
and type? 8-)

-- 
 --EMAIL-----------------------------PHONE-----------FAX------------
 | WORK: lawrence@combdyn.com      | (403)529-2162 | (403)529-2516 |
 | HOME: dreamer@lhaven.uumh.ab.ca | (403)526-6019 | (403)529-5102 |
 -------------------------------------------------------------------
  disclamer = (working_for && !representing) + (Combustion Dynamics Ltd.);
Newsgroups: can.domain