[tor-commits] [torspec/master] Prop 312: Clarify IPv6 ORPort Binding

[teor@xxxxxxxxxxxxxx]

commit 8af14dea81a2a39be2cb1f76a99a364827ec9d4e
Author: teor <teor@xxxxxxxxxxxxxx>
Date:   Tue Feb 11 14:11:09 2020 +1000

    Prop 312: Clarify IPv6 ORPort Binding
    
    Part of 33049.
---
 proposals/312-relay-auto-ipv6-addr.txt | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/proposals/312-relay-auto-ipv6-addr.txt b/proposals/312-relay-auto-ipv6-addr.txt
index 98c86c1..ba2ffcc 100644
--- a/proposals/312-relay-auto-ipv6-addr.txt
+++ b/proposals/312-relay-auto-ipv6-addr.txt
@@ -558,6 +558,12 @@ Ticket: #33073
    IP address (in a single API call). Tor should support both styles of
    networking API.
 
+   In particular, if binding to all IPv6 addresses fails, relays should still
+   try to discover their public IPv6 address, and check the reachability of
+   that address. Some OSes may not support the IPV6_V6ONLY flag, but they may
+   instead bind to all addresses at runtime. (The tor install may also have
+   compile-time / runtime flag mismatches.)
+
    If both reachability checks succeed, relays should publish their IPv4 and
    IPv6 ORPorts in their descriptor.
 

_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits