So, time for some real action?

[Dick Visser]

http://www.internetsociety.org/deploy360/blog/2013/12/campaign-turn-off-ipv4-on-6-june-2014-for-one-day/


​I fully support this idea. But I'm in doubt what to actually do on 6 June.
There isn't much benefit in turning off IPv4 on client devices in our
office, because we already have a good idea what will work and what won't.
Turning off IPv4 on all internet facing services would be better, because
it will point out any IPv6 connectivity problems that visitors have.
In that case, I can go about this in several ways.
Doing it through (low TTL + removal of A records) gives you less control
over things.
If you block IPv4 access at the service level (filtering/ACLs), then it's
easier to restore things.

Maybe some intermediate solution, such as serving up an explanation page to
IPv4 users?

Other ideas?



-- 
Dick Visser
System & Networking Engineer
TERENA Secretariat
Singel 468 D, 1017 AW Amsterdam
The Netherlands
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.cluenet.de/pipermail/ipv6-ops/attachments/20140206/307807d4/attachment.html