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

Jump to bottom

Add a MUST statement preventing 2 entries from having the same statusPurpose #173

Open
PatStLouis opened this issue Jul 24, 2024 · 0 comments
Open

Add a MUST statement preventing 2 entries from having the same statusPurpose #173

PatStLouis opened this issue Jul 24, 2024 · 0 comments
Labels
CR1 This item was processed during the first Candidate Recommendation phase. discuss This issue is a discussion with no clear change requested normative The item is normative in nature.

Comments

@PatStLouis
Copy link
Contributor

It would be advisable to prevent issuers from including 2 entries with the same statusPurpose. Or at the very least say that if 2 same purposes are included, each entry MUST have an id field.

Is there use cases where an issuer might want to provide 2 separate revocation entries? I could see it being a thing, however there needs to be a way to differentiate them both based on a unique id.
@msporny msporny added normative The item is normative in nature. CR1 This item was processed during the first Candidate Recommendation phase. labels Sep 16, 2024
@msporny msporny added the discuss This issue is a discussion with no clear change requested label Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
CR1 This item was processed during the first Candidate Recommendation phase. discuss This issue is a discussion with no clear change requested normative The item is normative in nature.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@msporny @PatStLouis