torproject/torspec
1
0
Fork 0
mirror of https://github.com/torproject/torspec.git synced 2024-12-12 20:55:35 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Prop 311 & 312: Some changes affect IPv6 stats

Browse Source 
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.
This commit is contained in:
teor 2020-02-10 12:45:49 +10:00
parent ec92bbba5d
commit 01105c2543
No known key found for this signature in database
GPG Key ID: 10FEAA0E7075672A
2 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
proposals/311-relay-ipv6-reachability.txt
View File

@ -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

5
proposals/312-relay-auto-ipv6-addr.txt
View File

@ -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