Re: [dns-privacy] [Ext] Secdir early review of draft-ietf-dprive-unilateral-probing-07

Paul Hoffman <paul.hoffman@icann.org> Sat, 24 June 2023 00:49 UTC

Return-Path: <paul.hoffman@icann.org>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A53AC151064; Fri, 23 Jun 2023 17:49:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gvS4s5_nzabI; Fri, 23 Jun 2023 17:49:43 -0700 (PDT)
Received: from ppa5.dc.icann.org (ppa5.dc.icann.org [192.0.46.78]) (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 91223C14CE44; Fri, 23 Jun 2023 17:49:43 -0700 (PDT)
Received: from MBX112-W2-CO-2.pexch112.icann.org (out.mail.icann.org [64.78.33.6]) by ppa5.dc.icann.org (8.17.1.19/8.17.1.19) with ESMTPS id 35O0nfHx014029 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 24 Jun 2023 00:49:41 GMT
Received: from MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) by MBX112-W2-CO-2.pexch112.icann.org (10.226.41.130) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.26; Fri, 23 Jun 2023 17:49:39 -0700
Received: from MBX112-W2-CO-1.pexch112.icann.org ([10.226.41.128]) by MBX112-W2-CO-1.pexch112.icann.org ([10.226.41.128]) with mapi id 15.02.1118.026; Fri, 23 Jun 2023 17:49:39 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: Rich Salz <rsalz@akamai.com>
CC: secdir <secdir@ietf.org>, "dns-privacy@ietf.org" <dns-privacy@ietf.org>, "draft-ietf-dprive-unilateral-probing.all@ietf.org" <draft-ietf-dprive-unilateral-probing.all@ietf.org>
Thread-Topic: [Ext] Secdir early review of draft-ietf-dprive-unilateral-probing-07
Thread-Index: AQHZmw/gG9yaHaV56UK7iFtUmx/wr6+ZqruA
Date: Sat, 24 Jun 2023 00:49:39 +0000
Message-ID: <02EF3E5D-DF77-430F-B85D-8BA52387951B@icann.org>
References: <168634204133.61641.15990253589636399258@ietfa.amsl.com>
In-Reply-To: <168634204133.61641.15990253589636399258@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.0.32.234]
x-source-routing-agent: True
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6B652ED9E94F6C41A5D8A5E589548A90@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.254,Aquarius:18.0.957,Hydra:6.0.591,FMLib:17.11.176.26 definitions=2023-06-23_14,2023-06-22_02,2023-05-22_02
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/vtOpPfWdqxn3ZhvpHsckL_v6Pz0>
Subject: Re: [dns-privacy] [Ext] Secdir early review of draft-ietf-dprive-unilateral-probing-07
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Addition of privacy to the DNS protocol <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Jun 2023 00:49:46 -0000

Belated thanks for this review. I've accepted many of the nits without note, but some notes below.

--Paul Hoffman

On Jun 9, 2023, at 1:20 PM, Rich Salz via Datatracker <noreply@ietf.org> wrote:
> 
> Reviewer: Rich Salz
> Review result: Has Nits
> 
> Sec  2.2  Is the main point of the first paragraph to say that DoQ and DoT
> don't address this type of deployment but leave it open for future docs?  If
> so, maybe that's worth stating directly.

That idea was contentious in the WG because others tried to write those "future docs" but got nowhere. I'd rather not poke at them. The possibility of future docs is touched on in the abstract and the security considerations.

> Sec 3 I think the ALPN the client "should" use (lowercase) is better than "may
> use"

This would lead to later reviews if we meant to capitalize the "should". :-)

> Appendix A, is that to be removed when published?  Should A and B explicitly
> say they are not normative?

The intended status of the document is now "experimental". Thus, Appendix A will remain in the document, and everything is not normative.