Automatic Certificate Management Environment (ACME)
draft-barnes-acme-04

Document Type Replaced Internet-Draft (individual)
Last updated 2016-01-22 (latest revision 2015-07-21)
Replaced by draft-ietf-acme-acme
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-acme-acme
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-barnes-acme-04.txt

Abstract

Certificates in the Web's X.509 PKI (PKIX) are used for a number of purposes, the most significant of which is the authentication of domain names. Thus, certificate authorities in the Web PKI are trusted to verify that an applicant for a certificate legitimately represents the domain name(s) in the certificate. Today, this verification is done through a collection of ad hoc mechanisms. This document describes a protocol that a certificate authority (CA) and an applicant can use to automate the process of verification and certificate issuance. The protocol also provides facilities for other certificate management functions, such as certificate revocation.

Authors

Richard Barnes (rlb@ipv.sx)
Jacob Hoffman-Andrews (jsha@eff.org)
James Kasten (jdkasten@umich.edu)

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