Chris's Wiki :: blog/sysadmin/WhyNoIPv6Nat Commentshttps://utcc.utoronto.ca/~cks/space/blog/sysadmin/WhyNoIPv6Nat?atomcommentsDWiki2014-09-03T11:20:10ZRecent comments in Chris's Wiki :: blog/sysadmin/WhyNoIPv6Nat.By David Magda on /blog/sysadmin/WhyNoIPv6Nattag:CSpace:blog/sysadmin/WhyNoIPv6Nat:b5007bf8ecff8bd8a2e560f80990206d98226f31David Magdahttp://www.magda.ca/<div class="wikitext"><blockquote><p><em>[…] and on top of that once you have NAT you start needing some sort of traffic tracking system so you can trace externally visible traffic back to its ultimate internal source.</em></p>
</blockquote>
<p>Instead of traditional NAT, one can perhaps use network prefix translation (NPT):</p>
<ul><li><a href="https://en.wikipedia.org/wiki/IPv6_prefix_translation">https://en.wikipedia.org/wiki/IPv6_prefix_translation</a></li>
<li><a href="https://tools.ietf.org/html/rfc6296">https://tools.ietf.org/html/rfc6296</a></li>
<li><a href="https://tools.ietf.org/html/rfc7157">https://tools.ietf.org/html/rfc7157</a> (multi-homing)</li>
</ul>
<p>The interface identifier (last /64) stays the same, and only routing prefix (/48) and subnet ID (/16) are generally fiddled with. NPT is designed to be stateless.</p>
</div>2014-09-03T11:20:10Z