jbvb@FTP.COM (James B. Van Bokkelen) (02/20/91)
"When a TCP connection is OPENed passively and a packet
arrives with a completed IP Source Route option (containing
a return route), TCP MUST save the return route and use it
for all segments sent on this connection..."
Ok, fine. But does this mean the passive end of the connection cannot
issue a source route of its own? Note that the preceding paragraph of
the RFC says
"An application MUST be able to specify a source route when
it actively opens a TCP connection, and this MUST take
precedence over a source route received in a datagram."
Where did this received source route come from if the passive end
has to save a received return route (presumably received from the
actively opened end) and 'use it for ALL segments sent on this
connection' ?
At the passive end, the active's source route is known to work (it got the
packet there, after all), and so the incoming source route should override
anything the application specified. If the active end got a response,
their initial route worked, and they should ignore anything that comes
back, in case some really quirky asymmetric routing situation required
that humans intervene on the passive side to make it work...
James B. VanBokkelen 26 Princess St., Wakefield, MA 01880
FTP Software Inc. voice: (617) 246-0900 fax: (617) 246-0901braden@VENERA.ISI.EDU (02/20/91)
At the passive end, the active's source route is known to work (it got the packet there, after all), and so the incoming source route should override anything the application specified. If the active end got a response, their initial route worked, and they should ignore anything that comes back, in case some really quirky asymmetric routing situation required that humans intervene on the passive side to make it work... James B. VanBokkelen 26 Princess St., Wakefield, MA 01880 FTP Software Inc. voice: (617) 246-0900 fax: (617) 246-0901 Thanks, James, as always you said it better than I did! Bob