Hi,
This version of the draft overhauls the CSR template that defines what
parameters the Name Delegation Client is allowed to use in its certificate
request.
This is work in progress, and we expect to publish another version before
Vancouver.
Thanks,
Yaron
On 2/18/20, 14:40, "[email protected]" <[email protected]> wrote:
A new version of I-D, draft-ietf-acme-star-delegation-02.txt
has been successfully submitted by Yaron Sheffer and posted to the
IETF repository.
Name: draft-ietf-acme-star-delegation
Revision: 02
Title: An ACME Profile for Generating Delegated STAR
Certificates
Document date: 2020-02-18
Group: acme
Pages: 19
URL:
https://www.ietf.org/internet-drafts/draft-ietf-acme-star-delegation-02.txt
Status:
https://datatracker.ietf.org/doc/draft-ietf-acme-star-delegation/
Htmlized:
https://tools.ietf.org/html/draft-ietf-acme-star-delegation-02
Htmlized:
https://datatracker.ietf.org/doc/html/draft-ietf-acme-star-delegation
Diff:
https://www.ietf.org/rfcdiff?url2=draft-ietf-acme-star-delegation-02
Abstract:
This memo proposes a profile of the ACME protocol that allows the
owner of an identifier (e.g., a domain name) to delegate to a third
party access to a certificate associated with said identifier. A
primary use case is that of a CDN (the third party) terminating TLS
sessions on behalf of a content provider (the owner of a domain
name). The presented mechanism allows the owner of the identifier to
retain control over the delegation and revoke it at any time by
cancelling the associated STAR certificate renewal with the ACME CA.
Another key property of this mechanism is it does not require any
modification to the deployed TLS ecosystem.
Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.
The IETF Secretariat
_______________________________________________
Acme mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/acme
