<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;
margin-bottom:.0001pt;
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">
<div class="WordSection1">
<p class="MsoNormal">Spec Call Notes 13-Feb-20<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">Brian Campbell<o:p></o:p></p>
<p class="MsoNormal">Bjorn Hjelm<o:p></o:p></p>
<p class="MsoNormal">George Fletcher<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">OAuth Specs in Flight<o:p></o:p></p>
<p class="MsoNormal"> MTLS and Resource Indicators are in Auth48<o:p></o:p></p>
<p class="MsoNormal"> JWT BCP is in Auth48<o:p></o:p></p>
<p class="MsoNormal"> JAR needs changes to partially unbreak it - allowing client_id as a request parameter<o:p></o:p></p>
<p class="MsoNormal"> RAR and PAR are just starting<o:p></o:p></p>
<p class="MsoNormal"> Security BCP and Browser-Based Apps are in flight<o:p></o:p></p>
<p class="MsoNormal"> PoP specs need defined directions<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Certification and Logout<o:p></o:p></p>
<p class="MsoNormal"> OP and RP logout certification are in pilot mode<o:p></o:p></p>
<p class="MsoNormal"> We want people testing before we take the Logout specs to Final status<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Mobile<o:p></o:p></p>
<p class="MsoNormal"> Bjorn is working to establish a relationship between 3GPP and OIDF<o:p></o:p></p>
<p class="MsoNormal"> He talked about a mission-critical access profile for first responders<o:p></o:p></p>
<p class="MsoNormal"> He will discuss this during today's EC call<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"> #1149 Front-channel logout that doesn't rely on cookies<o:p></o:p></p>
<p class="MsoNormal"> This proposes a completely different front-channel logout mechanism<o:p></o:p></p>
<p class="MsoNormal"> #1152 value and values processing and certification<o:p></o:p></p>
<p class="MsoNormal"> Closed: Certification doesn't require support for the "claims" request parameter<o:p></o:p></p>
<p class="MsoNormal"> #1153 redirect_uri definition contradiction in docs<o:p></o:p></p>
<p class="MsoNormal"> Closed: Joseph's description of the intent of the spec is accurate<o:p></o:p></p>
<p class="MsoNormal"> #1146 certification: is returning an empty address object permitted<o:p></o:p></p>
<p class="MsoNormal"> Asked: Joseph, is the new certification code handling this condition? If so, we can close this issue.<o:p></o:p></p>
<p class="MsoNormal"> #1148 certification and kid<o:p></o:p></p>
<p class="MsoNormal"> Duplicate of #1127<o:p></o:p></p>
<p class="MsoNormal"> #1147 certification: RFC6749 MUST for error_description<o:p></o:p></p>
<p class="MsoNormal"> Closed: Tracked by ticket in certification suite<o:p></o:p></p>
<p class="MsoNormal"> #1137 Is content-type application/x-www-form-urlencoded required when calling user info endpoint with empty body<o:p></o:p></p>
<p class="MsoNormal"> Joseph, is this now handled in the certification suite? If so, we can close this issue.<o:p></o:p></p>
<p class="MsoNormal"> #1109 Use empty object instead of null in the claim request<o:p></o:p></p>
<p class="MsoNormal"> This would be a breaking change to a final specification - therefore no change will be made<o:p></o:p></p>
<p class="MsoNormal"> #1135 Assurance: Timestamp resolution in examples<o:p></o:p></p>
<p class="MsoNormal"> This issue belongs to the eKYC-IdA working group now<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 working group call is scheduled for Monday, February 17 at 3pm Pacific Time<o:p></o:p></p>
<p class="MsoNormal"> This is Presidents Day in the US. Will people plan to attend the call?<o:p></o:p></p>
</div>
</body>
</html>