Path: utzoo!attcan!uunet!ncrlnk!ncr-sd!hp-sdd!hplabs!pyramid!comdesign!pst
From: pst@comdesign.cdi.com (Paul Traina)
Newsgroups: comp.mail.uucp
Subject: .US domain map entries incorrect
Keywords: .US domain, map
Message-ID: <537@comdesign.CDI.COM>
Date: 5 Oct 88 18:12:19 GMT
Sender: news@comdesign.CDI.COM
Lines: 39

I have a feeling that the recent article on how to apply for a .US domain
incorrectly specifies how the usenet map entry should be written.

In the article, Geoff stated that a map entry should look like this...

#N	.fernwood.mpk.ca.us, fernwood
#...blah blah blah
fernwood =	fernwood.mpk.ca.us
fernwood	.fernwood.mpk.ca.us
fernwood	foobar(DIRECT), mcvax(LOCAL), uunet(DEAD), .....

I take exception to the "fernwood	.fernwood.mpk.ca.us" line.

This implies that fernwood is a gateway to all machines under the
.fernwood.mpk.ca.us domain.  However, there is no such domain.  The
.US domain creators (in a move which I disagree with) decided that there
shall be only one host registered to one "quasi-domain".  (I use quasi-domain
because 'fernwood.mpk.ca.us' is not a domain, it is a _host_ in the '.mpk.ca.us'
domain.

Otherwise, we could theoretically start making 'jim.fernwood.mpk.ca.us' and
'fred.fernwood.mpk.ca.us' ...etc.

The 'evil line' :-) is just adding more crap into an alread crowded paths
file, and it is implying something (that for any other domain would be ok)
which is bogus (that it is a gateway into a domain).

Spaf (if you're out there?) and the rest of the map handlers should consider
removing these lines from the maps files.  (Isn't sed wonderful?)

						Paul

p.s. btw, this isn't a flame, just an observation (half-smile)
     do whatever you want to do,  just don't hold it against me :-)

------
Paul Traina				To believe that what is true for
{uunet|pyramid}!comdesign!pst		you in your private heart is true
pst@condor.cdi.com			for all men, that is genius.