Hi David, The requested validation method and error types are approved. The identifier types are NOT approved.
The document does not specify the content of the ACME identifier object when these identifier types are used. There is discussion of what a client may put in a CSR, but the JSON fields that appear in the identifier object are not defined. --Richard On Mon, Mar 2, 2026 at 5:30 PM David Dong via RT < [email protected]> wrote: > Dear Richard Barnes, Aaron Gable (cc: acme WG), > > Following up on this expert review request from February 11th; thank you. > > Best regards, > > David Dong > IANA Services Sr. Specialist > > On Wed Feb 18 20:56:17 2026, david.dong wrote: > > Dear Richard Barnes, Aaron Gable (cc: acme WG), > > > > Following up on this expert review request; thank you. > > > > Best regards, > > > > David Dong > > IANA Services Sr. Specialist > > > > On Wed Feb 11 00:36:58 2026, david.dong wrote: > > > Dear Richard Barnes, Aaron Gable (cc: acme WG), > > > > > > As the designated experts for the ACME Identifier Types, ACME > > > Validation Methods and ACME Error Type registries, can you review the > > > proposed registrations in draft-ietf-acme-device-attest-01 for us? > > > Please see: > > > > > > https://datatracker.ietf.org/doc/draft-ietf-acme-device-attest/ > > > > > > The due date is February 24th. > > > > > > If this is OK, when the IESG approves the document for publication, > > > we'll make the registration at: > > > > > > https://www.iana.org/assignments/acme/ > > > > > > Unless you ask us to wait for the other reviewer, we’ll act on the > > > first response we receive. > > > > > > With thanks, > > > > > > David Dong > > > IANA Services Sr. Specialist > >
_______________________________________________ Acme mailing list -- [email protected] To unsubscribe send an email to [email protected]
