IETF Logo Mail Archive

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

<john.loughney@nokia.com> Fri, 12 May 2006 10:49 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FeVDR-0002pp-9S; Fri, 12 May 2006 06:49:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FeVDQ-0002pk-7y for nsis@ietf.org; Fri, 12 May 2006 06:49:48 -0400
Received: from mgw-ext14.nokia.com ([131.228.20.173]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FeVDN-0003EY-HU for nsis@ietf.org; Fri, 12 May 2006 06:49:48 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145]) by mgw-ext14.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k4CAnceI027117; Fri, 12 May 2006 13:49:42 +0300
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 12 May 2006 13:49:20 +0300
Received: from esebe100.NOE.Nokia.com ([172.21.138.118]) by esebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 12 May 2006 13:49:20 +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: Fri, 12 May 2006 13:49:15 +0300
Message-ID: <615BD9B54CB01B41838C323DB9E91AAB4077BF@esebe100.NOE.Nokia.com>
In-Reply-To: <C095E458-0E69-4F52-8A37-A4866927B20D@netlab.nec.de>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [NSIS] NATFW NSLP support for NAT-PT (IPv4 to IPv6 translation)
Thread-Index: AcZ0/R9KppEDtV9UQXiu7o2RN6V3NgAtHIJg
From: john.loughney@nokia.com
To: stiemerling@netlab.nec.de, nsis@ietf.org
X-OriginalArrivalTime: 12 May 2006 10:49:20.0574 (UTC) FILETIME=[B9564DE0:01C675B1]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc:
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

>The draft -11 of the NATFW NSLP is somewhat unspecified about 
>the usage of the IPv4 to IPv6 (and vice versa) transition 
>mechanism NAT Protocol Translation (NAT-PT, RFC 2766). While 
>in the past the NSLP had some text specifying how the NSLP 
>should handle NAT-PT, it has been removed. One of the reasons 
>is the draft 
>http://www.ietf.org/internet-drafts/draft-ietf-v6ops-natpt-
>to-exprmntl-03.txt
>
>The question is where to go with NAT-PT. Should the NATFW NSLP 
>support NAT-PT or not? Probably, this is requires more a 
>political answer rather than a technical!

Well, I'd say that we don't need to address NAT-PT, unless anyone in
the audience (in the mailing list) is specifically interested in it.

John

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

v2.23.0 | Report a Bug | By Email