<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">Spec Call Notes 11-Feb-21<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">Tom Jones<o:p></o:p></p>
<p class="MsoNormal">George Fletcher<o:p></o:p></p>
<p class="MsoNormal">Tim Cappalli<o:p></o:p></p>
<p class="MsoNormal">Kristina Yasuda<o:p></o:p></p>
<p class="MsoNormal">Bjorn Hjelm<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">SCIM Update<o:p></o:p></p>
<p class="MsoNormal"> We apparently missed the window for a SCIM BoF at the upcoming IETF<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Browser Interactions Special Topic Call<o:p></o:p></p>
<p class="MsoNormal"> Notes were sent from the last call<o:p></o:p></p>
<p class="MsoNormal"> There have been no use cases submitted yet<o:p></o:p></p>
<p class="MsoNormal"> Edge plans to publish an "explainer" on their point of view<o:p></o:p></p>
<p class="MsoNormal"> Tom suggested that the CA Browser Forum also participate in the discussions<o:p></o:p></p>
<p class="MsoNormal"> We noted that the use cases document being prepared is using Markdown<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Client Credentials Flow<o:p></o:p></p>
<p class="MsoNormal"> RFC 6749 says that a Refresh Token SHOULD NOT be issues<o:p></o:p></p>
<p class="MsoNormal"> George asked about whether doing so is actually OK when using per-app instance Dynamic Client Registration<o:p></o:p></p>
<p class="MsoNormal"> Brian believes that the SHOULD NOT is there because you can always use the client credentials to get a new access token<o:p></o:p></p>
<p class="MsoNormal"> Brian also believes that there isn't actually a security issue in doing so<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">
https://bitbucket.org/openid/connect/issues</a><o:p></o:p></p>
<p class="MsoNormal"> All the new issues are SIOP issues, which will be triaged on the SIOP special topic call<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 Monday, February 15th, 2021 at 3pm Pacific Time<o:p></o:p></p>
</div>
</body>
</html>