NAT64: clarification on RST handling in V6 FIN RCV state
Dmitry Anipko <Dmitry.Anipko <at> microsoft.com>
2012-02-24 00:21:24 GMT
Hello,
RFC 6146, section 3.5.2.2, says that in V6 FIN RCV state *any* packet other than V4 FIN must set the session lifetime to no less than TCP_EST=2hours.
If the V4 target sent RST in response to the translated V6 FIN, what is the reason to keep the NAT mapping alive for TCP_EST instead of TCP_TRANS?
Should the language “if a V4 FIN packet is received,… lifetime is set to TCP_TRANS” be changed to “if a V4 FIN or V4 RST packet is received,… lifetime is set to TCP_TRANS”?
-Dmitry
<div>
<div class="Section1">
<p class="MsoNormal">Hello,<p></p></p>
<p class="MsoNormal"><p> </p></p>
<p class="MsoNormal">RFC 6146, section 3.5.2.2, says that in V6 FIN RCV state *any* packet other than V4 FIN must set the session lifetime to no less than TCP_EST=2hours.
<p></p></p>
<p class="MsoNormal"><p> </p></p>
<p class="MsoNormal">If the V4 target sent RST in response to the translated V6 FIN, what is the reason to keep the NAT mapping alive for TCP_EST instead of TCP_TRANS?<p></p></p>
<p class="MsoNormal"><p> </p></p>
<p class="MsoNormal">Should the language “if a V4 FIN packet is received,… lifetime is set to TCP_TRANS” be changed to “if a V4 FIN or V4 RST packet is received,… lifetime is set to TCP_TRANS”?<p></p></p>
<p class="MsoNormal"><p> </p></p>
<p class="MsoNormal">-Dmitry<p></p></p>
<p class="MsoNormal"><p> </p></p>
<p class="MsoNormal"><p> </p></p>
</div>
</div>