IETF Logo Mail Archive

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

Paul Hoffman <paul.hoffman@icann.org> Mon, 03 October 2022 22:54 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 53D45C1526E1; Mon, 3 Oct 2022 15:54:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 AQcKM7wkA1AB; Mon, 3 Oct 2022 15:54:34 -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 259DAC152591; Mon, 3 Oct 2022 15:54:07 -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 293Ms4YU002548 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 3 Oct 2022 22:54:04 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.12; Mon, 3 Oct 2022 15:54:03 -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:54:03 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: Linda Dunbar <linda.dunbar@futurewei.com>
CC: "gen-art@ietf.org" <gen-art@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] Genart last call review of draft-ietf-dnsop-dnssec-bcp-03
Thread-Index: AQHY13YbNhT7fxMjx0mfux+jp/d+V639vH2A
Date: Mon, 03 Oct 2022 22:54:03 +0000
Message-ID: <32AE2BD6-DD50-4584-AEA9-A4F7A6C04DA9@icann.org>
References: <166483552236.22697.11047665175399678108@ietfa.amsl.com>
In-Reply-To: <166483552236.22697.11047665175399678108@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=_C1A9A243-732C-41C1-99C6-E9F99C453075"; 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/t6-p-eanFvpkWTsy389ueB4e-_M>
Subject: Re: [Last-Call] [Ext] Genart 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:54:37 -0000

On Oct 3, 2022, at 3:18 PM, Linda Dunbar via Datatracker <noreply@ietf.org> wrote:
> Section 1.2 (Implementing DNSSEC) states that some of the DNSSEC-related RFCs
> have significant errata.
> 
> Is it possible to have a link to list those errata? so that people can easily
> access them.

It is not, unfortunately.

> I am not an expert in DNSSEC. It has been overwhelming going through so many
> RFCs for different aspects of the DNSSEC. It will be nicer if someone can write
> a deployment guideline in addition to this draft of listing all the RFCs.

This would be lovely, but not likely. I would be happy to be wrong here.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email