Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!ncar!woods
From: woods@ncar.ucar.edu (Greg Woods)
Newsgroups: news.software.b
Subject: Re: Solution to news dup site names
Message-ID: <616@ncar.ucar.edu>
Date: 22 Aug 88 23:53:09 GMT
References: <1445@datapg.MN.ORG> <20246@tut.cis.ohio-state.edu> <1474@datapg.MN.ORG>
Reply-To: woods@handies.UCAR.EDU (Greg Woods)
Distribution: na
Organization: Scientific Computing Division/NCAR, Boulder CO
Lines: 25

In article <1474@datapg.MN.ORG> sewilco@datapg.MN.ORG (Scot E Wilcoxon) writes:
>In article <20246@tut.cis.ohio-state.edu> karl@triceratops.cis.ohio-state.edu (Karl Kleinpaste) writes:
>>Why not just have fully-qualified domain names in the Path: header?
>
>To keep the Path: header from becoming inconveniently long.

  I decided to get the best of both worlds, and have fully-qualified names
from our internal hosts, but just make sure our gateway host (ncar) is
unique so I don't have to fully qualify it too. Thus, a path like
the one in Karl's posting will, if it comes from us, have our domain
name in it only once. The second is redundant. Including it once is, however,
necessary. It is simply not possible to keep all our names unique. For 
example, you might see:

Path: ...!ncar!groucho.ucar.edu!poster
From: poster@groucho.ucar.edu

In this case I have to qualify "groucho" because AT&T already has a registered
uucp host named "groucho", and this way they are distinguishable. In other
cases there are name conflicts with other UUCP hosts and our internal ones,
and in some cases there aren't, but I don't have to keep track of that.
Only the gateway name has to be unique. So, it is NOT necessary to qualify 
"ncar" because that name belongs to us in the UUCP maps. So you WON'T see 
"...!ncar.ucar.edu!groucho.ucar.edu!poster", nor should you have to.

--Greg