Xref: utzoo comp.mail.uucp:1620 comp.mail.headers:390 Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!cwjcc!hal!ncoast!allbery From: allbery@ncoast.UUCP (Brandon S. Allbery) Newsgroups: comp.mail.uucp,comp.mail.headers Subject: Re: what do _YOU_ mean by "all routing"?? Message-ID: <12220@ncoast.UUCP> Date: 14 Aug 88 19:08:40 GMT References: <676@bacchus.DEC.COM> <881@vsi1.UUCP>Organization: Cleveland Public Access UN*X, Cleveland, OH Lines: 22 In article , lear@NET.BIO.NET (Eliot Lear) writes: +--------------- | Note: The use of source routing is discouraged. Unless the | sender has special need of path restriction, the choice | of transmission route should be left to the mail tran- | sport service. | | [RFC-822: Section 6.7.2, Page 32] +--------------- Which was great, when the network(s) covered by RFC822 could propagate changes to the routing in an hour or so. With UUCP, the corresponding time can be measured in months in some cases. Quite aside from the fact that RFC822 insists that all sites named in an address be known; many small UUCP sites feel they have no need to register with the NIC. RFC822 is a bit naive. ++Brandon -- Brandon S. Allbery, uunet!marque!ncoast!allbery DELPHI: ALLBERY For comp.sources.misc send mail to ncoast!sources-misc