<div style="font-family:arial,helvetica,sans-serif;font-size:10pt">On Sun, Dec 2, 2012 at 11:39 PM, Philipp Kern <span dir="ltr"><<a href="mailto:phil@philkern.de" target="_blank">phil@philkern.de</a>></span> wrote:<br>
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">> We will. What you described is called 464XLAT<br>
> <a href="http://tools.ietf.org/html/draft-ietf-v6ops-464xlat-08" target="_blank">http://tools.ietf.org/html/draft-ietf-v6ops-464xlat-08</a>, and the prefix<br>
> discovery is at<br>
> <a href="http://tools.ietf.org/html/draft-ietf-behave-nat64-discovery-heuristic-13" target="_blank">http://tools.ietf.org/html/draft-ietf-behave-nat64-discovery-heuristic-13</a><br>
<br>
</div>does that scale to "everyone" running it on their desktops and laptops? It<br>
seems pretty gateway-focussed to me.<br></blockquote><div><br></div><div>I think scaling properties are the same. In both scenarios, you still have to send every packet to the NAT64, right? Because that's the only node in the network that has an IPv4 address.</div>
</div></div>