#25096: Bump up NumNTorsPerTAP to squeeze out v2 onion service traffic?
 Reporter:  arma              |          Owner:  dgoulet
     Type:  task              |         Status:  accepted
 Priority:  Medium            |      Milestone:
Component:  Core Tor/DirAuth  |        Version:
 Severity:  Normal            |     Resolution:
 Keywords:                    |  Actual Points:
Parent ID:                    |         Points:
 Reviewer:                    |        Sponsor:
Changes (by dgoulet):

 * status:  new => accepted
 * cc: dgoulet (removed)
 * component:  Core Tor/Tor => Core Tor/DirAuth
 * milestone:  Tor: 0.3.3.x-final =>
 * owner:  (none) => dgoulet
 * type:  defect => task


 Ok so this is a change in the dirauth-conf repository, nothing on the tor
 side afaict.

 Usually with consensus parameter change like that, I like to inform the
 dirauth list about the rationale.

 In the name of safety, what about ramping up to 200 by going through 150
 before? And we'll see how that goes with our relay stats or if someone
 does hack a client to checks delays on v2 onion vs v3 onion? And we can
 progressively ramp up more and more if we see that it helps. There is also
 an argument here to try to be more loud publicly about v3 adoption
 considering that we start squeezing out v2...

 If we have consensus, I can do the push and email.

Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25096#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
tor-bugs mailing list

Reply via email to