Automatic Certificate Management Environment (ACME) Device Attestation Extension
draft-ietf-acme-device-attest-10

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, acme-chairs@ietf.org, acme@ietf.org, debcooley1@gmail.com, draft-ietf-acme-device-attest@ietf.org, mike@ounsworth.ca, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'Automated Certificate Management Environment (ACME) Device Attestation Extension' to Proposed Standard (draft-ietf-acme-device-attest-09.txt)

The IESG has approved the following document:
- 'Automated Certificate Management Environment (ACME) Device Attestation
   Extension'
  (draft-ietf-acme-device-attest-09.txt) as Proposed Standard

This document is the product of the Automated Certificate Management
Environment Working Group.

The IESG contact persons are Christopher Inacio and Deb Cooley.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-acme-device-attest/

Ballot Text

Technical Summary

   This document specifies new identifiers and a challenge for the
   Automated Certificate Management Environment (ACME) protocol which
   allows validating the identity of a device using attestation.

Working Group Summary

   This document, as a whole, has been non-contentious since it is 
   documenting a technology already in wide adoption. There has not been 
   much debate, but mainly because its usefulness as an RFC is obvious.

  The working group did two rounds of wglc to ensure that the designated
  expert instructions were clear.  This will result in two IETF Last Calls
  which will ensure that the specification is clear and complete.

   There are other acme drafts which interact with this one.  But this 
   draft is clear in its objectives.

Document Quality

  There are no Yang modules, media type registrations, MIBs, or other 
  items that require special review.

  Implementations:  The protocol described in this document is implemented 
in Android, among others.  Several public and private CAs support or intend 
to support using this extension in ACME once an RFC exists. There is a
suspicion that CA/B Forum will adopt it once an RFC exists.

  Downrefs:  RFC 6973 (in the downref registry) and RFC 8809.  

Personnel

   The Document Shepherd for this document is Mike Ounsworth. The
   Responsible Area Director is Deb Cooley.

RFC Editor Note