<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;
mso-ligatures:standardcontextual;}
@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 31-Oct-22<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">Karthik Sivasamy<o:p></o:p></p>
<p class="MsoNormal">David Waite (DW)<o:p></o:p></p>
<p class="MsoNormal">Naveen CM<o:p></o:p></p>
<p class="MsoNormal">Dima Postnikov<o:p></o:p></p>
<p class="MsoNormal">Aaron Parecki<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">JARM Approval Vote<o:p></o:p></p>
<p class="MsoNormal"> JWT Secured Authorization Response Mode for OAuth 2.0 (JARM)<o:p></o:p></p>
<p class="MsoNormal"> Up for approval as a final spec<o:p></o:p></p>
<p class="MsoNormal"> Vote at <a href="https://openid.net/foundation/members/polls/286">
https://openid.net/foundation/members/polls/286</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Pull Requests<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"> PR #313 fix: removed duplicate word "endpoint" and changed addition to additional<o:p></o:p></p>
<p class="MsoNormal"> Fixes syntax errors in Native SSO spec<o:p></o:p></p>
<p class="MsoNormal"> Merged<o:p></o:p></p>
<p class="MsoNormal"> PR #338 [Errata] Specified the use of CORS at additional endpoints<o:p></o:p></p>
<p class="MsoNormal"> Fixes #980<o:p></o:p></p>
<p class="MsoNormal"> This is the last currently open errata PR<o:p></o:p></p>
<p class="MsoNormal"> Merged (with discussion on the issue as recorded below)<o:p></o:p></p>
<p class="MsoNormal"> PR #349 feat: [Federation] RS256 not mandatory anymore<o:p></o:p></p>
<p class="MsoNormal"> Closes #1681<o:p></o:p></p>
<p class="MsoNormal"> Merged<o:p></o:p></p>
<p class="MsoNormal"> PR #346 fix: [Federation] trust mark status HTTP method<o:p></o:p></p>
<p class="MsoNormal"> On the 31-Oct-22 working group call, we agreed to merge this after conflicts are resolved<o:p></o:p></p>
<p class="MsoNormal"> PR #320 rename to `credential_issuer` from the `issuer` in the Initiate Issuance Request<o:p></o:p></p>
<p class="MsoNormal"> Ready to merge after conflicts are resolved<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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"> #1681: [Federation] FAPI prohibits RS256<o:p></o:p></p>
<p class="MsoNormal"> Fixed by PR #349<o:p></o:p></p>
<p class="MsoNormal"> #980: Where else do we need to specify the use of CORS support?<o:p></o:p></p>
<p class="MsoNormal"> Fixed by PR #338<o:p></o:p></p>
<p class="MsoNormal"> We discussed possibly prohibiting the use of CORS on the authorization endpoint in the OAuth Security BCP<o:p></o:p></p>
<p class="MsoNormal"> Aaron said that he just added a statement about CORS on the token endpoint to the OAuth 2.1 spec<o:p></o:p></p>
<p class="MsoNormal"> DW distinguished between API endpoints and endpoints visited by the browser<o:p></o:p></p>
<p class="MsoNormal"> #1700: potentially add a section that explains basics of OAuth 2.0 (perhaps an addendum).<o:p></o:p></p>
<p class="MsoNormal"> Mike is mostly prone to let OAuth describe itself, but a few sentences of overview would be OK<o:p></o:p></p>
<p class="MsoNormal"> Aaron Parecki noted that “Basics could grow pretty quickly”<o:p></o:p></p>
<p class="MsoNormal"> #1699: OIDC4VCI - error response for missing nonce<o:p></o:p></p>
<p class="MsoNormal"> Mike noted that invalid_or_missing_proof doesn’t seem to fit the scenario<o:p></o:p></p>
<p class="MsoNormal"> #1698: Scope of an Access Token in VCI<o:p></o:p></p>
<p class="MsoNormal"> This probably needs discussion on a SIOP special topic call<o:p></o:p></p>
<p class="MsoNormal"> #1697: Server metadata needs to specify supported proof types / algorithms<o:p></o:p></p>
<p class="MsoNormal"> We looked at this on the 31-Oct-22 working group call. It would probably benefit from discussion on a SIOP special topic call.<o:p></o:p></p>
<p class="MsoNormal"> #1696: Is proof type flexibility needed?<o:p></o:p></p>
<p class="MsoNormal"> DW said that the information that needs to be included in the proof will, in general, vary by proof type<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">IETF in a week in London<o:p></o:p></p>
<p class="MsoNormal"> Aaron and Mike plan to be there<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 is on Thursday, November 3rd at 7am Pacific Time, followed by a SIOP Special Topic call the following hour<o:p></o:p></p>
</div>
</body>
</html>