<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>I probably do though I have to confess that I am too tired now to think critically. </div><div><br></div><div>How do we distinguish between port and authority section in that case? There was a ticket around it. </div>
<div><br>=nat via iPhone</div><div><br>Jun 29, 2013 20:21¡¢Mike Jones <<a href="mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>> ¤Î¥á¥Ã¥»©`¥¸:<br><br></div><blockquote type="cite"><div>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
<div class="WordSection1">
<p class="MsoPlainText">I'd add another "or" to prevent confusion as below, but otherwise I agree with this change. Do others?</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">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]</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText"> -- Mike</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">-----Original Message-----<br>
From: <a href="mailto:openid-specs-ab-bounces@lists.openid.net">openid-specs-ab-bounces@lists.openid.net</a> [<a href="mailto:openid-specs-ab-bounces@lists.openid.net">mailto:openid-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">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)</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">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">
<span style="color:windowtext;text-decoration:none">https://bitbucket.org/openid/connect/issue/856/discovery-uri-grammar-definition-doesnt</span></a></p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Justin Richer:</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">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:</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">```</p>
<p class="MsoPlainText"> a URI either in the form of scheme "://" authority path-abempty [ "?" query ] [ "#" fragment ] or authority path-abempty [ "?" query ] [ "#" fragment ] per RFC 3986 [RFC3986].
</p>
<p class="MsoPlainText">```</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">I think this needs an errata published as the intent was more like:</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">```</p>
<p class="MsoPlainText"> 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].
</p>
<p class="MsoPlainText">```</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">_______________________________________________</p>
<p class="MsoPlainText">Openid-specs-ab mailing list</p>
<p class="MsoPlainText"><a href="mailto:Openid-specs-ab@lists.openid.net"><span style="color:windowtext;text-decoration:none">Openid-specs-ab@lists.openid.net</span></a></p>
<p class="MsoPlainText"><a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab"><span style="color:windowtext;text-decoration:none">http://lists.openid.net/mailman/listinfo/openid-specs-ab</span></a></p>
</div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Openid-specs-ab mailing list</span><br><span><a href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a></span><br>
<span><a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a></span><br></div></blockquote></body></html>