Minor correction.<br><div><br><div class="gmail_quote">On Tue, Jun 21, 2011 at 8:23 AM, Mike Jones <span dir="ltr"><<a href="mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal">Spec call notes 20-Jun-11<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Nat Sakimura<u></u><u></u></p>
<p class="MsoNormal">Mike Jones<u></u><u></u></p>
<p class="MsoNormal">John Bradley<u></u><u></u></p>
<p class="MsoNormal">Edmund Jay<u></u><u></u></p>
<p class="MsoNormal">Breno de Medeiros<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">The Connect specs are now checked in at <a href="http://svn.openid.net/repos/specifications/connect/1.0/" target="_blank">
http://svn.openid.net/repos/specifications/connect/1.0/</a> and available in HTML and TXT versions in the <a href="http://openid.net" target="_blank">openid.net</a> specs directory. See:<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in"><a href="http://openid.net/specs/openid-connect-core-1_0.html" target="_blank">http://openid.net/specs/openid-connect-core-1_0.html</a><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in"><a href="http://openid.net/specs/openid-connect-ab-1_0.html" target="_blank">http://openid.net/specs/openid-connect-ab-1_0.html</a><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in"><a href="http://openid.net/specs/openid-connect-code-1_0.html" target="_blank">http://openid.net/specs/openid-connect-code-1_0.html</a><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in"><a href="http://openid.net/specs/openid-connect-swd-1_0.html" target="_blank">http://openid.net/specs/openid-connect-swd-1_0.html</a><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in"><a href="http://openid.net/specs/openid-connect-userinfo-1_0.html" target="_blank">http://openid.net/specs/openid-connect-userinfo-1_0.html</a><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Status check of each sub-specs:<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">- Core<u></u><u></u></p>
<p class="MsoNormal"> Breno to send feedback to the list, including about:<u></u><u></u></p>
<p class="MsoNormal"> Breno: Core section 4 - "Authorization type must include token"<u></u><u></u></p>
<p class="MsoNormal"> Request parameter name 4.1.1 "req" -> "request" for consistency<u></u><u></u></p>
<p class="MsoNormal"> Session audience "session_audience"<u></u><u></u></p>
<p class="MsoNormal"> 4.1.1.1 Why is "server_id" not "issuer" or "origin"?<u></u><u></u></p>
<p class="MsoNormal"> Different than other things named "*_id"<u></u><u></u></p>
<p class="MsoNormal"> Breno asked why the code binding is separate from the core?<u></u><u></u></p>
<p class="MsoNormal"> Nat responded because the core introduces the protocol elements and not just the messages</p></div></div></blockquote><meta charset="utf-8"> </div><div class="gmail_quote">
I stated that "code binding" introduces protocol elements to the "core". <div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div lang="EN-US" link="blue" vlink="purple">
<div><p class="MsoNormal"><u></u><u></u></p>
<p class="MsoNormal"> Breno said that having the code define the standard bindings would eliminate a lot of duplication<u></u><u></u></p>
<p class="MsoNormal"> One possibility is to have binding subsections defining the code binding in the core spec<u></u><u></u></p>
<p class="MsoNormal"> Nat asked how this applies to the implicit flow<u></u><u></u></p>
<p class="MsoNormal"> Session management spec currently in core. Maybe make separate?<u></u><u></u></p>
<p class="MsoNormal"> Session management may not make sense outside of HTTP binding<u></u><u></u></p>
<p class="MsoNormal"> Breno doesn't want to create more documents than we have to<u></u><u></u></p>
<p class="MsoNormal"> But session management is clearly specific to the HTTP binding<u></u><u></u></p>
<p class="MsoNormal"> Nat said that since a session is an identity token, it could make sense for other bindings </p></div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal"><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">- UserInfo<u></u><u></u></p>
<p class="MsoNormal"> Mike asked whether the address claim should be a structure or a set of individual claims<u></u><u></u></p>
<p class="MsoNormal"> We decided to use a structured address claim with fields like postal_code<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">- Session Management<u></u><u></u></p>
<p class="MsoNormal"> 4.1.1 Missing session parameter than can be passed in every request to indicate user<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">- Dynamic Registration<u></u><u></u></p>
<p class="MsoNormal"> John sent an OpenID Connect Simple Client Registration draft for feedback<u></u><u></u></p>
<p class="MsoNormal"> John gave us background <u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">- JWE<u></u><u></u></p>
<p class="MsoNormal"> Mike plans to do the JWT encryption work following an OAuth bearer token update<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">- OpenID 2.0 Migration<u></u><u></u></p>
<p class="MsoNormal"> Breno wants to defer working on the migration spec this until the discovery is solid<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">We agreed that finishing the missing functionality is the top priority (rather than editorial restructuring)<u></u><u></u></p>
<p class="MsoNormal">Nat will send an invitation for a supplemental call in three days on Thursday Pacific / Friday Japan at the standard time<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">We will begin doing version control at <a href="http://svn.openid.net/repos/specifications/connect" target="_blank">http://svn.openid.net/repos/specifications/connect</a><u></u><u></u></p>
<p class="MsoNormal">Mike will work on subversion access for the active editors using these e-mail addresses:<u></u><u></u></p>
<p class="MsoNormal"> <a href="mailto:sakimura@gmail.com" target="_blank">sakimura@gmail.com</a><u></u><u></u></p>
<p class="MsoNormal"> <a href="mailto:ve7jtb@ve7jtb.com" target="_blank">ve7jtb@ve7jtb.com</a><u></u><u></u></p>
<p class="MsoNormal"> <a href="mailto:ejay@mgi1.com" target="_blank">ejay@mgi1.com</a><u></u><u></u></p>
<p class="MsoNormal"> <a href="mailto:breno@google.com" target="_blank">breno@google.com</a><u></u><u></u></p>
</div>
</div>
<br>_______________________________________________<br>
Openid-specs-ab mailing list<br>
<a href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Nat Sakimura (=nat)<br><a href="http://www.sakimura.org/en/">http://www.sakimura.org/en/</a><br><a href="http://twitter.com/_nat_en">http://twitter.com/_nat_en</a><br>
</div>