Search RFCs

RFC Editor

File formats:

Also available:XML file for editing

 

Status:

PROPOSED STANDARD

Authors:

Y. Sheffer
D. López
A. Pastor Perales
T. Fossati

Stream:

IETF

Source:

acme (sec)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC9115

Discuss this RFC: Send questions or comments to the mailing listacme@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 9115

Abstract

This document defines a profile of the Automatic CertificateManagement Environment (ACME) protocol by which the holder of anidentifier (e.g., a domain name) can allow a third party to obtain anX.509 certificate such that the certificate subject is the delegatedidentifier while the certified public key corresponds to a privatekey controlled by the third party. A primary use case is that of aContent Delivery Network (CDN), the third party, terminating TLSsessions on behalf of a content provider (the holder of a domainname). The presented mechanism allows the holder of the identifierto retain control over the delegation and revoke it at any time. Importantly, this mechanism does not require any modification to thedeployed TLS clients and servers.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.