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

Improve language around holder binding #242

Closed
decentralgabe opened this issue Feb 23, 2024 · 0 comments · Fixed by #252
Closed

Improve language around holder binding #242

decentralgabe opened this issue Feb 23, 2024 · 0 comments · Fixed by #252
Assignees

Comments

@decentralgabe
Copy link
Collaborator

Currently, Section 5.1.3 with respect to the cnf property states:

If cnf is present in the JOSE Header or the JWT Claims , a verifier MAY use this parameter to identify a proof-of-possession key in the manner described in [RFC7800] for use in the verification process.

Related to this comment on the VC Data Model, I believe we should improve upon this language, especially for presentations, perhaps even to go as far as to require usage of the cnf property for presentations.

Another consideration is to speak to how the cnf property works with multiple subjects.

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

Successfully merging a pull request may close this issue.

2 participants