Path: utzoo!mnetor!uunet!husc6!bloom-beacon!gatech!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.uucp Subject: Re: Duplicate site names Message-ID: <7905@g.ms.uky.edu> Date: 21 Dec 87 21:15:01 GMT References: <271@ontenv.UUCP> Reply-To: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Organization: U of Kentucky, Mathematical Sciences Lines: 33 Keywords: pathalias maps duplicates In article <271@ontenv.UUCP> norm@ontenv.UUCP (Norman Soley) writes: >I noticed a new site posting for "mickey". > ... Shouldn't someone at uunet be checking the maps before they >connect a new site? Any other site could be excused but much of the >net counts on uunet as an authoritative source for routing. No, no, NO .. don't count on uunet as authoritative routing machine ... Rick has publicly stated that if everyone on the world starts treating uunet as they'd treated seismo, then he'd turn off auto routing features in his configuration. And, I suppose, take other measures that come to mind as needed. I'm one of the map makers (for Kentucky) ... to my knowledge the only tools we have for checking the map are things like grep and uuhosts. We do have some policies about this subject. For instance, a pre-existing entry using a particular name will keep any other entries from being made in the map. If a site lists a link to some place that doesn't have a map entry, we call it a ghost site and that name is "held" to be used by the linked-to-site, along with a small protocol to be used when someone wants to make a map entry with the same name as a ghost site. We're also supposed to urge the ghost site to send in an entry. We, of course, can't do much about how uunet runs itself. But it does seem like a good idea for the uunet people to check things like this when connecting a new site. -- <---- David Herron -- The E-Mail guy <---- or: {rutgers,uunet,cbosgd}!ukma!david, david@UKMA.BITNET <---- <---- Winter health warning: Remember, don't eat the yellow snow!