Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ACME Disclosure in CPS #569

Open
srdavidson opened this issue Jan 14, 2025 · 2 comments
Open

ACME Disclosure in CPS #569

srdavidson opened this issue Jan 14, 2025 · 2 comments
Labels
baseline-requirements Server Certificate CWG - Baseline Requirements

Comments

@srdavidson
Copy link

The use of automation for TLS lifecycle management is a major force in the WebPKI and is emphasized in root program requirements. It makes sense to define a CPS section for CAs to document their adoption of ACME and/or equivalent methods of certificate lifecycle automation.

The CPS section could also be used in the S/MIME BR, should the adoption of ACME for S/MIME (RFC 8823) proceed there.
@srdavidson srdavidson added the baseline-requirements Server Certificate CWG - Baseline Requirements label Jan 14, 2025
@github-actions GitHub Actions
Copy link

This issue was created based on:

  • TLS BR Version 2.1.2
  • EVG Version 2.0.1

@srdavidson
Copy link
Author

Starting point for discussion:
b7fd69b...d459457

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
baseline-requirements Server Certificate CWG - Baseline Requirements
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@srdavidson