<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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Spec call notes 18-Nov-13<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">Nat Sakimura<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">John Bradley<o:p></o:p></p>
<p class="MsoNormal">Zhanna Tsitkova (observer from MIT Kerberos Consortium)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Agenda:<o:p></o:p></p>
<p class="MsoNormal"> Open Issues<o:p></o:p></p>
<p class="MsoNormal"> E-mails to the list<o:p></o:p></p>
<p class="MsoNormal"> Editing Status<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"> #902 - Registration - 5.4 Client Read Error Response<o:p></o:p></p>
<p class="MsoNormal"> Clarification of the 401 vs. 403 wording would be helpful<o:p></o:p></p>
<p class="MsoNormal"> Mike will ask Justin about this on the mailing list<o:p></o:p></p>
<p class="MsoNormal"> Nothing significant on other issues besides what's in the tracker<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">E-mails to the list:<o:p></o:p></p>
<p class="MsoNormal"> "jti" claim in client_secret_jwt and private_key_jwt JWTs<o:p></o:p></p>
<p class="MsoNormal"> We will say that it's single use unless otherwise negotiated<o:p></o:p></p>
<p class="MsoNormal"> Processing sector_identifier_uri values<o:p></o:p></p>
<p class="MsoNormal"> We will say that the sector_identifier_uri is validated once at registration time and never fetched again<o:p></o:p></p>
<p class="MsoNormal"> Guidance on what the different flows are for<o:p></o:p></p>
<p class="MsoNormal"> Addressed by new Introduction in Core<o:p></o:p></p>
<p class="MsoNormal"> Authorization Request or Authentication Request?<o:p></o:p></p>
<p class="MsoNormal"> This is issue #896, which has been addressed<o:p></o:p></p>
<p class="MsoNormal"> Reviews solicited<o:p></o:p></p>
<p class="MsoNormal"> Registration read error example missing body?<o:p></o:p></p>
<p class="MsoNormal"> This is now included in issue #902<o:p></o:p></p>
<p class="MsoNormal"> Nonce value suggestion for the Implicit Flow<o:p></o:p></p>
<p class="MsoNormal"> Justin proposed new text for Web Server clients. The gist is:<o:p></o:p></p>
<p class="MsoNormal"> Web server clients may store the nonce on the server as part of the server side session information<o:p></o:p></p>
<p class="MsoNormal"> The server already identifies the browser through the session cookie in this case<o:p></o:p></p>
<p class="MsoNormal"> Review Comments on Dyn Reg<o:p></o:p></p>
<p class="MsoNormal"> Comment on jwks_uri - about native clients not being able to use asymmetric keys<o:p></o:p></p>
<p class="MsoNormal"> Native clients can use symmetric keys in the say we described<o:p></o:p></p>
<p class="MsoNormal"> We would have to push a JWKS at registration time<o:p></o:p></p>
<p class="MsoNormal"> But this doesn't enable key rotation<o:p></o:p></p>
<p class="MsoNormal"> There isn't a proposed change at this time<o:p></o:p></p>
<p class="MsoNormal"> Discussion should continue<o:p></o:p></p>
<p class="MsoNormal"> Nat will file a bug with possible proposed text<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Editing Status:<o:p></o:p></p>
<p class="MsoNormal"> Mike is almost done applying Nat's review comments to Core<o:p></o:p></p>
<p class="MsoNormal"> Justin Richer's Core review will then be applied<o:p></o:p></p>
<p class="MsoNormal"> We need to verify that the F2F results are incorporated<o:p></o:p></p>
<p class="MsoNormal"> The last step for Core will be to move the ID Token section up<o:p></o:p></p>
<p class="MsoNormal"> At that point we should have a Core release candidate<o:p></o:p></p>
<p class="MsoNormal"> Following that, the reviews to the other specs will be applied<o:p></o:p></p>
</div>
</body>
</html>