<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=utf-8">
<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;}
/* 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.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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]-->
</head>
<body bgcolor=white lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Should we add “Enabling discovery of public keys” to the scope?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> --
Mike<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><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-bounces@lists.openid.net
[mailto:openid-specs-bounces@lists.openid.net] <b>On Behalf Of </b>Nat<br>
<b>Sent:</b> Monday, April 19, 2010 4:18 PM<br>
<b>To:</b> Allen Tom<br>
<b>Cc:</b> openid-specs<br>
<b>Subject:</b> Re: 2nd Draft of the OpenID v.Next Discovery Working Group
Charter<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div>
<p class=MsoNormal>Hi Allen, <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Some Public Keys are public, so I think it can be advertised
on the XRD. (Does not have to be profiled as Webfinger, I guess.) <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>I was referring to all of OP, RP, and User's public key.
<o:p></o:p></p>
</div>
<p class=MsoNormal><br>
=nat @ Tokyo via iPhone<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
On 2010/04/20, at 7:30, Allen Tom <<a href="mailto:atom@yahoo-inc.com">atom@yahoo-inc.com</a>>
wrote:<o:p></o:p></p>
</div>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif"'>Hi Nat -<br>
<br>
Is this the user’s public key? If so, the user would probably need to
authenticate first, and the public key could be returned as an attribute via
AX. <br>
<br>
Alternatively, if the public key is considered to be public information, then
it could be shared via Webfinger (again, the RP needs to know who the user is
already). <br>
Another potential mechanism would be to use the new XAuth service that was
announced today.<br>
<br>
Regarding the normalization of identifiers – can you give an example use case
that illustrates the problem?<br>
<br>
Thanks<br>
Allen<br>
<br>
<br>
<br>
On 4/19/10 3:15 PM, "Nat" <<a href="mailto:sakimura@gmail.com">sakimura@gmail.com</a>>
wrote:</span><o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif"'>Thanks Tom. <br>
<br>
I think it is included in the attributes, but public key info may qualify as a
special item just like logo. <br>
<br>
BTW, is normalization of identifiers included in the discovery or elsewhere? <br>
<br>
=nat @ Tokyo via iPhone<br>
<br>
On 2010/04/20, at 7:00, Allen Tom <<a href="mailto:atom@yahoo-inc.com">atom@yahoo-inc.com</a>>
wrote:</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Hi
All,<br>
<br>
Mike Jones and I have revised the proposed charter for the OpenID v.Next
Discovery Working Group. The main change is that the infamous NASCAR
problem is within scope. There are many potential ways that we can try to solve
(or optimize) the NASCAR, including client/browser support, as well as
server-side approaches. The text “enable potential mechanisms for discovering
context-relevant OpenID providers” means that addressing the NASCAR issue is
within the scope of the Working Group.<br>
<br>
The other change was to correct a typo in the 3rd bullet point: enable
discovery of attributes about OpenID v.Next OPs and RPs, including, but <b><i>not
</i></b>limited to visual logos and human-readable site names. The previous
version of the draft omitted the “not”<br>
<br>
Here’s the current draft of the charter:<br>
<b><br>
(a) <i><u>Charter</u></i>.<br>
(i)</b>
<b>WG
name:</b> OpenID v.Next Discovery.<br>
<b>(ii)</b>
<b>Purpose:</b>
Produce a discovery specification or family of discovery specifications
for OpenID v.Next that address the limitations and drawbacks present in the
OpenID 2.0 discovery facilities that limit OpenID’s applicability, adoption,
usability, privacy, and security. Specific goals are:<br>
</span><span style='font-size:11.0pt;font-family:Symbol'>· </span><span
style='font-size:11.0pt'> </span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>enable discovery
for OpenID identifiers, including those utilizing e-mail address syntax and
those that are URLs,<br>
<br>
</span><span style='font-size:11.0pt;font-family:Symbol'>· </span><span
style='font-size:11.0pt'> </span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>enable discovery of
features supported by OpenID v.Next OpenID Providers and Relying Parties,<br>
<br>
</span><span style='font-size:11.0pt;font-family:Symbol'>· </span><span
style='font-size:11.0pt'> </span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>enable discovery of
attributes about OpenID v.Next OPs and RPs, including, but not limited to
visual logos and human-readable site names,<br>
<br>
</span><span style='font-size:11.0pt;font-family:Symbol'>· </span><span
style='font-size:11.0pt'> </span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>enable discovery
supporting a spectrum of clients, including passive clients per current usage,
thin active clients, and active clients with OP functionality,<br>
<br>
</span><span style='font-size:11.0pt;font-family:Symbol'>· </span><span
style='font-size:11.0pt'> </span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>enable discovery
supporting authentication to and use of attributes by non-browser applications,<br>
<br>
</span><span style='font-size:11.0pt;font-family:Symbol'>· </span><span
style='font-size:11.0pt'> </span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>enable potential
mechanisms for discovering context-relevant OpenID providers,<br>
<br>
</span><span style='font-size:11.0pt;font-family:Symbol'>· </span><span
style='font-size:11.0pt'> </span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>seamlessly
integrate with and complement the other OpenID v.Next specifications.<br>
<br>
Compatibility
with OpenID 2.0 is an explicit non-goal for this work.<br>
<b>(iii)</b>
<b>Scope:</b>
Produce a next generation OpenID discovery specification or specifications,
consistent with the purpose statement.<br>
<b>(iv)</b>
<b>Proposed
List of Specifications</b>: OpenID v.Next Discovery and possibly related
specifications.<br>
<b>(v)</b>
<b>Anticipated
audience or users of the work:</b> Implementers of OpenID Providers, Relying
Parties, Active Clients, and non-browser applications utilizing OpenID.<br>
<b>(vi)</b>
<b>Language
in which the WG will conduct business</b>: English.<br>
<b>(vii)</b>
<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.<br>
<b>(viii)</b>
<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.<br>
<b>(b) <i><u>Background Information</u></i>.<br>
(i)</b>
<b>Related
work being done in other WGs or organizations</b>: OpenID Authentication
2.0 and related specifications, including Yadis 1.0. OAuth and OAuth
WRAP. XRDS, XRD, and WebFinger.<br>
<b>(ii)</b>
<b>Proposers:</b>
<br>
Allen Tom, <a href="mailto:atom@yahoo-inc.com">atom@yahoo-inc.com</a> <<a
href="mailto:atom@yahoo-inc.com">mailto:atom@yahoo-inc.com</a>> , Yahoo!
(co-chair)<br>
Michael B. Jones, <a href="mailto:mbj@microsoft.com">mbj@microsoft.com</a> <<a
href="mailto:mbj@microsoft.com">mailto:mbj@microsoft.com</a>> , Microsoft
(co-chair)<br>
John Bradley, <a href="mailto:ve7jtb@ve7jtb.com">ve7jtb@ve7jtb.com</a> <<a
href="mailto:ve7jtb@ve7jtb.com">mailto:ve7jtb@ve7jtb.com</a>> , independent<br>
<i>Additional proposers to be added here<br>
</i><b>(iii)</b>
<b>Anticipated
Contributions</b>: None.<br>
<br>
<OpenID v.Next Discovery Working Group Charter.doc><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">http://lists.openid.net/mailman/listinfo/openid-specs</a></span><o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</blockquote>
</div>
</body>
</html>