ACME Challenges Using an Authority Token
draft-peterson-acme-authority-token-01

Document Type Expired Internet-Draft (individual)
Last updated 2018-09-06 (latest revision 2018-03-05)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
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-peterson-acme-authority-token-01.txt

Abstract

A number of proposed challenges for the Automated Certificate Management Environment (ACME) effectively rely on an external authority issuing a token according to a particular policy. This document specifies a generic Authority Token challenge for ACME which supports subtype claims different identifiers or namespaces that can be defined to represent a specific application of this Authority Token challenge.

Authors

Jon Peterson (jon.peterson@team.neustar)
Mary Barnes (mary.ietf.barnes@gmail.com)
David Hancock (davidhancock.ietf@gmail.com)
Chris Wendt (chris-ietf@chriswendt.net)

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