[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #7009 [Tor]: Handle unstable relays better
#7009: Handle unstable relays better
---------------------------------+------------------------------------------
Reporter: arma | Owner:
Type: project | Status: new
Priority: normal | Milestone: Tor: unspecified
Component: Tor | Version:
Keywords: tor-relay, SponsorJ | Parent:
Points: | Actualpoints:
---------------------------------+------------------------------------------
Here's what we promised:
"The Tor Project will investigate and expand our research and designs for
Consensus Diffs in Proposal 140. Tor clients and servers need a list of
which relays are on the network. This list, the consensus, is created by
authorities hourly and clients fetch a new copy of it every two to four
hours. We will research, design, and implement approaches that allow
clients to download diffs of the consensus at more frequent intervals.
This improvement will save bandwidth on both the client and relay side,
but more importantly it will allow clients to more quickly discover
changes in relay addresses."
I think scheduling this work for 0.2.5 is a good timeframe (assuming we
can stick to our 0.2.4 schedule).
This is intended to be a pretty broad scope of "better handle relays that
aren't so stable", so we should brainstorm and add related topics that
will also help -- such as "relays notice that their IP has changed faster
so they republish faster", "the bwauths form an opinion quicker about new
relays", "the dirauths should publish v3 interim votes between themselves
more often", etc.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7009>
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