<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br><br>Sent from my iPhone</div><div><br>On Feb 27, 2013, at 7:30 PM, Lorenzo Colitti <<a href="mailto:lorenzo@google.com">lorenzo@google.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">On Thu, Feb 28, 2013 at 5:30 AM, Christopher Palmer <span dir="ltr"><<a href="mailto:Christopher.Palmer@microsoft.com" target="_blank">Christopher.Palmer@microsoft.com</a>></span> wrote:<br><div class="gmail_extra">
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">2.<span style="font-size:7pt;font-family:'Times New Roman'">
</span></span><u></u><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">The majority of home users don’t have routers that support UPnP management of NAT/FW openings, at least from our telemetry.</span></p>
</div></div></blockquote><div><br></div><div style="">Amen. </div></div></div></div>
</div></blockquote><br><div>In the routers I've seen, it is off by default. But I'm not sure what this has to do with 6to4, since last I knew UPnP didn't support opening arbitrary IP protocol types. Or did it get extended?</div></body></html>