Re: [v6ops] Benjamin Kaduk's No Record on draft-ietf-v6ops-nat64-deployment-07: (with COMMENT)

Jordi Palet Martínez <jordi.palet@theipv6company.com> Sat, 13 July 2019 07:01 UTC

Return-Path: <prvs=1097a26248=jordi.palet@theipv6company.com>
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 76C781200BA; Sat, 13 Jul 2019 00:01:49 -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, FROM_EXCESS_BASE64=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=theipv6company.com
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 mfXlpiF9_EZh; Sat, 13 Jul 2019 00:01:47 -0700 (PDT)
Received: from consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C0D7120112; Sat, 13 Jul 2019 00:01:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=theipv6company.com; s=MDaemon; t=1563001302; x=1563606102; i=jordi.palet@theipv6company.com; q=dns/txt; h=User-Agent:Date: Subject:From:To:CC:Message-ID:Thread-Topic:References: In-Reply-To:Mime-version:Content-type:Content-transfer-encoding; bh=Or/nv9ph88ukW/GAddF5TcKZcD7VD/P4I6+o/0z5218=; b=IBin/XgMaGdlu Zen3Xa/513ezR/XHsKYG5WGVi42MxKa5/DvAIIfX1XJm2omZoXbJeIiBfvrETFjm +w0+CqKk5hml/0nNpat8Og054egggjnV+xJbPBBufcLSSKDCxNVdjyzMC+YlWlG5 BdbCpne6TRPDCa6xFOmSweYqS9huw4=
X-MDAV-Result: clean
X-MDAV-Processed: consulintel.es, Sat, 13 Jul 2019 09:01:42 +0200
X-Spam-Processed: consulintel.es, Sat, 13 Jul 2019 09:01:40 +0200
Received: from [10.10.10.146] by consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50006324285.msg; Sat, 13 Jul 2019 09:01:39 +0200
X-MDRemoteIP: 2001:470:1f09:495:968:ab2c:858c:531b
X-MDHelo: [10.10.10.146]
X-MDArrival-Date: Sat, 13 Jul 2019 09:01:39 +0200
X-Authenticated-Sender: jordi.palet@theipv6company.com
X-Return-Path: prvs=1097a26248=jordi.palet@theipv6company.com
X-Envelope-From: jordi.palet@theipv6company.com
User-Agent: Microsoft-MacOutlook/10.10.b.190609
Date: Sat, 13 Jul 2019 09:01:39 +0200
From: Jordi Palet Martínez <jordi.palet@theipv6company.com>
To: Benjamin Kaduk <kaduk@mit.edu>
CC: The IESG <iesg@ietf.org>, draft-ietf-v6ops-nat64-deployment@ietf.org, Mikael Abrahamsson <swmike@swm.pp.se>, v6ops-chairs@ietf.org, v6ops@ietf.org
Message-ID: <F45F4681-8928-4081-8AC9-46F6EC194C5F@theipv6company.com>
Thread-Topic: Benjamin Kaduk's No Record on draft-ietf-v6ops-nat64-deployment-07: (with COMMENT)
References: <156287111965.12025.574936602251693337.idtracker@ietfa.amsl.com> <1B6059DD-5BC9-4EBB-8278-A0EC436E543E@theipv6company.com> <20190713022625.GT16418@mit.edu>
In-Reply-To: <20190713022625.GT16418@mit.edu>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/-4klEcO2gECqzPbYITX5YZ8yXLs>
Subject: Re: [v6ops] Benjamin Kaduk's No Record 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: Sat, 13 Jul 2019 07:01:50 -0000

Thanks Ben,

I guess then the RFC Editor may tell something if they consider that that specific question should be reworded.

Regards,
Jordi
@jordipalet
 

El 13/7/19 4:26, "Benjamin Kaduk" <kaduk@mit.edu> escribió:

    On Thu, Jul 11, 2019 at 10:58:51PM +0200, Jordi Palet Martínez wrote:
    > Hi Benjamin,
    > 
    > I think if you put that question in the overall document context, the interpretation is different.
    
    Oh, definitely.  I was just making an editorial comment about the wording
    of question (a) in Section 3.3.
    
    > Actually, the document advocates clearly to avoid breaking DNSSEC, and the best way to do that is either not doing DNS64 or (even better), ensuring that hosts do DNSSEC validation + DNS64 by themselves. This is possible already if you're using 464XLAT.
    > 
    > Also remember that the NAT64 is going to be used only for those services that are IPv4-only. I think we should advocate for those services to be IPv6-enabled + DNSSEC-enabled. If we agree on that, then the only missing piece is older IPv4-only boxes (in the customer side), which if can't be upgraded to support IPv6, I expect as well they will not be upgraded to support DNSSEC.
    
    That sounds pretty likely, yeah; only some weird combination of legacy
    technology and regulatory decree seems likely to get past it.
    
    Thanks for writing the document; it was a good read!
    
    -Ben
    
    > Regards,
    > Jordi
    > @jordipalet
    >  
    > 
    > El 11/7/19 20:52, "Benjamin Kaduk via Datatracker" <noreply@ietf.org> escribió:
    > 
    >     Benjamin Kaduk has entered the following ballot position for
    >     draft-ietf-v6ops-nat64-deployment-07: No Record
    >     
    >     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:
    >     ----------------------------------------------------------------------
    >     
    >     Staying at No Record since I'm balloting late, but:
    >     
    >     Just asking "DNSSEC: Are there hosts validating DNSSEC?" may not be the
    >     best way to plan for the future, as it ignores the question of whether
    >     hosts may in the future start or want to start validating DNSSEC.
    >     It would be unfortunate if deploying a NAT64 solution hindered DNSSEC
    >     deployment as a side effect.
    >     
    >     
    >     
    > 
    > 
    > 
    > **********************************************
    > 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.
    > 
    > 
    > 
    



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