diff --git a/proposals/311-relay-ipv6-reachability.txt b/proposals/311-relay-ipv6-reachability.txt
index 85f089a..978dc9b 100644
--- a/proposals/311-relay-ipv6-reachability.txt
+++ b/proposals/311-relay-ipv6-reachability.txt
@@ -294,6 +294,12 @@ Ticket: #24404
    The testing relay will confirm that test circuits can extend to both its
    IPv4 and IPv6 ORPorts.
 
+   Checking IPv6 ORPort reachability will create extra IPv6 connections on the
+   tor network. (See [Proposal 313: Relay IPv6 Statistics].) It won't directly
+   create much extra traffic, because reachability circuits don't send many
+   cells. But some client circuits may use the IPv6 connections created by
+   relay reachability self-tests.
+
 4.2.1. Selecting the Final Extending Relay
 
    IPv6 ORPort reachability checks require an IPv6 extend-capable relay as
diff --git a/proposals/312-relay-auto-ipv6-addr.txt b/proposals/312-relay-auto-ipv6-addr.txt
index 08fbcde..8914cb7 100644
--- a/proposals/312-relay-auto-ipv6-addr.txt
+++ b/proposals/312-relay-auto-ipv6-addr.txt
@@ -487,6 +487,11 @@ Ticket: #33073
    IPv6 address, tor should use that address for reachability checks. If the
    reachability checks succeed, tor should use that address in its descriptor.
 
+   Doing relay directory fetches over IPv6 will create extra IPv6 connections
+   and IPv6 bandwidth on the tor network. (See
+   [Proposal 313: Relay IPv6 Statistics].) In addition, some client circuits
+   may use the IPv6 connections created by relay directory fetches.
+
 3.2.6. Disabling IPv6 Address Resolution
 
    Relays (and bridges) that have a reachable IPv6 address, but that address