Skip to main content

Additional Use Cases for Automatic Certificate Management (ACME)
draft-mattsson-acme-use-cases-00

Document Type Expired Internet-Draft (individual)
Authors John Preuß Mattsson , Robert Skog
Last updated 2015-09-10 (Latest revision 2015-03-09)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text xml htmlized pdfized bibtex
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)
This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at:
https://www.ietf.org/archive/id/draft-mattsson-acme-use-cases-00.txt

Abstract

Contacting a CA is just one way in which a newly deployed HTTPS server can get hold of the certificate to use. This document describes additional (and common) use cases that fall into the major guiding use case for ACME as stated by [I-D.barnes-acme], "obtaining certificates for Web sites".

Authors

John Preuß Mattsson
Robert Skog

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)