ACME Integrations
draft-friel-acme-integrations-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Owen Friel , Richard Barnes , Rifaat Shekh-Yusef | ||
| Last updated | 2019-10-24 | ||
| Replaced by | draft-ietf-acme-integrations | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-acme-integrations | |
| 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
This document outlines multiple advanced use cases and integrations that ACME facilitates without any modifications or enhancements required to the base ACME specification. The use cases include ACME integration with EST, BRSKI and TEAP.
Authors
Owen Friel
Richard Barnes
Rifaat Shekh-Yusef
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)