diff --git a/index.html b/index.html index fd4e9d5..da0e7c0 100644 --- a/index.html +++ b/index.html @@ -61,7 +61,7 @@ company: "Mesur.io", companyURL: "https://mesur.io/", w3cid: 130636 }, - { + { name: "Gabe Cohen", url: "https://github.com/decentralgabe", company: "Block", @@ -103,17 +103,24 @@ status: "Internet-Draft", publisher: "IETF" }, + "COSE-Sign-1": { + title: "CBOR Object Signing and Encryption (COSE): Structures and Process", + href: "https://datatracker.ietf.org/doc/html/draft-ietf-oauth-selective-disclosure-jwt", + authors: [ "Jim Schaad" ], + status: "Internet Standard", + publisher: "IETF" + }, "SD-JWT-VC": { title: "SD-JWT-based Verifiable Credentials (SD-JWT VC)", href: "https://datatracker.ietf.org/doc/html/draft-ietf-oauth-sd-jwt-vc", - authors: [ "Oliver Terbu", "Daniel Fett" ], + authors: [ "Oliver Terbu", "Daniel Fett", "Brian Campbell" ], status: "Internet-Draft", publisher: "IETF" }, "MULTIPLE-SUFFIXES": { title: "Media Types with Multiple Suffixes", href: "https://datatracker.ietf.org/doc/draft-ietf-mediaman-suffixes/", - authors: [ "Manu Sporny" , "Amy Guy" ], + authors: [ "Manu Sporny" , "Amy Guy" ], status: "Internet-Draft", publisher: "IETF" }, @@ -279,7 +286,7 @@

Securing JSON-LD Verifiable Presentations with JOSE

[[RFC7515]] MAY be used to secure this media type. The typ header parameter SHOULD be vp+ld+json+sd-jwt. - When present, the cty header parameter SHOULD be vp+ld+json. + When present, the cty header parameter SHOULD be vp+ld+json. See Registered Header Parameter Names for additional details regarding usage of typ and cty. @@ -359,7 +366,7 @@

Securing JSON-LD Verifiable Presentations with COSE

[[RFC9052]] MAY be used to secure this media type. The typ header parameter SHOULD be application/vp+ld+json+sd-jwt. - When present, the cty header parameter SHOULD be application/vp+ld+json. + When present, the cty header parameter SHOULD be application/vp+ld+json. See Common COSE Header Parameters for additional details.

@@ -380,9 +387,9 @@

JOSE Header Parameters and JWT Claims

The normative statements in - Registered Header Parameter Names, + Registered Header Parameter Names, JOSE Header, and - Replicating Claims as Header Parameters + Replicating Claims as Header Parameters apply to securing credentials and presentations.

@@ -391,8 +398,8 @@

JOSE Header Parameters and JWT Claims

It is RECOMMENDED to use - the IANA JSON Web Token Claims registry and - the IANA JSON Web Signature and Encryption Header Parameters registry + the IANA JSON Web Token Claims registry and + the IANA JSON Web Signature and Encryption Header Parameters registry to identify any claims and header parameters that might be confused with members defined by [[VC-DATA-MODEL-2.0]]. These include but are not limited to: iss, kid, @@ -412,7 +419,7 @@

JOSE Header Parameters and JWT Claims

Additional members may be present as header parameters and claims. - If they are not understood, they MUST be ignored. + If they are not understood, they MUST be ignored.

@@ -433,15 +440,15 @@

COSE Header Parameters and CWT Claims

The normative statements in - Registered Header Parameter Names, + Registered Header Parameter Names, Claims, and - CBOR Web Token (CWT) Claims in COSE Headers + CBOR Web Token (CWT) Claims in COSE Headers apply to securing credentials and presentations.

It is RECOMMENDED to use - the IANA CBOR Web Token Claims registry and - the IANA COSE Header Parameters registry + the IANA CBOR Web Token Claims registry and + the IANA COSE Header Parameters registry to identify any claims and header parameters that might be confused with members defined by [[VC-DATA-MODEL-2.0]]. These include but are not limited to: iss, kid, @@ -457,7 +464,7 @@

COSE Header Parameters and CWT Claims

Additional members may be present as header parameters and claims. - If they are not understood, they MUST be ignored. + If they are not understood, they MUST be ignored.

@@ -550,7 +557,7 @@

Key Discovery

When iss is present and is a [[URL]], the kid MUST match a key discovered via a JWT Issuer Metadata Request, - as described in [[SD-JWT-VC]]. + as described in [[SD-JWT-VC]].

@@ -1157,7 +1164,7 @@

Securing Verifiable Credentials

with JSON Web Tokens. When content types from [[VC-DATA-MODEL-2.0]] are secured using JSON Web Tokens, the header parameter "alg": "none", - MUST be used to communicate that a JWT Claims Set (a + MUST be used to communicate that a JWT Claims Set (a Verifiable Credential or a Verifiable Presentation) has no integrity protection. When a JWT Claims Set (a Verifiable Credential or a @@ -1305,6 +1312,105 @@

application/vp+ld+json+sd-jwt

+ +
+

application/vc+ld+json+cose

+

+ This specification registers the + application/vc+ld+json+cose Media Type specifically for + identifying a cose-sign1, as described in + conforming to the Verifiable Credential Data Model. +

+

+ Remove this note before publishing, see this similar example: + + application/voucher+cose + +

+ + + + + + + + + + + + + + + + + + + + + + + + + +
Type name: `application`
Subtype name: `vc+ld+json+cose`
Required parameters: None
Encoding considerations: + binary (CBOR) +
Security considerations: +

As defined in this specification. See also the security + considerations in .

+
Contact: + W3C Verifiable Credentials Working Group public-vc-wg@w3.org +
+
+
+

application/vp+ld+json+cose

+

+ This specification registers the + application/vp+ld+json+cose Media Type specifically for + identifying a cose-sign1, as described in + conforming to the Verifiable Credential Data Model. +

+

+ Remove this note before publishing, see this similar example: + + application/voucher+cose + +

+ + + + + + + + + + + + + + + + + + + + + + + + + +
Type name: `application`
Subtype name: `vp+ld+json+cose`
Required parameters: None
Encoding considerations: + binary (CBOR) +
Security considerations: +

As defined in this specification. See also the security + considerations in .

+
Contact: + W3C Verifiable Credentials Working Group public-vc-wg@w3.org +
+
@@ -1784,4 +1890,4 @@

Validation Algorithm

- + \ No newline at end of file