Re: [DNSOP] [Ext] Martin Duke's Discuss on draft-ietf-dnsop-dnssec-iana-cons-04: (with DISCUSS and COMMENT)

Paul Hoffman <paul.hoffman@icann.org> Wed, 29 September 2021 17:25 UTC

Return-Path: <paul.hoffman@icann.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 397273A07AE; Wed, 29 Sep 2021 10:25:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 vg5QUC8XuNuQ; Wed, 29 Sep 2021 10:25:55 -0700 (PDT)
Received: from ppa2.lax.icann.org (ppa2.lax.icann.org [192.0.33.77]) (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 A38933A00CF; Wed, 29 Sep 2021 10:25:55 -0700 (PDT)
Received: from MBX112-W2-CO-2.pexch112.icann.org (out.mail.icann.org [64.78.33.6]) by ppa2.lax.icann.org (8.16.0.43/8.16.0.43) with ESMTPS id 18THPruN031456 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 29 Sep 2021 17:25:53 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.922.13; Wed, 29 Sep 2021 10:25:52 -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.0922.013; Wed, 29 Sep 2021 10:25:52 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: Martin Duke <martin.h.duke@gmail.com>
CC: The IESG <iesg@ietf.org>, dnsop <dnsop@ietf.org>
Thread-Topic: [Ext] Martin Duke's Discuss on draft-ietf-dnsop-dnssec-iana-cons-04: (with DISCUSS and COMMENT)
Thread-Index: AQHXtJeGVXjj3c5YVkKRJ14eKwfv0qu7nzeAgAAHeoCAABOTAA==
Date: Wed, 29 Sep 2021 17:25:52 +0000
Message-ID: <E51D0552-E471-4E61-8990-5CDB284D4204@icann.org>
References: <163285408723.29955.12780997671770548944@ietfa.amsl.com> <AE26C926-F618-4C16-88E6-5DD4AED2B178@icann.org> <CAM4esxTC4QHvg+bihhMudO3jpyrpMu0G1YkCrSJH=PLSJkNZHw@mail.gmail.com>
In-Reply-To: <CAM4esxTC4QHvg+bihhMudO3jpyrpMu0G1YkCrSJH=PLSJkNZHw@mail.gmail.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: Processed
Content-Type: multipart/signed; boundary="Apple-Mail=_BFF950FA-E997-4E8C-9B3F-86D698D02CFB"; protocol="application/pkcs7-signature"; micalg="sha-256"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.790 definitions=2021-09-29_06:2021-09-29, 2021-09-29 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/3dqJR22h91Pcsoayf0Et5F9EPKM>
Subject: Re: [DNSOP] [Ext] Martin Duke's Discuss on draft-ietf-dnsop-dnssec-iana-cons-04: (with DISCUSS and COMMENT)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2021 17:25:57 -0000

On Sep 29, 2021, at 9:15 AM, Martin Duke <martin.h.duke@gmail.com> wrote:
> 
> Thank you for clarifying. If 4033-4035 fully replaced 3658,

They really do.

> then one of them should have picked up the specification of the registry that 3658 established.

Not "one of them", unfortunately. The semantics for the DS record from 3658 are spread out in 4034 and 4035 (which have a lot of other things in them as well).

> Maybe this is something that could be addressed in this document, or perhaps somewhere else; I'd like to have the discussion.

If the scope is "what does this particular IANA registry page list as references", maybe this is not in scope for this document (which only updates the registration requirements), but instead in scope for a discussion between the IESG and IANA.

--Paul Hoffman