diff options
| -rw-r--r-- | proposals/311-relay-ipv6-reachability.txt | 12 |
1 files changed, 9 insertions, 3 deletions
diff --git a/proposals/311-relay-ipv6-reachability.txt b/proposals/311-relay-ipv6-reachability.txt index 88204dd..ea2f422 100644 --- a/proposals/311-relay-ipv6-reachability.txt +++ b/proposals/311-relay-ipv6-reachability.txt @@ -172,9 +172,9 @@ Ticket: #24404 If relays try both the IPv4 and IPv6 ORPorts, then the circuit would succeed. For example, relays could try the alternative port after a 250ms - delay, as in [Proposal 306: Client Auto IPv6 Connections]. This design - results in an average circuit delay of up to 125ms per new connection, - rather than failure. + delay, as in [Proposal 306: Client Auto IPv6 Connections]. The design in + this proposal results in an average circuit delay of up to 125ms + (250ms / 2) per new connection, rather than failure. However, partial relay connectivity should be uncommon. And relays keep connections open long-term, so new relay connections are a small proportion @@ -651,6 +651,12 @@ Ticket: #24404 * failure rates. Collecting statistics like these could impact user privacy. +9. Changes to Other Proposals + + [Proposal 306: Client Auto IPv6 Connections] needs to be modified to keep + bridge IPv6 behaviour in sync with client IPv6 behaviour. (See section + 3.3.2.) + References: [Onion Service Protocol]: In particular, Version 3 of the Onion Service Protocol supports IPv6: https://gitweb.torproject.org/torspec.git/tree/rend-spec-v3.txt |