<html><head><meta http-equiv="Content-Type" content="text/html charset=gb18030"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">The problem with normalizing "user@host" to "https:user@host" is mostly that simple WF servers may only match on the acct: form it seems to be the recommended thing to normalize input to.<div><br></div><div>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:".</div><div><br></div><div>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.</div><div><br></div><div>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. </div><div><br></div><div>John B.</div><div><br></div><div><br><div><div>On 2013-06-29, at 9:16 PM, Nat Sakimura <<a href="mailto:sakimura@gmail.com">sakimura@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="content-type" content="text/html; charset=utf-8"><div dir="auto"><div>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. </div>
<div><br></div><div>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</div><div><br>Jun 30, 2013 2:17¡¢Mike Jones <<a href="mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>> ¤Î¥á¥Ã¥»©`¥¸:<br>
<br></div><blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<base href="x-msg://294/"><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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="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></p><div><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><br class="webkit-block-placeholder"></div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> Thanks both,</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> -- Mike</span></p><div><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><br class="webkit-block-placeholder"></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">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">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></p>
</div>
</div><div> <br class="webkit-block-placeholder"></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 "//".</p>
<div><div> <br class="webkit-block-placeholder"></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) .</p>
</div>
<div><div> <br class="webkit-block-placeholder"></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.</p>
</div>
<div><div> <br class="webkit-block-placeholder"></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.</p>
</div>
<div><div> <br class="webkit-block-placeholder"></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.</p>
</div>
<div><div> <br class="webkit-block-placeholder"></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.</p>
</div>
<div><div> <br class="webkit-block-placeholder"></div>
</div>
<div><p class="MsoNormal">There is also a problem with differentiating <a href="http://foo.org/">
foo.org</a>:8080 as that could be interpreted as a scheme or <a href="http://foo.org/">
foo.org</a> with a path of 8080 so being explicit about what schemes without higher-part are supported may be a good idea. </p>
</div>
<div><div> <br class="webkit-block-placeholder"></div>
</div>
<div><p class="MsoNormal">John B.</p>
</div>
<div><div> <br class="webkit-block-placeholder"></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">Michael.Jones@microsoft.com</a>> wrote:</p>
</div><p class="MsoNormal"><br>
<br>
</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></p>
</div>
<div><div><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><br class="webkit-block-placeholder"></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 class="apple-converted-space"> </span><span style="color:red">or<span class="apple-converted-space"> </span></span>authority
path-abempty [ "?" query ] [ "#" fragment ]<span class="apple-converted-space"> </span><span style="color:red">or scheme ":" userinfo "@" host</span><span class="apple-converted-space"> </span>per RFC 3986 [RFC3986]</span></p>
</div>
<div><div><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><br class="webkit-block-placeholder"></div>
</div>
<div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> -- Mike</span></p>
</div>
<div><div><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><br class="webkit-block-placeholder"></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">openid-specs-ab-bounces@lists.openid.net</a> [mailto:<a href="mailto:openid-">openid-</a><a href="mailto:specs-ab-bounces@lists.openid.net">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)</span></p>
</div>
<div><div><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><br class="webkit-block-placeholder"></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"><span style="color:windowtext;text-decoration:none">https://bitbucket.org/openid/connect/issue/856/discovery-uri-grammar-definition-doesnt</span></a></span></p>
</div>
<div><div><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><br class="webkit-block-placeholder"></div>
</div>
<div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Justin Richer:</span></p>
</div>
<div><div><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><br class="webkit-block-placeholder"></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></p>
</div>
<div><div><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><br class="webkit-block-placeholder"></div>
</div>
<div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">```</span></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></p>
</div>
<div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">```</span></p>
</div>
<div><div><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><br class="webkit-block-placeholder"></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></p>
</div>
<div><div><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><br class="webkit-block-placeholder"></div>
</div>
<div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">```</span></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></p>
</div>
<div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">```</span></p>
</div>
<div><div><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><br class="webkit-block-placeholder"></div>
</div>
<div><div><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><br class="webkit-block-placeholder"></div>
</div>
<div><div><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><br class="webkit-block-placeholder"></div>
</div>
<div><div><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><br class="webkit-block-placeholder"></div>
</div>
<div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">_______________________________________________</span></p>
</div>
<div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Openid-specs-ab mailing list</span></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"><span style="color:windowtext;text-decoration:none">Openid-specs-ab@lists.openid.net</span></a></span></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"><span style="color:windowtext;text-decoration:none">http://lists.openid.net/mailman/listinfo/openid-specs-ab</span></a></span></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"><span style="color:purple">Openid-specs-ab@lists.openid.net</span></a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab"><span style="color:purple">http://lists.openid.net/mailman/listinfo/openid-specs-ab</span></a></span></p>
</div>
</div><div> <br class="webkit-block-placeholder"></div>
</div>
</div>
</blockquote><blockquote type="cite"><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></blockquote></div>
</blockquote></div><br></div></body></html>