home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!zaphod.mps.ohio-state.edu!rpi!ghost.dsi.unimi.it!univ-lyon1.fr!not-for-mail
- From: Christophe.Wolfhugel@grasp.insa-lyon.fr (Christophe Wolfhugel)
- Newsgroups: comp.mail.uucp
- Subject: Re: Are costs relevant ? (was Re: UUCP map entries)
- Date: 21 Nov 1992 14:22:07 +0100
- Organization: INSA Informatique (Grasp), Lyon, France
- Lines: 31
- Message-ID: <1eld5vINN98h@grasp1.univ-lyon1.fr>
- References: <1dtdonINN58c@grasp1.univ-lyon1.fr> <4001@ecicrl.ocunix.on.ca> <1eaojtINN6a9@grasp1.univ-lyon1.fr> <4013@ecicrl.ocunix.on.ca>
- NNTP-Posting-Host: grasp1.univ-lyon1.fr
-
- clewis@ferret.ocunix.on.ca (Chris Lewis) == "cl>"
-
- wolf>The shortest way from an Internet host to my machine is following the MX
- wolf>routing, but when just one node before a site has digested the maps
- wolf>it generates a folkoric route...
-
- cl> I don't quite understand you here. Are you talking about sites
- cl> rabid-routing *after* your MX forwarder?
-
- No, I have not been clear enough (in fact this issue has already been
- discussed a little bit a while ago):
-
- I have some of my correspondants in the US who are UUCP connected to
- an Internet mail relay host, but they fully process the maps, which
- means for this site, due to the top-level aliases, will directly
- generate a path like:
-
- ...!uunet!mcsun!corton!grasp.insa-lyon.fr!wolf
-
- Whereas the logic would have excpected just ...!uunet!grasp.insa-lyon.fr!wolf
- which would have allowed MX routing on the Internet part of the travel.
- And in this particular case it avoid relays and uses different lines.
-
- This is one of the reasons I'm fully *against* top-level domains aliasing
- why the hell has this been done (map coordinators, you may answer this
- question). I don't remember this has been discussed in this group, or in
- others.
-
- --
- Christophe Wolfhugel | Email: Christophe.Wolfhugel@grasp.insa-lyon.fr
- "Pour le bien-etre de tous, il est interdit de pisser dans le metro."
-