2013 - the year of the NAT. (the only way a single stacked address family is going to be able to talk to a single stacked member of a different address family... and unless we start agressive reuse of v4, this will happen sooner than later (dual-stack is rate limited to the smaller of the address families -UNLESS- NAT makes reuse possible... :)
But since NAT is going to be required -anyway-.... 2013 will be the year of the NAT. /bill On Tue, Nov 27, 2012 at 06:32:27AM +0100, Mikael Abrahamsson wrote: > On Tue, 27 Nov 2012, Dobbins, Roland wrote: > > >Yet everyone (except you) insist that it does work with everything, and > >that all this CGN and 444 stuff and 644 stuff isn't necessary, and that > >I'm a fool for doubting all these (to me) wildly overoptimistic > >assertions about the coming ubiquity of native IPv6, end-to-end, heh. > > Dual stack works with "everything". IPv6 only access does not (with > 464XLAT it might). However, people are complaining that operators are > focusing more on CGN and NAT44(4) than they are on IPv6. Which I can > understand, but I believe we're getting closer to getting out of the dead > lock. My hope is that 2013 is going to be the year we're going to see > widespread IPv6 (dual stack) adoption on mobile devices outside of the US. > It's looking good so far. > > People are advocating dual stack now (at least that's what I do), for a > future goal of IPv6 only. > > The main problem with IPv6 only is that most app developers (most > programmers totally) do not really have access to this, so no testing is > being done. > > -- > Mikael Abrahamsson email: [email protected]
