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

Don't require CAs to cap lifetime or check CAA until May 1. #396

Merged
merged 1 commit into from
Mar 1, 2019
Merged

Don't require CAs to cap lifetime or check CAA until May 1. #396

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions draft-yasskin-http-origin-signed-responses.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -999,6 +999,9 @@ as invalid. Instead:
* After 2019-08-01, clients MUST reject all certificates with this extension
that have a Validity Period longer than 90 days.

The above requirements on CAs to limit the Validity Period and check for a CAA
parameter are effective starting 2019-05-01.

### Extensions to the CAA Record: cansignhttpexchanges Parameter {#caa-cansignhttpexchanges}

A CAA parameter "cansignhttpexchanges" is defined for the "issue" and
Expand Down