ACME End User Client and Code Signing Certificates
draft-moriarty-acme-client-05
| Document | Type |
Replaced Internet-Draft
(acme WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Kathleen Moriarty | ||
| Last updated | 2020-08-13 (Latest revision 2020-08-05) | ||
| Replaced by | draft-ietf-acme-client | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-acme-client | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Automated Certificate Management Environment (ACME) core protocol addresses the use case of web server certificates for TLS. This document extends the ACME protocol to support end user client, device client, and code signing certificates.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)