Re: [tor-dev] Doesn't hidden services break RFC 3986?

Subject: Re: [tor-dev] Doesn't hidden services break RFC 3986?

From: Alec Muffett <alec.muffett@xxxxxxxxx>

Date: Mon, 14 Aug 2017 08:56:37 +0100

Delivery-date: Mon, 14 Aug 2017 03:56:56 -0400

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=i1L5709xRtwhArXdvfNZTmmFLVoXVgHdIzu5qy+H4NY=; b=R1Eds6bpJei7Gmbzyb+IoidVJIVgEEu+LjheTv6Qr7FKxxmYi83hD1FAoJqxSbSAgu Chuk0/VaSmtoyFk+O2arTCSPBHzxJ9PMY8BAx0vkf8zhAdoL3qs4tpkI+xp6E/qEE7qZ /9e2LB3bq8VXgZQj9sFbHdpnul+m1bh7gF29RQRqcj5kmAnsIEIOB/ovrRvMUNS/dhhF JwvAI5vT681LRQKM7zBuSnWQYjUdj9VW2oa+HoAioP76zLO+5843x4ZVY0USq2Z4LQi3 IpahCdQNF76E2eJaYGjAS2uz9+eZyS8aXgR5jXm0+cmYUjow92SlbGxdlf7AGvNNC5eK 8f7g==

In-reply-to: <20170814075338.GA8285@inner.h.apk.li>

List-archive: <http://lists.torproject.org/pipermail/tor-dev/>

List-help: <mailto:tor-dev-request@lists.torproject.org?subject=help>

List-id: discussion regarding Tor development <tor-dev.lists.torproject.org>

List-post: <mailto:tor-dev@lists.torproject.org>

List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev>, <mailto:tor-dev-request@lists.torproject.org?subject=subscribe>

List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-dev>, <mailto:tor-dev-request@lists.torproject.org?subject=unsubscribe>

References: <CAO7N=i2oyevRwNCkLt56RJCNLz0OQ3EnE9Sivxxa3JOZUY0DYg@mail.gmail.com> <20170814075338.GA8285@inner.h.apk.li>

Reply-to: tor-dev@xxxxxxxxxxxxxxxxxxxx

Sender: "tor-dev" <tor-dev-bounces@xxxxxxxxxxxxxxxxxxxx>

Also: just because it's HTTP/S running over a different network stack, doesn't make it a new scheme.

Just because your dinner arrives on a different plate doesn't mean the recipe has changed. :-)

On 14 Aug 2017 8:53 am, "Andreas Krey" <a.krey@xxxxxx> wrote:

On Sun, 13 Aug 2017 17:06:20 +0000, Ryan Carboni wrote:
> https://tools.ietf.org/html/rfc3986#section-3
> By placing the scheme within the authority as a tld while using the same
> authority as the HTTP specification, this probably breaks RFC 3986 and
> maybe others.

RFC7686 deals with that.

Andreas

--
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800
_______________________________________________
tor-dev mailing list
tor-dev@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

_______________________________________________ tor-dev mailing list tor-dev@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev