<div dir="ltr">I agree with allowing acct: etc. grammatically though it is not so simple. <div style><br></div><div><div style>As a chair of the WG, I have objection on changing the normative normalization rule because of the process reason. If it were to happen, it should have happened before the Public Review Period. The reason like "we intended to be, and examples are showing ... " is not acceptable. We are creating a standard, and normative language is everything. Just changing normative language technically after the freeze announcement will put the integrity of the process in question. </div>
<div style><br></div><div style>We could deal with technical changes in the comment resolution meetings, but we should not make on-the-fly changes. </div></div><div style><br></div><div style>Note: this does not prevent interop participants to do the acct: normalization "experiments". </div>
<div style>I expect that is going to be harder than https:// normalization though because you have to hand code the host part extraction by yourself and that's actually error prone. </div><div style><br></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">2013/7/2 Justin Richer <span dir="ltr"><<a href="mailto:jricher@mitre.org" target="_blank">jricher@mitre.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Agree with Mike -- I think the best bet would be that the grammar
simply allow all of the examples given in the document.<span class="HOEnZb"><font color="#888888"><br>
<br>
-- Justin</font></span><div><div class="h5"><br>
<br>
<div>On 07/01/2013 12:49 PM, Mike Jones
wrote:<br>
</div>
<blockquote type="cite">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I
agree that we should apply errata to have the grammar match
the examples. Let’s agree on specific wording on today’s
call in 6 hours.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I
would be strongly against normalizing everything to https:
because that would be an unnecessary breaking change.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">
-- Mike<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<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"">
Nat Sakimura [<a href="mailto:sakimura@gmail.com" target="_blank">mailto:sakimura@gmail.com</a>]
<br>
<b>Sent:</b> Monday, July 01, 2013 9:47 AM<br>
<b>To:</b> John Bradley<br>
<b>Cc:</b> Mike Jones; Justin Richer;
<a href="mailto:openid-specs-ab@lists.openid.net" target="_blank">openid-specs-ab@lists.openid.net</a> List; Peter Saint-Andre<br>
<b>Subject:</b> Re: [Openid-specs-ab] Issue #856: Discovery
- URI grammar definition doesn't allow acct: scheme
(openid/connect)<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">Agreed, and there, Cool URI people would
say: everything should normalized to <a>https://</a> !<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I am ok with the errata that will allow
acct: and mailto:, tel: etc. to be dealt with. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Normatively changing the normalization
rule from adding <a>https://</a> to acct: is probably not given
it did not make into before the public review period and
sticking to <a>https://</a> has values such as less
susceptibility towards the change. <u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p>
<div>
<p class="MsoNormal">2013/7/2 John Bradley <<a href="mailto:ve7jtb@ve7jtb.com" target="_blank">ve7jtb@ve7jtb.com</a>><u></u><u></u></p>
<div>
<p class="MsoNormal">It was discussed on the June 17 call
and Mike asked me to write up a Errata to have the
normative text match the examples showing acct:.<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">In the original you are correct
user@host was normalized to <a>https://</a> and it was not
legal in the normalization rules to have
acct:user@host as user input.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">As a side note we are also missing
normalization to the tel: uri for strings beginning
with + (that can be added later)<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">If we revert back to normalizing to
<a>https://</a> then the examples need to change to match.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I am not emotionally attached to
"acct:" but I thought we were fully adopting WF in
this draft, and that implies normalizing things to
"acct:" though that is a touch vague as has been
pointed out in there review. If every protocol
picks a different scheme to normalize the resource URI
to that will cause problems for WF deployment.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">John B.<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On 2013-07-01, at 11:13 AM,
Nat Sakimura <<a href="mailto:sakimura@gmail.com" target="_blank">sakimura@gmail.com</a>>
wrote:<u></u><u></u></p>
</div>
<p class="MsoNormal"><br>
<br>
<u></u><u></u></p>
<div>
<p class="MsoNormal">Right, we normalized to
<a>https://</a> when a user just typed user@host and
that was a quite deliberate thing I did. It
was not just left off from SWD day. We had
plenty of days to review it, and I did. There
were several reasons: <u></u><u></u></p>
<div>
<ol start="1" type="1">
<li class="MsoNormal">
I was not certain of what will become of
acct: uri. I am still concerned that some
Cool URI people may ring in at the very
end and jeopardize; <u></u><u></u></li>
<li class="MsoNormal">
Minimal impact to the existing codes;<u></u><u></u></li>
<li class="MsoNormal">
Easy for the code: they can use
conventional URI parser to extract
userinfo, host, and port. <u></u><u></u></li>
<li class="MsoNormal">
There is nothing wrong with using <a>https://</a>
instead of acct: as far as Webfinger is
concerned. <u></u><u></u></li>
</ol>
<div>
<p class="MsoNormal">True, the Webfinger has
in its non-normative example, acct: uri
example for OpenID Connect. However, that
is just an example. When we went to
implementer's draft review period, we had
a normative text around
<a>https://</a>,
which has no problem on our part. Switch
from acct: to <a>https://</a> is not an editorial
errata. It is a technical change and
should not be dealt with lightly from the
process point of view. <u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Also, I cannot find the
ticket which is associated with the change
set <a href="https://bitbucket.org/openid/connect/commits/20ebf0461dea1daa76d63aeb824fb36dd79fd2f2" target="_blank">20ebf04</a>, which is a
normative change after the start of the
review period. Is there one? If not, we need
to create it. <u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Nat<u></u><u></u></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p>
<div>
<p class="MsoNormal">2013/7/1 John Bradley
<<a href="mailto:ve7jtb@ve7jtb.com" target="_blank">ve7jtb@ve7jtb.com</a>><u></u><u></u></p>
<div>
<p class="MsoNormal">The problem with
normalizing "user@host" to
<a href="https:user@host" target="_blank">"https:user@host"</a> is mostly that simple
WF servers may only match on the acct:
form it seems to be the recommended thing
to normalize input to.<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Before we made the
last change in normalization rules to
support "acct:" all input without a
scheme was normalized to "https:" ,
even if we backed that out we would
still need to still need a rule to
support non-higher-archical URI like
"acct:".<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">The bottom line is if
someone types "user@host" we should
have one way of converting that to a URI
for WF, otherwise we are headed for
interoperability issues.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">We also need to think
about what we do for RFC3541 "tel:" as
it is also not higher-archical, though
likely it will need some sort of
meta-data service/proxy to be useful. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">John B.<u></u><u></u></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On
2013-06-29, at 9:16 PM, Nat
Sakimura <<a href="mailto:sakimura@gmail.com" target="_blank">sakimura@gmail.com</a>>
wrote:<u></u><u></u></p>
</div>
<p class="MsoNormal"><br>
<br>
<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal">Actually, I
and John discussed this issue
over Skype last night and
John's response was the result
of it. So my comments are
included in his response. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">BTW, what
is the value in normalizing to
acct scheme? To me, https
seems perfectly fine, and
would not cause the problems
that Justin is getting. <br>
<br>
=nat via iPhone<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
Jun 30, 2013 2:17<span lang="JA">$B!"(B</span>Mike Jones
<<a href="mailto:Michael.Jones@microsoft.com" target="_blank">Michael.Jones@microsoft.com</a>>
<span lang="JA">$B$N%a%C%;!<%8(B</span>:<u></u><u></u></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Can
you work on a concrete
proposal to apply as
errata, John? And Nat,
once you’re able to think
critically, maybe you
could work on this as
well?</span><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">
Thanks both,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">
-- Mike</span><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
</div>
<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 [<a href="mailto:ve7jtb@ve7jtb.com" target="_blank">mailto:ve7jtb@ve7jtb.com</a>]
<br>
<b>Sent:</b> Saturday,
June 29, 2013 9:19 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Justin
Richer; <a href="mailto:openid-specs-ab@lists.openid.net" target="_blank">
openid-specs-ab@lists.openid.net</a> List; Peter Saint-Andre<br>
<b>Subject:</b> Re:
[Openid-specs-ab]
Issue #856: Discovery
- URI grammar
definition doesn't
allow acct: scheme
(openid/connect)</span><u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<p class="MsoNormal">I
think part of our problem is
that in RFC3986 "host" is
part of authority and
authority is part of
higher-part which begins
with "//".<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal">The
"mailto" scheme stuffs
everything into path so
doesn't have and authority
owing to dealing with
multiple recipients (it is
a complex scheme) .<u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal">If
"acct" was using
higher-part rather than
path it would simplify our
job trying to normalize
the various sorts of
inputs for discovery.<u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal">The
"acct" scheme uses ":"
userpart "@" host (It
defines userpart rather
than re using userinfo).
While being unusual
having host in a path, I
am guessing it is just the
ABNF, so is a different
host from the one in
higher-part.<u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal">I
don't think the below
works for generic URI
without a higher-part so
we would be better saying
or "acct" ":" userpart
"@" host.<u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal">That
leaves out the mailto uri
but processing rules to
generically pick that
apart are a real
challenge, and would need
to be restricted to a
single recipient with no
headers etc so would need
it's own section for that
scheme specifically if we
want to support it.<u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal">There
is also a problem with
differentiating
<a href="http://foo.org/" target="_blank">foo.org</a>:8080
as that could be
interpreted as a scheme or
<a href="http://foo.org/" target="_blank">foo.org</a>
with a path of 8080 so
being explicit about what
schemes without
higher-part are supported
may be a good idea. <u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal">John
B.<u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal">On
2013-06-29, at 7:20
AM, Mike Jones <<a href="mailto:Michael.Jones@microsoft.com" target="_blank">Michael.Jones@microsoft.com</a>>
wrote:<u></u><u></u></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">I'd
add another "or"
to prevent
confusion as
below, but
otherwise I agree
with this change.
Do others?</span><u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">a
URI in the form of
scheme "://"
authority
path-abempty [ "?"
query ] [ "#"
fragment ] <span style="color:red">or </span>authority
path-abempty [ "?"
query ] [ "#"
fragment ] <span style="color:red">or
scheme ":"
userinfo "@"
host</span> per
RFC 3986 [RFC3986]</span><u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
-- Mike</span><u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">-----Original
Message-----<br>
From: <a href="mailto:openid-specs-ab-bounces@lists.openid.net" target="_blank">openid-specs-ab-bounces@lists.openid.net</a>
[mailto:<a href="mailto:openid-" target="_blank">openid-</a><a href="mailto:specs-ab-bounces@lists.openid.net" target="_blank">specs-ab-bounces@lists.openid.net</a>]
On Behalf Of
Justin Richer<br>
Sent: Friday, June
28, 2013 6:55 AM<br>
To: <a href="mailto:openid-specs-ab@lists.openid.net" target="_blank">openid-specs-ab@lists.openid.net</a><br>
Subject:
[Openid-specs-ab]
Issue #856:
Discovery - URI
grammar definition
doesn't allow
acct: scheme
(openid/connect)</span><u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">New
issue 856:
Discovery - URI
grammar definition
doesn't allow
acct: scheme<a href="https://bitbucket.org/openid/connect/issue/856/discovery-uri-grammar-definition-doesnt" target="_blank"><span style="color:windowtext;text-decoration:none">https://bitbucket.org/openid/connect/issue/856/discovery-uri-grammar-definition-doesnt</span></a></span><u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Justin
Richer:</span><u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">The
instructions as
written in
2.1.1/2.1.2 don't
actually allow for
the acct: URI
scheme. The acct:
scheme is a
non-heirarchical
URI, which means
it doesn't include
the "//"
component, and the
text currently
states:</span><u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">```</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
a URI either in
the form of scheme
"://" authority
path-abempty [ "?"
query ] [ "#"
fragment ] or
authority
path-abempty [ "?"
query ] [ "#"
fragment ] per RFC
3986 [RFC3986].</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">```</span><u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">I
think this needs
an errata
published as the
intent was more
like:</span><u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">```</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
a URI in the form
of scheme "://"
authority
path-abempty [ "?"
query ] [ "#"
fragment ],
authority
path-abempty [ "?"
query ] [ "#"
fragment ], **or
scheme ":"
userinfo "@"
host** per RFC
3986 [RFC3986].</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">```</span><u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">_______________________________________________</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Openid-specs-ab
mailing list</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><a href="mailto:Openid-specs-ab@lists.openid.net" target="_blank"><span style="color:windowtext;text-decoration:none">Openid-specs-ab@lists.openid.net</span></a></span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank"><span style="color:windowtext;text-decoration:none">http://lists.openid.net/mailman/listinfo/openid-specs-ab</span></a></span><u></u><u></u></p>
</div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">_______________________________________________<br>
Openid-specs-ab
mailing list<br>
<a href="mailto:Openid-specs-ab@lists.openid.net" target="_blank"><span style="color:purple">Openid-specs-ab@lists.openid.net</span></a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank"><span style="color:purple">http://lists.openid.net/mailman/listinfo/openid-specs-ab</span></a></span><u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">_______________________________________________<br>
Openid-specs-ab mailing list<br>
<a href="mailto:Openid-specs-ab@lists.openid.net" target="_blank">Openid-specs-ab@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><u></u><u></u></p>
</blockquote>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal">-- <br>
Nat Sakimura (=nat)<u></u><u></u></p>
<div>
<p class="MsoNormal">Chairman, OpenID
Foundation<br>
<a href="http://nat.sakimura.org/" target="_blank">http://nat.sakimura.org/</a><br>
@_nat_en<u></u><u></u></p>
</div>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal">-- <br>
Nat Sakimura (=nat)<u></u><u></u></p>
<div>
<p class="MsoNormal">Chairman, OpenID Foundation<br>
<a href="http://nat.sakimura.org/" target="_blank">http://nat.sakimura.org/</a><br>
@_nat_en<u></u><u></u></p>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Openid-specs-ab mailing list
<a href="mailto:Openid-specs-ab@lists.openid.net" target="_blank">Openid-specs-ab@lists.openid.net</a>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a>
</pre>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Nat Sakimura (=nat)<div>Chairman, OpenID Foundation<br><a href="http://nat.sakimura.org/" target="_blank">http://nat.sakimura.org/</a><br>@_nat_en</div>
</div>