<div dir="ltr">This is a really good list, thanks for sharing. I just gave a talk on this topic this week, this is timely. For operational reality, the implementation phase is highly dependent on the environment. For an environment that has full control of systems to peerings, the overhead will be less than an environment that has less control on end points or has a fractured internal structure. <div><br></div><div>The point of the protocols being ships in the night is very important and is often forgotten, keeping that in mind is key as is minimizing the method of users disabling IPv6 to fix issues. I often recommend someone on the deployment team setting up an IPv6 only station and using it to see what does and does not function, both internally and externally. A VM works well for this but I find that an actual workstation makes me actually use it more. This does a few things, but most importantly it makes it obvious what doesn't work on v6, which will be at least 50% of your initial roll out troubleshooting. </div><div><br></div><div>Keep good metrics and monitoring on *both* IPv4 and IPv6, this helps both up front and over time. Anything that is measured and monitored in v4 should also by measured and monitored for v6 in my opinion. Make sure your security policy is as close to v4 as you can reasonably get it (but be mindful of ICMP) .his includes all packet captures, filters, ACLs and security appliance provided services. </div><div><br></div><div>nb</div><div> </div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><font face="arial, helvetica, sans-serif"><span style="color:rgb(0,0,0);text-align:-webkit-auto">---</span><br style="color:rgb(0,0,0);text-align:-webkit-auto"><span style="color:rgb(0,0,0);text-align:-webkit-auto">Nick Buraglio</span><span style="color:rgb(0,0,0);text-align:-webkit-auto;white-space:pre"> </span><span style="color:rgb(0,0,0);text-align:-webkit-auto;white-space:pre"> </span><span style="color:rgb(0,0,0);text-align:-webkit-auto;white-space:pre"> </span><span style="color:rgb(0,0,0);text-align:-webkit-auto;white-space:pre"> </span><span style="color:rgb(0,0,0);text-align:-webkit-auto;white-space:pre"> </span><span style="color:rgb(0,0,0);text-align:-webkit-auto;white-space:pre"> </span><span style="color:rgb(0,0,0);text-align:-webkit-auto;white-space:pre"> </span><span style="color:rgb(0,0,0);text-align:-webkit-auto;white-space:pre"> </span><br style="color:rgb(0,0,0);text-align:-webkit-auto"><span style="color:rgb(0,0,0);text-align:-webkit-auto">ESnet Network Engineering Group (AS293) </span><br style="color:rgb(0,0,0);text-align:-webkit-auto"><span style="color:rgb(0,0,0);text-align:-webkit-auto">Lawrence Berkeley National Laboratory</span><br style="color:rgb(0,0,0);text-align:-webkit-auto"><a href="mailto:buraglio@es.net" style="text-align:-webkit-auto" target="_blank">buraglio@es.net</a><span style="color:rgb(0,0,0);text-align:-webkit-auto"> </span><br style="color:rgb(0,0,0);text-align:-webkit-auto"><span style="color:rgb(0,0,0);text-align:-webkit-auto">+1 (510) 995-6068</span></font><br></div></div></div>
<br><div class="gmail_quote">On Thu, Mar 26, 2015 at 6:33 AM, John Mann <span dir="ltr"><<a href="mailto:john.mann@monash.edu" target="_blank">john.mann@monash.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div><div><div>Deployment work overload could be 5%.</div></div><div><br></div><div>For deployment of dual stack, you should minimise work overload by:</div><div>- taking advantage of normal refresh cycles and bundle enabling of dual stack into the refresh or deployment of new management systems, procedures, and services</div><div>- picking "low hanging fruit" tasks that will advance deployment with minimum effort</div><div> (some legacy systems may never be capable of or required to be accessed over IPv6 - leave them).</div><div><div>- don't provide some IPv6 network or service that doesn't have similar performance and reliability as IPv4 has; wait until you can<br></div></div><div>- taking things slowly to allow time for staff to mentally adjust to dual-stack as being normal,<br></div><div> and to keep IPv6 issues from being on the critical path</div><div><br></div><div>For run phase, I think it really depends upon what type of IT issues you normally see:</div><div>- something used to work over network and now it doesn't == need to check IPv6 as well as IPv4.<br></div><div><div>- database management, or PC malware == no IPv6 involvement</div></div><div>- IPv4 address space micromanagement == easy as IPv6 /64 subnet is never too small<br></div><div><br></div><div>Run-time recommendations:</div><div>- make sure setup *and* changes to firewall / ACL rules permit/deny equivalently for IPv4 and IPv6</div><div>- promptly investigate any network problems that could be blamed on IPv6 to avoid users advising each other </div><div> "just turn off IPv6 to fix things", and then never turning it back on again.<br></div><div><br></div><div>Thanks,</div><div> John</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div> </div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 26 March 2015 at 20:04, BERENGUER Christophe <span dir="ltr"><<a href="mailto:Christophe.BERENGUER@solucom.fr" target="_blank">Christophe.BERENGUER@solucom.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div style="font-size:12pt;color:#000000;background-color:#ffffff;font-family:Calibri,Arial,Helvetica,sans-serif">
<p style="margin-top:0px;margin-bottom:0px">Hello everybody,</p>
<p style="margin-top:0px;margin-bottom:0px"><br>
</p>
<p style="margin-top:0px;margin-bottom:0px">I work for a consulting firm.</p>
<p style="margin-top:0px;margin-bottom:0px"><br>
</p>
<p style="margin-top:0px;margin-bottom:0px">For a client, I would like to estimate the work overload for IT operations team to deploy IPv6 dual stack and for day to day operations.<br>
</p>
<p style="margin-top:0px;margin-bottom:0px"><br>
</p>
<p style="margin-top:0px;margin-bottom:0px">On the internet, I have found an estimation around 20% of work overload for the run phase. But if you have operational feedback it would be the best!</p>
<p style="margin-top:0px;margin-bottom:0px"><br>
</p>
<p style="margin-top:0px;margin-bottom:0px">Thanks in advance for your answers,</p>
<p style="margin-top:0px;margin-bottom:0px">Have a nice day.<br>
</p>
<p style="margin-top:0px;margin-bottom:0px"><br>
</p>
<p style="margin-top:0px;margin-bottom:0px">Best regards,<br>
</p>
<p style="margin-top:0px;margin-bottom:0px"><br>
</p>
<div>
<div name="divtagdefaultwrapper">
<span lang="fr">
<div style="margin:0 0 12pt 0"><font face="Arial,sans-serif"><span style="font-size:10pt"><font color="navy"><span style="font-size:8.5pt"><b>Christophe BERENGUER</b></span></font><font color="navy"><span style="font-size:8.5pt"><b><br>
</b></span></font><font color="#5F5F5F"><span style="font-size:8.5pt">Consultant</span></font><font color="#5F5F5F"><span style="font-size:8.5pt"><br>
Fixe : <a href="tel:%2B33%20%280%291%2049%2003%2085%2086" value="+33149038586" target="_blank">+33 (0)1 49 03 85 86</a></span></font><font color="#5F5F5F"><span style="font-size:8.5pt"><br>
</span></font><a href="mailto:christophe.berenguer@solucom.fr" target="_blank"><font><span style="font-size:8.5pt">christophe.berenguer@solucom.fr</span></font></a><font color="#5F5F5F"><span style="font-size:8.5pt"><br>
</span></font><font color="navy">solucom</font><font color="navy"><br>
</font><font color="#5F5F5F"><span style="font-size:8.5pt">Tour Franklin : 100 - 101 terrasse Boieldieu
</span></font><font color="#5F5F5F"><span style="font-size:8.5pt"><br>
92042 Paris La Défense Cedex</span></font><font color="#5F5F5F"><span style="font-size:8.5pt"><br>
</span></font></span></font></div>
</span></div>
</div>
</div>
</div>
</blockquote></div><br></div>
</blockquote></div><br></div>