IETF Logo Mail Archive

Re: [BEHAVE] draft-ietf-behave-nat64-discovery-heuristic in PCP-enabled networks?

<teemu.savolainen@nokia.com> Fri, 07 September 2012 07:12 UTC

Return-Path: <teemu.savolainen@nokia.com>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 915A121E809A for <behave@ietfa.amsl.com>; Fri, 7 Sep 2012 00:12:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tla-vLoM7z-a for <behave@ietfa.amsl.com>; Fri, 7 Sep 2012 00:12:16 -0700 (PDT)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by ietfa.amsl.com (Postfix) with ESMTP id B454021E808A for <behave@ietf.org>; Fri, 7 Sep 2012 00:12:15 -0700 (PDT)
Received: from vaebh104.NOE.Nokia.com (vaebh104.europe.nokia.com [10.160.244.30]) by mgw-da02.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q877BSiN008606; Fri, 7 Sep 2012 10:12:14 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.47]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Fri, 7 Sep 2012 10:11:52 +0300
Received: from 008-AM1MPN1-053.mgdnok.nokia.com ([169.254.3.232]) by 008-AM1MMR1-013.mgdnok.nokia.com ([2002:4136:1e2f::4136:1e2f]) with mapi id 14.02.0309.003; Fri, 7 Sep 2012 09:11:51 +0200
From: teemu.savolainen@nokia.com
To: mohamed.boucadair@orange.com, behave@ietf.org
Thread-Topic: draft-ietf-behave-nat64-discovery-heuristic in PCP-enabled networks?
Thread-Index: Ac2MxAyc7zD6FB63TBeiX8PaDuv0LgAAxlPw
Date: Fri, 07 Sep 2012 07:11:50 +0000
Message-ID: <916CE6CF87173740BC8A2CE4430969620444AB9D@008-AM1MPN1-053.mgdnok.nokia.com>
References: <94C682931C08B048B7A8645303FDC9F36E57B08679@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36E57B08679@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-tituslabs-classifications-30: TLPropertyRoot=Nokia; Confidentiality=Nokia Internal Use Only; Project=None;
x-titus-version: 3.3.8.1
x-headerinfofordlp: None
x-tituslabs-classificationhash-30: VgNFIFU9Hx+/nZJb9Kg7InqTkps8u7XkfvsMuD5807G9+xWipz3rWFJnQsKpRE+L3W8bHr1x7LA/8ESXCHSfn3v1moTxuezKv1AQB2ThX1Yzp0GVWXa3sMiZ2oj+qK5Y/UxWhXBIuHJUOi/5bR1xd1zAT9Yefe3OYLrsgrfetE8kkLEj5fGOjObd/4xH4lB701bj0/DRw+mn7IBRBa33Q2sFPHLRQrPH90hnlTldSO2zixuidHMrZsmOdR3xOVl8Pxf87MietZdmflzp5wQISeHXlxPluSra0mZ9vNe7Jr0=
x-originating-ip: [10.163.19.180]
Content-Type: multipart/alternative; boundary="_000_916CE6CF87173740BC8A2CE4430969620444AB9D008AM1MPN1053mg_"
MIME-Version: 1.0
X-OriginalArrivalTime: 07 Sep 2012 07:11:52.0422 (UTC) FILETIME=[0E42D060:01CD8CC8]
X-Nokia-AV: Clean
Subject: Re: [BEHAVE] draft-ietf-behave-nat64-discovery-heuristic in PCP-enabled networks?
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Sep 2012 07:12:16 -0000

Hi Med, All,



It is justified, because the heuristic approach was specifically developed to allow discovery of Pref64::/n when the network does not explicitly provide the information (by any means that are generally available). Even if PCP would provide this information, there is no telling what kind of deployment PCP will see and especially will there always be PCP when there is NAT64.



Furthermore, will the PCP *always* tell the Pref64::/n, or is that also PCP deployment specific detail?



IMHO PCP proposal for Pref64::/n falls to similar category as DHCPv6 in the draft-ietf-behave-nat64-learn-analysis-03.txt. I.e. it may not be deployed alongside NAT64, it requires PCP client implementation on a node, and so forth.



Best regards,



                Teemu



From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf Of ext mohamed.boucadair@orange.com
Sent: 07. syyskuuta 2012 09:43
To: behave@ietf.org
Subject: [BEHAVE] draft-ietf-behave-nat64-discovery-heuristic in PCP-enabled networks?



Dear all,



I bring this discussion point to behave ML as draft-ietf-behave-nat64-discovery-heuristic was cited by Simon and Reddy in PCP ML.



Context: There are plans to use PCP to control an upstream NAT64. For such contexts, using PCP to retrieve the PREFI64 is straightforward.



Discussion: Should draft-ietf-behave-nat64-discovery-heuristic say something about the applicability scope? Is it justified to implement this heuristic to retrieve an information which is available via PCP?



Cheers,

Med

v2.23.0 | Report a Bug | By Email