<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;
mso-ligatures:standardcontextual;}
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">Spec Call Notes 17-Jul-23<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Mike Jones<o:p></o:p></p>
<p class="MsoNormal">Aaron Parecki<o:p></o:p></p>
<p class="MsoNormal">Nat Sakimura<o:p></o:p></p>
<p class="MsoNormal">Vittorio Bertocci<o:p></o:p></p>
<p class="MsoNormal">David Waite<o:p></o:p></p>
<p class="MsoNormal">Edmund Jay<o:p></o:p></p>
<p class="MsoNormal">Brian Campbell<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Events<o:p></o:p></p>
<p class="MsoNormal"> OAuth Security Workshop<o:p></o:p></p>
<p class="MsoNormal"> <a href="https://oauth.secworkshop.events/osw2023">
https://oauth.secworkshop.events/osw2023</a><o:p></o:p></p>
<p class="MsoNormal"> Registration is now open<o:p></o:p></p>
<p class="MsoNormal"> IETF 117 San Francisco<o:p></o:p></p>
<p class="MsoNormal"> <a href="https://www.ietf.org/how/meetings/117/">
https://www.ietf.org/how/meetings/117/</a><o:p></o:p></p>
<p class="MsoNormal"> Please review <a href="https://datatracker.ietf.org/doc/html/draft-jones-oauth-resource-metadata-04">
https://datatracker.ietf.org/doc/html/draft-jones-oauth-resource-metadata-04</a><o:p></o:p></p>
<p class="MsoNormal"> Used by Federation<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Digital Credentials Protocols Working Group<o:p></o:p></p>
<p class="MsoNormal"> The new Digital Credentials Protocols Working Group has been formed<o:p></o:p></p>
<p class="MsoNormal"> The next step is to schedule the first working group meeting and choose chairs during that meeting<o:p></o:p></p>
<p class="MsoNormal"> People will need to sign a new IPR Contribution agreement unless their existing agreement specifies "all working groups"<o:p></o:p></p>
<p class="MsoNormal"> The new WG intends to continue work on five specifications currently in the OpenID Connect Working Group<o:p></o:p></p>
<p class="MsoNormal"> Two specifications have only been contributed but not updated:<o:p></o:p></p>
<p class="MsoNormal"> - UserInfo Verifiable Credentials<o:p></o:p></p>
<p class="MsoNormal"> - OpenID4VP over BLE<o:p></o:p></p>
<p class="MsoNormal"> A possible quick path forward for those is for the original submitters to submit them for adoption by the new WG<o:p></o:p></p>
<p class="MsoNormal"> At that point, the Connect WG versions would be considered to be inactive<o:p></o:p></p>
<p class="MsoNormal"> Three specifications have been actively updated, with the current drafts not being Implementer's Drafts<o:p></o:p></p>
<p class="MsoNormal"> - OpenID4VP<o:p></o:p></p>
<p class="MsoNormal"> - OpenID4VCI<o:p></o:p></p>
<p class="MsoNormal"> - SIOPv2<o:p></o:p></p>
<p class="MsoNormal"> The Connect WG should actively progress these to Implementer's Drafts so there are IPR-clean specs to move<o:p></o:p></p>
<p class="MsoNormal"> This was how OpenID Connect for Identity Assurance was moved into the eKYC-IDA working group<o:p></o:p></p>
<p class="MsoNormal"> Now would be a great time to review all three of these specifications!<o:p></o:p></p>
<p class="MsoNormal"> Brian asked what will happen with existing issues<o:p></o:p></p>
<p class="MsoNormal"> Mike would like to hear what eKYC-IDA did for issues when they moved the spec<o:p></o:p></p>
<p class="MsoNormal"> Torsten should remember<o:p></o:p></p>
<p class="MsoNormal"> Options appear to be to move the existing issues to the new repository or recreate the open ones<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Open Issues<o:p></o:p></p>
<p class="MsoNormal"> <a href="https://bitbucket.org/openid/connect/issues?status=new&status=open">
https://bitbucket.org/openid/connect/issues?status=new&status=open</a><o:p></o:p></p>
<p class="MsoNormal"> #1983: New issues not posted to the mail list<o:p></o:p></p>
<p class="MsoNormal"> Nat pointed out that Connect issues aren't being sent to the mailing list
<o:p></o:p></p>
<p class="MsoNormal"> Whereas FAPI issues are<o:p></o:p></p>
<p class="MsoNormal"> Mike will have a look at it<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Issues with Status "Submitted"<o:p></o:p></p>
<p class="MsoNormal"> <a href="https://bitbucket.org/openid/connect/issues?is_spam=%21spam&status=submitted">
https://bitbucket.org/openid/connect/issues?is_spam=%21spam&status=submitted</a><o:p></o:p></p>
<p class="MsoNormal"> #1988: Checks in Section 11.2<o:p></o:p></p>
<p class="MsoNormal"> Changed status to "New"<o:p></o:p></p>
<p class="MsoNormal"> #1934 Adding DID service endpoint type to spec<o:p></o:p></p>
<p class="MsoNormal"> Changed status to "New"<o:p></o:p></p>
<p class="MsoNormal"> #1933: Test whether non-members can file issues<o:p></o:p></p>
<p class="MsoNormal"> Resolved<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">PRs<o:p></o:p></p>
<p class="MsoNormal"> <a href="https://bitbucket.org/openid/connect/pull-requests/">
https://bitbucket.org/openid/connect/pull-requests/</a><o:p></o:p></p>
<p class="MsoNormal"> We didn't discuss any specific PRs<o:p></o:p></p>
<p class="MsoNormal"> Mike created PRs 559-566 based on a full read of OpenID4VCI<o:p></o:p></p>
<p class="MsoNormal"> He did so to help prepare it to progress to an Implementer's Draft<o:p></o:p></p>
<p class="MsoNormal"> He also created issues #1970-1980 and #1984-1986 for the same purpose<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Next Call<o:p></o:p></p>
<p class="MsoNormal"> The next call will be the SIOP Special Topic Call on Thursday, July 20th at 7am Pacific Time<o:p></o:p></p>
</div>
</body>
</html>