<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=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Hi everyone,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’m Richard Barnes from Cisco. I’m new to OpenID, but might be familiar to some folks from the IETF, where I’ve worked on crypto things like TLS, MLS, and ACME (and JOSE back in the day).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I wanted to bring to the group some proposed new work on “UserInfo Verifiable Credentials” that I’ve been working on with Kristina Yasuda, Pieter Kasselman, and Morteza Ansari.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">MD: <a href="https://github.com/bifurcation/userinfo-vc/blob/main/userinfo-vc.md">
https://github.com/bifurcation/userinfo-vc/blob/main/userinfo-vc.md</a><o:p></o:p></p>
<p class="MsoNormal">HTML: <a href="https://bifurcation.github.io/userinfo-vc">https://bifurcation.github.io/userinfo-vc</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The high-level idea here is to take the OpenID for Verifiable Credential Issuance spec and give it the same level of easy interoperability as OpenID Connect. The generality of the VCI mechanism is powerful, but means the wallet and issuer
need to agree on a bunch of details, each of which is a chance for interop failure.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Concretely, the proposal is to define a profile of VC and VCI that is tailored to OpenID Connect. A “UserInfo VC” carries the same claims that are provided by the UserInfo endpoint, wrapped as a VC. The issuance process is just VCI with
certain knobs pre-set (e.g., proof of possession is always via a JWT).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We would love to see this work adopted by this WG. In any case, feedback welcome!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal">--Richard<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>