RE: Adoption call for <draft-pref64folks-6man-ra-pref64-02>

<mohamed.boucadair@orange.com> Fri, 07 December 2018 09:44 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64C17128C65; Fri, 7 Dec 2018 01:44:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tVS-D82DMaMv; Fri, 7 Dec 2018 01:44:51 -0800 (PST)
Received: from orange.com (mta240.mail.business.static.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E0BA128A6E; Fri, 7 Dec 2018 01:44:51 -0800 (PST)
Received: from opfedar03.francetelecom.fr (unknown [xx.xx.xx.5]) by opfedar21.francetelecom.fr (ESMTP service) with ESMTP id 43B6y967hHz7txK; Fri, 7 Dec 2018 10:44:49 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.13]) by opfedar03.francetelecom.fr (ESMTP service) with ESMTP id 43B6y94dRmzCqkS; Fri, 7 Dec 2018 10:44:49 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM6D.corporate.adroot.infra.ftgroup ([fe80::54f9:a6c3:c013:cbc7%19]) with mapi id 14.03.0415.000; Fri, 7 Dec 2018 10:44:49 +0100
From: mohamed.boucadair@orange.com
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>, Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>
CC: IETF IPv6 Mailing List <ipv6@ietf.org>, 神明達哉 <jinmei@wide.ad.jp>, 6man Chairs <6man-chairs@ietf.org>
Subject: RE: Adoption call for <draft-pref64folks-6man-ra-pref64-02>
Thread-Topic: Adoption call for <draft-pref64folks-6man-ra-pref64-02>
Thread-Index: AQHUjgryEecCZrgn+kCGp9bWcJNWUqVzBH0w
Date: Fri, 07 Dec 2018 09:44:49 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302E054EC6@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <BD1717B3-C013-4718-9140-283F312C1634@employees.org> <CAJE_bqd3eXQa4xK5t8fbNE+frHrUrAebrKK2=4-jeV1EiJGkWA@mail.gmail.com> <EEFE399E-A197-47FC-82DC-551819EBCE82@gmail.com> <787AE7BB302AE849A7480A190F8B93302E054BB2@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CAFU7BARuKv-hAmpCeiusxqYsVYB1dr3POq8bB5D=g9_ksZ0WhA@mail.gmail.com> <787AE7BB302AE849A7480A190F8B93302E054CE8@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CAKD1Yr32KG-u_rDGv=4GJnJi5jGxttX0iwGTO6M_Z=Z9J=-GEw@mail.gmail.com> <4A8AFDA1-AF5E-4781-A5FC-CCA4A69C31EC@consulintel.es>
In-Reply-To: <4A8AFDA1-AF5E-4781-A5FC-CCA4A69C31EC@consulintel.es>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.4]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B93302E054EC6OPEXCLILMA3corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/UxuOPYQRf5bRZ4HUn82cGt_Iw-4>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Dec 2018 09:44:54 -0000

Hi Jordi,

Please see inline.

Cheers,
Med

De : JORDI PALET MARTINEZ [mailto:jordi.palet@consulintel.es]
Envoyé : vendredi 7 décembre 2018 09:58
À : Lorenzo Colitti; BOUCADAIR Mohamed TGI/OLN
Cc : IETF IPv6 Mailing List; 神明達哉; 6man Chairs
Objet : Re: Adoption call for <draft-pref64folks-6man-ra-pref64-02>

I think in fact we should adopt both solutions, a RA based and DHCPv6 one (https://www.ietf.org/archive/id/draft-li-intarea-nat64-prefix-dhcp-option-01.txt).

Many ISPs rely in DHCPv6 to provide all the parameters, same as in RA.
[Med] Perhaps I missed your point, but I’m not aware of any provider who uses RA for all configuration purposes.

Each ISP should be able to choose.
[Med] This is a fair discussion but a separate one. The argument applies to any piece of configuration (SIP Proxy, DS-Lite AFTR, ..).

However I’m fine if we just do RA (or we just do DHCPv6).

Regards,
Jordi



De: ipv6 <ipv6-bounces@ietf.org> en nombre de Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>
Fecha: viernes, 7 de diciembre de 2018, 9:52
Para: "<mohamed.boucadair@orange.com>" <mohamed.boucadair@orange.com>
CC: IETF IPv6 Mailing List <ipv6@ietf.org>, 神明達哉 <jinmei@wide.ad.jp>, 6man Chairs <6man-chairs@ietf.org>
Asunto: Re: Adoption call for <draft-pref64folks-6man-ra-pref64-02>

On Fri, Dec 7, 2018 at 4:42 PM <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>> wrote:
   Compared to the DHCPv6 equivalent solution in Section 5.6, the
   management overhead is greater with the RA-based solution.  With the
   DHCPv6-based solution, the management can be centralized to a few
   DHCPv6 servers compared to the RA-based solution where each access
   router is supposed to be configured with the same information.

That text ignores the operational reality that in large networks router configuration is largely either highly uniform, using tools such as apply-groups, or entirely autogenerated (at scale, it's the only way to ensure network configuration is correct).
-------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------

**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.