From: "Matthew Pounsett" <matt(_at_)conundrum(_dot_)com>
To: "Franck Martin" <franck(_at_)peachymango(_dot_)org>
Cc: "IETF" <ietf(_at_)ietf(_dot_)org>
Sent: Tuesday, January 24, 2017 3:23:34 PM
Subject: Re: IPv4 outage at next IETF in Chicago
On 24 January 2017 at 15:11, Franck Martin <
franck(_at_)peachymango(_dot_)org > wrote:
So to be conservative but at the same time futurist and like it was done a
few
years back, why not create again an IPv4 outage of a few hours where the
above
2 networks would be the only networks available?
Depending on results, this outage could be expanded to a full day at the
following meeting, until the IPv4 network is totally removed from the WiFi?
If you wish to test that your networks are reachable from a v6-only
environment,
there is already a v6-only network you can use to test that. Many of us
require
access to the entire Internet to do our jobs, however.
NAT64 allows you to reach the entire IPv4 network, so you should be able to
continue to do your job. NAT64 is already deployed on many mobiles in the US.
Why moving from dual stack IPv4/IPv6 to IPv6 with NAT64?
It ensures that all the OS and client applications can work in an IPv6 only
environment while still be able to reach legacy systems (aka IPv4).