<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 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:Consolas;
panose-1:2 11 6 9 2 2 4 3 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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle19
{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;}
/* List Definitions */
@list l0
{mso-list-id:193883344;
mso-list-type:hybrid;
mso-list-template-ids:85356540 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</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 style='word-wrap: break-word;
-webkit-nbsp-mode: space;-webkit-line-break: after-white-space'>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>John,<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'>Yes, that’s what I’m suggesting. The reason is
simply to avoid making a lot of changes in some of the basic parts of OpenID.<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'>I understand the concern with multiple XML schemas and let’s
not forget, too, that Yadis might not even be used and one might have to parse
the HTML document itself looking for headers. I personally think that’s
unfortunate, but it made sense for folks running blogs and who didn’t
have the ability to insert Yadis headers or generate the required XML. (I
assume, anyway. Whatever the case, there are a couple of places one must
look for pointers to the OP.<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'>In any case, the world has clearly gotten beyond that and OpenID
2.0 is reasonably-well supported. Adding WebFinger does introduce another
step, but it’s a generic service likely to be used for lots of
things. The “discovery” issue that OpenID faces is one faced
by lots of web services, so it’s an extra step I can live with.<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'>Perhaps one thing we could do to help this process is put two
values into the Webfinger document:<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>1)<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The claimed ID<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>2)<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The URL to the OP endpoint<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'>That would reduce the number of queries one needs to make, arms
the OP with all of the information that would it would normally have, and does
cut out the need to deal with either Yadis or digging through HTTP tags.
(Still, the latter has to be kept to maintain backward compatibility and to
support those who don’t have Webfinger and just enter their OpenID URI
directly.)<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'>Paul<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 style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<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"'> John Bradley
[mailto:john.bradley@wingaa.com] <br>
<b>Sent:</b> Saturday, May 15, 2010 8:36 AM<br>
<b>To:</b> David Recordon<br>
<b>Cc:</b> Paul E. Jones; openid-specs@lists.openid.net<br>
<b>Subject:</b> Re: OpenID V.Next - Some Views to Consider<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>David,<o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>If I understand Paul correctly he is asking for a two stage
resolution.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Stage 1 Webfinger to get a openID identifier for the person.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>Stage 2 Current Yadis resolution on that ID to get the
endpoint.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>That is why he prefers claimed ID to remain http: URI.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>This would require 3 or 4 GET to go from input identifier
acct:foo@bar.com to a openID endpoint the RP can query.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>It also requires the RP to parse the current XRDS XML and
the new XRD XML with different schema and semantics.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>I think he and some others are looking at this as webfinger
being a separate front end to existing openID 2.0 authentication.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Paul correct me if I have that wrong.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>John B.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div>
<p class=MsoNormal>On 2010-05-15, at 1:16 AM, David Recordon wrote:<o:p></o:p></p>
</div>
<p class=MsoNormal><br>
<br>
<o:p></o:p></p>
<p class=MsoNormal>Hey Paul,<o:p></o:p></p>
<div>
<p class=MsoNormal>That sounds right. I'd really like to see us simplify it
though. Ideally getting to where a RP can make a single HTTP request and end up
with the OpenID endpoint. For example, why not combine steps #3 and #4?<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>--David<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal>On Thu, May 13, 2010 at 9:00 AM, Paul E. Jones <<a
href="mailto:paulej@packetizer.com">paulej@packetizer.com</a>> wrote:<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>John,</span><o:p></o:p></p>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>Perhaps we need to walk through this so
that I don’t get confused.</span><o:p></o:p></p>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>I had assumed it would work this way:</span><o:p></o:p></p>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>1) I enter <a
href="mailto:paulej@packetizer.com" target="_blank">paulej@packetizer.com</a>
into the RP’s login window</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>2) The RP would assume this is <a
href="mailto:acct%3Apaulej@packetizer.com" target="_blank">acct:paulej@packetizer.com</a></span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>3) The RP would query <a
href="http://www.packetizer.com/.well-known/host-meta" target="_blank">http://www.packetizer.com/.well-known/host-meta</a>
to get an XRD document that contains an lrdd link relation with, for example,
an href="<a href="http://www.packetizer.com/lrdd/?uri=%7Buri%7D"
target="_blank">http://www.packetizer.com/lrdd/?uri={uri}</a>"</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>4) The RP would then query the LRDD link
with the acct: URI</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>5) The would return another XRD document
with a <Subject> of <a href="mailto:acct%3Apaulej@packetizer.com"
target="_blank">acct:paulej@packetizer.com</a>, and a <Link> with a link
relation value of “openid” (or whatever the group wants to define)</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>6) The href associated with the above
<Link> would be the user’s claimed ID.</span><o:p></o:p></p>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>At this point, the RP has an OpenID
claimed ID, just as if the user had entered that value into the current OpenID
login box to begin with.</span><o:p></o:p></p>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>BTW, all of this is functioning on my
site now if you want to actually issue queries to see the results.
It’s not being used for anything right now, but I implemented it just for
the heck of it :-)</span><o:p></o:p></p>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>So, if you’re suggesting the
mapping from <a href="mailto:paulej@packetizer.com" target="_blank">paulej@packetizer.com</a>
to claimed ID would work differently, what steps are you proposing to be taken?</span><o:p></o:p></p>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>Paul</span><o:p></o:p></p>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:10.0pt'>From:</span></b><span style='font-size:10.0pt'> John
Bradley [mailto:<a href="mailto:john.bradley@wingaa.com" target="_blank">john.bradley@wingaa.com</a>]
<br>
<b>Sent:</b> Thursday, May 13, 2010 11:25 AM<br>
<b>To:</b> Paul E. Jones<br>
<b>Cc:</b> 'Santosh Rajan'; <a href="mailto:openid-specs@lists.openid.net"
target="_blank">openid-specs@lists.openid.net</a></span><o:p></o:p></p>
<div>
<div>
<p class=MsoNormal><br>
<b>Subject:</b> Re: OpenID V.Next - Some Views to Consider<o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>The
openID link relation is to your openID service eg Google not your claimed_id.<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>The
<Subject> of the XRD is the name of the thing you are looking up.<o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>If
you input <span style='font-size:11.5pt;color:#1F497D'><a
href="mailto:paulej@packetizer.com" target="_blank">paulej@packetizer.com</a> </span><span
style='font-size:9.0pt;color:black'>into a LRDD resolution process and use
webfinger for normalization you will get a XRD.</span><o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:9.0pt;color:black'>That XRD may have the <Subject>
</span><span style='font-size:10.0pt;font-family:"Courier New";
color:#1F497D'><a href="http://openid.packetizer.com/paulej" target="_blank">http://openid.packetizer.com/paulej</a> </span><o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:9.0pt;color:black'>That would be up to you or your OP to
decide. </span><o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:9.0pt;color:black'>I think Santosh wants to allow you the
option of having <a href="mailto:acct%3Apaulej@packetizer.com" target="_blank">acct:paulej@packetizer.com</a>
as the subject of the XRD.</span><o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:9.0pt;color:black'>This leads to questions about what the core
protocol is validating. Is it the claimed_id or the openid.identity.
</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:9.0pt;color:black'>Do we need both, is delegation
supported, and if so how, etc.</span><o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:9.0pt;color:black'>I think the WG needs to consider what
impact having non http/https URI as claimed ID has on the overall protocol.</span><o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:9.0pt;color:black'>I don't want to restrict the WG from
considering the issue via the charter.</span><o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:9.0pt;color:black'>John B.</span><o:p></o:p></p>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On
2010-05-13, at 10:51 AM, Paul E. Jones wrote:<o:p></o:p></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><o:p> </o:p></p>
<div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>Santosh,</span><o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>The subject of <a
href="mailto:paulej@packetizer.com" target="_blank">paulej@packetizer.com</a> is
what?</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>If that can be assumed to be <a
href="mailto:acct%3Apaulej@packetizer.com" target="_blank">acct:paulej@packetizer.com</a>,
then when WebFinger is employed, the Subject of the XRD document is <a
href="mailto:acct%3Apaulej@packetizer.com" target="_blank">acct:paulej@packetizer.com</a>.
That’s not what I want.</span><o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>Inside the XRD document should be a link
like this:</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Courier New";color:#1F497D'><Link
rel="openid" href="<a href="http://openid.packetizer.com/paulej"
target="_blank">http://openid.packetizer.com/paulej</a>"/></span><o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>The link relation value is still subject
to debate, but that’s what I think we should use to identify the claimed
ID.</span><o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>Paul</span><o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
</div>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt;
border-width:initial;border-color:initial'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in;
border-width:initial;border-color:initial'>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><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>Santosh Rajan<br>
<b>Sent:</b> Thursday, May 13, 2010 1:50 AM<br>
<b>To:</b> John Bradley<br>
<b>Cc:</b> <a href="mailto:openid-specs@lists.openid.net" target="_blank">openid-specs@lists.openid.net</a><br>
<b>Subject:</b> Re: OpenID V.Next - Some Views to Consider</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'>I will
vote for the Subject of the XRD to be the claimed_id. It only seems natural,
and clean to do that. <o:p></o:p></p>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On
Thu, May 13, 2010 at 3:17 AM, John Bradley <<a
href="mailto:john.bradley@wingaa.com" target="_blank">john.bradley@wingaa.com</a>>
wrote:<o:p></o:p></p>
</div>
<div>
<div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>So
if openID supports LRDD then normalization rules for Acct: and other URI
schemes could be specified so that they to can be resolved to a XRD.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>The
question will be for the core protocol what to use as the claimed_id.
<o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>There
are three schools of thought.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>1
The normalized input identifier<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>2
The Subject of the XRD<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>3
The claimed_id that the OP returns.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>There
are arguments to be made for all three.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I
expect this to be addressed in the WG.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt;
border-width:initial;border-color:initial'>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On
2010-05-12, at 12:34 PM, Santosh Rajan wrote:<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
</div>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>
<div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Starting
a new thread here based on an earlier one quoted below.<o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Let
us reconsider the definition of OpenID for V.next. I would like to see a new
definition for OpenID.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>"An
OpenID is Any Valid URI that can be resolved to it's Descriptor".<o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Now
let me give a little explanation on the above, with a few points.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>1)
Existing OpenID's version 1 and 2 are compatible with the above definition.
(http(s) OpenId's version 1 and 2 do resolve to their descriptor's)<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>2)
Email like identifiers are compatible with the above definition with the
webfinger protocol, and ofcourse resolve to their descriptor's.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Now
any other future protocol that can make its URI resolvable to a descriptor,
will also be a Valid OpenID. Let me give an example.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>According
to the above definition we can make "tag URI's" valid OpenID's, as
long as we have a protocol to resolve this URI to its's descriptor.<o:p></o:p></p>
</div>
</div>
<div>
<div style='border:dashed #2F6FAB 1.0pt;padding:12.0pt 12.0pt 12.0pt 12.0pt;
background-repeat:initial'><pre style='line-height:13.2pt;background:#F9F9F9'><span
style='color:black'> </span><o:p></o:p></pre><pre style='line-height:13.2pt;
background:#F9F9F9;background-repeat:initial;border-width:initial;border-color:
initial'><span style='color:black'><a href="mailto:tag%3Auser@example.com"
target="_blank">tag:user@example.com</a>,2007-11-02:Tag_URI</span><o:p></o:p></pre></div>
<div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Now
as far as I am concerned tag URI's are even better as OpenID's, because they
are unique over space and time.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Webfinger
support for tag URI's anyone? :-)<o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'>----------
Forwarded message ----------<br>
From: <b>Paul E. Jones</b> <<a href="mailto:paulej@packetizer.com"
target="_blank">paulej@packetizer.com</a>><br>
Date: Wed, May 12, 2010 at 8:11 AM<br>
Subject: RE: Draft charter for v.Next Attributes working group<br>
To: Santosh Rajan <<a href="mailto:santrajan@gmail.com" target="_blank">santrajan@gmail.com</a>><br>
Cc: Mike Jones <<a href="mailto:Michael.Jones@microsoft.com" target="_blank">Michael.Jones@microsoft.com</a>>, <a
href="mailto:jsmarr@stanfordalumni.org" target="_blank">jsmarr@stanfordalumni.org</a>, <a
href="mailto:openid-specs@lists.openid.net" target="_blank">openid-specs@lists.openid.net</a>, <a
href="mailto:tech-comm@openid.net" target="_blank">tech-comm@openid.net</a><br>
<br>
<o:p></o:p></p>
<div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>Santosh,</span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>Why not store the claimed ID in the
webfinger (LRDD) XRD document?</span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>The objective, I would hope, is to make
it easier to log into web sites. Email-style identifiers make that
easier, but the system does not have to be built around those.</span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>So, I sign up with a service
provider. Let’s just use my own site as an example. I am
assigned an email address <a href="mailto:paulej@packetizer.com"
target="_blank">paulej@packetizer.com</a>. Behind the scenes, I am also
assign an OpenID ID <a href="http://openid.packetizer.com/paulej"
target="_blank">http://openid.packetizer.com/paulej</a>. Now, when I
visit a web site, I can type ‘<a href="mailto:paulej@packetizer.com"
target="_blank">paulej@packetizer.com</a>’ and the site can perform a
webfinger query to discovery by OpenID ID. We would define a link
relation (something we’ve talked about before) that represents
openid. It could be <a href="http://openid.net/identity"
target="_blank">http://openid.net/identity</a> or it could be simply “openid”
(since link relations need not be URIs). Looking at the href of the
“openid” link relation, one would find my OpenID URI<a
href="http://openid.packetizer.com/paulej" target="_blank">http://openid.packetizer.com/paulej</a>.</span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>Now, should I wish to have a different
email provider than my openid provider, that’s fine: I could change the
record associated with the openid link relation to contain a different OpenID
identifier. Alternatively, I could just get an account at <a
href="http://someopenidop.com/" target="_blank">someopenidop.com</a> and
they might assign an e-mail style address like <a
href="mailto:paulej@someopenidop.com" target="_blank">paulej@someopenidop.com</a> and
perform the Webfinger resolution behind the scenes.</span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>Anyway, issue this request:</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'>$ curl <a
href="http://www.packetizer.com/lrdd/?uri=acct:paulej@packetizer.com"
target="_blank">http://www.packetizer.com/lrdd/?uri=acct:paulej@packetizer.com</a></span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>You’ll see the link relation for
my claimed ID:</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'><Link
rel="<a href="http://openid.net/identity" target="_blank">http://openid.net/identity</a>"</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'>
href="<a href="http://openid.packetizer.com/paulej" target="_blank">http://openid.packetizer.com/paulej</a>"/></span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>It does introduce another protocol, but
I think these play nicely together. The real identity would remain the
URL that OpenID uses today. The email identifier would just be an alias
for it.</span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>Paul</span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
</div>
</div>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt;
border-width:initial;border-color:initial'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in;
border-width:initial;border-color:initial'>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:10.0pt'>From:</span></b><span style='font-size:10.0pt'> Santosh
Rajan [mailto:<a href="mailto:santrajan@gmail.com" target="_blank">santrajan@gmail.com</a>] <br>
<b>Sent:</b> Tuesday, May 11, 2010 12:39 PM<br>
<b>To:</b> Paul E. Jones<br>
<b>Cc:</b> Mike Jones; <a href="mailto:jsmarr@stanfordalumni.org"
target="_blank">jsmarr@stanfordalumni.org</a>; <a
href="mailto:openid-specs@lists.openid.net" target="_blank">openid-specs@lists.openid.net</a>; <a
href="mailto:tech-comm@openid.net" target="_blank">tech-comm@openid.net</a><br>
<b>Subject:</b> Re: Draft charter for v.Next Attributes working group</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
<div style='margin-bottom:12.0pt'>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On
Tue, May 11, 2010 at 8:55 AM, Paul E. Jones <<a
href="mailto:paulej@packetizer.com" target="_blank">paulej@packetizer.com</a>>
wrote:<o:p></o:p></p>
</div>
<div>
<div>
<div>
<div>
<div>
<p class=MsoNormal><span style='font-size:11.5pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>Adding support for email-style addresses
is something I like, but something that can be provided via webfinger.
Thus, no change to the base protocol.</span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<div>
<div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I
beg to disagree here. I think the base protocol needs to address the issue of
email like identifiers. I would like to see that email like identifiers are
valid OpenID claimed id's.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>So
something like acct:example @ <a href="http://example.com/" target="_blank">example.com</a> should
be a valid OpenID claimed_id.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Also
this discussion should not be in this thread (about attributes) and maybe
someone could start a new thread on this subject.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Thanks<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Santosh<o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><a
href="http://hi.im/santosh" target="_blank">http://hi.im/santosh</a><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><br>
<br clear=all>
<br>
-- <br>
<a href="http://hi.im/santosh" target="_blank">http://hi.im/santosh</a><br>
<br>
<o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>_______________________________________________<br>
specs mailing list<br>
<a href="mailto:specs@lists.openid.net" target="_blank">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><o:p></o:p></p>
</div>
</blockquote>
</div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><br>
<br clear=all>
<br>
-- <br>
<a href="http://hi.im/santosh" target="_blank">http://hi.im/santosh</a><br>
<br>
<o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><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><o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>