<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 15-Jun-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">John Bradley<o:p></o:p></p>
<p class="MsoNormal">Tony Nadalin<o:p></o:p></p>
<p class="MsoNormal">Jeremie Miller<o:p></o:p></p>
<p class="MsoNormal">David Waite (DW)<o:p></o:p></p>
<p class="MsoNormal">Adam Lemmon<o:p></o:p></p>
<p class="MsoNormal">Edmund Jay<o:p></o:p></p>
<p class="MsoNormal">Pamela Dingle<o:p></o:p></p>
<p class="MsoNormal">Nat Sakimura<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">External Organizations<o:p></o:p></p>
<p class="MsoNormal"> Identiverse (next week)<o:p></o:p></p>
<p class="MsoNormal"> Panel: Where we are with SIOP and DIDs<o:p></o:p></p>
<p class="MsoNormal"> <a href="https://identiverse.com/idv2021/session/SESCJBD86OHB664FD/">
https://identiverse.com/idv2021/session/SESCJBD86OHB664FD/</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Open SIOP Issues<o:p></o:p></p>
<p class="MsoNormal"> <a href="https://bitbucket.org/openid/connect/issues?status=new&status=open&component=SIOP">
https://bitbucket.org/openid/connect/issues?status=new&status=open&component=SIOP</a><o:p></o:p></p>
<p class="MsoNormal"> #1242: Specify how multiple claims should be included in a Verifiable Presentation<o:p></o:p></p>
<p class="MsoNormal"> The draft specifies an array<o:p></o:p></p>
<p class="MsoNormal"> Closed during the call since the array format in the specification already enables this<o:p></o:p></p>
<p class="MsoNormal"> #1230: Adopt Presentation Exchange as an officially supported mechanism within SIOP<o:p></o:p></p>
<p class="MsoNormal"> Closed during the call, since PR #20 accomplishes this<o:p></o:p></p>
<p class="MsoNormal"> #1218: Verifiable Presentations do not work outside of their own protocol<o:p></o:p></p>
<p class="MsoNormal"> Closed during the call, since PR #21 addressed this issue<o:p></o:p></p>
<p class="MsoNormal"> There was an ensuing discussion about presentation requests and formats for them<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Terminology HackMD Document<o:p></o:p></p>
<p class="MsoNormal"> <a href="https://hackmd.io/@dwaite/Hyg0vTZFd">
https://hackmd.io/@dwaite/Hyg0vTZFd</a><o:p></o:p></p>
<p class="MsoNormal"> This arose from issue #1239: We should stop using "SIOP" as an umbrella term and instead talk about individual features.<o:p></o:p></p>
<p class="MsoNormal"> Mike disagreed with including the "Collective" term, as the instances are not cooperating with one another<o:p></o:p></p>
<p class="MsoNormal"> There was a discussion on the definition of "Trust Framework"<o:p></o:p></p>
<p class="MsoNormal"> Tony pointed out that OIX has a definition - in The Open Identity Trust Framework (OITF) Model<o:p></o:p></p>
<p class="MsoNormal"> There was a discussion on the use of the issuer self-issued.me as a protocol switch<o:p></o:p></p>
<p class="MsoNormal"> We agreed that it was OK to say this non-normatively in the SIOP V2 draft<o:p></o:p></p>
<p class="MsoNormal"> DW said that using universal links might require using a different authorization endpoint<o:p></o:p></p>
<p class="MsoNormal"> Mike suggested that we write down a proposal for how to use universal links<o:p></o:p></p>
<p class="MsoNormal"> We agreed to the "Cryptographically Proven Subject Authority" remarks<o:p></o:p></p>
<p class="MsoNormal"> We discussed the "No Cryptographically-stated Subject Userinfo" point<o:p></o:p></p>
<p class="MsoNormal"> Mike said that even for the UserInfo Endpoint, there's still a cryptographic chain assuring the integrity of the claims<o:p></o:p></p>
<p class="MsoNormal"> DW said that with 3rd party issuers, they're asserting the claims, rather than the SIOP<o:p></o:p></p>
<p class="MsoNormal"> Nat said that the Claims Aggregation draft is partly dealing with that<o:p></o:p></p>
<p class="MsoNormal"> Mike said that, per Tom Jones' earlier issue #1232, the signature on claims merely provides integrity protection for the claims<o:p></o:p></p>
<p class="MsoNormal"> It doesn't mean that they're verified, in general<o:p></o:p></p>
<p class="MsoNormal"> We said that eKYC, VCs, and/or Claims Aggregation can fill this gap for particular use cases<o:p></o:p></p>
</div>
</body>
</html>