[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-bugs] #21213 [Core Tor/Tor]: Write and analyze proposals for fetching consensuses/microdescriptors less frequently?

#21213: Write and analyze proposals for fetching consensuses/microdescriptors less
frequently?
------------------------------+--------------------------------
     Reporter:  nickm         |      Owner:
         Type:  task          |     Status:  new
     Priority:  Medium        |  Milestone:  Tor: 0.3.1.x-final
    Component:  Core Tor/Tor  |    Version:
     Severity:  Normal        |   Keywords:  sponsor4
Actual Points:                |  Parent ID:  #21209
       Points:                |   Reviewer:
      Sponsor:                |
------------------------------+--------------------------------
 '''The idea''': Our current algorithm for deciding whether you need a new
 consensus is ad hoc; we just picked an interval more or less at random.

 Depending on the results from #21205, we may learn that it's not as
 necessary as we had thought for a client to fetch consensuses and
 microdescriptors so often.  If that's the case, we should have proposals
 and analyses for (optionally?) decreasing the frequency of our downloads.

 There may be different results here for "busy" and "not so busy" clients.

 Of course, the analysis needs to include the security impact.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21213>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs