<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" 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: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:D = "DAV:" xmlns:x2 =
"http://schemas.microsoft.com/office/excel/2003/xml" 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:sps =
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi =
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf =
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf =
"http://schemas.microsoft.com/sharepoint/soap/workflow/" 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:ex12t =
"http://schemas.microsoft.com/exchange/services/2006/types"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-2022-jp">
<META content="MSHTML 6.00.6000.16481" name=GENERATOR>
<STYLE>@font-face {
        font-family: Calibri;
}
@font-face {
        font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
LI.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
DIV.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
A:link {
        COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
        COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
        COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
        COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
        COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-reply
}
.MsoChpDefault {
        mso-style-type: export-only
}
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 lang=EN-US vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=218535009-10072007><FONT face="MS Pゴシック"
color=#0000ff size=2>Hi.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=218535009-10072007><FONT face="MS Pゴシック"
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=218535009-10072007><FONT face="MS Pゴシック"
color=#0000ff size=2>It was first time for me to see the PAPE and was nice. At
the same time, I started to wonder about the relationship between AQE and PAPE.
If you (David) could enlighten me on this topic, it would be very nice.
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=218535009-10072007><FONT face="MS Pゴシック"
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=218535009-10072007><FONT face="MS Pゴシック"
color=#0000ff size=2>Now, coming to the topic of this "classified OPs", I would
rather like to think of it as the AQ and Reputation issue. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=218535009-10072007><FONT face="MS Pゴシック"
color=#0000ff size=2>To me, Assertion Quality is defined by "Enrollment
Quality", "Authentication Quality", and "Operational Quality of OP".
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=218535009-10072007><FONT face="MS Pゴシック"
color=#0000ff size=2>AQE has the first two (though I would like to add several
more enrollment properties: oob is too broad. I would like to see something like
In-Person-with-photo-id etc. added.) . The last one can be taken care of by
Reputation (and audit). </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=218535009-10072007><FONT face="MS Pゴシック"
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=218535009-10072007><FONT face="MS Pゴシック"
color=#0000ff size=2>Ideally, there would be multiple reputation services that
RP can subscribe. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=218535009-10072007><FONT face="MS Pゴシック"
color=#0000ff size=2>Also, for audit, OPs should be able to present the audit
status, which can be verified at the audit service provider site in turn.
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=218535009-10072007><FONT face="MS Pゴシック"
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=218535009-10072007><FONT face="MS Pゴシック"
color=#0000ff size=2>This way, we would avoid having central authority
classifying OPs and yet allwoing RPs to have reasonable information for the
evaluation of the assertion. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=218535009-10072007><FONT face="MS Pゴシック"
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=218535009-10072007><FONT face="MS Pゴシック"
color=#0000ff size=2>=nat</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=ja dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> general-bounces@openid.net
[mailto:general-bounces@openid.net] <B>On Behalf Of </B>Recordon,
David<BR><B>Sent:</B> Monday, July 09, 2007 4:13 AM<BR><B>To:</B> John Wang;
OpenID - General<BR><B>Subject:</B> Re: [OpenID] Initial thoughts on
OpenID<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Hey
John,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Saw
your post yesterday and actually syndicated it on <A
href="http://planet.openid.net">http://planet.openid.net</A>.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Generally
I agree with you, I think the classification of providers and reliers is
reasonable though really crosses the border from just the OpenID world as
well.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">I
don't think I agree that there are a lot of Relying Parties also issuing
OpenIDs and then only consuming their own. Rather, I think part of the
current problem is there being an unproportionate number of Providers to
Relying Parties. This is however changing with sites like <A
href="http://ma.gnolia.com">http://ma.gnolia.com</A> only being an OpenID
Relying Party and AOL bringing on Relying Parties later this
month.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Have
you seen <A
href="http://openid.net/specs/openid-provider-authentication-policy-extension-1_0-01.html">http://openid.net/specs/openid-provider-authentication-policy-extension-1_0-01.html</A>
by any chance?<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">--David<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<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'">
general-bounces@openid.net [mailto:general-bounces@openid.net] <B>On Behalf Of
</B>John Wang<BR><B>Sent:</B> Saturday, July 07, 2007 11:27 PM<BR><B>To:</B>
OpenID - General<BR><B>Subject:</B> [OpenID] Initial thoughts on
OpenID<o:p></o:p></SPAN></P></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Recently I started considering OpenID authentication for a
project. I watched two screencasts and spoke to a few people to get a general
feel for the project and then jotted down my thoughts here:<BR><BR><A
href="http://www.dev411.com/blog/2007/07/07/initial-thoughts-on-openid"
target=_blank>http://www.dev411.com/blog/2007/07/07/initial-thoughts-on-openid</A><BR><BR>Some
of the thoughts are similar to some posts on this list. Please let me know
where/if I'm wrong. I considered inlining the text but it's kind of long.
<BR><BR>--<BR>John Wang<BR><A
href="http://www.dev411.com/blog/">http://www.dev411.com/blog/</A><o:p></o:p></P></DIV></BLOCKQUOTE></BODY></HTML>