[Acme] [Technical Errata Reported] RFC9448 (9173)
rfc-editor@rfc-editor.org Fri, 11 September 2026 16:23 UTC
Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: acme@ietf.org
Delivered-To: acme@mail2.ietf.org
Received: from errata-celery-6f84c7996-wb2x7 (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 35D9E13916ACC; Fri, 11 Sep 2026 09:23:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1789143821; bh=eR3sqenVE+2MVme4615bgUWzvefW+3KQ/Vcwm0gemxo=; h=Subject:From:To:Cc:Date; b=Vi3qboB+ZM3a3T5WTI19qhWZZghE5SOeTSCqEv0PnMvlrmx4CKIsOPq1E27/2E7h3 /+1NgEwzYNQCd52EYl1RmFjyBe5xc7SvogpS2O0rZEmH7DeZmBg2QdgLlzph+/dZPF 8hlv54jebu/5MR4bRX+m8j6lrR0IBc+iXkP/5hPo=
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: rfc-editor@rfc-editor.org
To: rdd@cert.org, jon.peterson@transunion.com, david_hancock@comcast.com, rsalz@akamai.com, stndrds-inacio@andrew.cmu.edu, mary.ietf.barnes@gmail.com, debcooley1@gmail.com, chris@appliedbits.com
Date: Fri, 11 Sep 2026 16:23:41 -0000
message-id: <178914382108.21.9963259803901718789@rfc-editor.org>
Message-ID-Hash: ZLE3OOJYJ6EYX4SG3ASUEHB3U4TU4LC3
X-Message-ID-Hash: ZLE3OOJYJ6EYX4SG3ASUEHB3U4TU4LC3
X-MailFrom: rfc-editor@rfc-editor.org
X-Mailman-Rule-Hits: nonmember-moderation
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-acme.ietf.org-0
CC: rfc-editor@rfc-editor.org, acme@ietf.org, chris@appliedbits.com
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Acme] [Technical Errata Reported] RFC9448 (9173)
List-Id: Automated Certificate Management Environment <acme.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/3Pow6FlPTXO2ZnXtV7qCCBP3JSg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Owner: <mailto:acme-owner@ietf.org>
List-Post: <mailto:acme@ietf.org>
List-Subscribe: <mailto:acme-join@ietf.org>
List-Unsubscribe: <mailto:acme-leave@ietf.org>
The following errata report has been submitted for RFC9448, "TNAuthList Profile of Automated Certificate Management Environment (ACME) Authority Token" -------------------------------------- You may review the report below and at: https://errata.rfc-editor.org/eid9173/ -------------------------------------- Type: Technical Reported by: Chris Wendt <chris@appliedbits.com> Section 7 says: Original Text ------------- "identifiers": [ "type":"TNAuthList", "value":"F83n2a...avn27DN3" ], Corrected Text -------------- "identifiers": [ {"type":"TNAuthList", "value":"F83n2a...avn27DN3"} ], Notes ----- The "identifiers" member is a JSON array, but its contents are written as a sequence of bare name/value pairs, which is not valid JSON. Per RFC 8555, each ACME identifier is a JSON object, so the array must contain an object: [{"type":"TNAuthList","value":"..."}]. This matches the form used correctly elsewhere in the document (e.g., the new-order request examples). The example is informative, but as printed it cannot be parsed as JSON. Instructions: ------------- This erratum is currently posted as "Reported". Please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party will log in to change the status and edit the report, if necessary. -------------------------------------- RFC9448 (draft-ietf-acme-authority-token-tnauthlist) -------------------------------------- Title : TNAuthList Profile of Automated Certificate Management Environment (ACME) Authority Token Publication Date : September 2023 Author(s) : C. Wendt, D. Hancock, M. Barnes, J. Peterson Category : Proposed Standard Source : acme (sec) Stream : IETF Verifying Party : IESG