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

Add instructions for updating CAA Domains and Problem Reporting Mechanism as part of anual update (creation of Audit Case) #2

Closed
WilsonKathleen opened this issue Jul 18, 2017 · 1 comment

Comments

@WilsonKathleen
Copy link
Contributor

Please add instructions to http://ccadb.org/cas/updates about the "Recognized CAA Domains" and "Problem Reporting Mechanism" fields.

In #3 add bullet:
The 'Recognized CAA Domains' and 'Problem Reporting Mechanism' fields will be automatically filled in when you click on the 'Submit' button, so leave them blank to begin with. You can change them later if needed.

Then add another step (15?) for updating these two fields...
Check that the information in the 'Recognized CAA Domains' and 'Problem Reporting Mechanism' fields is current and of the correct format.
-- 'Recognized CAA Domains' should be a comma-separated list of Certification Authority Authorization (CAA) domain names recognized in a CAA record's issue and issue wild property tags.
-- 'Problem Reporting Mechanism' should provide brief instructions for reporting suspected Private Key Compromise, Certificate misuse, or other types of fraud, compromise, misuse, inappropriate conduct, or any other matter relating to certificates.

@gerv
Copy link
Contributor

gerv commented Jul 20, 2017

@WilsonKathleen: I went with:

  1. Check that the information in the 'Recognized CAA Domains' and 'Problem
    Reporting Mechanism' fields is current and of the correct format.
    • 'Recognized CAA Domains' should be a comma-separated list of domain names
      recognized in a CAA record's 'issue' and 'issuewild' property tags as
      permitting issuance under this root certificate.
    • 'Problem Reporting Mechanism' should provide brief instructions for
      reporting suspected misissuance, private key compromise, information
      inaccuracy or other types of problem relating to certificates issued
      under this root certificate.

Let me know if that wording is a problem at all. I wanted to avoid "misuse" given the lack of definition of that word.

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

No branches or pull requests

2 participants