Re: [Acme] [Technical Errata Reported] RFC9115 (7336)
Alice Russo <arusso@amsl.com> Tue, 07 February 2023 21:52 UTC
Return-Path: <arusso@amsl.com>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59CFDC14CEFE for <acme@ietfa.amsl.com>; Tue, 7 Feb 2023 13:52:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 Zres_jzo-pyJ for <acme@ietfa.amsl.com>; Tue, 7 Feb 2023 13:52:22 -0800 (PST)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80630C14CEE4 for <acme@ietf.org>; Tue, 7 Feb 2023 13:52:22 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 46BC6424F0C0; Tue, 7 Feb 2023 13:52:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HpzWyXVivr-J; Tue, 7 Feb 2023 13:52:22 -0800 (PST)
Received: from smtpclient.apple (unknown [76.146.133.47]) by c8a.amsl.com (Postfix) with ESMTPSA id BFA2B424B429; Tue, 7 Feb 2023 13:52:21 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Alice Russo <arusso@amsl.com>
In-Reply-To: <9B3BF4F3-5A01-447D-88E3-8C621E8CB0C5@tzi.org>
Date: Tue, 07 Feb 2023 13:52:21 -0800
Cc: Yaron Sheffer <yaronf.ietf@gmail.com>, "Diego R. Lopez" <diego.r.lopez@telefonica.com>, antonio.pastorperales@telefonica.com, Thomas Fossati <thomas.fossati@arm.com>, "Roman D. Danyliw" <rdd@cert.org>, Paul Wouters <paul.wouters@aiven.io>, decoole@radium.ncsc.mil, debcooley1@gmail.com, ynir.ietf@gmail.com, acme@ietf.org, RFC Errata System <rfc-editor@rfc-editor.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <97A774E5-7744-45D4-8BF2-AB610C1A8134@amsl.com>
References: <20230206233552.C595011E4FC@rfcpa.amsl.com> <9B3BF4F3-5A01-447D-88E3-8C621E8CB0C5@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/4JRcvVoataLANKMdKApFcdMcGMg>
X-Mailman-Approved-At: Tue, 07 Feb 2023 15:11:12 -0800
Subject: Re: [Acme] [Technical Errata Reported] RFC9115 (7336)
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2023 21:52:27 -0000
Carsten, Thanks for noting the missing backslashes within the email; the issue has been noted for the developer. Looks like the errata report on the web is accurate (backslashes are intact): https://www.rfc-editor.org/errata/eid7336 Please let us know if you disagree. Thanks, Alice > On Feb 6, 2023, at 3:45 PM, Carsten Bormann <cabo@tzi.org> wrote: > > This is hilarious — the errata reporting form apparently ate my double backslashes. > > Here is the corrected Corrected Text: > > oid = text .regexp "([0-2])((\\.0)|(\\.[1-9][0-9]*))*” > > And here is how I would write this, having been bitten by backslashes in RFCs before: > > oid = text .regexp "([0-2])(([.]0)|([.][1-9][0-9]*))*” > > (Actually, I would write this: > > oid = text .regexp "[0-2]([.](0|([1-9][0-9]*)))*” > > …but this is a style issue.) > > Grüße, Carsten > > >> On 2023-02-07, at 00:35, RFC Errata System <rfc-editor@rfc-editor.org> wrote: >> >> The following errata report has been submitted for RFC9115, >> "An Automatic Certificate Management Environment (ACME) Profile for Generating Delegated Certificates". >> >> -------------------------------------- >> You may review the report below and at: >> https://www.rfc-editor.org/errata/eid7336 >> >> -------------------------------------- >> Type: Technical >> Reported by: Carsten Bormann <cabo@tzi.org> >> >> Section: Appendix A >> >> Original Text >> ------------- >> oid = text .regexp "([0-2])((\.0)|(\.[1-9][0-9]*))*" >> >> >> Corrected Text >> -------------- >> oid = text .regexp "([0-2])((\.0)|(\.[1-9][0-9]*))*" >> >> >> Notes >> ----- >> Backslashes need to be doubled in CDDL strings (as they are done in Appendix B). >> >> An alternative fix would be to replace \. by [.] >> >> Note that the equivalent fix is not required for >> >> regtext = text .regexp "([^\*].*)|([\*][^\*].*)|([\*][\*].+)" >> >> as the fact that the single backslashes have no effect is irrelevant here — the backslashes are not needed in the character classes [...]. >> As an editorial enhancement, the backslashes could be entirely removed from this line. >> >> Instructions: >> ------------- >> This erratum is currently posted as "Reported". If necessary, please >> use "Reply All" to discuss whether it should be verified or >> rejected. When a decision is reached, the verifying party >> can log in to change the status and edit the report, if necessary. >> >> -------------------------------------- >> RFC9115 (draft-ietf-acme-star-delegation-09) >> -------------------------------------- >> Title : An Automatic Certificate Management Environment (ACME) Profile for Generating Delegated Certificates >> Publication Date : September 2021 >> Author(s) : Y. Sheffer, D. López, A. Pastor Perales, T. Fossati >> Category : PROPOSED STANDARD >> Source : Automated Certificate Management Environment >> Area : Security >> Stream : IETF >> Verifying Party : IESG >
- [Acme] [Technical Errata Reported] RFC9115 (7336) RFC Errata System
- Re: [Acme] [Technical Errata Reported] RFC9115 (7… Carsten Bormann
- Re: [Acme] [Technical Errata Reported] RFC9115 (7… Thomas Fossati
- Re: [Acme] [Technical Errata Reported] RFC9115 (7… Alice Russo
- Re: [Acme] [Technical Errata Reported] RFC9115 (7… Carsten Bormann