Another +1 from me. And with respect to the alleged mistake made 15 years ago, two facts may help: 1. The transition model was complete - because it was based on vendors and ISPs supporting dual stack globally well *before* IPv4 exhaustion. It's because that didn't happen that we have a bit of a panic now. It didn't happen because short term economic incentives triumphed over enlightened self interest. Fine, lesson learned, let's move on, which the ISPs are now doing. 2. There is, mathematically and logically, no 'backwards compatible' IP with bigger addresses than IPv4. That's because IPv4 doesn't contain any provision for extensible addresses. So please let's not hear complaints that IPvN isn't backwards compatible; it never could have been and never will be, and that is the fault of the IPv4 design. So the issue of interworking between legacy IPv4-only systems and the world of bigger addresses is an unavoidable fact of the physical universe. Which is why BEHAVE is currently doing NAT64. Regards Brian Carpenter On 2010-10-09 06:02, james woodyatt wrote: > everyone-- > > IPv6 may have been born with a developmental disability, but we're not dealing with a corpse yet. The patient is still alive, getting better, and with a bit of love and proper care, might yet grow up to make better and brighter music than IPv4. > > Maybe I'm being overly sentimental and using anthropomorphism inappropriately here, but really folks-- isn't it a bit unseemly to be arguing over how we went so "wrong" with IPv6-- and how we could do ever so much better the *next* time we get to reinvent the Internet if we avoid all the killing mistakes we made in bringing IPv6 up-- while there are, today, more people than ever before taking what are perceived to be enormous risks actually making the v4->v6 transition start to happen? > > > -- > james woodyatt <jhw@xxxxxxxxx> > member of technical staff, communications engineering > > > _______________________________________________ > Ietf mailing list > Ietf@xxxxxxxx > https://www.ietf.org/mailman/listinfo/ietf > _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf