LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Parts/Attachments: text/plain (13 lines)
Print Reply
Sender:
The Revised LISTSERV Distribution List <LSTSRV-L@EB0UB011>
Subject:
From:
Nick Gimbrone <NJG@CORNELLA>
Date:
Wed, 26 Nov 86 12:01:08 EST
In-Reply-To:
Message of Wed, 26 Nov 86 08:14:02 EST from <DPL1646@IRISHVM>
Reply-To:
The Revised LISTSERV Distribution List <LSTSRV-L@EB0UB011>
>What about loops in the network?  If someone "beyond" PSUVM sends mail
>to CEARN (for example) it is easily possible that the file would go
>through the BITNET-EARNET link on the way to Europe but that a reply
>would come back through DEARN-GWUVM instead.  If the networking software
>were expecting all files from a node to come a certain direction, all
>such loops would have to be eliminated and routing would have to stay
>static.
I'd think that it should be possible to teach it that some set of nodes
have multiple paths to <reach/be reached by> them. I don't see this as
a major problem (assuming that you know the entire network topology,
which may not be reasonable).
-njg

ATOM RSS1 RSS2