<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 10-Nov-11<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">Edmund Jay<o:p></o:p></p>
<p class="MsoNormal">Nat Sakimura<o:p></o:p></p>
<p class="MsoNormal">Tony Nadalin<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"> Editing status<o:p></o:p></p>
<p class="MsoNormal"> Open Issues<o:p></o:p></p>
<p class="MsoNormal"> Potential Design Changes<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"> 2 more changes with only local impact<o:p></o:p></p>
<p class="MsoNormal"> A few global changes remaining (mostly keyword spelling)<o:p></o:p></p>
<p class="MsoNormal"> Mike still needs to go through Yaron's comments to file issues<o:p></o:p></p>
<p class="MsoNormal"> We can discuss these issues on Monday<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"> #283: Basic - 4. What are "User Info Endpoint Servers" ?<o:p></o:p></p>
<p class="MsoNormal"> Delete space in "User Info" - Mike<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> #232 Client sends a request to the Authorization Server (Editorial)<o:p></o:p></p>
<p class="MsoNormal"> Nat will add explanation that not always a redirect<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> #222: Registration 4.1. js_origin_uri needs documentation (Normative)<o:p></o:p></p>
<p class="MsoNormal"> Waiting on Breno - will probably stay open at Implementer's Draft time<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> #281: Obtaining claims without requiring additional round trips<o:p></o:p></p>
<p class="MsoNormal"> Mike needs to follow up with Yaron about how he wants this to happen<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Potential Design Changes:<o:p></o:p></p>
<p class="MsoNormal"> Specify that the id_token token type is JWT in Basic<o:p></o:p></p>
<p class="MsoNormal"> Consensus to do so<o:p></o:p></p>
<p class="MsoNormal"> Be clear that Basic implementations MAY do crypto themselves<o:p></o:p></p>
<p class="MsoNormal"> Reference Standard for how to do this<o:p></o:p></p>
<p class="MsoNormal"> Mike will make that change<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Should the audience of the Access and ID tokens should be the resources, not the client?<o:p></o:p></p>
<p class="MsoNormal"> Because it is the endpoints making resource access decisions, not the client<o:p></o:p></p>
<p class="MsoNormal"> Mike will file an issue, send to mailing list<o:p></o:p></p>
<p class="MsoNormal"> We should bring to John's and Breno's (or Naveen's) attention<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Currently the audience of the id_token is the client<o:p></o:p></p>
<p class="MsoNormal"> Currently there is no audience specified for the access token<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> This may make sense for the id_token, since the client can retrieve the claims<o:p></o:p></p>
<p class="MsoNormal"> The Check ID endpoint needs to preserve the audience when it sends back the claims<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Doesn't make sense for the Access Token<o:p></o:p></p>
<p class="MsoNormal"> (unless #281 is adopted, but this might no longer be an Access Token then)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> We need to add an audience to the access token of the resource server<o:p></o:p></p>
<p class="MsoNormal"> Mike will file issue<o:p></o:p></p>
<p class="MsoNormal"> Mike will say that will be done unless security arguments on why it's not necessary are convincing<o:p></o:p></p>
<p class="MsoNormal"> Use SHOULD or STRONGLY RECOMMENDED language<o:p></o:p></p>
</div>
</body>
</html>