<html><head></head><body bgcolor="#FFFFFF"><div>I'm not sure I understand the 'it consumes too much time' argument either.</div><div><br></div><div>After we got dual-stack on a couple of our transit providers early last year, I've been putting in at *most* an hour a month bringing dual-stack through the network. Because it was there at the edge, we could strategically turn it on when replacing routers and firewalls for other reasons, and it's now at the point (as of 3-4 months ago) where we have it on our server and internal IT desktop VLANs. Our public website has been dual-stack for about six months.</div><div><br></div><div>The availability means the applications and other infrastructure teams can start enabling it when commissioning new systems, and it should start to spread much faster. We've identified a few application bugs (and patched one) and a couple of gotchas. None of these have caused major problems; we had to roll back one production change and there was some trouble with some of the desktops, which is why you confine the initial rollout to a non-user VLAN. </div><div><br></div><div>There's been a need for a fair amount of internal advocacy, and (learning from experience here :) early engagement with other technical staff is critical.</div><div><br></div><div>That said - unless you're Google, getting production v6 dual-stack through to a DMZ test VLAN is 20 minutes during a maintenance window for something else, and perhaps a Saturday of testing and prep. And Google's deployed it. </div><div><br></div><div>Telstra (I believe), Amcom, Nextgen can all provide BGPv6 transit. There's no requirement to do the entire network at once. I certainly don't plan on ditching v4 any time soon.</div><div><br>Cheers,<div><br></div><div>Patrick</div></div><div><br>On 20/07/2012, at 6:45 PM, "Joseph Goldman" <<a href="mailto:joe@apcs.com.au">joe@apcs.com.au</a>> wrote:<br><br></div><div><span></span></div><blockquote type="cite"><div>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
I think it's important to remember that we are on this list for
reasonable discussion among professionals, delving into arguments
and sarcasm won't benefit the discussion.<br>
<br>
I also think it's safe to say that IPv6 is possible, but may not be
practical for all. Mostly, such as my case, limitations on resources
to implement such as current hardware and time. As Don was
mentioning, those outfits with limited resources in the interest of
lowering costs as much as possible to stay cut-throat competitive,
IPv6 implementation just isn't high on the list due to the knowledge
it will still take a long time yet before IPv4 is dropped in any
meaningful way.<br>
<br>
/my 2c<br>
<br>
On 20/07/12 8:36 PM, Matthew Moyle-Croft wrote:
<blockquote cite="mid:95EA56A5-E6D6-4B23-B37F-2E764E72D5E6@mmc.com.au" type="cite"><br>
<div>
<div>On 20/07/2012, at 7:03 PM, Don Gould wrote:</div>
<blockquote type="cite">
<div><font class="Apple-style-span" color="#000000"><br>
</font></div>
</blockquote>
<blockquote type="cite">
<div>
<blockquote type="cite">Single stack is a long way off. <br>
</blockquote>
<br>
We've got a single stack now - v4<br>
<br>
It's dual stacking that really seems a long way off.<br>
</div>
</blockquote>
</div>
<br>
<div>Yep. Far away. <a moz-do-not-send="true" href="http://www.worldipv6launch.org/">http://www.worldipv6launch.org/</a></div>
<div><br>
</div>
<div>MMC</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
AusNOG mailing list
<a class="moz-txt-link-abbreviated" href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a>
<a class="moz-txt-link-freetext" href="http://lists.ausnog.net/mailman/listinfo/ausnog">http://lists.ausnog.net/mailman/listinfo/ausnog</a>
</pre>
</blockquote>
<br>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>AusNOG mailing list</span><br><span><a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a></span><br><span><a href="http://lists.ausnog.net/mailman/listinfo/ausnog">http://lists.ausnog.net/mailman/listinfo/ausnog</a></span><br></div></blockquote></body></html>
<table><tr><td bgcolor=#ffffff><font color=#000000><pre>This email, together with any attachments, is intended for the
addressee only. It may contain confidential or privileged information.
If you are not the intended recipient of this email, please notify
the sender, delete the email and attachments from your system and
destroy any copies you may have taken of the email and its attachments.
Duplication or further distribution by hardcopy, by electronic means
or verbally is not permitted without permission.</pre></font></td></tr></table>