Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utcsri!utegc!rayan
From: rayan@ai.toronto.edu
Newsgroups: ont.uucp
Subject: Re: UUCP Domains
Message-ID: <8702212042.AA04814@ephemeral.ai.toronto.edu>
Date: Sat, 21-Feb-87 15:47:00 EST
Article-I.D.: ephemera.8702212042.AA04814
Posted: Sat Feb 21 15:47:00 1987
Date-Received: Sat, 21-Feb-87 17:43:07 EST
Reply-To: Rayan Zachariassen <rayan>
Followup-To: ont.uucp
Distribution: ont
Organization: University of Toronto, AI group
Lines: 34
Checksum: 02825
Summary: status of .CAN domain

Perhaps I can clarify the current situation w.r.t. use of .CAN a bit...

In article <702@dvlmarv.UUCP> alanm@dvlmarv.UUCP (Alan Matsuoka) writes:
[ that Frank Pronk writes: ]
# > I've chosen to not become part of the USA's name space, and instead use
# > a top-level domain name of .CAN.  For example, in the uucp world, sites
# > here at UBC will soon be known as host.UBC.CAN.  Other sites in
# > Vancouver will likely also become known as host.CAN, or for larger
# > organisations, host.sub-domain.CAN.

[ Aside: .EDU et al are not "the USA's name space", although to some people
  they may appear to be. ]

Frank sent me map entries for UBC hosts and MPR hosts that had .CAN
in them (as in cs.ubc.can e.g.). This presented a problem, since:

There is no .CAN domain currently in existence. There should be one
Real Soon now (a few weeks?).

Advertising such names while the domain isn't real, is not a good thing.

Chances are that the .CAN domain will not accept hosts or simple organizations
for second level domains. Therefore the names chosen a priori may not
be valid anyway in the final scheme of things.

For these reasons I had to comment out references to .CAN in the entries,
before adding them to the map (giving Frank an explanation, and the offer
to list the entries under some other existing domain).

If UUCP site sysadmins have questions or concerns regarding these issues,
feel free to mail me. I shall try to respond or relay as appropriate, as my
time permits.

rayan