<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<small><font face="Helvetica, Arial, sans-serif">+1<br>
<br>
If OpenID is intended to cover needs other than near zero security
social networks, it is essential - also from a branding perspective -
that we take a holistic perspective on the authentication use cases,
covering various initial login scenarios as well as stepping up from a
lower to a higher authentication level.<br>
<br>
Currently many potential RP organizations are basing their evaluation
of OpenID on a few peoples personal use of the larger existing
providers, which makes it an uphill battle to convince these
organizations that OpenID may also aim at applications with higher
security requirements.<br>
<br>
Maybe Robert Ott's presentation "<span
style="font-family: Helvetica,Arial,sans-serif; color: rgb(0, 0, 0);">OpenID
in conjunction with Strong Authentication (OTP, YubiKey, Biometrics,
iPhone, Certificates, SuisseID)" at the upcoming OpenID Summit in
London next week can stimulate this discussion. </span><a class="moz-txt-link-freetext" href="https://wiki.openid.net/2010-OpenID-Summit-EU">https://wiki.openid.net/2010-OpenID-Summit-EU</a></font></small><br>
<pre class="moz-signature" cols="72">
=henrik
</pre>
<br>
Mike Jones skrev:
<blockquote
cite="mid:A38B81087C0DD74788C1C5A631ED6C1F439CCA37@TK5EX14MBXC138.redmond.corp.microsoft.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
@font-face
{font-family:"Lucida Grande";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* 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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</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]-->
<div class="Section1">
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">Hi
Chris,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">Thanks
for getting this out.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">In
my view, you should leave support for active clients in scope for
consideration by the working group since having an active client
definitely should impact the RP user experience. For instance, if you
have identity in the browser, you probably want the RP to be aware of
it and delegate some or all of the identity UX to the active client,
rather than handling it itself by putting up a NASCAR screen, etc.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">
Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">
-- Mike<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<div
style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif";">From:</span></b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif";">
<a class="moz-txt-link-abbreviated" href="mailto:openid-specs-ui-bounces@lists.openid.net">openid-specs-ui-bounces@lists.openid.net</a>
[<a class="moz-txt-link-freetext" href="mailto:openid-specs-ui-bounces@lists.openid.net">mailto:openid-specs-ui-bounces@lists.openid.net</a>]
<b>On Behalf Of </b>Chris Messina<br>
<b>Sent:</b> Monday, May 31, 2010 4:40 PM<br>
<b>To:</b> Dick Hardt<br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:specs-council@openid.net">specs-council@openid.net</a>; <a class="moz-txt-link-abbreviated" href="mailto:openid-specs@lists.openid.net">openid-specs@lists.openid.net</a>;
<a class="moz-txt-link-abbreviated" href="mailto:specs-ui@lists.openid.net">specs-ui@lists.openid.net</a><br>
<b>Subject:</b> Re: [Specs-ui] [OIDFSC] Draft OpenID 2.x User
Experience working group charter<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">No, there hasn't been any consensus about
renaming it. I'm putting it out there as a draft for discussion.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I'll take that as one vote for keeping that line
in the charter. Looking forward to other feedback!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Chris<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Mon, May 31, 2010 at 4:28 PM, Dick Hardt <<a
moz-do-not-send="true" href="mailto:dick.hardt@gmail.com">dick.hardt@gmail.com</a>>
wrote:<o:p></o:p></p>
<div>
<p class="MsoNormal">Chris, <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I have not seen any consensus to renaming v.Next
to 2.x. Having said that, I don't think this WG needs to have a version
does it?<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I think this work would be really useful to the
full spectrum of clients.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color: rgb(136, 136, 136);">-- Dick</span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On 2010-05-31, at 3:27 PM, Chris Messina wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<p class="MsoNormal">Mike Jones prepared the initial version of this
charter, and I took the liberty of renaming v.Next to 2.x, and made
compatibility with 2.x an explicit goal of this work.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I'm reluctant of the applicability of this work
to active clients and have subsequently removed this line:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">· produce user experience guidelines for
supporting for a spectrum of clients, including passive clients per
current usage, thin active clients, and active clients with OP
functionality,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Feedback welcome.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Chris<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><b>(a) <i><u>Charter</u></i>.</b><o:p></o:p></p>
</div>
<p
style="margin-right: 0in; margin-bottom: 1.2pt; margin-left: 0.4in;">
<b><span style="font-size: 8pt; font-family: "Arial","sans-serif";">(i)</span></b><span
style="font-size: 8pt; font-family: "Arial","sans-serif";">
<b>WG name:</b> OpenID 2.x User Experience.<o:p></o:p></span></p>
<p
style="margin-right: 0in; margin-bottom: 1.2pt; margin-left: 0.4in;">
<b><span style="font-size: 8pt; font-family: "Arial","sans-serif";">(ii)</span></b><span
style="font-size: 8pt; font-family: "Arial","sans-serif";">
<b>Purpose:</b> Produce a user experience specification or family of
specifications for OpenID 2.x that address the limitations and
drawbacks present in the OpenID 2.0 that limit OpenID’s applicability,
adoption, usability, privacy, and security. Specific goals are:<o:p></o:p></span></p>
<p
style="margin-right: 0in; margin-bottom: 1.2pt; margin-left: 0.5in;">
<span style="font-size: 8pt; font-family: "Lucida Grande","serif";">·</span><span
style="font-size: 5.5pt;">
</span><span
style="font-size: 8pt; font-family: "Arial","sans-serif";">produce
user experience guidelines for less intrusive authentication user
experiences than full-page browser redirect,<o:p></o:p></span></p>
<p
style="margin-right: 0in; margin-bottom: 1.2pt; margin-left: 0.5in;">
<span style="font-size: 8pt; font-family: "Lucida Grande","serif";">·</span><span
style="font-size: 5.5pt;">
</span><span
style="font-size: 8pt; font-family: "Arial","sans-serif";">produce
user experience guidelines for controlled and uncontrolled release of
attributes,<o:p></o:p></span></p>
<p
style="margin-right: 0in; margin-bottom: 1.2pt; margin-left: 0.5in;">
<span style="font-size: 8pt; font-family: "Lucida Grande","serif";">·</span><span
style="font-size: 5.5pt;">
</span><span
style="font-size: 8pt; font-family: "Arial","sans-serif";">produce
user experience guidelines for use of identities and attributes by
non-browser applications,<o:p></o:p></span></p>
<p
style="margin-right: 0in; margin-bottom: 1.2pt; margin-left: 0.5in;">
<span style="font-size: 8pt; font-family: "Lucida Grande","serif";">·</span><span
style="font-size: 5.5pt;">
</span><span
style="font-size: 8pt; font-family: "Arial","sans-serif";">produce
user experience guidelines for optimized protocol flows combining
authentication, attribute release, and resource authorization,<o:p></o:p></span></p>
<p
style="margin-right: 0in; margin-bottom: 1.2pt; margin-left: 0.5in;">
<span style="font-size: 8pt; font-family: "Lucida Grande","serif";">·</span><span
style="font-size: 5.5pt;">
</span><span
style="font-size: 8pt; font-family: "Arial","sans-serif";">produce
user experience guidelines for use of OpenID on mobile devices,<o:p></o:p></span></p>
<p
style="margin-right: 0in; margin-bottom: 1.2pt; margin-left: 0.5in;">
<span style="font-size: 8pt; font-family: "Lucida Grande","serif";">·</span><span
style="font-size: 5.5pt;">
</span><span
style="font-size: 8pt; font-family: "Arial","sans-serif";">seamlessly
integrate with and complement the other OpenID 2.x specifications.<o:p></o:p></span></p>
<p
style="margin-right: 0in; margin-bottom: 1.2pt; margin-left: 0.4in; min-height: 15px;">
<span style="font-size: 8pt; font-family: "Arial","sans-serif";"><o:p> </o:p></span></p>
<p
style="margin-right: 0in; margin-bottom: 1.2pt; margin-left: 0.4in;">
<span style="font-size: 8pt; font-family: "Arial","sans-serif";">Compatibility
with OpenID 2.x is an explicit goal for this work.<o:p></o:p></span></p>
<p
style="margin-right: 0in; margin-bottom: 1.2pt; margin-left: 0.4in; min-height: 15px;">
<span style="font-size: 8pt; font-family: "Arial","sans-serif";"><o:p> </o:p></span></p>
<p
style="margin-right: 0in; margin-bottom: 1.2pt; margin-left: 0.4in;">
<b><span style="font-size: 8pt; font-family: "Arial","sans-serif";">(iii)</span></b><span
style="font-size: 8pt; font-family: "Arial","sans-serif";">
<b>Scope:</b> Produce a current generation OpenID user experience
specification or specifications, consistent with the purpose statement.<o:p></o:p></span></p>
<p
style="margin-right: 0in; margin-bottom: 1.2pt; margin-left: 0.4in;">
<b><span style="font-size: 8pt; font-family: "Arial","sans-serif";">(iv)</span></b><span
style="font-size: 8pt; font-family: "Arial","sans-serif";">
<b>Proposed List of Specifications</b>: OpenID 2.x User Experience
and possibly related specifications.<o:p></o:p></span></p>
<p
style="margin-right: 0in; margin-bottom: 1.2pt; margin-left: 0.4in;">
<b><span style="font-size: 8pt; font-family: "Arial","sans-serif";">(v)</span></b><span
style="font-size: 8pt; font-family: "Arial","sans-serif";">
<b>Anticipated audience or users of the work:</b> Implementers of
OpenID Providers, Relying Parties, Active Clients, and non-browser
applications utilizing OpenID.<o:p></o:p></span></p>
<p
style="margin-right: 0in; margin-bottom: 1.2pt; margin-left: 0.4in;">
<b><span style="font-size: 8pt; font-family: "Arial","sans-serif";">(vi)</span></b><span
style="font-size: 8pt; font-family: "Arial","sans-serif";">
<b>Language in which the WG will conduct business</b>: English.<o:p></o:p></span></p>
<p
style="margin-right: 0in; margin-bottom: 1.2pt; margin-left: 0.4in;">
<b><span style="font-size: 8pt; font-family: "Arial","sans-serif";">(vii)</span></b><span
style="font-size: 8pt; font-family: "Arial","sans-serif";">
<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.<o:p></o:p></span></p>
<p
style="margin-right: 0in; margin-bottom: 1.2pt; margin-left: 0.4in;">
<b><span style="font-size: 8pt; font-family: "Arial","sans-serif";">(viii)</span></b><span
style="font-size: 8pt; font-family: "Arial","sans-serif";">
<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 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 maximal consensus on the draft
has been achieved, consistent with the purpose and scope.<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><b>(b) <i><u>Background Information</u></i>.</b><o:p></o:p></p>
</div>
<p
style="margin-right: 0in; margin-bottom: 1.2pt; margin-left: 0.4in;">
<b><span style="font-size: 8pt; font-family: "Arial","sans-serif";">(i)</span></b><span
style="font-size: 8pt; font-family: "Arial","sans-serif";">
<b>Related work being done in other WGs or organizations</b>: <a
moz-do-not-send="true"
href="http://wiki.openid.net/OpenID-User-Interface-Work-Group-Proposal"
target="_blank">
Draft User Interface (UI) Extension</a>. <a moz-do-not-send="true"
href="http://kantarainitiative.org/confluence/display/ulx/"
target="_blank">
Kantara Universal Login Experience (ULX) </a>working group. <a
moz-do-not-send="true" href="http://rpxnow.com/" target="_blank">
RPX product design</a>. <a moz-do-not-send="true"
href="http://developers.facebook.com/docs/authentication/"
target="_blank">
Facebook Authentication Guidelines</a>. <a moz-do-not-send="true"
href="http://sites.google.com/site/oauthgoog/UXFedLogin"
target="_blank">
Google user authentication research</a>.<o:p></o:p></span></p>
<p
style="margin-right: 0in; margin-bottom: 1.2pt; margin-left: 0.4in;">
<b><span style="font-size: 8pt; font-family: "Arial","sans-serif";">(ii)</span></b><span
style="font-size: 8pt; font-family: "Arial","sans-serif";">
<b>Proposers:</b><o:p></o:p></span></p>
<div style="margin-left: 0.4in;">
<p class="MsoNormal">Chris Messina, <a moz-do-not-send="true"
href="mailto:chris.messina@gmail.com" target="_blank">
<span style="color: rgb(0, 101, 204);">chris.messina@gmail.com</span></a>
(chair)<o:p></o:p></p>
</div>
<div style="margin-left: 0.4in;">
<p class="MsoNormal"><span style="color: black;">Dick Hardt, <a
moz-do-not-send="true" href="mailto:dick.hardt@gmail.com"
target="_blank">
dick.hardt@gmail.com</a></span><span style="color: rgb(0, 101, 204);"><o:p></o:p></span></p>
</div>
<div style="margin-left: 0.4in;">
<p class="MsoNormal"><i>Additional proposers to be added here</i><o:p></o:p></p>
</div>
<p
style="margin-right: 0in; margin-bottom: 1.2pt; margin-left: 0.4in;">
<b><span style="font-size: 8pt; font-family: "Arial","sans-serif";">(iii)</span></b><span
style="font-size: 8pt; font-family: "Arial","sans-serif";">
<b>Anticipated Contributions</b>: None.<o:p></o:p></span></p>
<p class="MsoNormal"><br>
-- <br>
Chris Messina<br>
Open Web Advocate, Google<br>
<br>
Personal: <a moz-do-not-send="true" href="http://factoryjoe.com/"
target="_blank">http://factoryjoe.com</a><br>
Follow me on Buzz: <a moz-do-not-send="true"
href="http://buzz.google.com/chrismessina" target="_blank">
http://buzz.google.com/chrismessina</a> <br>
...or Twitter: <a moz-do-not-send="true"
href="http://twitter.com/chrismessina" target="_blank">http://twitter.com/chrismessina</a>
<br>
<br>
This email is: [ ] shareable [X] ask first [ ] private<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<br>
-- <br>
Chris Messina<br>
Open Web Advocate, Google<br>
<br>
Personal: <a moz-do-not-send="true" href="http://factoryjoe.com">http://factoryjoe.com</a><br>
Follow me on Buzz: <a moz-do-not-send="true"
href="http://buzz.google.com/chrismessina">http://buzz.google.com/chrismessina</a>
<br>
...or Twitter: <a moz-do-not-send="true"
href="http://twitter.com/chrismessina">http://twitter.com/chrismessina</a>
<br>
<br>
This email is: [ ] shareable [X] ask first [ ] private<o:p></o:p></p>
</div>
</div>
</div>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
specs mailing list
<a class="moz-txt-link-abbreviated" href="mailto:specs@lists.openid.net">specs@lists.openid.net</a>
<a class="moz-txt-link-freetext" href="http://lists.openid.net/mailman/listinfo/openid-specs">http://lists.openid.net/mailman/listinfo/openid-specs</a>
</pre>
</blockquote>
</body>
</html>