Prop 313: Add IPv6 bandwidth statistics safety

Also make BandwidthStatistics an optional change.

Part of 33159.

1 files changed, 16 insertions, 14 deletions

diff --git a/proposals/313-relay-ipv6-stats.txt b/proposals/313-relay-ipv6-stats.txt
index e615afe..7da142a 100644
--- a/proposals/313-relay-ipv6-stats.txt
+++ b/proposals/313-relay-ipv6-stats.txt
@@ -1,6 +1,6 @@
 Filename: 313-relay-ipv6-stats.txt
 Title: Tor Relay IPv6 Statistics
-Author: teor
+Author: teor, Karsten Loesing, Nick Mathewson
 Created: 10-February-2020
 Status: Draft
 Ticket: #33159
@@ -135,20 +135,11 @@ Ticket: #33159
    (The IPv4 statistics can be calculated by subtracting the IPv6 statistics
    from the existing total consumed bandwidth statistics.)
 
-   We propose adding a new BandwidthStatistics torrc option and consensus
-   parameter, which activates reporting of all these statistics. Currently,
-   the existing statistics are controlled by ExtraInfoStatistics, but we
-   propose using the new BandwidthStatistics option for them as well.
-
-   The default value of this option should be "auto", which checks the
-   consensus parameter. If there is no consensus parameter, the default should
-   be 1. (The existing bandwidth statistics are reported by default.)
+   We believe that collecting IPv6 consumed bandwidth statistics is about as
+   safe as the existing IPv4+IPv6 total consumed bandwidth statistics.
 
-   TODO: Should we collect IPv6 bandwidth statistics on bridges?
-         On bridges, should bandwidth statistics be on or off by default?
-
-         If we do want to collect bridge statistics, and we think it's safe,
-         modify proposals 311 and 312 to allow bridge statistics.
+   See also section 7.5, which adds a BandwidthStatistics torrc option and
+   consensus parameter. BandwidthStatistics is an optional change.
 
 5. Collecting IPv6 Connection Statistics
 
@@ -317,6 +308,17 @@ Ticket: #33159
      * as a stacked graph, like
        [Tor Metrics: Advertised and consumed bandwidth by relay flags]
 
+7.5. Add a BandwidthStatistics option
+
+   We propose adding a new BandwidthStatistics torrc option and consensus
+   parameter, which activates reporting of all these statistics. Currently,
+   the existing statistics are controlled by ExtraInfoStatistics, but we
+   propose using the new BandwidthStatistics option for them as well.
+
+   The default value of this option should be "auto", which checks the
+   consensus parameter. If there is no consensus parameter, the default should
+   be 1. (The existing bandwidth statistics are reported by default.)
+
 8. Test Plan
 
    We provide a quick summary of our testing plans.