{"id":2734,"date":"2025-07-09T12:12:58","date_gmt":"2025-07-09T19:12:58","guid":{"rendered":"https:\/\/self-issued.info\/?p=2734"},"modified":"2025-07-09T12:12:58","modified_gmt":"2025-07-09T19:12:58","slug":"more-spiceyness","status":"publish","type":"post","link":"https:\/\/self-issued.info\/?p=2734","title":{"rendered":"More SPICEyness"},"content":{"rendered":"<p><span class=\"plain\"><img decoding=\"async\" align=\"right\" src=\"https:\/\/self-issued.info\/images\/ietf-logo.png\" alt=\"IETF logo\"><\/span><\/span>In April, <a href=\"https:\/\/self-issued.info\/?p=2650\">I wrote about several useful developments<\/a> in the IETF <a href=\"https:\/\/datatracker.ietf.org\/wg\/spice\/about\/\">Secure Patterns for Internet CrEdentials (SPICE)<\/a> working group.  I&#8217;ve recently contributed to progressing several specifications in preparation for the SPICE working group meeting at <a href=\"https:\/\/www.ietf.org\/meeting\/123\/\">IETF 123 in Madrid<\/a>.  Here&#8217;s a tour&#8230;<\/p>\n<p>I&#8217;ve become a contributor to the <a href=\"https:\/\/datatracker.ietf.org\/doc\/draft-ietf-spice-sd-cwt\/\">Selective Disclosure CWT (SD-CWT)<\/a> specification.  The <a href=\"https:\/\/www.ietf.org\/archive\/id\/draft-ietf-spice-sd-cwt-04.html\">draft we just published<\/a> in preparation for IETF 123 contains significant enhancements, including better alignment with both <a href=\"https:\/\/datatracker.ietf.org\/doc\/draft-ietf-oauth-selective-disclosure-jwt\/\">SD-JWT<\/a> and <a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc8392\">CWT<\/a>, clearer and simpler specification of the use of encryption, creation of the Verifiable Credential Type Identifiers registry, using a CBOR simple value for redacted claims, and numerous editorial improvements.  See the <a href=\"https:\/\/www.ietf.org\/archive\/id\/draft-ietf-spice-sd-cwt-04.html#name-draft-ietf-spice-sd-cwt-04\">history entry<\/a> for more details.  This was joint work with <a href=\"https:\/\/www.linkedin.com\/in\/rohan-mahy-70985\/\">Rohan Mahy<\/a> and <a href=\"https:\/\/www.linkedin.com\/in\/or13b\/\">Orie Steele<\/a>.<\/p>\n<p>I&#8217;ve become an editor of the <a href=\"https:\/\/datatracker.ietf.org\/doc\/draft-ietf-spice-oidc-cwt\/\">OpenID Connect Standard Claims Registration for CBOR Web Tokens<\/a> specification, along with <a href=\"https:\/\/www.linkedin.com\/in\/beltram-%F0%9F%A6%80-maldant-2930b880\/\">Beltram Maldant<\/a>.  It creates <a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc8392\">CWT<\/a> equivalents of the <a href=\"https:\/\/openid.net\/specs\/openid-connect-core-1_0.html#StandardClaims\">standard JWT claims defined by OpenID Connect<\/a>.  The <a href=\"https:\/\/www.ietf.org\/archive\/id\/draft-ietf-spice-oidc-cwt-01.html\">draft we just published<\/a> in preparation for IETF 123 aligns the terminology used with <a href=\"https:\/\/openid.net\/connect\">OpenID Connect<\/a>.  I believe it&#8217;s ready for working group last call.<\/p>\n<p><a href=\"https:\/\/www.linkedin.com\/in\/bzundel\/\">Brent Zundel<\/a> and I updated the <a href=\"https:\/\/datatracker.ietf.org\/doc\/draft-ietf-spice-glue-id\/\">GLobal Unique Enterprise (GLUE) Identifiers<\/a> specification to fix some links and update his association to <a href=\"https:\/\/tradeverifyd.com\/\">Tradeverifyd<\/a>.  I believe this one is also ready for working group last call.<\/p>\n<p>Finally, Brent and I updated the <a href=\"https:\/\/datatracker.ietf.org\/doc\/draft-prorock-spice-cwt-traceability-claims\/\">Traceability Claims<\/a> specification to tighten up many of the claim definitions.  See the <a href=\"https:\/\/www.ietf.org\/archive\/id\/draft-prorock-spice-cwt-traceability-claims-02.html#name-document-history\">history entries<\/a> for details.<\/p>\n<p>I&#8217;m looking forward to continued progress at the SPICE meeting in two weeks!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In April, I wrote about several useful developments in the IETF Secure Patterns for Internet CrEdentials (SPICE) working group. I&#8217;ve recently contributed to progressing several specifications in preparation for the SPICE working group meeting at IETF 123 in Madrid. Here&#8217;s a tour&#8230; I&#8217;ve become a contributor to the Selective Disclosure CWT (SD-CWT) specification. The draft [&hellip;]<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29,8,32,25],"tags":[],"class_list":["post-2734","post","type-post","status-publish","format-standard","hentry","category-cbor","category-claims","category-ietf","category-specifications"],"_links":{"self":[{"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/posts\/2734","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/self-issued.info\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2734"}],"version-history":[{"count":2,"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/posts\/2734\/revisions"}],"predecessor-version":[{"id":2736,"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/posts\/2734\/revisions\/2736"}],"wp:attachment":[{"href":"https:\/\/self-issued.info\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2734"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/self-issued.info\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2734"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/self-issued.info\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2734"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}