<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
We've had a 6to4 gateway for quite a few years now.
<div><br>
</div>
<div>However, we offer dual stack optin for customers so it doesn't see much traffic!</div>
<div><br>
</div>
<div>Broken 6to4 is the major cause of issues with v6 connectivity. Reality is that no v6 is better than 6to4 or terredo most of the time.</div>
<div><br>
</div>
<div>(Have a look at Lorenzo's presentation at the Google IPv6 implementors conference last year - <span class="Apple-style-span" style="font-family: Arial, Helvetica, 'Nimbus Sans L', sans-serif; font-size: 13px; line-height: 15px; -webkit-text-size-adjust: none; "> <a href="http://bit.ly/laqHji">http://bit.ly/laqHji</a>
)</span></div>
<div><br>
</div>
<div>MMC</div>
<div><br>
<div>
<div>On 08/06/2011, at 10:01 AM, Mark Andrews wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div><br>
And to help alleviate 6to4 problems caused by the extra traffic how<br>
many Australian ISP's have turned on 6to4 relay routers? Even if<br>
you can't deliver IPv6 directly to your customers almost all<br>
Australian ISP's should be capable of bringing up 6to4 relay routers<br>
and de-encapulating the traffic.<br>
<br>
You are helping your own customers if you do this. You don't<br>
have to let the anycast prefix leave your IGP.<br>
<br>
Note you don't have to do this on your usual routers if you are<br>
worried about it taking cpu. Just send the traffic to dedicated<br>
boxes.<br>
<br>
<span class="Apple-tab-span" style="white-space:pre"></span> World<br>
<span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"></span>|<br>
<span class="Apple-tab-span" style="white-space:pre"></span> Router <-> 6to4 Relay Router (2002::/16, 192.88.99.0/24)<br>
<span class="Apple-tab-span" style="white-space:pre"></span><span class="Apple-tab-span" style="white-space:pre"></span>|<br>
<span class="Apple-tab-span" style="white-space:pre"></span> Customers<br>
<br>
Mark<br>
<br>
In message <<a href="mailto:032C9DD4-60EF-4D27-AE88-B0B6D62DB97D@internode.com.au">032C9DD4-60EF-4D27-AE88-B0B6D62DB97D@internode.com.au</a>>, Matthew Moy<br>
le-Croft writes:<br>
<blockquote type="cite">It's started:<br>
</blockquote>
<blockquote type="cite"><br>
</blockquote>
<blockquote type="cite">dig +short www.facebook.com<<a href="http://www.facebook.com">http://www.facebook.com</a>> aaaa<br>
</blockquote>
<blockquote type="cite">2620::1c00:0:face:b00c:0:2<br>
</blockquote>
<blockquote type="cite"><br>
</blockquote>
<blockquote type="cite">dig +short www.bing.com<<a href="http://www.bing.com">http://www.bing.com</a>> aaaa<br>
</blockquote>
<blockquote type="cite">ipv6.search.ms.com.edgesuite.net.<br>
</blockquote>
<blockquote type="cite">a1877.dscb.akamai.net<<a href="http://a1877.dscb.akamai.net">http://a1877.dscb.akamai.net</a>>.<br>
</blockquote>
<blockquote type="cite">2001:44b8:60:3::9665:6250<br>
</blockquote>
<blockquote type="cite">2001:44b8:60:3::9665:624e<br>
</blockquote>
<blockquote type="cite"><br>
</blockquote>
<blockquote type="cite">dig +short www.google.com<<a href="http://www.google.com">http://www.google.com</a>> aaaa<br>
</blockquote>
<blockquote type="cite">www.l.google.com<<a href="http://www.l.google.com">http://www.l.google.com</a>>.<br>
</blockquote>
<blockquote type="cite">2404:6800:4006:802::1013<br>
</blockquote>
<blockquote type="cite"><br>
</blockquote>
<blockquote type="cite">dig +short www.yahoo.com<<a href="http://www.yahoo.com">http://www.yahoo.com</a>> aaaa<br>
</blockquote>
<blockquote type="cite">fpfd.wa1.b.yahoo.com.<br>
</blockquote>
<blockquote type="cite">2001:4998:f011:1fe::3001<br>
</blockquote>
<blockquote type="cite">2001:4998:f011:1fe::3000<br>
</blockquote>
<blockquote type="cite"><br>
</blockquote>
<blockquote type="cite"><br>
</blockquote>
</div>
</blockquote>
</div>
<div></div>
<br>
</div>
</body>
</html>