Le 29 juil. 2011 à 18:21, Michel Py a écrit : >> Rémi Després wrote: >> - 6to4 delivers native IPv6 prefixes to customer sites, which 6to4 doesn't. > > That is playing with words. In that case, any router that delivers native > IPv6 to the hosts (by having the tunnel software on the router, not on the > hosts) can be called a native solution. > > This is just flat out WRONG. ANY solution that needs IPv4 to transport IPv6 > is NOT native IPv6, and regardless of who states it and their great > contributions, it will remain the same. > > Some please stop calling things what they are not; a native IPv6 solution is > one that works when IPv4 has been removed, anything else is called a > transition mechanism.
We have, it seems, a different understanding of the situation. The distinction to be made, and which I make, is between - native addresses vs well-known-prefix addresses (the former start with an ISP allocated prefix, the latter, e.g. those of 6to4 and Teredo, have a routing problem in the Internet backbone) - native IPv6 routing (IPv6-only or dual stack) vs IPv4-only routing 6rd is designed to offer native IPv6 prefixes across IPv4-only routing domains. Regards, RD _______________________________________________ Ietf mailing list [email protected] https://www.ietf.org/mailman/listinfo/ietf
