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

Adjust language in PR #99

Closed
OR13 opened this issue Sep 19, 2023 · 5 comments
Closed

Adjust language in PR #99

OR13 opened this issue Sep 19, 2023 · 5 comments
Assignees
Milestone

Comments

@OR13
Copy link
Collaborator

OR13 commented Sep 19, 2023

I don't love the language we added in:

If an issuer uses multiple DIDs (for instance, because their clients support different resolution methods), they MUST ensure that statements signed under each DID are consistent.

#95 (comment)

I said:

The verifier is interested in the authenticity of the issuer of the transparent statement and signed statement... The verifier trusts the TS to vet the issuer of the signed statement... the verifier benefits from the transparency service, if they can't trust the TS, there is no reason to do SCITT.

@OR13
Copy link
Collaborator Author

OR13 commented Sep 19, 2023

I suggest we remove the MUST here, and just say that verifiers are required to trust all issuer keys associated with issuer identifiers, in order to perform their role.

@SteveLasker
Copy link
Collaborator

@OR13, I just saw this. Can you this to a PR, and maybe update the Title of this issue?

@OR13
Copy link
Collaborator Author

OR13 commented Oct 23, 2023

I think the whole section on DIDs needs to be reworked.

Also the VCWG is currently trying to generalize the concept of DIDs to controller documents... And I'm starting to feel that perhaps it's better to remove references to them entirely.

@SteveLasker
Copy link
Collaborator

Closing, with the request to open a specific issue to DIDs, or build on #117 or #36

@SteveLasker
Copy link
Collaborator

Accidental re-open for the wrong issue

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

No branches or pull requests

2 participants