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

[Tor Bug Tracker & Wiki]

#21213: Write and analyze proposals for fetching consensuses/microdescriptors 
less
frequently?
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:  wontfix
 Keywords:  sponsor4, TorCoreTeam201705  |  Actual Points:
Parent ID:  #21209   | Points:  1
 Reviewer:   |Sponsor:  Sponsor4
-+-
Changes (by nickm):

 * status:  accepted => closed
 * resolution:   => wontfix


Comment:

 This turns out to be a "don't" -- the consensus diff changes make it so
 that downloading less frequently isn't worthwhile.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#21213: Write and analyze proposals for fetching consensuses/microdescriptors 
less
frequently?
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  task | Status:  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.1.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  sponsor4, TorCoreTeam201703  |  Actual Points:
Parent ID:  #21209   | Points:  1
 Reviewer:   |Sponsor:  Sponsor4
-+-
Changes (by nickm):

 * owner:   => nickm
 * status:  new => accepted
 * points:   => 1


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#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| Resolution:
 Keywords:  sponsor4  |  Actual Points:
Parent ID:  #21209| Points:
 Reviewer:|Sponsor:
--+

Comment (by nickm):

 See also proposal 212

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#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: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs