<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><br><div>On 12 Oct 2017, at 09:15, Santiago R.R. <<a href="mailto:santiagorr@riseup.net">santiagorr@riseup.net</a>> wrote:<br><br></div><blockquote type="cite"><div><span>(Moving this thread from tor-relay)</span><br><span></span><br><span>El 03/10/17 a las 14:25, teor escribió:</span><br><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>On 3 Oct 2017, at 10:57, Roman Mamedov <<a href="mailto:rm@romanrm.net">rm@romanrm.net</a>> wrote:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>On Tue, 3 Oct 2017 09:53:46 -0400</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>teor <<a href="mailto:teor2345@gmail.com">teor2345@gmail.com</a>> wrote:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span> For interposing dual-protocoled nodes along the way, how many do there</span><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>have to be for it to become "not too limiting"?</span><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>This is one of the questions we need researchers to answer.</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>I can't help but feel you are overcomplicating this.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Clients create a circuit by randomly picking 3 nodes out of the all-nodes</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>pile, right? If all 3 happen to be IPv6-capable, then the circuit can go over</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>IPv6 and all is fine. If some of the 3 happen to be IPv6-only while others are</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>IPv4-only, the whole selection can be thrown away and repeated.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>That way IPv6-only relays could get some usage on a totally random basis, with</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>no compromises and no restraining "of the next hop based on the previous one",</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>not hurting anonymity. Clients just need to know which nodes are IPv4-only,</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>IPv6-only or dual-stack, to not attempt unworkable combinations, discarding</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>them instead.</span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Discarding unworkable combinations and restraining node choices seem</span><br></blockquote><blockquote type="cite"><span>equivalent to me, although the relay weights may be different.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>And as there are more and more dual-stack or IPv6-only relays, the "throw</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>away" step will be needed less and less often.</span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>If you think this will work and is safe for client anonymity, then the next step</span><br></blockquote><blockquote type="cite"><span>is to write a tor proposal. Having a concrete design could help with</span><br></blockquote><blockquote type="cite"><span>analysing the anonymity implications as well.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I think IPv6-only relays are a lower priority than better IPv6 and dual-stack</span><br></blockquote><blockquote type="cite"><span>client support, and IPv6-only bridge support But we could do both in the</span><br></blockquote><blockquote type="cite"><span>same release.</span><br></blockquote><span></span><br><span>Hello tor-dev,</span><br><span></span><br><span>With my colleague JC Bach (in CC), we have proposed a last-year student</span><br><span>project to address IPv6-related issues in Tor for the upcoming semester,</span><br><span>at IMT Atlantique engineering school. There will be two students working</span><br><span>on it. It is hard to say now how far we will arrive, especially because</span><br><span>this is our first approach to Tor entrails.</span><br><span></span><br><span>So this message is to say we have good chances to come back here looking</span><br><span>for help :-)</span><br></div></blockquote><br><div>Hi Santiago,</div><div><br></div><div>This is great! We would like some help with Tor's IPv6 support.</div><div>And we are happy to help you and your students.</div><div><br></div><div>How many students?</div><div>How much time?</div><div>What are your goals for the project?</div><div>How much do you expect to get done?</div><div><br></div><div>We are at a Tor meeting this week.</div><div>We are revising Tor's IPv6 roadmap for the next year.</div><div>Next week, this page will be updated:</div><div><a href="https://trac.torproject.org/projects/tor/wiki/org/meetings/2017Amsterdam/IPv6Hackfest">https://trac.torproject.org/projects/tor/wiki/org/meetings/2017Amsterdam/IPv6Hackfest</a></div><div><br></div><div>We want to help people get code accepted into tor.</div><div>Here is how we write code:</div><div><a href="https://gitweb.torproject.org/tor.git/tree/doc/HACKING/GettingStarted.md">https://gitweb.torproject.org/tor.git/tree/doc/HACKING/GettingStarted.md</a></div><div><a href="https://gitweb.torproject.org/tor.git/tree/doc/HACKING/CodingStandards.md">https://gitweb.torproject.org/tor.git/tree/doc/HACKING/CodingStandards.md</a></div><div><br></div><div>It can help to start by submitting a small change, so you can see how we work.</div><div>Then you can make larger changes more easily.</div><div>Our bug tracker is:</div><div><a href="https://trac.torproject.org/">https://trac.torproject.org/</a></div><div><br></div><div>We are also in #tor-dev IRC on <a href="http://irc.oftc.net">irc.oftc.net</a>.</div><div><br></div><div>Please ask questions early, and ask often!</div><div>We would love to help you help tor.</div><div><br></div><div>Tim (teor)</div></body></html>