Re: Pseudo "last call" for draft-ietf-ipngwg-ipv6-2260-02.txt

[itojun@iijlab.net]

>>From an enterprise end-user point of view, this approach adds more
>confusion to a solution that already has major concerns.  The number 1
>concern that we have to deal with in this multihoming scheme is the path
>selection by the originating TCP stack through its selection of source and
>destination addresses.

	draft-ietf-ipngwg-ipv6-2260 does not add more confusion, but protects
	you from unreachability of certain prefix in multiple-prefix-assigned-
	to-site style of multihoming.  without draft-ietf-ipngwg-ipv6-2260,
	source address selection problem is a critical task since if you
	pick P::a (from P::a and Q::b) while P::/48 is unreachable, you are
	dead.  with draft-ietf-ipngwg-ipv6-2260, you can pick either P::a or
	Q::b, regardless from the external link status (tunnels will always
	ensure that P::/48 and Q::/48 are reachable, assuming that the upstream
	ISP is reachable).

itojun