Opened 3 years ago

Closed 2 years ago

#21213 closed task (wontfix)

Write and analyze proposals for fetching consensuses/microdescriptors less frequently?

Reported by: nickm Owned by: nickm
Priority: Medium Milestone: Tor: 0.3.2.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: sponsor4, TorCoreTeam201705
Cc: Actual Points:
Parent ID: #21209 Points: 1
Reviewer: Sponsor: Sponsor4

Description

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.

Child Tickets

Change History (10)

comment:1 Changed 3 years ago by nickm

See also proposal 212

comment:2 Changed 3 years ago by nickm

Sponsor: Sponsor4

Setting "sponsor4" sponsor on all tickets that have the sponsor4 keyword, but have no sponsor set.

comment:3 Changed 3 years ago by nickm

Keywords: TorCoreTeam201703 added

comment:4 Changed 3 years ago by nickm

Owner: set to nickm
Points: 1
Status: newaccepted

comment:5 Changed 3 years ago by nickm

Keywords: 031-reach added

comment:6 Changed 3 years ago by nickm

Keywords: TorCoreTeam201705 added
Milestone: Tor: 0.3.1.x-finalTor: 0.3.2.x-final

These are things I should work on during May, but they're prep work for 0.3.2 and beyond.

comment:7 Changed 3 years ago by nickm

Remove Sponsor4 keyword, now that Sponsor4 is the value of the Sponsor field.

comment:8 Changed 3 years ago by nickm

Keywords: TorCoreTeam201703 removed

comment:9 Changed 3 years ago by nickm

Keywords: 031-reach removed

comment:10 Changed 2 years ago by nickm

Resolution: wontfix
Status: acceptedclosed

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

Note: See TracTickets for help on using tickets.