Re: [tor-dev] Proposal 312: Automatic Relay IPv6 Addresses

2020-02-04 Thread teor
Hi, > On 4 Feb 2020, at 07:17, s7r wrote: > > teor wrote: >> Hi s7r, >> >> Thanks for bringing up IPv6 address privacy extensions. >> >>> On 30 Jan 2020, at 02:19, s7r wrote: >>> >> >> I read RFCs 4941 and 3041, looked at the tor directory spec, and did some >> analysis: >> * tor clients

Re: [tor-dev] Proposal 312: Automatic Relay IPv6 Addresses

2020-02-04 Thread teor
Hi Nick, Thanks so much for your review! I've made most of the changes you've suggested, you can see the latest version of the proposal here: https://github.com/torproject/torspec/pull/105/files I've also made changes in response to s7r's feedback about IPv6 privacy extensions. Since sending

Re: [tor-dev] Proposal 312: Automatic Relay IPv6 Addresses

2020-02-04 Thread Mirimir
On 02/04/2020 03:13 PM, s7r wrote: > These privacy extensions IPv6 addresses might be good for outbound bind > exit addresses (for Exit relays), and maybe (not sure) for regular > clients that could connect to their entry guards or bridges using a > temporary IPv6 address. Thanks. Those are

Re: [tor-dev] Proposal 312: Automatic Relay IPv6 Addresses

2020-02-04 Thread s7r
Mirimir wrote: > On 02/03/2020 02:17 PM, s7r wrote: > > > >> In the current form of this proposal, it looks kind of optional ("We >> propose this optional change, to improve..."). I propose removing the >> line which contains "this optional change" and changing the following: >> >> In

Re: [tor-dev] Proposal 312: Automatic Relay IPv6 Addresses

2020-02-03 Thread Mirimir
On 02/03/2020 02:17 PM, s7r wrote: > In the current form of this proposal, it looks kind of optional ("We > propose this optional change, to improve..."). I propose removing the > line which contains "this optional change" and changing the following: > > In practice, each operating system has

Re: [tor-dev] Proposal 312: Automatic Relay IPv6 Addresses

2020-02-03 Thread s7r
Hi teor, teor wrote: > Hi s7r, > > Thanks for bringing up IPv6 address privacy extensions. > >> On 30 Jan 2020, at 02:19, s7r wrote: >> > > I read RFCs 4941 and 3041, looked at the tor directory spec, and did some > analysis: > * tor clients get new relay addresses within 4.5 hours > * IPv6

Re: [tor-dev] Proposal 312: Automatic Relay IPv6 Addresses

2020-02-03 Thread teor
Hi s7r, Thanks for bringing up IPv6 address privacy extensions. > On 30 Jan 2020, at 02:19, s7r wrote: > > There is another RFC (older), that is in use by Debian apparently: > RFC3041. https://tools.ietf.org/rfc/rfc3041.txt > > From: >

Re: [tor-dev] Proposal 312: Automatic Relay IPv6 Addresses

2020-01-30 Thread Nick Mathewson
On Wed, Jan 29, 2020 at 9:04 AM teor wrote: Hello again! This looks like another fine proposal. I'm leaving comments inline, and clipping sections that I'm not commenting on. > > Filename: 312-relay-auto-ipv6-addr.txt > Title: Tor Relays Automatically Find Their IPv6 Address > Author: teor >

Re: [tor-dev] Proposal 312: Automatic Relay IPv6 Addresses

2020-01-29 Thread s7r
Hi again, Apologies, a quick follow-up: There is another RFC (older), that is in use by Debian apparently: RFC3041. https://tools.ietf.org/rfc/rfc3041.txt From: https://manpages.debian.org/buster/iproute2/ip-address.8.en.html see `mngtmpaddr` RFC4941 is newer and with some improvements,

Re: [tor-dev] Proposal 312: Automatic Relay IPv6 Addresses

2020-01-29 Thread s7r
Hi teor, Thanks for this epic work, some lecture for me to deeply go over this weekend. By briefly reviewing I've noticed something important is missing that should be a part of this proposal. I am not sure under which section it should go under. I guess `3.2.2. Use the Advertised ORPort IPv4