Path: utzoo!utgpu!watserv1!watmath!att!ucbvax!desktalk.com!rlg
From: rlg@desktalk.com (Richard L. Gralnik)
Newsgroups: comp.protocols.tcp-ip
Subject: (none)
Message-ID: <9102151743.AA15455@desktalk.desktalk.com>
Date: 15 Feb 91 17:43:22 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The Internet
Lines: 26

Anyone care to take a shot at this one ?

In the Host Requirements RFC (Section 4.2.3.8.  Page 103) it says,

	"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' ?

Thanks in advance,

Richard Gralnik
(rlg@desktalk.desktalk.com)