Age | Commit message (Collapse) | Author |
|
Part of 33052.
|
|
Part of 33052.
|
|
We don't want to put stats on Consensus Health, if they depend on Wgd,
because those stats are designed for Sponsor 55 in 2020.
(If Wgd ever changes, we don't want the stats to be wrong.)
Part of 33052.
|
|
Part of 33049.
|
|
Part of 33049.
|
|
|
|
Keep the monitoring summaries in proposals 311 and 312 in sync with
proposal 313.
Part of 33159.
|
|
We currently have enough relays reporting connection stats,
but these reports might be a bug.
Make the ConnDirectionStatistics consensus paramter into an
optional change, depending on the outcome of the bug.
Part of 33159.
|
|
Also make BandwidthStatistics an optional change.
Part of 33159.
|
|
Remove the tor logs from the proposal, only write a script.
(Some of these calculations are medium-term, and are most relevent
during Sponsor 55.)
Part of 33159.
|
|
Part of 33159.
|
|
Related to tickets: 33159 (proposal), 33051 and 33052 (implementation).
|
|
Part of 33159.
|
|
Part of 33073.
|
|
Add an optional change that makes relays do bandwidth self-tests over
IPv6.
This change increases the connection and bandwidth IPv6 statistics.
Related to proposal 313, which covers IPv6 statistics.
Related to 33159.
|
|
When a change increases an IPv6 statistic, mention the impact in
proposals 311 and 312.
Related to proposal 313, which covers IPv6 statistics.
Part of 33159.
|
|
Add the standard future statements, so Python 2 will use some
Python 3 features.
Open files as UTF-8. As a consequence of this change, proposals
must be encoded in UTF-8.
Closes ticket 33164.
|
|
Some people don't have their best python in /usr/bin.
Other people only have python in /usr/local/bin, or other places.
|
|
|
|
Part of 24404.
|
|
Part of 33073.
|
|
|
|
As suggested by s7r.
Part of 33073.
|
|
Part of 33073.
|
|
Document tor's current address detection state management, and our
new state management for IPv4 and IPv6 address detection.
As suggested by Nick Mathewson.
Part of 33073.
|
|
As suggested by Nick Mathewson.
Part of 33073.
|
|
Add an optional change.
Part of 33073.
|
|
As suggested by Nick Mathewson and s7r.
Part of 33073.
|
|
Only use explicit IPv4 and IPv6 address literals, configured in Address
or ORPort lines, for directory authority addresses.
As suggested by Nick Mathewson.
Part of 33073.
|
|
Part of 33073.
|
|
As suggested by Nick Mathewson.
Part of 33073.
|
|
All these changes are optional in the proposal:
* Add the NETINFO cell address detection method
(as suggested by Nick Mathewson)
* Defer decisions about ignoring some addresses, or using those
addresses as the lowest priority method
* Simplify the load-balancing design
Part of 33073.
|
|
Explain why we might need to turn IPv6 address detection off.
Part of 33073.
|
|
Add an optional section, where we propose using a directory authority
IPv4 and IPv6 address for socket-based local interface address
detection.
As suggested by Nick Mathewson.
Part of 33073.
|
|
As suggested by Nick Mathewson.
Part of 33073.
|
|
Explain why some relays may not have any publicly routable interface
addresses.
Part of 33073.
|
|
It's unlikely to be useful for most configurations.
As suggested by Nick Mathewson.
Part of 33073.
|
|
Explain how we choose between multiple addresses, in a list, and over
time.
Part of 33073.
|
|
And describe a potential attack that gives a relay the wrong address,
then monitors its traffic.
As suggested by Nick Mathewson.
Part of 33073.
|
|
Since relays put the discovered IPv6 address in their descriptor,
it needs to be publicly routable. (If the relay is on the public
network.)
As suggested by Nick Mathewson.
Also fix inconsistent use of directory authority, directory server,
and directory mirror.
Part of 33073.
|
|
Add an optional change to support clients extending as soon as
possible, after a relay restarts.
Part of 33073.
|
|
Add information about binding to IPv4 and IPv6.
Also do a slight reformat.
Part of 33073.
|
|
Part of 33073.
|
|
And why it shouldn't affect tor relays, at least with the default
settings.
As suggested by s7r.
Part of 33073.
|
|
Part of 33073.
|
|
And explain why we didn't use the existing ORPort IPv4Only flag to
disable IPv6 address resolution.
Part of 33073.
|
|
Part of 33073
|
|
Part of 33073.
|
|
Related tickets: 33073 (proposal), 5940 (implementation).
|
|
Part of 24404.
|