commit 6664ed79ed4688209065e39a4eafb5e2bb59de66 Author: teor teor@torproject.org Date: Mon Jan 13 20:27:24 2020 +1000
Prop 306: Add an optional ClientPreferIPv6ORPort consensus parameter
Part of 29801. --- proposals/306-ipv6-happy-eyeballs.txt | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/proposals/306-ipv6-happy-eyeballs.txt b/proposals/306-ipv6-happy-eyeballs.txt index 3d5c92c..d24fe63 100644 --- a/proposals/306-ipv6-happy-eyeballs.txt +++ b/proposals/306-ipv6-happy-eyeballs.txt @@ -186,7 +186,8 @@ Ticket: https://trac.torproject.org/projects/tor/ticket/29801
When the majority of clients and relay are IPv6-capable, we could set the default value of ClientPreferIPv6ORPort to 1, in order to take advantage - of IPv6. + of IPv6. We could add a ClientPreferIPv6ORPort consensus parameter, so we + can make this change network-wide.
5. Relay Statistics
@@ -233,7 +234,8 @@ Ticket: https://trac.torproject.org/projects/tor/ticket/29801 optional.)
* A default setup capable of both IPv4 and IPv6 connections with the - options described in Section 4.1 + options described in Section 4. (The ClientPreferIPv6ORPort consensus + parameter is optional.)
8. Optional Features
@@ -255,6 +257,8 @@ Ticket: https://trac.torproject.org/projects/tor/ticket/29801 adjusted, for instance, if clients often fail IPv6 connections. (Section 3.3.)
+ * ClientPreferIPv6ORPort consensus parameter. (Section 4.) + * IPv4, IPv6, and Prop306 connection Statistics. While optional, this may be useful for debugging and reliability testing, and metrics on IPv4 vs IPv6. (Section 5.)