vc+jwt
OR13 opened this issue · comments
Orie Steele commented
Before w3c/vc-jose-cose#88 can be closed, this draft must request registration for vc+jwt
.
Example text:
### application/vc+jwt {#application-vc-jwt}
The Internet media type for a JWT VC is `application/vc+jwt`.
Type name: : `application`
Subtype name: : `vc+jwt`
Required parameters: : n/a
Optional parameters: : n/a
Encoding considerations: : binary; A VC JWT is a JWT; JWT values are encoded as a series of base64url-encoded values (some of which may be the empty string) separated by period ('.') characters.
Security considerations: : See Security Considerations in (#security-considerations).
Interoperability considerations: : n/a
- Published specification: : RFC TODO
- Applications that use this media type: : Applications that issue, present,
verify verifiable credentials and presentations.
- Additional information:
- Magic number(s): n/a
- File extension(s): n/a
- Macintosh file type code(s): n/a
- Person & email address to contact for further information: TBD
- Intended usage: COMMON
- Restrictions on usage: none
- Author: Oliver Terbu <oliver.terbu@spruceid.com>
- Change controller: IETF
Oliver Terbu commented
Can you give an example of how this media type is used in the spec? Ideally, you could provide an example of the header+payload.
Oliver Terbu commented
@OR13 Haven't we agreed that we would use vc+sd-jwt
to represent non-selective-disclosable SD-JWTs which are plain JWTs? Why is it still required to register this?
Orie Steele commented
@awoie I didn't agree to that... but regardless, you are walking into an easy argument if you are encouraging token confusion.
Torsten Lodderstedt commented
Let's discuss in the upcoming meeting.
Orie Steele commented
Suggest closing
Oliver Terbu commented
Closing this issue since we agreed to use vc+sd-jwt.