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

"Hancock, Robert" <robert.hancock@roke.co.uk> Fri, 12 May 2006 11:08 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FeVVV-00056v-IJ; Fri, 12 May 2006 07:08:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FeVVU-00056q-6o for nsis@ietf.org; Fri, 12 May 2006 07:08:28 -0400
Received: from rsys002x.roke.co.uk ([193.118.201.109]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FeVVS-0004IC-Ok for nsis@ietf.org; Fri, 12 May 2006 07:08:28 -0400
Received: from rsys005a.comm.ad.roke.co.uk (rsys005a [193.118.193.85]) by rsys002x.roke.co.uk (8.13.1/8.13.1) with ESMTP id k4CB84Xq013491; Fri, 12 May 2006 12:08:09 +0100
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 12:08:03 +0100
Message-ID: <A632AD91CF90F24A87C42F6B96ADE5C57EBF37@rsys005a.comm.ad.roke.co.uk>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [NSIS] NATFW NSLP support for NAT-PT (IPv4 to IPv6 translation)
Thread-Index: AcZ0/R9KppEDtV9UQXiu7o2RN6V3NgAtHIJgAABP8PA=
From: "Hancock, Robert" <robert.hancock@roke.co.uk>
To: john.loughney@nokia.com, stiemerling@netlab.nec.de, nsis@ietf.org
X-MailScanner-roke.co.uk: Found to be clean
X-MailScanner-roke.co.uk-SpamCheck:
X-MailScanner-From: robert.hancock@roke.co.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
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

hi,

i think this is a question of what is the current deployment. 

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.

if NAT-PT is not currently seriously deployed, then we can
probably forget about it.

r.

> -----Original Message-----
> From: john.loughney@nokia.com [mailto:john.loughney@nokia.com] 
> Sent: 12 May 2006 11:49
> To: stiemerling@netlab.nec.de; nsis@ietf.org
> Subject: RE: [NSIS] NATFW NSLP support for NAT-PT (IPv4 to 
> IPv6 translation)
> 
> 
> 
> >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
> 

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