Opened 3 weeks ago

Last modified 3 weeks ago

#33221 assigned task

Prop 311: 4. Check Relay and Bridge IPv6 ORPort Reachability

Reported by: teor Owned by: teor
Priority: Medium Milestone: Tor: 0.4.4.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: ipv6, prop311
Cc: Actual Points:
Parent ID: #33048 Points: 10
Reviewer: Sponsor: Sponsor55-must

Description

This is a parent ticket.

We propose that relays (and bridges) check their own IPv6 ORPort
reachability.

To check IPv6 ORPort reachability, relays (and bridges) extend circuits via
other relays (but not other bridges), and back to their own IPv6 ORPort.

If IPv6 reachability checks fail, relays (and bridges) should refuse to
publish their descriptors, if they believe IPv6 reachability checks are
reliable, and their IPv6 address was explicitly configured. (See
[Proposal 312: Relay Auto IPv6 Address] for the ways relays can guess their
IPv6 addresses.)

Directory authorities always publish their descriptors.

From Proposal 311, section 4:
https://gitweb.torproject.org/torspec.git/tree/proposals/311-relay-ipv6-reachability.txt#n246

Child Tickets

TicketStatusOwnerSummaryComponent
#33222assignedteorProp 311: 4.2. Checking IPv6 ORPort ReachabilityCore Tor/Tor
#33223assignedteorProp 311: 4.3.1. Refusing to Publish Descriptor if IPv6 ORPort is UnreachableCore Tor/Tor
#33224assignedteorProp 311: 4.3.2. Add AssumeIPv6Reachable OptionCore Tor/Tor

Change History (1)

comment:1 Changed 3 weeks ago by teor

Points: 10
Note: See TracTickets for help on using tickets.