<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=us-ascii">
<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">SIOP Special Call Notes 13-May-21<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Kristina Yasuda<o:p></o:p></p>
<p class="MsoNormal">Mike Jones<o:p></o:p></p>
<p class="MsoNormal">Adrian Gropper - Brings a patient perspective to identity discussions<o:p></o:p></p>
<p class="MsoNormal">Jo Vercammen - CTO for Meeco, in Belgium<o:p></o:p></p>
<p class="MsoNormal">David Chadwick - CEO of Verifiable Credentials Ltd. - spinout from University of Kent, Covid Credentials with OpenID Connect<o:p></o:p></p>
<p class="MsoNormal">Oliver Terbu<o:p></o:p></p>
<p class="MsoNormal">Torsten Lodderstedt<o:p></o:p></p>
<p class="MsoNormal">Tony Nadalin<o:p></o:p></p>
<p class="MsoNormal">Nat Sakimura<o:p></o:p></p>
<p class="MsoNormal">Justin Richer<o:p></o:p></p>
<p class="MsoNormal">Adam Lemmon<o:p></o:p></p>
<p class="MsoNormal">Pamela Dingle<o:p></o:p></p>
<p class="MsoNormal">Jeremie Miller<o:p></o:p></p>
<p class="MsoNormal">Tim Cappalli<o:p></o:p></p>
<p class="MsoNormal">Alen Horvat<o:p></o:p></p>
<p class="MsoNormal">David Waite (DW)<o:p></o:p></p>
<p class="MsoNormal">John Bradley<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Relationship between Claims Aggregation and OIDC4VCO drafts<o:p></o:p></p>
<p class="MsoNormal"> Tony spoke to his desire to see the drafts merged<o:p></o:p></p>
<p class="MsoNormal"> He believes that they're solving the same problem at the high level<o:p></o:p></p>
<p class="MsoNormal"> He wants to avoid having two ways to deliver sets of claims<o:p></o:p></p>
<p class="MsoNormal"> David Chadwick said that verifiable credentials are a single package, versus sets of claims<o:p></o:p></p>
<p class="MsoNormal"> He said that with VPs, it's not an OpenID Provider doing the packaging<o:p></o:p></p>
<p class="MsoNormal"> Tony said that it could be<o:p></o:p></p>
<p class="MsoNormal"> Torsten said that claims aggregation is a packaging mechanism<o:p></o:p></p>
<p class="MsoNormal"> He said that we could investigate whether aggregated claims are suitable for delivering VPs<o:p></o:p></p>
<p class="MsoNormal"> He said that the Claims Aggregation draft fills in gaps left in OpenID Connect Core<o:p></o:p></p>
<p class="MsoNormal"> He reported that the special group and IIW thought that other mechanisms could be used instead of aggregated claims<o:p></o:p></p>
<p class="MsoNormal"> Nat said that the Claims Aggregation draft also talks about presentation<o:p></o:p></p>
<p class="MsoNormal"> Torsten disagreed<o:p></o:p></p>
<p class="MsoNormal"> Nat said that the current writing is a bit muddled, but it is talking about presentation<o:p></o:p></p>
<p class="MsoNormal"> Nat has filed issues about improving the text<o:p></o:p></p>
<p class="MsoNormal"> Torsten said that we need request syntax for requesting verifiable presentations<o:p></o:p></p>
<p class="MsoNormal"> Torsten said that the OIDC4VCO draft hasn't yet been accepted by the working group<o:p></o:p></p>
<p class="MsoNormal"> Nat said that the call for adoption was done just a week ago<o:p></o:p></p>
<p class="MsoNormal"> The adoption decision should occur by consensus<o:p></o:p></p>
<p class="MsoNormal"> This discussion is happening as a result of concerns raised<o:p></o:p></p>
<p class="MsoNormal"> This is explained in issue #1229<o:p></o:p></p>
<p class="MsoNormal"> Torsten was in favor of aggregated claims but is concerned that the WG and IIW said that that was not preferred<o:p></o:p></p>
<p class="MsoNormal"> Nat suggested possibly including the approach in OIDC4VCO in the Claims Aggregation draft<o:p></o:p></p>
<p class="MsoNormal"> Pam expressed that these things could be addressed separately<o:p></o:p></p>
<p class="MsoNormal"> Torsten thought that it would be more efficient for WG members to read both drafts and form their own opinions<o:p></o:p></p>
<p class="MsoNormal"> Nat said that it's normal for things to change after adoption<o:p></o:p></p>
<p class="MsoNormal"> Mike spoke up in favor adopting the existing draft<o:p></o:p></p>
<p class="MsoNormal"> He said that we can later merge things if it makes sense - just as we did with the Messages and Standard drafts<o:p></o:p></p>
<p class="MsoNormal"> Nat said that, as chair, he's working towards consensus<o:p></o:p></p>
<p class="MsoNormal"> Tony said that he wants to understand the full scope of what we're trying to do<o:p></o:p></p>
<p class="MsoNormal"> Kristina noted that VCs are quite different than JWT claims in the current Connect specifications<o:p></o:p></p>
<p class="MsoNormal"> Torsten suggests that people read both drafts and we discuss next steps during the upcoming Connect calls<o:p></o:p></p>
<p class="MsoNormal"> Nat agreed<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Trust Frameworks and SIOP<o:p></o:p></p>
<p class="MsoNormal"> DW spoke to the message he said to the list<o:p></o:p></p>
<p class="MsoNormal"> <a href="http://lists.openid.net/pipermail/openid-specs-ab/2021-May/008286.html">
http://lists.openid.net/pipermail/openid-specs-ab/2021-May/008286.html</a><o:p></o:p></p>
<p class="MsoNormal"> He said that particular communities will specify profiles of how things work for their use cases<o:p></o:p></p>
<p class="MsoNormal"> He said that Trust Frameworks may also specify invocation mechanisms<o:p></o:p></p>
<p class="MsoNormal"> As opposed to having a special-purpose mechanism using openid:// and
<a href="https://self-issued.me/">https://self-issued.me/</a><o:p></o:p></p>
<p class="MsoNormal"> He talked about using universal links<o:p></o:p></p>
<p class="MsoNormal"> This could avoid NASCAR-like behaviors<o:p></o:p></p>
<p class="MsoNormal"> Oliver said that he'd be interested in how this would apply to open source wallets<o:p></o:p></p>
<p class="MsoNormal"> DW said that secure wallets could seek certification within trust frameworks<o:p></o:p></p>
<p class="MsoNormal"> DW said that universal links can reduce the complexity<o:p></o:p></p>
<p class="MsoNormal"> DW said that using OpenID Federation Entity IDs could enable for automatic registrations using resolvable sets of metadata<o:p></o:p></p>
<p class="MsoNormal"> Adrian asked how Federation relates to Trust Frameworks and Authenticators<o:p></o:p></p>
<p class="MsoNormal"> DW said that Trust Frameworks have the benefit of starting with more constrained profiles<o:p></o:p></p>
<p class="MsoNormal"> There was discussion of CTAP authenticators and choices made by Trust Frameworks<o:p></o:p></p>
<p class="MsoNormal"> Adrian said that he's concerned with what the CAIRN alliance is doing<o:p></o:p></p>
<p class="MsoNormal"> John spoke to Trust Frameworks, such as Open Banking in the UK<o:p></o:p></p>
<p class="MsoNormal"> Adrian said that this is the opposite of self-sovereign technology<o:p></o:p></p>
<p class="MsoNormal"> John said that self-sovereign deployments still need to know about the veracity of information used<o:p></o:p></p>
</div>
</body>
</html>