On 3/13/2012 2:49 AM, Kengo Naito wrote:
> Hello Mr.Nishida,
>
> Thank you for your advice.
> Sorry some part of my draft is not ready.
> I'll write the answer below,
>
> (2012/03/12 13:20), Yoshifumi Nishida wrote:
>> Hello Mr. Naito,
>>
>> I believe the draft aims to solve the following issue.
>> If server performs active close, it will enter into TIME_WAIT and keep
>> connection info for 2MSL. if client or NAT picks the same port for a
>> new connection to the server during this 2MSL period, the connection
>> attempt will be rejected. On busy NAT boxes, this will prone to
>> happen.
> Well, this may be a problem, but in my draft I focus on NAT equipment,
> which resource is restricted.
> Problem I state is TIME_WAIT entered into at NAT equipment,
> and it disables new connection.
As it should. Please don't forget that as far as the rest of the network
is concerned, the NAT *is* the endpoint of that TCP connection, and all
of the rules of IP, ICMP, TCP, and host requirements and their updates
apply.
Joe
_______________________________________________
tcpm mailing list
tcpm@...
https://www.ietf.org/mailman/listinfo/tcpm
