Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!vsi1!lmb From: lmb@vsi1.UUCP (Larry Blair) Newsgroups: comp.mail.uucp Subject: Re: re/routing (was: why you should say "-d ru) Message-ID: <901@vsi1.UUCP> Date: 9 Aug 88 18:07:18 GMT References: <676@bacchus.DEC.COM> <881@vsi1.UUCP><3674@palo-alto.DEC.COM> <891@vsi1.UUCP> Reply-To: lmb@vsi1.UUCP (Larry Blair) Organization: VICOM Systems Inc., San Jose, CA Lines: 49 In article pleasant@porthos.rutgers.edu (Mel Pleasant) writes: >In article <891@vsi1.UUCP> lmb@vsi1.UUCP (Larry Blair) writes: > >> The usual case here is that either foo or baz talks to a machine named bar >> which is NOT advertised in the maps. It has been a clear Usenet policy that >> every site need not advertise every machine they talk to. It has also been >> a clear policy that sites should not list every local machine (heaven help us > >systems to GENERATE PATHS BY. I, as a person who communicates with people >all the time about map entry production, do *not* say in an unqualified way >that internal links should not be listed in a map entry. My answers to >questions pertaining to what should appear in a map entry is consistent with >this point of view. > >The UUCP Mapping Project would love to see all unqualified (without domain) >names _appear_ in the map files. By the same token, I would also like to >see the files become smaller. I encourage this by saying, "get yourself a >domain and USE SMAIL or some home grown equivalent." Along with this, make >sure all of your internal nodes generate fully qualified hostnames for >themselves. If you do have an unqualified name that escapes into the >`network' at large via mail or news headers, that name *should* (verging on >`must') appear in a map entry someplace. It's nice to see that both Mel and Bill, the targets of our recent abuse, have finally gotten into the fray. If I understand what you are saying here, you are saying that all sites must either: a) hide their local systems; b) register the names of their local systems (with _unique_ names); or c) use domain-type names. Since you are using a Sun, you find it pretty easy do either a or c. Others do not have such an easy time of it. On top of that, you are saying, "If you want to mail to a site machine that isn't registered, don't let it route through rutgers". Well, that's been the point of this discussion. Reiterating my main point: when I say rutgers!foo!baz I'm not saying rutgers!baz.uucp. You are entitled to do what ever you want to send it to foo; you might even be justified in rerouting it to baz.uucp IF I had said baz.uucp, but all I've told you about is foo. It is foo's job to send it to their baz, which may or may not be baz.uucp. What I'm still not sure of is why you reroute. What benefit does rerouting provide to rutgers? Passive pouting (as Paul Vixie has called it) would serve completely for your smart-host function. Rerouting can only make a working route break. -- * * O Larry Blair ames-----\ * * O VICOM Systems Inc. pyramid---\ * * O 2520 Junction Ave. uunet!ubvax!vsi1!lmb * * O San Jose, CA 95134 sun-------/ * * O +1-408-432-8660 +1-800-538-3905