>How is a typical v6 TCP client at a multihomed site, with address
>prefixes from multiple upstream providers, supposed to choose
>amongst it's local addresses when contacting a remote server?
regardless from how hard you try to pick the "best" address, that
may not be the best one for your peer. i believe
draft-ietf-ipngwg-default-addr-select-01.txt covers your goal enough,
and does the best we can without having global information (like
the whole topology map inbetween).
>One way might be for each host to keep a full routing table with
>link-global nexthop addresses. In which case the typical connect()
>sequence would go something like this:
what is "link-global" nexthop here?
itojun
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
