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.

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

Section 4.9.2 Who can request revocation #59

Closed
jaspenc opened this issue Jan 18, 2017 · 4 comments · Fixed by #137
Closed

Section 4.9.2 Who can request revocation #59

jaspenc opened this issue Jan 18, 2017 · 4 comments · Fixed by #137

Comments

@jaspenc
Copy link

jaspenc commented Jan 18, 2017

For the FPKI Device Root, should the FPKIPA or other governing body be identified as authorized to request revocation?

@lachellel
Copy link
Contributor

Draft in section4 branch:

Added to 10

The technical content or format of the Certificate presents an unacceptable risk to Application Software Suppliers or Relying Parties (e.g. the FPKI Policy Authority or CA/Browser Forum might determine that a deprecated cryptographic/signature algorithm or key size presents an unacceptable risk and that such Certificates should be revoked and replaced by CAs within a given period of time)

@lachellel
Copy link
Contributor

Should it be stated explicitly in an addition (add 11 to the list)?

@LarryFrank
Copy link

For the FPKI Device Root, should the FPKIPA or other governing body be identified as authorized to request revocation?

Right now - says "The PMA SHALL direct any revocation of a CA certificate."

@lachellel
Copy link
Contributor

#137
ready for close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

3 participants