Re: [tor-relays] Emerald Onion's new relays

Subject: Re: [tor-relays] Emerald Onion's new relays

Date: Tue, 13 Aug 2019 19:42:09 +0200

Delivery-date: Wed, 14 Aug 2019 04:50:24 -0400

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=afo-tm.org; s=afo-tm.org; h=sender:subject:to:references:from:message-id:date:mime-version :in-reply-to:content-language; bh=a6f/W6tHx9dceOxQ+Ra8MwL8OFIhtWDRViN7qFeG7i4=; b=QV5DULqwHRPfmZu56jqgmxesA32VH34lnmgqddotPbxFuK1VsO5DOVbdJ//nf6lEw6 8DAEAQ+FuwkZR/UgpCWTaK2xLCaFFTekxyJNEvaLp1nsNjJ4+KFkyTcoGeX49wqO+hWT +qEHUtVsyjY+THTQl2N2rowTeDWlX7YMWtpbs=

In-reply-to: <06830E45-8E86-476C-A08B-262FD54DEAA4@riseup.net>

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

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

List-id: "support and questions about running Tor relays \(exit, non-exit, bridge\)" <tor-relays.lists.torproject.org>

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

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

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

References: <BN8PR19MB275621999383793C67E71923C5560@BN8PR19MB2756.namprd19.prod.outlook.com> <4a09597e-6004-2904-3778-4fca260086d8@riseup.net> <CACiAZpgXcAwiCZq7y099YHSxc66fm_xYBWakUfwXpetUqcU8og@mail.gmail.com> <CAD2Ti29nACAi43b6esmMM-HdRyGBsw_=_QXWt-HyvUr34rg97g@mail.gmail.com> <MWHPR19MB01602B374DF0C739E78C0D68C5D30@MWHPR19MB0160.namprd19.prod.outlook.com> <20190813000819.334557d7@natsu> <06830E45-8E86-476C-A08B-262FD54DEAA4@riseup.net>

Reply-to: tor-relays@xxxxxxxxxxxxxxxxxxxx

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

On 12.08.2019 23:39, teor wrote:

Hi,

On 13 Aug 2019, at 05:08, Roman Mamedov <rm@xxxxxxxxxxx> wrote:

On Mon, 12 Aug 2019 00:46:50 +0000
Christopher Sheats <yawnbox@xxxxxxxxxxxxxxxx> wrote:

Tor Project, please increase your #IPv6 awareness/outreach similar to how

ARIN and the other RIRs try very hard to do.

Before outreach Tor would need some actual IPv6 support, as in using it for
the actual traffic of relay-to-relay communication. I tried running a few
relays with very fast IPv6 and slow IPv4 (due to a common NAT frontend which
was the bottleneck), but it was a complete nonstarter.

Tor relays currently don't connect over IPv6. When 10% of the network

supported IPv6, there wasn't much point, because putting a very small

number of paths over IPv6 has privacy risks. So we focused on client, guard,

and exit IPv6 support.

But currently, about 30% of the consensus weight supports IPv6. So we

are working on a grant for IPv6 support (see below).

We won't be able to prefer IPv6 until 50-67% of relays support IPv6, for

load-balancing and privacy reasons. But we plan on using the

"Happy Eyeballs" (RFC 8305) algorithm on dual-stack relays. So

sufficiently slow IPv4 will cause relays to connect over IPv6. (And we can

tune the load-balancing using the IPv4 to IPv6 delay.)

I still would say that these stats are deeply flawed. Looking at the Autonomous Systems where the relays are located from the top100, 99 of them do support IPv6 (85,7625& consensus weight), the only one which doesn't support is AS4224 but since they manage their AS themselves they would only need to ask their LIR and would get IPv6.

So my conclusion is not that there is any need to wait for adaption, only for software support.

Release one stable from which point you need IPv6 and the operator will see that there is something to be done. You won't affect older versions since they still can speak with you but you won't get in the consensus from that point because you don't fulfill all requirements for it.

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