<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=iso-2022-jp"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:SimSun;
mso-fareast-language:ZH-CN;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
p.xxmsonormal, li.xxmsonormal, div.xxmsonormal
{mso-style-name:x_x_msonormal;
margin:0in;
font-size:12.0pt;
font-family:SimSun;
mso-fareast-language:ZH-CN;}
p.xxgmail-m945014664908734494msolistparagraph, li.xxgmail-m945014664908734494msolistparagraph, div.xxgmail-m945014664908734494msolistparagraph
{mso-style-name:x_x_gmail-m_945014664908734494msolistparagraph;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:SimSun;
mso-fareast-language:ZH-CN;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1646858621;
mso-list-template-ids:1464626796;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>Not quite the case as there are specific rules for encoding and decoding JWT in the verifiable credential specification and how to process certain JWT claims iss, aud, etc. So I$B!G(Bm still confused what you are trying to accomplish.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Kristina Yasuda <Kristina.Yasuda@microsoft.com> <br><b>Sent:</b> Wednesday, April 7, 2021 6:53 PM<br><b>To:</b> Artifact Binding/Connect Working Group <openid-specs-ab@lists.openid.net><br><b>Cc:</b> Anthony Nadalin <nadalin@prodigy.net>; oliver.terbu@mesh.xyz<br><b>Subject:</b> Re: [Openid-specs-ab] Defining JWT Claims to represent W3C Verifiable Credentials objects<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><span style='font-family:"Calibri",sans-serif;color:black'>VC specification defined `vp`, `vc` claims, but they are defined only to include "tthose parts of the standard verifiable credentials and verifiable presentations where no explicit encoding rules for JWT exist". Hence `vp`, `vc` claims are only a part of the the entire VP, VC. <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri",sans-serif;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri",sans-serif;color:black;background:white'>There is a need a define a standard way to return VPs using OpenID Connect, and the proposal is to use `vp_jwt`, `vp_ldp` claims that would include entire VP inside the ID token. (VP in a JWT format inside `vp_jwt` would include `vp` claim) </span><span style='font-family:"Calibri",sans-serif;color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri",sans-serif;color:black;background:white'>Example can be found here: <a href="https://hackmd.io/grbDXDHqTE6lhu6fvVFIuA">Examples for the vp_jwt, vp_ldp proposal - HackMD</a></span><span style='font-family:"Calibri",sans-serif;color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri",sans-serif;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri",sans-serif;color:black'>Note that this proposal is intended to work not only with SIOP V2, but also if VPs are to be returned from the user_info endpoint for example.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri",sans-serif;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri",sans-serif;color:black;background:white'>Best,</span><span style='font-family:"Calibri",sans-serif;color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri",sans-serif;color:black;background:white'>Kristina</span><span style='font-family:"Calibri",sans-serif;color:black'><o:p></o:p></span></p></div><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="98%" align=center></div><div id=divRplyFwdMsg><p class=MsoNormal><b><span lang=ZH-CN style='font-size:11.0pt;color:black'>$B:9=P?M(B</span></b><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'>:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'> Openid-specs-ab <<a href="mailto:openid-specs-ab-bounces@lists.openid.net">openid-specs-ab-bounces@lists.openid.net</a>> </span><span lang=ZH-CN style='font-size:11.0pt;color:black'>$B$,(B</span><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'> ANTHONY NADALIN via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a>> </span><span lang=ZH-CN style='font-size:11.0pt;color:black'>$B$NBeM}$GAw?.(B</span><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'><br></span><b><span lang=ZH-CN style='font-size:11.0pt;color:black'>$BAw?.F|;~(B</span></b><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'>:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'> 2021</span><span lang=ZH-CN style='font-size:11.0pt;color:black'>$BG/(B</span><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'>4</span><span lang=ZH-CN style='font-size:11.0pt;color:black'>$B7n(B</span><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'>8</span><span lang=ZH-CN style='font-size:11.0pt;color:black'>$BF|(B</span><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'> 10:09<br></span><b><span lang=ZH-CN style='font-size:11.0pt;color:black'>$B08@h(B</span></b><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'>:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'> Artifact Binding/Connect Working Group <<a href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a>><br><b>CC:</b> Anthony Nadalin <<a href="mailto:nadalin@prodigy.net">nadalin@prodigy.net</a>>; <a href="mailto:oliver.terbu@mesh.xyz">oliver.terbu@mesh.xyz</a> <<a href="mailto:oliver.terbu@mesh.xyz">oliver.terbu@mesh.xyz</a>><br></span><b><span lang=ZH-CN style='font-size:11.0pt;color:black'>$B7oL>(B</span></b><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'>:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'> Re: [Openid-specs-ab] Defining JWT Claims to represent W3C Verifiable Credentials objects</span> <o:p></o:p></p><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Arial",sans-serif;color:black'>I don't quite understand this proposal as if you read the verifiable credential specification you will see a section called JWT encoding and JWT decoding based upon what Mike is written I don't understand how you could abide by a fully compliant verifiable credential specification without encoding and decoding JWT's into verifiable credentials.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Arial",sans-serif;color:black'><o:p> </o:p></span></p></div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Arial",sans-serif;color:black'>Get <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2FAAb9ysg&data=04%7C01%7CKristina.Yasuda%40microsoft.com%7C692e57f56b6a438a91ab08d8fa2d9bad%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637534421379557988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=FnWyXWRCNoPtQ%2FoIYYiXJKqx%2BPdJwGjmPDNEm%2BgyZ3I%3D&reserved=0">Outlook for Android</a><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Arial",sans-serif;color:black'><o:p> </o:p></span></p></div><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="98%" align=center></div><div id="x_divRplyFwdMsg"><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'> Openid-specs-ab <<a href="mailto:openid-specs-ab-bounces@lists.openid.net">openid-specs-ab-bounces@lists.openid.net</a>> on behalf of Tom Jones via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a>><br><b>Sent:</b> Wednesday, April 7, 2021 6:00:29 PM<br><b>To:</b> Artifact Binding/Connect Working Group <<a href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a>><br><b>Cc:</b> Tom Jones <<a href="mailto:thomasclinganjones@gmail.com">thomasclinganjones@gmail.com</a>>; <a href="mailto:oliver.terbu@mesh.xyz">oliver.terbu@mesh.xyz</a> <<a href="mailto:oliver.terbu@mesh.xyz">oliver.terbu@mesh.xyz</a>><br><b>Subject:</b> Re: [Openid-specs-ab] Defining JWT Claims to represent W3C Verifiable Credentials objects</span> <o:p></o:p></p><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><div><p class=MsoNormal>I have an alternate proposal. In my system the claim should have a name that represents what it is. For example the existing claims acr and amr should be enabled to carry a vc or vp as its value. In this system the encoding of the value would carry the syntax of the claim, beit vc-sjon, vc-ld or whatever. The one proposal I did make was to use jose encoding. If we wanted to use this the jose header could contain the syntax of the contained element as Mike has indicated in his proposal. <o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I think it is not helpful for the name of the claim to be just the syntax of the element.<o:p></o:p></p></div><div><p class=MsoNormal><br clear=all><o:p></o:p></p><div><div><div><div><p class=MsoNormal><span style='font-size:10.5pt;color:black;background:#F2F2F2'>Be the change you want to see in the world </span>..tom<o:p></o:p></p></div></div></div></div><p class=MsoNormal><o:p> </o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Wed, Apr 7, 2021 at 5:25 PM Mike Jones via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p class=xxmsonormal>In our discussions over the past few months, it$B!G(Bs become clear that there are multiple use cases where different forms of W3C Verifiable Credential objects will be communicated as JWT claims (or as UserInfo Endpoint claims). I had a useful conversation with Oliver Terbu and Kristina Yasuda this week during which we agreed that it would be useful to write a short, focused specification defining and registering JWT claims enabling standard representations for this purpose. These claims could be used both by SIOP use cases and other use cases.<o:p></o:p></p><p class=xxmsonormal> <o:p></o:p></p><p class=xxmsonormal>Bear in mind that the W3C Verifiable Credentials specification defines two representations of the objects that it defines – JWT and JSON-LD and it also orthogonally defines two kinds of objects – Verifiable Credentials and Verifiable Presentations. Thus, there are actually four different data types that these use cases might want to utilize.<o:p></o:p></p><p class=xxmsonormal> <o:p></o:p></p><p class=xxmsonormal>I would therefore propose the following four claim definitions for these purposes:<o:p></o:p></p><p class=xxmsonormal> <o:p></o:p></p><ul type=disc><li class=xxgmail-m945014664908734494msolistparagraph style='mso-list:l0 level1 lfo1'><b><span style='font-family:"Courier New"'>vc_jwt</span></b>: A claim whose value is a W3C Verifiable Credential object using the JWT representation, which is a JSON string. The claim$B!G(Bs value may also be an array of W3C Verifiable Credential objects using the JWT representation if the use case calls for multiple JWT VCs.<o:p></o:p></li><li class=xxgmail-m945014664908734494msolistparagraph style='mso-list:l0 level1 lfo1'><b><span style='font-family:"Courier New"'>vp_jwt</span></b>: A claim whose value is a W3C Verifiable Presentation object using the JWT representation, which is a JSON string. The claim$B!G(Bs value may also be an array of W3C Verifiable Presentation objects using the JWT representation if the use case calls for multiple JWT VPs.<o:p></o:p></li><li class=xxgmail-m945014664908734494msolistparagraph style='mso-list:l0 level1 lfo1'><b><span style='font-family:"Courier New"'>vc_ld</span></b>: A claim whose value is a W3C Verifiable Credential object using the JSON-LD representation, which is a JSON object. The claim$B!G(Bs value may also be an array of W3C Verifiable Credential objects using the JSON-LD representation if the use case calls for multiple JSON-LD VCs.<o:p></o:p></li><li class=xxgmail-m945014664908734494msolistparagraph style='mso-list:l0 level1 lfo1'><b><span style='font-family:"Courier New"'>vp_ld</span></b>: A claim whose value is a W3C Verifiable Presentation object using the JSON-LD representation, which is a JSON object. The claim$B!G(Bs value may also be an array of W3C Verifiable Presentation objects using the JSON-LD representation if the use case calls for multiple JSON-LD VPs.<o:p></o:p></li></ul><p class=xxmsonormal> <o:p></o:p></p><p class=xxmsonormal>Let$B!G(Bs discuss this proposal during the European-friendly Connect call ~13.5 hours from now.<o:p></o:p></p><p class=xxmsonormal> <o:p></o:p></p><p class=xxmsonormal> -- Mike<o:p></o:p></p><p class=xxmsonormal> <o:p></o:p></p></div></div><p class=MsoNormal>_______________________________________________<br>Openid-specs-ab mailing list<br><a href="mailto:Openid-specs-ab@lists.openid.net" target="_blank">Openid-specs-ab@lists.openid.net</a><br><a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.openid.net%2Fmailman%2Flistinfo%2Fopenid-specs-ab&data=04%7C01%7CKristina.Yasuda%40microsoft.com%7C692e57f56b6a438a91ab08d8fa2d9bad%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637534421379557988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=t%2Bg7TOqpJ6MugoogevZ2ga8oCZuxQCVPf5e2GajhTAA%3D&reserved=0" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><o:p></o:p></p></blockquote></div></div></div></div></body></html>