|
»
« Return to Thread: Re: New Version Notification for draft-naito-nat-resource-optimizing-extension-00.txt
Re: New Version Notification for draft-naito-nat-resource-optim
by Yoshifumi Nishida-2
::
Rate this Message:
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.
I think there are 3 entities in this draft: TCP client, TCP server and
NAT. I think it would be better to articulate which entity your
proposals are aiming.
I think the section 2.1 describes the behavior of NAT. This seems to
be a bit out of scope for tcpm.
The section 2.2 seems to describe the behavior of tcp server, although
the section title seems to indicate updating the behavior of NAT.
In addition, in order to make this work properly, I think client, NAT
and server will need to support rfc6191. But, the deployment of this
approach looks difficult. The authors might need to describe the case
where this approach doesn't work.
Also, can we use the approach described in the section 4.2.2.13 of
rfc1122 instead of rfc6191?
Thanks,
--
Yoshifumi Nishida
On Mon, Mar 5, 2012 at 4:59 PM, Kengo Naito <naito.kengo@...> wrote:
> Pasi,
> tcpm members,
>
> Hi, I wrote a new draft written below.
>
> https://datatracker.ietf.org/doc/draft-naito-nat-resource-optimizing-extension/?include_text=1
>
> I've already asked Pasi for adding this discussion to Agenda, Paris.
> There's some topic I want to add to my draft, which I'll do so by Paris.
> (which I wrote like "I'll write this part by Paris" in 00 version)
>
> I would appreciate your comments and advice.
>
> Best regards,
>
>
> (2012/03/05 21:50), internet-drafts@... wrote:
>>
>> A new version of I-D, draft-naito-nat-resource-optimizing-extension-00.txt
>> has been successfully submitted by Kengo and posted to the IETF repository.
>>
>> Filename: draft-naito-nat-resource-optimizing-extension
>> Revision: 00
>> Title: NAT resource optimizing extension
>> Creation date: 2012-03-05
>> WG ID: Individual Submission
>> Number of pages: 4
>>
>> Abstract:
>> When NAT is used in address resource restricted environment, or when
>> a lot of users are located under a NAT device, IP address and port
>> resources may be eaten up, and it brings severe bad effects on user
>> experiences. This situation can be greatly mitigated by tweaking
>> mapping behavior and session timer handling at NAT function. This
>> document proposes to NAT IP address and port resource optimizing
>> extension for address resource restricted environment. One extension
>> is to enable simultaneous use of a port for different transport
>> sessions, and the other is to make use of TCP timestamp for TIME_WAIT
>> Assassination.
>>
>>
>>
>>
>> The IETF Secretariat
>>
>>
>
>
> --
> ----------------------------------------
> NTT Service Integration Laboratories
> Kengo Naito
> E-Mail: naito.kengo@...
> TEL: +81 422-59-4949
> ----------------------------------------
>
>
> _______________________________________________
> tcpm mailing list
> tcpm@...
> https://www.ietf.org/mailman/listinfo/tcpm_______________________________________________
tcpm mailing list
tcpm@...
https://www.ietf.org/mailman/listinfo/tcpm
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.
I think there are 3 entities in this draft: TCP client, TCP server and
NAT. I think it would be better to articulate which entity your
proposals are aiming.
I think the section 2.1 describes the behavior of NAT. This seems to
be a bit out of scope for tcpm.
The section 2.2 seems to describe the behavior of tcp server, although
the section title seems to indicate updating the behavior of NAT.
In addition, in order to make this work properly, I think client, NAT
and server will need to support rfc6191. But, the deployment of this
approach looks difficult. The authors might need to describe the case
where this approach doesn't work.
Also, can we use the approach described in the section 4.2.2.13 of
rfc1122 instead of rfc6191?
Thanks,
--
Yoshifumi Nishida
On Mon, Mar 5, 2012 at 4:59 PM, Kengo Naito <naito.kengo@...> wrote:
> Pasi,
> tcpm members,
>
> Hi, I wrote a new draft written below.
>
> https://datatracker.ietf.org/doc/draft-naito-nat-resource-optimizing-extension/?include_text=1
>
> I've already asked Pasi for adding this discussion to Agenda, Paris.
> There's some topic I want to add to my draft, which I'll do so by Paris.
> (which I wrote like "I'll write this part by Paris" in 00 version)
>
> I would appreciate your comments and advice.
>
> Best regards,
>
>
> (2012/03/05 21:50), internet-drafts@... wrote:
>>
>> A new version of I-D, draft-naito-nat-resource-optimizing-extension-00.txt
>> has been successfully submitted by Kengo and posted to the IETF repository.
>>
>> Filename: draft-naito-nat-resource-optimizing-extension
>> Revision: 00
>> Title: NAT resource optimizing extension
>> Creation date: 2012-03-05
>> WG ID: Individual Submission
>> Number of pages: 4
>>
>> Abstract:
>> When NAT is used in address resource restricted environment, or when
>> a lot of users are located under a NAT device, IP address and port
>> resources may be eaten up, and it brings severe bad effects on user
>> experiences. This situation can be greatly mitigated by tweaking
>> mapping behavior and session timer handling at NAT function. This
>> document proposes to NAT IP address and port resource optimizing
>> extension for address resource restricted environment. One extension
>> is to enable simultaneous use of a port for different transport
>> sessions, and the other is to make use of TCP timestamp for TIME_WAIT
>> Assassination.
>>
>>
>>
>>
>> The IETF Secretariat
>>
>>
>
>
> --
> ----------------------------------------
> NTT Service Integration Laboratories
> Kengo Naito
> E-Mail: naito.kengo@...
> TEL: +81 422-59-4949
> ----------------------------------------
>
>
> _______________________________________________
> tcpm mailing list
> tcpm@...
> https://www.ietf.org/mailman/listinfo/tcpm
tcpm mailing list
tcpm@...
https://www.ietf.org/mailman/listinfo/tcpm
« Return to Thread: Re: New Version Notification for draft-naito-nat-resource-optimizing-extension-00.txt
| Free embeddable forum powered by Nabble | Forum Help |
