Re: [v6ops] Roman Danyliw's No Objection on draft-ietf-v6ops-nat64-deployment-07: (with COMMENT)

Roman Danyliw <rdd@cert.org> Fri, 12 July 2019 01:36 UTC

Return-Path: <rdd@cert.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C866120020; Thu, 11 Jul 2019 18:36:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cert.org
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 DKU9a6hVU64w; Thu, 11 Jul 2019 18:36:24 -0700 (PDT)
Received: from taper.sei.cmu.edu (taper.sei.cmu.edu [147.72.252.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A40712004D; Thu, 11 Jul 2019 18:36:24 -0700 (PDT)
Received: from korb.sei.cmu.edu (korb.sei.cmu.edu [10.64.21.30]) by taper.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x6C1aJe1006753; Thu, 11 Jul 2019 21:36:19 -0400
DKIM-Filter: OpenDKIM Filter v2.11.0 taper.sei.cmu.edu x6C1aJe1006753
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1562895379; bh=/qxHoOa/F1l0AloUL2zJd0a3waLzk0rXOv7MzqPZNMc=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=GNsSL6m2x6EiQoAOQ866gl0aWeHCc55WLu57AVcqdzBUVtQaMO2WCScSDGGvtp7KM 3bvvMGU3iRHHMqEi1ndNrGCXalCkMQWCTh2WLhnc1RwMj6tRqB2Lyz7GVxJBgn57Gh X3vWv7/ObhLwGWIAGIyQyAr7lS4Nl32zc5BytkjM=
Received: from CASSINA.ad.sei.cmu.edu (cassina.ad.sei.cmu.edu [10.64.28.249]) by korb.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x6C1aGss019322; Thu, 11 Jul 2019 21:36:16 -0400
Received: from MARCHAND.ad.sei.cmu.edu ([10.64.28.251]) by CASSINA.ad.sei.cmu.edu ([10.64.28.249]) with mapi id 14.03.0439.000; Thu, 11 Jul 2019 21:36:16 -0400
From: Roman Danyliw <rdd@cert.org>
To: Jordi Palet Martínez <jordi.palet@theipv6company.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, Jordi Palet Martínez <jordi.palet=40theipv6company.com@dmarc.ietf.org>, The IESG <iesg@ietf.org>
CC: "v6ops@ietf.org" <v6ops@ietf.org>, "draft-ietf-v6ops-nat64-deployment@ietf.org" <draft-ietf-v6ops-nat64-deployment@ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>
Thread-Topic: Roman Danyliw's No Objection on draft-ietf-v6ops-nat64-deployment-07: (with COMMENT)
Thread-Index: AQHVN4HXDqwoxMuSdEau0nlmDxvmhqbFOx6AgAAG+oCAAAYZgIAA6+5g
Date: Fri, 12 Jul 2019 01:36:15 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFC01B33CE0F3@marchand>
References: <156280587243.15387.3448756354265835528.idtracker@ietfa.amsl.com> <E34C8182-E7C9-48A3-91F0-23BABA469292@theipv6company.com> <787AE7BB302AE849A7480A190F8B93302EAC9D83@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <2A20F73E-F59A-4945-B563-8E6C9EDEDA03@theipv6company.com>
In-Reply-To: <2A20F73E-F59A-4945-B563-8E6C9EDEDA03@theipv6company.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.64.22.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/aN5OzYK4ZssY68h1o5Y7-Cu_SoM>
Subject: Re: [v6ops] Roman Danyliw's No Objection on draft-ietf-v6ops-nat64-deployment-07: (with COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jul 2019 01:36:26 -0000

Hi!

> -----Original Message-----
> From: Jordi Palet Martínez [mailto:jordi.palet@theipv6company.com]
> Sent: Thursday, July 11, 2019 3:27 AM
> To: mohamed.boucadair@orange.com; Jordi Palet Martínez
> <jordi.palet=40theipv6company.com@dmarc.ietf.org>; Roman Danyliw
> <rdd@cert.org>; The IESG <iesg@ietf.org>
> Cc: v6ops@ietf.org; draft-ietf-v6ops-nat64-deployment@ietf.org; v6ops-
> chairs@ietf.org
> Subject: Re: Roman Danyliw's No Objection on draft-ietf-v6ops-nat64-
> deployment-07: (with COMMENT)
> 
> Hi Med,
> 
> Thanks a lot! that's a very good "middle point" reference. It is only about US,
> I will try to see if there is a similar one that shows also other regions.
> 
> Regards,
> Jordi
> @jordipalet
> 
> 
> El 11/7/19 9:05, "mohamed.boucadair@orange.com"
> <mohamed.boucadair@orange.com> escribió:
> 
>     Hi Jordi, all,
> 
>     One comment below.
> 
>     Cheers,
>     Med
> 
>     > -----Message d'origine-----
>     > De : v6ops [mailto:v6ops-bounces@ietf.org] De la part de Jordi Palet
>     > Martínez
>     > Envoyé : jeudi 11 juillet 2019 08:41
>     > À : Roman Danyliw; The IESG
>     > Cc : v6ops@ietf.org; draft-ietf-v6ops-nat64-deployment@ietf.org; v6ops-
>     > chairs@ietf.org
>     > Objet : Re: [v6ops] Roman Danyliw's No Objection on draft-ietf-v6ops-
>     > nat64-deployment-07: (with COMMENT)
>     >
>     > Hi Roman,
>     >
>     > Thanks a lot for your inputs.
>     >
>     > See below, in-line.
>     >
>     > Regards,
>     > Jordi
>     > @jordipalet
>     >
>     >
>     > El 11/7/19 2:44, "Roman Danyliw via Datatracker" <noreply@ietf.org>
>     > escribió:
>     >
>     >     Roman Danyliw has entered the following ballot position for
>     >     draft-ietf-v6ops-nat64-deployment-07: No Objection
>     >
>     >     When responding, please keep the subject line intact and reply to all
>     >     email addresses included in the To and CC lines. (Feel free to cut
>     > this
>     >     introductory paragraph, however.)
>     >
>     >
>     >     Please refer to https://www.ietf.org/iesg/statement/discuss-
>     > criteria.html
>     >     for more information about IESG DISCUSS and COMMENT positions.
>     >
>     >
>     >     The document, along with other ballot positions, can be found here:
>     >     https://datatracker.ietf.org/doc/draft-ietf-v6ops-nat64-deployment/
>     >
>     >
>     >
>     >     ----------------------------------------------------------------------
>     >     COMMENT:
>     >     ----------------------------------------------------------------------
>     >
>     >     (1) Section 5.  Is there an informative reference that can be made
>     > about the
>     >     successful deployment on cellular networks?
>     >
>     > Do you mean citing specific operators? I can name several in almost
> every
>     > continent, but I'm not convinced this is correct in an IETF document ...
>     >

I'm flexible.  The text asserts this is used widely.  I was wondering if any informative reference could point to that.

>     [Med] No need to be exhaustive here, I suggest to add one single pointer:
> https://www.worldipv6launch.org/major-mobile-us-networks-pass-50-ipv6-
> threshold/. Having an informative reference is helpful for this kind of
> statements (because otherwise, this may be considered as speculative).
>
> 
>     >     (2) Section 7.  Consider adding an explicit statement such as the
>     > following
>     >     after the intro sentence that “no new security considerations are
>     > added”:
>     >
>     >     As noted in the relevant sections above, the NAT64 and DNS64
>     > technologies can
>     >     impact the efficacy or functionality of key security (i.e., DNSSEC and
>     > VPNs)
>     >     and privacy preserving (i.e., DNS-over-TLS and DNS-over-HTTP)
>     > technologies.
>     >
>     > -> I will need to reword it. This is right in the reference to DNSSEC.
>     > However VPNs and DNS privacy, the point is on the other way around
> (those
>     > technologies can avoid the DNS64 performing correctly, and thus, break
>     > NAT64).

Right.  I botched what-breaks-what so please do reword it.  

>     >     (3) Editorial Nits
>     >
>     >     ** Section 1.  Editorial. s/today unrealistic/unrealistic today/
>     >
>     >     ** Section 5.  Typo.  s/learn he/learn the/
>     >
>     >     ** Section 5.  Editorial.  “Hundreds of millions of users” mentioned
>     > twice.
>     >
>     >     OLD:
>     >     NAT64/464XLAT has demonstrated to be a valid choice in several
>     > scenarios
>     >     (IPv6-IPv4 and IPv4-IPv6-IPv4), with hundreds of millions of users,
>     > being the
>     >     predominant mechanism in the majority of the cellular networks
> (which
>     > account
>     >     for hundreds of millions of users).
>     >
>     >     NEW:
>     >     NAT64/464XLAT has demonstrated to be a valid choice in several
>     > scenarios
>     >     (IPv6-IPv4 and IPv4-IPv6-IPv4) in cellular networks which account for
>     > hundreds
>     >     of millions of users.
>     >
>     > Noted and corrected all those nits in my internal version. I will wait a
>     > couple of days before publishing it, in case there are any further inputs.

Thanks for fixing these.

Thanks,
Roman

>     >
> 
> 
> 
> 
> **********************************************
> 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.
> 
>