<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 24-Sep-12 <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">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"> Interop<o:p></o:p></p>
<p class="MsoNormal"> Editing<o:p></o:p></p>
<p class="MsoNormal"> Open Issues<o:p></o:p></p>
<p class="MsoNormal"> IIW WG Meeting<o:p></o:p></p>
<p class="MsoNormal"> IETF Meeting<o:p></o:p></p>
<p class="MsoNormal"> URI Templates<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Interop:<o:p></o:p></p>
<p class="MsoNormal"> Roland has been specifying instructions for RP tests<o:p></o:p></p>
<p class="MsoNormal"> He's already done 18 of the current 32 RP tests<o:p></o:p></p>
<p class="MsoNormal"> including important ones like tests for aggregated and distributed claims<o:p></o:p></p>
<p class="MsoNormal"> See http://osis.idcommons.net/wiki/Special:RecentChanges<o:p></o:p></p>
<p class="MsoNormal"> Mike will send a note to openid-connect-interop describing which RP tests are live<o:p></o:p></p>
<p class="MsoNormal"> Mike began linking the OP test instructions to the automated tests<o:p></o:p></p>
<p class="MsoNormal"> See http://osis.idcommons.net/wiki/OC4:FeatureTest-Support_code_Response_Type for the first updated instructions<o:p></o:p></p>
<p class="MsoNormal"> Mike will send a note to the interop list letting people know to do testing and record results<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Edmund asked whether https://github.com/rohe/oictest has been replaced by https://github.com/andreassolberg/oictest<o:p></o:p></p>
<p class="MsoNormal"> There is a link to the non-existent page at http://www.kodtest.se/oictest/install.html<o:p></o:p></p>
<p class="MsoNormal"> Hopefully Roland can update these instructions to point to the right places<o:p></o:p></p>
<p class="MsoNormal"> Mike will follow up with Roland and Andreas<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Editing:<o:p></o:p></p>
<p class="MsoNormal"> John and Nat checked in a number of changes<o:p></o:p></p>
<p class="MsoNormal"> Nat cleared all but two of his outstanding issues<o:p></o:p></p>
<p class="MsoNormal"> John closed 5 and is working on another one that he needs Nat's help with - #643<o:p></o:p></p>
<p class="MsoNormal"> Needs a Japanese Unicode application name and help with Unicode encodings<o:p></o:p></p>
<p class="MsoNormal"> We need to figure out how and where to specify the UTF-8 encoding both for this use and for others<o:p></o:p></p>
<p class="MsoNormal"> We need to audit the specs for encodings in general<o:p></o:p></p>
<p class="MsoNormal"> Nat filed an issue for this - #655<o:p></o:p></p>
<p class="MsoNormal"> For instance, encoding needs to be specified for the UserInfo endpoint<o:p></o:p></p>
<p class="MsoNormal"> John did edits about application type - #360<o:p></o:p></p>
<p class="MsoNormal"> People should review the details of this for native client applications (which changed)<o:p></o:p></p>
<p class="MsoNormal"> John asked whether we forgot to restrict redirect URIs to HTTPs<o:p></o:p></p>
<p class="MsoNormal"> We need to review this issue<o:p></o:p></p>
<p class="MsoNormal"> John also mentioned an IE browser header that Google supports having to do with native applications<o:p></o:p></p>
<p class="MsoNormal"> John will file an issue about this<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"> #653 Registration - 2.1 policy_url SHOULD be displayed?<o:p></o:p></p>
<p class="MsoNormal"> Or should this be a MUST?<o:p></o:p></p>
<p class="MsoNormal"> We will discuss this during the face-to-face WG meeting<o:p></o:p></p>
<p class="MsoNormal"> #654 Messages - (ed) 2.3.2 Userinfo Response - Make a new top level section called Standard Claims<o:p></o:p></p>
<p class="MsoNormal"> We agreed this should be its own section<o:p></o:p></p>
<p class="MsoNormal"> We will also look into whether there's a way to top-align the table rows<o:p></o:p></p>
<p class="MsoNormal"> #655 All - Specify UTF-8 as encoding scheme whenever necessary<o:p></o:p></p>
<p class="MsoNormal"> Assigned to Nat<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">IIW WG Meeting:<o:p></o:p></p>
<p class="MsoNormal"> We currently have 13 people registered - see http://connect-wg-oct-2012.eventbrite.com/<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">IETF Meeting:<o:p></o:p></p>
<p class="MsoNormal"> The IETF approved our meeting request and they are scheduling space Sunday afternoon<o:p></o:p></p>
<p class="MsoNormal"> John will create an eventbrite page for this: connect-ietf-85.eventbrite.com<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">URI Templates:<o:p></o:p></p>
<p class="MsoNormal"> Nat wrote about possibly using URI templates at<o:p></o:p></p>
<p class="MsoNormal"> http://nat.sakimura.org/2012/09/16/uri-template-in-openid-connect-provider-configuration-response/<o:p></o:p></p>
<p class="MsoNormal"> Also see http://tools.ietf.org/html/rfc6570<o:p></o:p></p>
<p class="MsoNormal"> This could be used in the server provider configuration response<o:p></o:p></p>
<p class="MsoNormal"> This could declare what parameters would go to each endpoint<o:p></o:p></p>
<p class="MsoNormal"> JSON Schema could help more precisely specify the JSON Schemas<o:p></o:p></p>
<p class="MsoNormal"> URI Templates could help more precisely specify what can be sent to each endpoint<o:p></o:p></p>
<p class="MsoNormal"> This could add value for the optional parameters (the required ones are already specified in the specs)<o:p></o:p></p>
<p class="MsoNormal"> These could be specified in appendices<o:p></o:p></p>
<p class="MsoNormal"> John pointed out that JSON Schema is controversial and possibly in flux<o:p></o:p></p>
<p class="MsoNormal"> Mike would be OK with non-normative schema language in an appendix but not in normative text<o:p></o:p></p>
<p class="MsoNormal"> We will add this to the agenda for the face-to-face WG meeting<o:p></o:p></p>
</div>
</body>
</html>