<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 1-Aug-13<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Nat Sakimura<o:p></o:p></p>
<p class="MsoNormal">Brian Campbell<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">John Bradley<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"> New examples in JWT and JOSE specs<o:p></o:p></p>
<p class="MsoNormal"> Open Issues<o:p></o:p></p>
<p class="MsoNormal"> Topics raised at OpenID meeting at IETF<o:p></o:p></p>
<p class="MsoNormal"> Nat's experiment <o:p></o:p></p>
<p class="MsoNormal"> Next steps for the specs<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">New examples in JWT and JOSE specs<o:p></o:p></p>
<p class="MsoNormal"> Mike added nested JWT and key agreement examples in the latest JWT and JOSE specs<o:p></o:p></p>
<p class="MsoNormal"> He asked Edmund, Brian, and others to please verify the examples<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"> #863 - Stateless Registration Discovery/Messages<o:p></o:p></p>
<p class="MsoNormal"> John will still needs to a comment about the alternative method for doing this<o:p></o:p></p>
<p class="MsoNormal"> By returning registration state encoded in client_id value<o:p></o:p></p>
<p class="MsoNormal"> #864 - Native Client code leakage<o:p></o:p></p>
<p class="MsoNormal"> The effect upon native apps would be that they would use the nonce as the HTTP basic password<o:p></o:p></p>
<p class="MsoNormal"> Google is already doing this for their native apps<o:p></o:p></p>
<p class="MsoNormal"> Brian would prefer that this be an OAuth level solution, rather than at the Connect level<o:p></o:p></p>
<p class="MsoNormal"> Or this could be sent as a different parameter, rather than as the password<o:p></o:p></p>
<p class="MsoNormal"> John still needs to add a comment describing Brian's concern about mixing the layers<o:p></o:p></p>
<p class="MsoNormal"> John still needs to file a bug on the possibility of clients using the Code flow registering for "alg":"none"<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Topics raised at OpenID meeting at IETF:<o:p></o:p></p>
<p class="MsoNormal"> MTI Discussion<o:p></o:p></p>
<p class="MsoNormal"> Torsten had asked for the implicit flow not to be required in the closed case<o:p></o:p></p>
<p class="MsoNormal"> We've agreed to this change<o:p></o:p></p>
<p class="MsoNormal"> Mike will file a bug<o:p></o:p></p>
<p class="MsoNormal"> John asked if we should also allow just the implicit flow in the closed case<o:p></o:p></p>
<p class="MsoNormal"> We agreed to allow this as well<o:p></o:p></p>
<p class="MsoNormal"> Torsten asked us to put the response_types in the section 8 MTI list<o:p></o:p></p>
<p class="MsoNormal"> We will do that - this is an editorial change - not a spec change<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Possible next steps for the specs:<o:p></o:p></p>
<p class="MsoNormal"> Possibly reorganize the specs<o:p></o:p></p>
<p class="MsoNormal"> Nat did an experiment merging Messages and Standard<o:p></o:p></p>
<p class="MsoNormal"> We could decompose Messages and Standard into feature groups:<o:p></o:p></p>
<p class="MsoNormal"> Core<o:p></o:p></p>
<p class="MsoNormal"> Individual Claims<o:p></o:p></p>
<p class="MsoNormal"> Distributed & Aggregated Claims<o:p></o:p></p>
<p class="MsoNormal"> UserInfo<o:p></o:p></p>
<p class="MsoNormal"> Self-Issued<o:p></o:p></p>
<p class="MsoNormal"> JSON-Based Requests<o:p></o:p></p>
<p class="MsoNormal"> (Some of those could be combined)<o:p></o:p></p>
<p class="MsoNormal"> (Or we could just combine Messages and Standard)<o:p></o:p></p>
<p class="MsoNormal"> We could make the uses of the definitions links<o:p></o:p></p>
<p class="MsoNormal"> Give each claim definition its own section heading<o:p></o:p></p>
<p class="MsoNormal"> Possibly give each definition its own section heading<o:p></o:p></p>
<p class="MsoNormal"> Then link from the first use of each term in a section to its definition<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>