<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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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-reply;
font-family:"Calibri","sans-serif";
color:#002060;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060">Reacting to the JWT comments below – the header is first in JWT to provide a clear and actionable description of what comes next. It may be a signature. It
may be encrypted content. The FB field order doesn’t have this useful property.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060">JWT has significant and growing adoption as-is. At most, perhaps we could entertain a discussion about using longer member names in some circumstances. But
I believe that trying to undo the numerous and interlocking consensus decisions that led to the JWT, JWS, and soon the JSE format, would be highly counter-productive.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060"> Best wishes,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060"> -- Mike<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> openid-specs-ab-bounces@lists.openid.net [mailto:openid-specs-ab-bounces@lists.openid.net]
<b>On Behalf Of </b>Edmund Jay<br>
<b>Sent:</b> Thursday, August 04, 2011 5:33 PM<br>
<b>To:</b> openid-specs-ab@lists.openid.net<br>
<b>Subject:</b> [Openid-specs-ab] Spec call notes 04-Aug-11<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">Spec call notes 04-Aug-11<br>
<br>
John Bradley<br>
Nat Sakimura<br>
Johnny Bufu<br>
Allen Tom<br>
George Fletcher<br>
Edmund Jay<br>
Breno de Medeiros (joined later)<br>
<br>
Updates<br>
John waiting for more feedback on Lite/Discovery/Registration specs <br>
before writing new drafts<br>
Newcastle is doing some work on registration that may be used for <br>
feedback/reference<br>
<br>
Breno met with Facebook and discussed some issues with JWT<br>
- FB would like to use longer parameter names and change order of <br>
signature parameters by putting the signature first. <br>
- Discussed using FB signed requests and how to make it more functionally<br>
like JWT.<br>
- Issue unresolved, put off for later.<br>
<br>
Edmund needs to update Messages spec using todays feedback before <br>
circulating<br>
<br>
<br>
John asked about response_type, scope, and how id_token is returned<br>
- The 'respone_type' will no longer include id_token value since it <br>
only indicates the flow method used<br>
- The 'scope' parameter specifies a additive list on what is to be <br>
returned at userinfo endpoint<br>
openid - returns ID Token only<br>
profile - default userinfo claims excluding email/address and possibly others<br>
email - returns email<br>
address - returns address<br>
other values to be determined<br>
<br>
<br>
Breno raised the issue of how to facilitate work on the OpenID Connect specs<br>
Disussed writing specs in more generic way and put specifics and options in <br>
extension specs separately later. <br>
- Nat/John agree that extension should be part of a WG and should not be done<br>
willy nilly<br>
John suggested pushing Lite spec to implementor's draft first.<br>
- Nat says not a good idea<br>
<br>
<br>
Breno to find time to rework/collaborate on Session Management spec.<br>
Nat will try to find resource to help Breno in next few days<br>
<br>
<br>
Current spec set is the following:<br>
Messages (merge of former Core, Framewor, and UserInfo)<br>
Standard (Binding for Messages) - to be written<br>
Lite (Minimal Binding spec for RPs)<br>
Session Management<br>
Registration<br>
Discovery<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">OpenID Connect Discovery:
<a href="http://openid.net/specs/openid-connect-discovery-1_0.html" target="_blank">
http://openid.net/specs/openid-connect-discovery-1_0.html</a><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">OpenID Connect Dynamic Client Registration:
<a href="http://openid.net/specs/openid-connect-registration-1_0.html" target="_blank">
http://openid.net/specs/openid-connect-registration-1_0.html</a><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">OpenID Connect Lite:
<a href="http://openid.net/specs/openid-connect-lite-1_0.html" target="_blank">http://openid.net/specs/openid-connect-lite-1_0.html</a><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">OpenID Connect Session Management:
<a href="http://openid.net/specs/openid-connect-session-1_0.html" target="_blank">
http://openid.net/specs/openid-connect-session-1_0.html</a><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">OpenID Connect Messages - not yet available<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">OpenID Conenct Standard - not yet available<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"><a href="http://openid.net/specs/openid-connect-framework-1_0.html" target="_blank"><br>
</a><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">All available specs are in SubVersion at
<a href="http://svn.openid.net/repos/specifications/connect/1.0/" target="_blank">
http://svn.openid.net/repos/specifications/connect/1.0/</a>.<o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>