RE: [NSIS] NATFW NSLP support for NAT-PT (IPv4 to IPv6 translation)

<john.loughney@nokia.com> Sat, 13 May 2006 07:23 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FeoTZ-00084o-0h; Sat, 13 May 2006 03:23:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FeoTX-00084j-Tw for nsis@ietf.org; Sat, 13 May 2006 03:23:43 -0400
Received: from mgw-ext13.nokia.com ([131.228.20.172]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FeoTW-0001MU-FV for nsis@ietf.org; Sat, 13 May 2006 03:23:43 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-ext13.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k4D7NeEA001755; Sat, 13 May 2006 10:23:41 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 13 May 2006 10:23:40 +0300
Received: from esebe100.NOE.Nokia.com ([172.21.138.118]) by esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 13 May 2006 10:23:40 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] NATFW NSLP support for NAT-PT (IPv4 to IPv6 translation)
Date: Sat, 13 May 2006 10:23:39 +0300
Message-ID: <615BD9B54CB01B41838C323DB9E91AAB4077CE@esebe100.NOE.Nokia.com>
In-Reply-To: <4464B11B.8090609@uni-tuebingen.de>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [NSIS] NATFW NSLP support for NAT-PT (IPv4 to IPv6 translation)
Thread-Index: AcZ13Z/JPof6kXrLTRaRTmNAWmrL4QAgD1kw
From: john.loughney@nokia.com
To: ali.fessi@uni-tuebingen.de, robert.hancock@roke.co.uk
X-OriginalArrivalTime: 13 May 2006 07:23:40.0184 (UTC) FILETIME=[284DF980:01C6765E]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: stiemerling@netlab.nec.de, nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=subscribe>
Errors-To: nsis-bounces@ietf.org

Ali,

>aren't NAT-PTs deployed to connect 3G PS domains to the Internet?

NAT-PTs have been discussed as a way to connected 3G IMS deployments to
internet SIP deployments, but in practice, I don't know if anything has
been deployed.  

But this is more of a question to the list - does anyone see any major
NAT-PT
deployments, and would the NATFW NSLP be something do consider in this
type of deployment?

John

>> if NAT-PT is currently seriously deployed to any extent, we have to 
>> deal with it. however, dealing with it may simply mean detecting and 
>> returning an error condition.
>
>that would be one option. The other option is that the NATFW 
>signaling can be scoped at the NAT-PT, which acts as NR.
>NATFW NSLP does already support this with the proxy mode.


_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis