commit 5c0aa29f810cf4a58ed2cc859d08b81ba49a1925 Author: teor <teor@torproject.org> Date: Wed Jan 29 22:41:59 2020 +1000 Prop 311: Improve RelaySendIPv6Extends option name As suggested by Nick Mathewson. Part of 24404. --- proposals/311-relay-ipv6-reachability.txt | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/proposals/311-relay-ipv6-reachability.txt b/proposals/311-relay-ipv6-reachability.txt index 40917f2..29c4f1a 100644 --- a/proposals/311-relay-ipv6-reachability.txt +++ b/proposals/311-relay-ipv6-reachability.txt @@ -536,14 +536,11 @@ Ticket: #24404 ongoing preemptive circuits. (Bridges can not change their behaviour, because they try to imitate clients.) - We propose a torrc option and consensus parameter SendIPv6CircuitExtends, + We propose a torrc option and consensus parameter RelaySendIPv6Extends, which is only supported on relays (and not bridges or clients). This option makes relays send IPv4 and IPv6 ORPorts in all their extend cells, when supported by the extending and receiving relay. (See section 3.2.1.) - TODO: Is there a shorter name, that isn't easily confused with enabling - support for other nodes to perform IPv6 extends via this relay? - The default value for this option is "auto", which checks the consensus parameter. If the consensus parameter is not set, it defaults to "0" in the initial release.