Re: [tcpm] TCP, multiple addresses and soft errors when connecting

[Kacheong Poon <kacheong.poon@sun.com>]

Fernando Gont wrote:

> So why not implement such a "higher-level" connect(), and handle all the 
> relevant issues inside the API?

FYI, SCTP has this same problem.  So sctp_connectx() was added in the
API draft to allow an app to pass in an array of addresses.  How does
the stack handle this is implementation dependent.  One way may be to
have a policy on the priority of addresses to try and when to switch
to another one.  If connectx() is implemented as a general call for
other protocols, a policy for TCP may be that TCP will try another
address if it gets an ICMPv6 message following the suggestion in
draft-ietf-v6ops-v6onbydefault-01.txt,

Check section 8.9 in draft-ietf-tsvwg-sctpsocket-08.txt on
sctp_connectx().


--

						K. Poon.
						kacheong.poon@sun.com