On Wed, Dec 2, 2009 at 12:33 AM, Simon Perreault <[email protected]> wrote: > Sri Gundavelli wrote, on 2009-12-01 11:13: >> 1.) IPv6 App communicating with an IPv6 App >> 2.) IPv4 App communicating with an IPv4 App >> 3.) IPv6 App communicating with a legacy IPv4 App >> 4.) IPv4 legacy App communicating with a future IPv6 App > > I haven't fully followed the discussion up to this point, but here goes... > > New "IPv6 apps" are usually not IPv6-only. They are version-independent. See > e.g. RFC4038. So your future app will try IPv4 if it cannot get IPv6 > connectivity. Which, it seems to me, would make case 4 fold into case 2.
Hi Simon, I checked 4038 and found it is informational. And I do not think applications developers will indeed follow this. For example, RFC4294 defines IPsec as a MUST for IPv6 node, but from our equipment test, we found this is a myth. Thanks, Zhen _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
