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

Revocation of PAA/PAI: by Trustees #460

Open
ashcherbakov opened this issue Mar 23, 2023 · 3 comments
Open

Revocation of PAA/PAI: by Trustees #460

ashcherbakov opened this issue Mar 23, 2023 · 3 comments

Comments

@ashcherbakov
Copy link
Contributor

User Stories:

  • Revocation of PAI (by Trustees): A Trustee can propose a transaction to publish the location of the CRL distribution point for a PAA. This SHALL require approval of two thirds of the trustees vote.
  • Revocation of DAC (by Trustees): A Trustee can propose a transaction to publish the location of the CRL distribution point for a PAI. This SHALL require approval of two thirds of the trustees vote.

Acceptance criteria:

@ashcherbakov ashcherbakov added this to Backlog in DCL via automation Mar 23, 2023
@ashcherbakov ashcherbakov moved this from Backlog to To do in DCL Mar 23, 2023
@ashcherbakov ashcherbakov moved this from To do to Backlog in DCL Apr 28, 2023
@ashcherbakov
Copy link
Contributor Author

It seems this feature is not needed and can go to backlog.

@jcps07
Copy link
Contributor

jcps07 commented Nov 30, 2023

@ashcherbakov , should we close or update this? Is it different from the current revocation implementation?

@ashcherbakov
Copy link
Contributor Author

@jcps07
It's just another way to publish revocation lists. In the current implementation revocation is published by Vendors (owners of corresponding certificates). This ticket proposes to allow Trustees (quorum of Trustees) to publish the revocation info as well.
If we decide that this feature is not needed - then we can close the task.
If we think that it can be useful in future - we can keep it in the backlog.

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