[Acme] [Errata Verified] RFC8555 (6364)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 22 March 2024 14:57 UTC
Return-Path: <wwwrun@rfcpa.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 BCAACC1CAF3D; Fri, 22 Mar 2024 07:57:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.658
X-Spam-Level:
X-Spam-Status: No, score=-1.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 Qj1ds75I7UHg; Fri, 22 Mar 2024 07:57:21 -0700 (PDT)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (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 EC668C1D4CF0; Fri, 22 Mar 2024 07:57:21 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id C3A495BDCA4; Fri, 22 Mar 2024 07:57:21 -0700 (PDT)
To: ekaratsiolis@mtg.de, rlb@ipv.sx, jsha@eff.org, cpu@letsencrypt.org, jdkasten@umich.edu
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: debcooley1@gmail.com, iesg@ietf.org, acme@ietf.org, iana@iana.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240322145721.C3A495BDCA4@rfcpa.amsl.com>
Date: Fri, 22 Mar 2024 07:57:21 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/EdopHrdGGK7hPv5ureDH7xNROHc>
X-Mailman-Approved-At: Fri, 22 Mar 2024 08:24:42 -0700
Subject: [Acme] [Errata Verified] RFC8555 (6364)
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: Fri, 22 Mar 2024 14:57:25 -0000
The following errata report has been verified for RFC8555, "Automatic Certificate Management Environment (ACME)". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid6364 -------------------------------------- Status: Verified Type: Technical Reported by: Evangelos Karatsiolis <ekaratsiolis@mtg.de> Date Reported: 2020-12-23 Verified by: Deb Cooley (IESG) Section: 7.1.4 Original Text ------------- wildcard (optional, boolean): This field MUST be present and true for authorizations created as a result of a newOrder request containing a DNS identifier with a value that was a wildcard domain name. For other authorizations, it MUST be absent. Wildcard domain names are described in Section 7.1.3. Corrected Text -------------- wildcard (optional, boolean): This field MUST be present and true for authorizations created as a result of a newOrder request containing a DNS identifier with a value that was a wildcard domain name. For other authorizations, it MUST be absent or false. For pre-authorizations, it MUST be absent or false. Wildcard domain names are described in Section 7.1.3. Notes ----- This section states that the wildcard field must be absent for other authorizations, but the example in this section has an explicitly set wildcard field with value false. The proposed change allows both options, either omitting it or explicitly setting it to false. Also a sentence has been added to explicitly describe the behavior for pre-authorizations. -------------------------------------- RFC8555 (draft-ietf-acme-acme-18) -------------------------------------- Title : Automatic Certificate Management Environment (ACME) Publication Date : March 2019 Author(s) : R. Barnes, J. Hoffman-Andrews, D. McCarney, J. Kasten Category : PROPOSED STANDARD Source : Automated Certificate Management Environment Stream : IETF Verifying Party : IESG
- [Acme] [Errata Verified] RFC8555 (6364) RFC Errata System