Re: WGLC: draft-ietf-nsis-nslp-natfw-16.txt

Hi all,

Regarding NAT traversal, NSIS Mobility Applicability draft also has two
open issues (as shown below). But I am not sure Mobility draft is proper
place to handle these issues. I would like to ask whether these two
issues can be discussed in NATFW draft.

Issue 1:
When MN moves, IP address and routing are changed.  In this case, new
NAT/FW pinhole need to be opened and old one should be torn. When and
how should NSIS tear old pinhole?

(For this issue, some comments were already made that the old pinhole
should be torn by time out, and this prefer to be mentioned in Mobility
draft.)

Issue 2: In mobility scenario, it is possible that MN attaches to
private network. But MN cannot know if the NAT is NSIS aware or not.
Therefore should it be mandatory that MN sets S-flag when it detect
attaching a private network?

cheers,
Takako





On Fri, 23 Nov 2007 13:44:20 +0100
Martin Stiemerling <[email protected]> wrote:

> [writing as WG chair]
> 
> Dear all,
> 
> The authors believe that the NATFW NSLP
> (draft-ietf-nsis-nslp-natfw-16.txt) is ready for WGLC.
> 
> The WGLC starts today and will run until December 14th.
> 
> Please review the draft, and comment if you feel that this draft
> is ready to be sent to the IESG.  A simple mail saying that the
> draft is ready for publication would be great.
> 
> Of course, if you read the draft and find open issues, then please
> send a summary of your issue with the current draft.
> 
> Thanks,
> 
>    John and Martin
> 
> [email protected]
> NEC Laboratories Europe - Network Research Division
> 
> NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road,  
> London W3 6BL | Registered in England 2832014
> 
>