<div dir="ltr"><div>hi Johathan, <br></div><div><br></div><div>this question was already addressed last week by Teor.</div><div>email on this mailing list doesn't always seem to arrive in a logical sequence.... possible due to spam filters and so on.</div><div><br></div><div>gr. Paul<br></div><div>
<table class="gmail-cf gmail-gJ" cellpadding="0"><tbody><tr class="gmail-acZ"><td class="gmail-gF gmail-gK"><table class="gmail-cf gmail-ix" cellpadding="0"><tbody><tr><td class="gmail-c2"><h3 class="gmail-iw"><span class="gmail-qu" tabindex="-1"><span name="teor" class="gmail-gD">teor</span> <span class="gmail-go"><a href="mailto:teor@riseup.net">teor@riseup.net</a></span> <span class="gmail-go"><a target="_blank" href="https://support.google.com/mail/answer/1311182?hl=en" class="gmail-acP">via</a> <a href="http://lists.torproject.org">lists.torproject.org</a> </span></span></h3></td></tr></tbody></table></td><td class="gmail-gH gmail-bAk"><div class="gmail-gK"><span></span><span id="gmail-:34f" class="gmail-g3" title="Dec 13, 2019, 8:26 AM" alt="Dec 13, 2019, 8:26 AM" tabindex="-1">Fri, Dec 13, 8:26 AM (3 days ago)</span></div></td></tr></tbody></table><table class="gmail-cf gmail-gJ" cellpadding="0"><tbody><tr class="gmail-acZ"><td class="gmail-gH"><br></td><td class="gmail-gH gmail-acX gmail-bAm" rowspan="2"></td></tr></tbody></table><table class="gmail-cf gmail-gJ" cellpadding="0"><tbody><tr class="gmail-acZ gmail-xD"><td colspan="3"><table class="gmail-cf gmail-adz" cellpadding="0"><tbody><tr><td class="gmail-ady"><div class="gmail-iw gmail-ajw"><div>We won't be disabling IPv4 on relays any time soon.</div><div><br></div><div>The RIPE grant covers IPv6 address autodetection and self-testing.</div><div>If the feature is reliable enough, we may turn on IPv6 on dual-stack relays</div><div>by default. (When autodetection and self-testing both pass.)</div><div><br></div><div>We don't have any plans to disable IPv4 on relays. We'd need most relays</div><div>to be dual-stack first. (Or we'd need research about privacy in non-clique</div><div>networks.) And we'd need to write code that allows relays to turn off IPv4.</div><div><br></div><div>When that's all deployed, we would have to make an engineering decision</div><div>about the capacity of current IPv4-only relays, and the potential capacity</div><div>of IPv6-only relays.</div><div><br></div><div>One possible transition strategy is to allow IPv6-only bridges and exits.</div><div>But to do that, we need more dual-stack guards and middles. That's why</div><div>we are improving support for dual-stack relays with this funding.</div><font color="#888888"><div><br></div><div>T</div></font>
<span class="gmail-hb"><span dir="ltr" name="tor-relays" class="gmail-g2"></span> </span></div><div id="gmail-:33o" class="gmail-ajy" tabindex="0"><img class="gmail-ajz" src="https://mail.google.com/mail/u/0/images/cleardot.gif" alt=""></div></td></tr></tbody></table></td></tr></tbody></table></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Dec 16, 2019 at 12:33 PM Jonathan Sélea <<a href="mailto:jonathan@selea.se">jonathan@selea.se</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p>I am unable to see why this is a good idea actually.<br>
As someone said already, I too would be unable to provide bridges
and relays thanks to my ISP (Telia) does not provide an IPv6.<br>
But removing IPv4 only nodes from the network - you are basically
removing a large chunk of relays from the network without any real
reason.<br>
</p>
<p><br>
</p>
<div>On 12/12/2019 5:49 PM, NOC wrote:<br>
</div>
<blockquote type="cite">
<p>Great,</p>
<p>than lets drop all IPv4 only relays from consensus 2020
finally.</p>
<p>P.S. whitelist me so it doesn't take days till my emails appear
on the mailing list.</p>
<p>Thank you<br>
</p>
<div>On 11.12.2019 03:20, teor wrote:<br>
</div>
<blockquote type="cite">
<pre>Dear relay operators,
I just wanted to let you know that RIPE has announced funding for The
Tor Project to improve IPv6 support on relays. (RIPE is the European
internet infrastructure organisation.)
<a href="https://www.ripe.net/support/cpf/funding-recipients-2019" target="_blank">https://www.ripe.net/support/cpf/funding-recipients-2019</a>
We'll have more details early in 2020, when we've worked out an
implementation plan and a start time.
Thanks for your patience with our current IPv6 support. And thanks
to all those volunteer coders who have worked hard to get us this far.
T
--
teor
----------------------------------------------------------------------
</pre>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
tor-relays mailing list
<a href="mailto:tor-relays@lists.torproject.org" target="_blank">tor-relays@lists.torproject.org</a>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a>
</pre>
</blockquote>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
tor-relays mailing list
<a href="mailto:tor-relays@lists.torproject.org" target="_blank">tor-relays@lists.torproject.org</a>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a>
</pre>
</blockquote>
</div>
_______________________________________________<br>
tor-relays mailing list<br>
<a href="mailto:tor-relays@lists.torproject.org" target="_blank">tor-relays@lists.torproject.org</a><br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" rel="noreferrer" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br>
</blockquote></div>