This is a minor update to address a few remaining comments by Ben.
Thanks,
Yaron
On 6/11/21, 11:27, "[email protected]" <[email protected]> wrote:
A new version of I-D, draft-ietf-acme-star-delegation-09.txt
has been successfully submitted by Yaron Sheffer and posted to the
IETF repository.
Name: draft-ietf-acme-star-delegation
Revision: 09
Title: An ACME Profile for Generating Delegated Certificates
Document date: 2021-06-11
Group: acme
Pages: 48
URL:
https://www.ietf.org/archive/id/draft-ietf-acme-star-delegation-09.txt
Status:
https://datatracker.ietf.org/doc/draft-ietf-acme-star-delegation/
Html:
https://www.ietf.org/archive/id/draft-ietf-acme-star-delegation-09.html
Htmlized:
https://datatracker.ietf.org/doc/html/draft-ietf-acme-star-delegation
Diff:
https://www.ietf.org/rfcdiff?url2=draft-ietf-acme-star-delegation-09
Abstract:
This document defines a profile of the Automatic Certificate
Management Environment (ACME) protocol by which the holder of an
identifier (e.g., a domain name) can allow a third party to obtain an
X.509 certificate such that the certificate subject is the delegated
identifier while the certified public key corresponds to a private
key controlled by the third party. A primary use case is that of a
Content Delivery Network (CDN, the third party) terminating TLS
sessions on behalf of a content provider (the holder of a domain
name). The presented mechanism allows the holder of the identifier
to retain control over the delegation and revoke it at any time.
Importantly, this mechanism does not require any modification to the
deployed TLS clients and servers.
The IETF Secretariat
_______________________________________________
Acme mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/acme
