Prop 311 & 312: Update monitoring based on 313

Keep the monitoring summaries in proposals 311 and 312 in sync with
proposal 313.

Part of 33159.

1 files changed, 8 insertions, 8 deletions

diff --git a/proposals/311-relay-ipv6-reachability.txt b/proposals/311-relay-ipv6-reachability.txt
index 9f536d3..fd131e1 100644
--- a/proposals/311-relay-ipv6-reachability.txt
+++ b/proposals/311-relay-ipv6-reachability.txt
@@ -731,23 +731,23 @@ Ticket: #24404
 
 7. Ongoing Monitoring
 
-   To monitor the impact of these changes, relays should collect basic IPv4
-   and IPv6 connection and bandwidth statistics (see [Proposal 313: Relay IPv6
-   Statistics]).
-
-   We may also collect separate statistics on connections from:
-     * clients (and bridges, because they act like clients), and
-     * other relays (and authorities, because they act like relays).
+   To monitor the impact of these changes:
+     * relays should collect basic IPv6 connection statistics, and
+     * relays and bridges should collect basic IPv6 bandwidth statistics.
+   (See [Proposal 313: Relay IPv6 Statistics]).
 
    Some of these statistics may be included in tor's heartbeat logs, making
    them accessible to relay operators.
 
    We do not propose to collect additional statistics on:
-     * bridges,
      * circuit counts, or
      * failure rates.
    Collecting statistics like these could impact user privacy.
 
+   We also plan to write a script to calculate the number of IPv6 relays in
+   the consensus. This script will help us monitor the network during the
+   deployment of these new IPv6 features.
+
 8. Changes to Other Proposals
 
    [Proposal 306: Client Auto IPv6 Connections] needs to be modified to keep