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

Update contact policy #9

Closed
gerv opened this issue Oct 30, 2017 · 0 comments
Closed

Update contact policy #9

gerv opened this issue Oct 30, 2017 · 0 comments

Comments

@gerv
Copy link
Contributor

gerv commented Oct 30, 2017

The CCADB stores a couple of different types of "contact" records:

  • Primary POC (1 or more): someone who is "authorized to speak for and to bind the CA that they represent."
  • POC (0 or more): Another contact at that CA.
  • Email Alias (1 or 2): defined as "more likely to continue working as personnel change".

All are per-organization values, and I don't believe any of them are published. However, this then leads to a question about which contacts should be used in what circumstances.

The Common CCADB Policy says:

"Notification of security and audit-related issues will be emailed to all POCs and the email aliases; CAs are advised to supply sufficient POCs that will enable them to respond to an issue promptly."

This is a bit of an administrative pain.

The proposal is that we change this to "email the primary POCs and CC the first email alias", to reduce the administrative burden on Root Stores.

Gerv

@gerv gerv closed this as completed Nov 3, 2017
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

1 participant