Adding power grid meters to the scope of v.Next, profiles of the Core spec from the start, and discovery of trust frameworks (from Tony in another thread) are perfect examples of why I believe that v.Next is trying to bite off far too much. I have no issue with these being long term goals, but shouldn't slow down near term progress.<div>
<br></div><div>--David</div><div><br><br><div class="gmail_quote">On Mon, May 24, 2010 at 8:51 AM, Anthony Nadalin <span dir="ltr"><<a href="mailto:tonynad@microsoft.com">tonynad@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><div class="im">
<p class="MsoNormal" style="margin-bottom:2.0pt;text-autospace:none"><span style="font-size:11.0pt;color:#1F497D">></span><span style="font-size:13.0pt"> ensure the use of OpenID on mobile
devices,</span></p>
</div><p class="MsoNormal" style="margin-bottom:2.0pt;text-autospace:none"><span style="font-size:13.0pt">Ensure the use of OpenID on devices
</span></p>
<p class="MsoNormal" style="margin-bottom:2.0pt;text-autospace:none"><span style="font-size:13.0pt"> </span></p>
<p class="MsoNormal" style="margin-bottom:2.0pt;text-autospace:none"><span style="font-size:13.0pt">Would like to make sure we cover devices that are not really in the mobile space (like power grid meters, switches, etc)</span></p>
<div class="im">
<p class="MsoNormal" style="margin-bottom:2.0pt;text-autospace:none"><span style="font-size:13.0pt"> </span></p>
<p class="MsoNormal" style="margin-bottom:2.0pt;text-autospace:none"><span style="font-size:13.0pt">></span><span style="font-size:9.0pt"> </span><span style="font-size:13.0pt">define profiles
and support features intended to enable OpenID to be used at levels of assurance higher than NIST SP800-63 v2 level 1 ,</span></p>
</div><p class="MsoNormal" style="margin-bottom:2.0pt;text-autospace:none"><span style="font-size:13.0pt">Define profiles and support features intended to enable OpenID to be used at least 1 level of assurance higher than NIST SP800-63
v2 level 1.</span></p>
<p class="MsoNormal" style="margin-bottom:2.0pt;text-autospace:none"><span style="font-size:13.0pt"> </span></p>
<p class="MsoNormal" style="margin-bottom:2.0pt;text-autospace:none"><span style="font-size:13.0pt">Want to make sure we set a goal that may be reachable but not to go after the highest level and fail.
</span></p>
<p class="MsoNormal" style="margin-bottom:2.0pt;text-autospace:none"> </p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </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">From:</span></b><span style="font-size:10.0pt"> <a href="mailto:openid-specs-bounces@lists.openid.net" target="_blank">openid-specs-bounces@lists.openid.net</a> [mailto:<a href="mailto:openid-specs-bounces@lists.openid.net" target="_blank">openid-specs-bounces@lists.openid.net</a>]
<b>On Behalf Of </b>Dick Hardt</span></p><div class="im"><br>
<b>Sent:</b> Sunday, May 23, 2010 3:29 PM<br>
<b>To:</b> OpenID Specs Mailing List<br>
</div><b>Subject:</b> OpenID v.Next Core Protocol WG Charter :: DRAFT 2<p></p>
</div>
</div><div><div></div><div class="h5">
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">Hello All</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Thanks for the feedback to date, below is a revised draft. Changes are:</p>
</div>
<div>
<p class="MsoNormal">- changed use of public key from ensure to evaluate. </p>
</div>
<div>
<p class="MsoNormal">- added goal to evaluate single sign out</p>
</div>
<div>
<p class="MsoNormal">- broke multiple atttibute sources and verification of attributes and sources into separate goals</p>
</div>
<div>
<p class="MsoNormal">- added a number of additional proposers (Yes, Shade is in the list as he is supportive of this WG.)</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">I welcome any further feedback or additional requests to be added as a proposer. If I receive no significant feedback by EOB tomorrow, I will consider the charter bashing done.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">-- Dick</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in;text-autospace:none">
<b><span style="font-size:13.0pt">(a) <i><u>Charter</u></i>.</span></b></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:84.0pt;text-autospace:none">
<b><span style="font-size:13.0pt">(i)</span></b><span style="font-size:13.0pt"> <b>WG name:</b> OpenID v.Next Core Protocol.</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:84.0pt;text-autospace:none">
<b><span style="font-size:13.0pt">(ii)</span></b><span style="font-size:13.0pt"> <b>Purpose:</b> Produce a core protocol specification or family of specifications for OpenID
v.Next that address the limitations and drawbacks present in OpenID 2.0 that limit OpenID’s applicability, adoption, usability, privacy, and security. Specific goals are:</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:96.0pt;text-autospace:none">
<span style="font-size:13.0pt;font-family:Symbol">·</span><span style="font-size:9.0pt"> </span><span style="font-size:13.0pt">define core message flows and verification methods,</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:96.0pt;text-autospace:none">
<span style="font-size:13.0pt;font-family:Symbol">·</span><span style="font-size:9.0pt"> </span><span style="font-size:13.0pt">enable support for controlled release of attributes,</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:96.0pt;text-autospace:none">
<span style="font-size:13.0pt;font-family:Symbol">·</span><span style="font-size:9.0pt"> </span><span style="font-size:13.0pt">enable aggregation of attributes from multiple attribute sources,</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:96.0pt;text-autospace:none">
<span style="font-size:13.0pt;font-family:Symbol">·</span><span style="font-size:9.0pt"> </span><span style="font-size:13.0pt">enable attribute sources to provide verified attributes,</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:96.0pt;text-autospace:none">
<span style="font-size:13.0pt;font-family:Symbol">·</span><span style="font-size:9.0pt"> </span><span style="font-size:13.0pt">enable the sources of attributes to be verified,</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:96.0pt;text-autospace:none">
<span style="font-size:13.0pt;font-family:Symbol">·</span><span style="font-size:9.0pt"> </span><span style="font-size:13.0pt">enable support for a spectrum of clients, including passive clients per current usage, thin
active clients, and active clients with OP functionality,</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:96.0pt;text-autospace:none">
<span style="font-size:13.0pt;font-family:Symbol">·</span><span style="font-size:9.0pt"> </span><span style="font-size:13.0pt">enable authentication to and use of attributes by non-browser applications,</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:96.0pt;text-autospace:none">
<span style="font-size:13.0pt;font-family:Symbol">·</span><span style="font-size:9.0pt"> </span><span style="font-size:13.0pt">enable optimized protocol flows combining authentication, attribute release, and resource authorization,</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:96.0pt;text-autospace:none">
<span style="font-size:13.0pt;font-family:Symbol">·</span><span style="font-size:9.0pt"> </span><span style="font-size:13.0pt">define profiles and support features intended to enable OpenID to be used at levels of assurance
higher than NIST SP800-63 v2 level 1 ,</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:96.0pt;text-autospace:none">
<span style="font-size:13.0pt;font-family:Symbol">·</span><span style="font-size:9.0pt"> </span><span style="font-size:13.0pt">ensure the use of OpenID on mobile devices,</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:96.0pt;text-autospace:none">
<span style="font-size:13.0pt;font-family:Symbol">·</span><span style="font-size:9.0pt"> </span><span style="font-size:13.0pt">ensure the use of OpenID on existing browsers with URL length restrictions,</span><span style="font-size:13.0pt;font-family:Symbol">
</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:96.0pt;text-autospace:none">
<span style="font-size:13.0pt;font-family:Symbol">·</span><span style="font-size:9.0pt"> </span><span style="font-size:13.0pt">define an extension mechanism for identified capabilities that are not in the core specification</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:96.0pt;text-autospace:none">
<span style="font-size:9.0pt"> </span><span style="font-size:13.0pt;font-family:Symbol">·</span><span style="font-size:9.0pt"> </span><span style="font-size:13.0pt">evaluate the use of public key technology to enhance, security,
scalability and performance,</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:96.0pt;text-autospace:none">
<span style="font-size:13.0pt;font-family:Symbol">·</span><span style="font-size:9.0pt"> </span><span style="font-size:13.0pt">evaluate inclusion of single sign out
</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:96.0pt;text-autospace:none">
<span style="font-size:13.0pt;font-family:Symbol">·</span><span style="font-size:9.0pt"> </span><span style="font-size:13.0pt">complement OAuth 2.0</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:96.0pt;text-autospace:none">
<span style="font-size:13.0pt;font-family:Symbol">·</span><span style="font-size:9.0pt"> </span><span style="font-size:13.0pt">minimize migration effort from OpenID 2.0</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:96.0pt;text-autospace:none">
<span style="font-size:13.0pt;font-family:Symbol">·</span><span style="font-size:9.0pt"> </span><span style="font-size:13.0pt">seamlessly integrate with and complement the other OpenID v.Next specifications.</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:84.0pt;text-autospace:none">
<span style="font-size:13.0pt"> Compatibility with OpenID 2.0 is an explicit non-goal for this work.</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:84.0pt;text-autospace:none">
<b><span style="font-size:13.0pt">(iii)</span></b><span style="font-size:13.0pt"> <b>Scope:</b> Produce a next generation OpenID core protocol specification or specifications,
consistent with the purpose statement.</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:84.0pt;text-autospace:none">
<b><span style="font-size:13.0pt">(iv)</span></b><span style="font-size:13.0pt"> <b>Proposed List of Specifications</b>: OpenID v.Next Core Protocol and possibly related specifications.</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:84.0pt;text-autospace:none">
<b><span style="font-size:13.0pt">(v)</span></b><span style="font-size:13.0pt"> <b>Anticipated audience or users of the work:</b> Implementers of OpenID Providers, Relying Parties,
Active Clients, and non-browser applications utilizing OpenID.</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:84.0pt;text-autospace:none">
<b><span style="font-size:13.0pt">(vi)</span></b><span style="font-size:13.0pt"> <b>Language in which the WG will conduct business</b>: English.</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:84.0pt;text-autospace:none">
<b><span style="font-size:13.0pt">(vii)</span></b><span style="font-size:13.0pt"> <b>Method of work: </b>E-mail discussions on the working group mailing list, working group
conference calls, and face-to-face meetings at the Internet Identity Workshop and OpenID summits.</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:84.0pt;text-autospace:none">
<b><span style="font-size:13.0pt">(viii)</span></b><span style="font-size:13.0pt"> <b>Basis for determining when the work of the WG is completed:</b> Work will not be deemed
to be complete until there is a rough consensus that the resulting protocol specification or family of specifications fulfills the working group goals. Additional proposed changes beyond that initial consensus will be evaluated on the basis of whether they
increase or decrease consensus within the working group. The work will be completed once it is apparent that rough consensus on the draft has been achieved and there are two working, interoperating implementations, consistent with the purpose and scope.</span></p>
<p class="MsoNormal" style="margin-left:.5in;text-autospace:none">
<b><span style="font-size:13.0pt">(b) <i><u>Background Information</u></i>.</span></b></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:84.0pt;text-autospace:none">
<b><span style="font-size:13.0pt">(i)</span></b><span style="font-size:13.0pt"> <b>Related work being done in other WGs or organizations</b>: OpenID Authentication 2.0 and related
specifications, including Attribute Exchange (AX), Contract Exchange (CX), Provider Authentication Policy Extension (PAPE), Artifact Binding (AB) and the draft User Interface (UI) Extension. OAuth 2.0, SAML 2.0 Core and SAML Authn Context.</span></p>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:2.0pt;margin-left:84.0pt;text-autospace:none">
<b><span style="font-size:13.0pt">(ii)</span></b><span style="font-size:13.0pt"> <b>Proposers:</b></span></p>
<p class="MsoNormal" style="margin-left:.5in;text-autospace:none">
<span style="font-size:13.0pt">Dick Hardt, <a href="mailto:dick.hardt@gmail.com" target="_blank"><span style="color:#6187AD">dick.hardt@gmail.com</span></a> (chair)</span></p>
<p class="MsoNormal" style="margin-left:.5in;text-autospace:none">
<span style="font-size:13.0pt">Michael B. Jones, <a href="mailto:mbj@microsoft.com" target="_blank"><span style="color:#6187AD">mbj@microsoft.com</span></a></span></p>
<p class="MsoNormal" style="margin-left:.5in;text-autospace:none">
<span style="font-size:13.0pt">Breno de Medeiros, <a href="mailto:breno@google.com" target="_blank"><span style="color:#6187AD">breno@google.com</span></a></span></p>
<p class="MsoNormal" style="margin-left:.5in;text-autospace:none">
<span style="font-size:13.0pt">Ashish Jain, <a href="mailto:Ashish.Jain@paypal.com" target="_blank"><span style="color:#6187AD">Ashish.Jain@paypal.com</span></a></span></p>
<p class="MsoNormal" style="margin-left:.5in;text-autospace:none">
<span style="font-size:13.0pt">George Fletcher, <a href="mailto:gffletch@aol.com" target="_blank"><span style="color:#6187AD">gffletch@aol.com</span></a></span></p>
<p class="MsoNormal" style="margin-left:.5in;text-autospace:none">
<span style="font-size:13.0pt">John Bradley, <a href="mailto:ve7jtb@ve7jtb.com" target="_blank">
ve7jtb@ve7jtb.com</a></span></p>
<p class="MsoNormal" style="margin-left:.5in;text-autospace:none">
<span style="font-size:13.0pt">Nat Sakimura, <a href="mailto:n-sakimura@nri.co.jp" target="_blank">
n-sakimura@nri.co.jp</a></span></p>
<p class="MsoNormal" style="margin-left:.5in;text-autospace:none">
<span style="font-size:13.0pt">Shade, <span style="color:#6187AD"><a href="mailto:sysadmin@shadowsinthegarden.com" target="_blank">sysadmin@shadowsinthegarden.com</a></span></span></p>
<p class="MsoNormal" style="margin-left:.5in;text-autospace:none">
<span style="font-size:13.0pt"> </span></p>
<p class="MsoNormal" style="margin-left:.5in">
<b><span style="font-size:13.0pt"> (iii)</span></b><span style="font-size:13.0pt"> <b>Anticipated Contributions</b>: None.</span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
</div></div></div>
</div>
<br>_______________________________________________<br>
specs mailing list<br>
<a href="mailto:specs@lists.openid.net">specs@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs</a><br>
<br></blockquote></div><br></div>