Re: [tor-dev] Adding a NotDir router status flag

[s7r <s7r@xxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Matt,

Nice to hear there's ongoing work for this proposal.

I also see the NotDir flag as useful for migration, because for quite
some time after prop 237 is implemented we will still have relays in
the consensus which will have DirPort open (separate from ORPort). A
client needs to know to make directory requests on DirPort for the
relays with V2Dir flag, and know to make directory requests on ORPort
for the relays which only have ORPort open and NotDir flag.


After (hopefully) medium time we can drop the V2Dir flag (we are way
passed from V2 directory anyway) and after longer time we can also
drop NotDir. I guess this depends if directory requests on ORPort will
be only implemented in new Tor releases or also backport? I guess we
can say it's safe to drop both flags when over 95% of the relays
respond to directory requests on ORPort. We will just need Valid flag
to make sure we can separate the relays which try to poison directory
data.

On 5/29/2015 3:58 AM, Matthew Finkel wrote:
> Sadly it took a few months for me to get back to prop 237 (All
> relays are directory servers), but now I have a revised version of
> the proposal and updated tor[0] and torspec[1][2] branches. These
> will benefit from your review.
> 
> Previously, proposal 237 took advantage of the V2Dir flag because 
> Authorities already vote on it and it accomplished 90% of what we
> need. But I realized that's not exactly what we want. Now the
> proposal introduces a new status flag, NotDir. The reasoning for
> this is the V2Dir flag indicates a router (is expected to) respond
> to directory requests, usually, because the operator configured the
> router's DirPort. But, in a network where nearly all relays are
> directory servers, why are relays with the V2Dir flag special?
> Basically, after this proposal is implemented nearly every relay
> should receive the V2Dir flag, so the NotDir flag is the complement
> of V2Dir. This allows the V2Dir be deprecated at some time in the
> future.
> 
> Thoughts?
> 
> Thanks, Matt
> 
> [0] https://git.torproject.org/user/sysrqb/tor.git,
> feature12538_rebased_6 [1]
> https://git.torproject.org/user/sysrqb/torspec.git, prop237_update 
> [2] feature12538
> 
> 
> 
> _______________________________________________ tor-dev mailing
> list tor-dev@xxxxxxxxxxxxxxxxxxxx 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBCAAGBQJVaExxAAoJEIN/pSyBJlsRSvcIAKyFuccOBocuv6y8v2HbanZX
W2al+2h4rI9bPQsY+ZMOu/YpuFqZdGmT6N8Pm2mDGVcc5+g8gus7XgKXxfm0tnbV
BrXGlqdNdzxUH6oaR8Faik3o+zr84vEmLhTk6T5bjrSXJV6zFOhmgdozjlFG+xHj
0pJTGWkwT4JTUipTMXz23zeBbLd4V1rTDW3SKAVep7DosGXcGWTQWOmX9TLLZw60
/qj9883wi6S3HaQkuZSi5jD6BEw6Z62QxNOeDewOVaHoaFZuqdasT0kyVHMQF3lk
pWgJsx0QV7WRt6FaKq2iqYK4G+ofucQ84nDlhLSpzWw4UTZk8O4Q8JQp8yBZ3ro=
=dyRq
-----END PGP SIGNATURE-----
_______________________________________________
tor-dev mailing list
tor-dev@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev