[arin-ppml] The non-deployment of IPv6
trejrco at gmail.com
Tue Dec 15 14:58:20 EST 2009
> -----Original Message-----
> From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On
> Of Owen DeLong
> Realistically, the only way the "transition" is going to happen is to
> them to buy new firewalls that can do NAT64 and let them continue on in
> RFC1918-isolated bliss. And, really, as long as their v4-only internal
> DMZ hosts can talk to the v6 Internet somehow, isn't that good enough for
> You do not need to look behind the curtain, Dorothy.
> There's two different transitions being discussed here, and, we need to be
> more accurate about how we talk about them. I think much of the
> resistance stems from the misuse of the words transition or migration to
> describe the first step. The first step is dual-stacking. Dual-stacking
> should be relatively painless and should not require a great deal of
> application testing, etc. Yes, removal of IPv4 will be painful and take
> The good news is that the first test cases for that will be new hosts
> IPv4 addresses are no longer available with the possibility of using IPv4
> as a fallback to back-stop that issue initially while the native
> IPv6 issues are resolved. Once the IPv6-only new hosts are working fine
> without needing IPv4, then, we can look at removing IPv4 from the
> dual-stack hosts and finally the network infrastructure.
> So, let's focus on getting existing services dual-stacked, then worry
> the next steps.
Transition is a poorly chosen term, perhaps with hindsight that is easier to
say than without.
More information about the ARIN-PPML