Re: [Last-Call] [Ext] Secdir last call review of draft-ietf-dnsop-dnssec-bcp-03

Paul Hoffman <paul.hoffman@icann.org> Mon, 03 October 2022 22:56 UTC

Return-Path: <paul.hoffman@icann.org>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD4CCC1526E6; Mon, 3 Oct 2022 15:56:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 h7DOiYLhgdRb; Mon, 3 Oct 2022 15:56:15 -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 6FBDDC1526E1; Mon, 3 Oct 2022 15:56:02 -0700 (PDT)
Received: from MBX112-E2-CO-1.pexch112.icann.org (out.mail.icann.org [64.78.33.7]) by ppa5.dc.icann.org (8.17.1.5/8.17.1.5) with ESMTPS id 293Mu0IB003997 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 3 Oct 2022 22:56:00 GMT
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 Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.12; Mon, 3 Oct 2022 15:55:59 -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.012; Mon, 3 Oct 2022 15:55:59 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: Catherine Meadows <catherine.meadows@nrl.navy.mil>
CC: secdir <secdir@ietf.org>, "dnsop@ietf.org" <dnsop@ietf.org>, "draft-ietf-dnsop-dnssec-bcp.all@ietf.org" <draft-ietf-dnsop-dnssec-bcp.all@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>
Thread-Topic: [Ext] Secdir last call review of draft-ietf-dnsop-dnssec-bcp-03
Thread-Index: AQHY1Q+ILJU1ilZf7k2cVdV2ff4ZZ639wdSA
Date: Mon, 03 Oct 2022 22:55:59 +0000
Message-ID: <537E262B-24D8-4A71-8E5A-610FAD9F1CF6@icann.org>
References: <166457156513.58271.8499802491034836184@ietfa.amsl.com>
In-Reply-To: <166457156513.58271.8499802491034836184@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [192.0.32.234]
x-source-routing-agent: True
Content-Type: multipart/signed; boundary="Apple-Mail=_5114E463-3CCF-433D-B3DA-F21D80874EDE"; protocol="application/pkcs7-signature"; micalg="sha-256"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.895,Hydra:6.0.528,FMLib:17.11.122.1 definitions=2022-10-03_02,2022-09-29_03,2022-06-22_01
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/n22mVQDv03ut8z0OfN9C5c5xgys>
Subject: Re: [Last-Call] [Ext] Secdir last call review of draft-ietf-dnsop-dnssec-bcp-03
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Oct 2022 22:56:15 -0000

On Sep 30, 2022, at 1:59 PM, Catherine Meadows via Datatracker <noreply@ietf.org> wrote:
> I found one thing that could use improving:
> 
> The descriptions given in the additional documents of interest section all seem
> to be quotations from the documents described.  In most cases this worked well,
> but  I found the description of RFC4470 a little puzzling.  It says that the
> RFC "describes how to construct DNSSEC NSEC resource records that cover a
> smaller range of names than called for by [RFC4034]".
> 
>  All the other descriptions mentioned have to do with some security-relevant
>  topic, but it is hard to see what the security relevance of this is without
>  more information.  In this case, it might be helpful to include the next
>  sentence, which is
> “By generating and signing these records on demand, authoritative name servers
> can effectively stop the disclosure of zone contents  otherwise made possible
> by walking the chain of NSEC records in assigned zone.”
> 
> This is still a little opaque, but then at least the reader should understand 
> that the reason this document is relevant is that it prevents an attacker from
> learning all the names  in a zone.
> 

Thanks, this is a good catch. Fixed in the -04.

--Paul Hoffman