> > That said, what actually bothers me is the classic chicken-and-egg > > problem. Application writers are reluctant to add IPv6 support > > because they know that there is little to none of IPv6 infrastructure > > (read: ISPs supporting IPv6) out there. ISPs, on the other hand, > > are reluctant to do IPv6 business because they know that there are > > few to none of IPv6-ready applications out there. Two-way secret > > crush. I guess what we need to focus on is how to become a messenger > > of love. =) > > This analysis is flawed. App developers have little influence over > deployment and so do ISPs. The market (read, consumer and enterprises) > decides if a protocol is successful.
The Teredo design is predicated on the idea that we can ship IPv6 as a software upgrade on the PC. The update can be enabled as part of an application development. That is actually quite powerful, and does break the chicken-and-egg problem. -- Christian Huitema -------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
