<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>That's a fair point -- the intent was native apps use either</p>
<p> - custom uri</p>
<p> - localhost (or equivalent)</p>
<p> -- Justin<br>
</p>
<br>
<div class="moz-cite-prefix">On 2/27/2017 6:56 AM, John Bradley via
Openid-specs-ab wrote:<br>
</div>
<blockquote
cite="mid:CAANoGh+VZ2da1bhDzQ1jS7pwZfwULE8m1hdshvZ-OsVPzs5d7Q@mail.gmail.com"
type="cite">
<div dir="auto">We can explicitly mentioned loopback ip. I always
considered them synonims as the hosts file maps localhost to
127.0.0.1 in DNS anyway.
<div dir="auto">John B. </div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Feb 27, 2017 2:14 AM, "William
Denniss" <<a moz-do-not-send="true"
href="mailto:wdenniss@google.com">wdenniss@google.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">+openid-specs-ab
<div><br>
</div>
<div>Please note the below errata for dynamic client
registration.</div>
<div><br>
</div>
<div>The clarification is that either custom URI schemes
(com.example.app:/*), or a localhost redirect with http
(http://localhost:*/*) schemes are acceptable redirects
for Native Clients – there is no requirement that
localhost must be used with a custom URI scheme (in fact
such redirects have no host component).</div>
<div><br>
</div>
<div>Should we also explicitly mention that the IP literal
form in place of localhost is acceptable? i.e.
127.0.0.1 and [::1]?</div>
<div><br>
</div>
<div class="gmail_extra">
<div class="gmail_quote">On Thu, Dec 8, 2016 at 10:18
AM, Mike Jones <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:Michael.Jones@microsoft.com"
target="_blank">Michael.Jones@microsoft.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px
0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">I'll add it to my
errata issues list. Thanks!<br>
<div class="m_-4968413277794455521gmail-HOEnZb">
<div class="m_-4968413277794455521gmail-h5"><br>
-----Original Message-----<br>
From: John Bradley [mailto:<a
moz-do-not-send="true"
href="mailto:ve7jtb@ve7jtb.com"
target="_blank">ve7jtb@ve7jtb.com</a>]<br>
Sent: Thursday, December 8, 2016 10:14 AM<br>
To: Mike Jones <<a moz-do-not-send="true"
href="mailto:Michael.Jones@microsoft.com"
target="_blank">Michael.Jones@microsoft.com</a>><br>
Cc: William Denniss <<a
moz-do-not-send="true"
href="mailto:wdenniss@google.com"
target="_blank">wdenniss@google.com</a>><br>
Subject: Dynamic registration possible errata<br>
<br>
William found a developer with a interesting
take on the registration spec.<br>
<br>
They are trying to enforce localhost for custom
scheme URI<br>
<br>
The relevant sentence is:<br>
Native Clients MUST only register redirect_uris
using custom URI schemes or URLs using the http:
scheme with localhost as the hostname.<br>
<br>
The way I intended that to be parsed was<br>
<br>
Native Clients MUST only register
(redirect_uris using custom URI schemes) or
(URLs using the http: scheme with localhost as
the hostname).<br>
<br>
At least this reader is parsing it as:<br>
<br>
Native Clients MUST only register
(redirect_uris using custom URI schemes or URLs
using the http: scheme ) with localhost as the
hostname.<br>
<br>
Perhaps a comma before the or?<br>
<br>
What is your opinion as grammar expert.<br>
<br>
If we can make that clearer we should in the
upcoming errata.<br>
<br>
John B.<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Openid-specs-ab mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a>
<a class="moz-txt-link-freetext" href="http://lists.openid.net/mailman/listinfo/openid-specs-ab">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a>
</pre>
</blockquote>
<br>
</body>
</html>