Xref: utzoo comp.mail.uucp:2351 comp.mail.misc:1401 Path: utzoo!utgpu!watmath!clyde!att!ulysses!gamma!sword!faline!bellcore!rutgers!mailrus!husc6!purdue!decwrl!vixie From: vixie@bacchus.pa.dec.com (vixie) Newsgroups: comp.mail.uucp,comp.mail.misc Subject: Re: Another example why not to re-route Message-ID: Date: 26 Nov 88 09:49:13 GMT References: <140@minya.UUCP> Sender: vixie@decwrl.dec.com Organization: DEC Western Research Lab Lines: 37 In-reply-to: jc@minya.UUCP's message of 24 Nov 88 14:57:37 GMT Another victim of the active rerouters. Sigh. You have my sympathy, but it seems that the decision has been made and since no facts were taken into account originally, I don't see that announcing more facts now is going to change anything. People reroute because they want to, and it seems to give them endless pleasure to see other folks complain about it. There's an ambiguity in your article; I'd like to resolve it: # Note that I'm not objecting to routing, just rerouting. That is, if I # submit some mail to foo@bar.dom.ain, I expect that mailers will figure # out a route for me. But if I send mail to x.uucp!y.bitnet!bar!foo, I # prefer that the mailers deliver it along exactly that route, or bounce # it back to me. I feel that x.uucp is justified in trying to find a route to y.bitnet, but that if y.bitnet (really: the "next hop") is not reachable via routing, the message should be returned. Under no circumstances should a site peek ahead (to "bar", in this example). Well, maybe as matt@oddjob suggests, one could peek ahead to fully qualified domains. But even that I'd tend to argue against (anybody want to? I doubt it...). This is the distinction between "routing" and "rerouting" -- no peeking. One more thing: could you tell me who those neighbors were? The ones that rerouted and sent the fixit request back toward you? I am building a list of rerouters that those who care about such things will be able to mark as "dead" when they build their paths database. The rerouting sites themselves seem largely to want to remain undiscovered, though one of them finally did send me a list of sites. Anyway, anyone who runs or knows of a site who peeks, please send me mail so that my paths database can avoid it. -- Paul Vixie Work: vixie@decwrl.dec.com decwrl!vixie +1 415 853 6600 Play: paul@vixie.sf.ca.us vixie!paul +1 415 864 7013