<div dir="auto">Also: just because it's HTTP/S running over a different network stack, doesn't make it a new scheme.<div dir="auto"><br></div><div dir="auto">Just because your dinner arrives on a different plate doesn't mean the recipe has changed. :-)</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 14 Aug 2017 8:53 am, "Andreas Krey" <<a href="mailto:a.krey@gmx.de">a.krey@gmx.de</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Sun, 13 Aug 2017 17:06:20 +0000, Ryan Carboni wrote:<br>
> <a href="https://tools.ietf.org/html/rfc3986#section-3" rel="noreferrer" target="_blank">https://tools.ietf.org/html/<wbr>rfc3986#section-3</a><br>
> By placing the scheme within the authority as a tld while using the same<br>
> authority as the HTTP specification, this probably breaks RFC 3986 and<br>
> maybe others.<br>
<br>
RFC7686 deals with that.<br>
<br>
Andreas<br>
<br>
--<br>
"Totally trivial. Famous last words."<br>
From: Linus Torvalds <torvalds@*.org><br>
Date: Fri, 22 Jan 2010 07:29:21 -0800<br>
______________________________<wbr>_________________<br>
tor-dev mailing list<br>
<a href="mailto:tor-dev@lists.torproject.org">tor-dev@lists.torproject.org</a><br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev" rel="noreferrer" target="_blank">https://lists.torproject.org/<wbr>cgi-bin/mailman/listinfo/tor-<wbr>dev</a><br>
</blockquote></div></div>