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, 9 insertions, 11 deletions

diff --git a/proposals/312-relay-auto-ipv6-addr.txt b/proposals/312-relay-auto-ipv6-addr.txt
index 5228c6c..659e5a1 100644
--- a/proposals/312-relay-auto-ipv6-addr.txt
+++ b/proposals/312-relay-auto-ipv6-addr.txt
@@ -1479,24 +1479,22 @@ Ticket: #33073
 
 6. 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,
-     * address resolution,
      * circuit counts, or
      * failure rates.
-   Collecting statistics like these could impact user privacy, or relay
-   security.
+   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.
 
 7. Changes to Other Proposals