[Acme] [Technical Errata Reported] RFC9448 (9172)

rfc-editor@rfc-editor.org Fri, 11 September 2026 16:23 UTC

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:32 -0000
message-id: <178914381230.16.2749915498052541897@rfc-editor.org>
Message-ID-Hash: Z5RTDGD43EXQ7U5AC2MUPIKWWF3JV3DZ
CC: rfc-editor@rfc-editor.org, acme@ietf.org, chris@appliedbits.com
Precedence: list
Subject: [Acme] [Technical Errata Reported] RFC9448 (9172)
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/CGNjRM9BCOWDVHz-YwUNYSNreJ4>

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/eid9172/

--------------------------------------
Type: Technical
Reported by: Chris Wendt <chris@appliedbits.com>

Section 4 says:

Original Text
-------------
"challenges": [
    {
      "type": "tkauth-01",
      "tkauth-type": "atc",
      "token-authority": "https://authority.example.org",
      "url": "https://example.com/acme/chall/prV_B7yEyA4",
      "token": "IlirfxKKXAsHtmzK29Pj8A"
    }
  ]

Corrected Text
--------------
"challenges": [
    {
      "type": "tkauth-01",
      "tkauth-type": "atc",
      "token-authority": "https://authority.example.org",
      "url": "https://example.com/acme/chall/prV_B7yEyA4",
      "status": "pending",
      "token": "IlirfxKKXAsHtmzK29Pj8A"
    }
  ]

Notes
-----
RFC 8555, Section 8, lists "status" as a required field of a challenge object.
The tkauth-01 challenge object within the "challenges" array omits it. At this
point in the flow the challenge is pending, so the object should include
"status": "pending". (The enclosing authorization object correctly carries its
own "status": "pending"; the omission is only on the inner challenge object.)

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

[Acme] [Technical Errata Reported] RFC9448 (9172) rfc-editor