Jason Livingood wrote:
> This thread seems to have died out.
As I already summarized, the problem is that:
> The problem is lack of support of TCP/IP for hosts with multiple
> addresses.
> Its scope is not limited to IPv6 nor HTTP but TCP/IP in general.
> A host with two IPv4 addresses also suffers, when one of its
> addresses is sometimes unreachable from its peer.
and the short and long term approaches to the solution are: that
> The solution can be properly constructed not at the connectionless
> IP layer but at the lowest layer above IP to support connection,
> which means TCP needs a major revision. Or, you can say SCTP,
> though it may also need a major revision to be really usable
> against the problem.
and that
> When almost all hosts have single IPv4 addresses (and single IPv6
> addresses), the most practical tentative solution is not to deploy
> IPv6.
> Long term solutions need drastic changes on treatment of multihomed
> ISPs and address allocation policies, which also excludes, with
> RFC2374 obsoleted, IPv6.
That's all.
Masataka Ohta
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
