Opened 6 months ago

Last modified 2 months ago

#33221 assigned task

Prop 311: 4. Ensure Relay and Bridge IPv6 ORPorts are Reachable

Reported by: teor Owned by: teor
Priority: Medium Milestone:
Component: Core Tor/Tor Version:
Severity: Normal Keywords: ipv6, prop311, network-team-roadmap-2020Q2, 044-deferred
Cc: Actual Points:
Parent ID: #33048 Points: 10
Reviewer: Sponsor: Sponsor55-must


This is a parent ticket.

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

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:

Child Tickets

#33222closedteorProp 311: 4.2. Implement IPv6 ORPort Reachability Self-TestsCore Tor/Tor
#33223assignedProp 311: 4.3.1. Don't Publish Descriptor if IPv6 ORPort is UnreachableCore Tor/Tor
#33224assignedProp 311: 4.3.2. Add AssumeReachableIPv6 Option and Consensus ParameterCore Tor/Tor
#33225newProp 311: 4.4.1. Extend IPv6 From All Supported Second-Last HopsCore Tor/Tor
#33860assignednickmFinish test_onionskin_answer()Core Tor/Tor
#34064newAdd an AssumeReachable consensus parameterCore Tor/Tor
#34065needs_reviewneelMake routerset_contains_router() support IPv6Core Tor/Tor
#34067assignedteorSeparate tor's IPv4 and IPv6 reachability flagsCore Tor/Tor
#34068newDecide how to handle control port events for IPv6 reachability self-testsCore Tor/Tor
#34069newAllow extend_info to contain both IPv4 and IPv6 ORPortsCore Tor/Tor
#34200closedteorRefactor tor's circuit path node selection checksCore Tor/Tor
#34412newAdditonal unit tests for functions related to ipv6 self-testCore Tor/Tor

Change History (5)

comment:1 Changed 6 months ago by teor

Points: 10

comment:2 Changed 4 months ago by gaba

Keywords: network-team-roadmap-2020Q2 added

Add s55 tickets to the 2020 Q2 roadmap for the network team.

comment:3 Changed 4 months ago by teor

Summary: Prop 311: 4. Check Relay and Bridge IPv6 ORPort ReachabilityProp 311: 4. Ensure Relay and Bridge IPv6 ORPorts are Reachable

comment:4 Changed 2 months ago by nickm

Keywords: 044-deferred added
Milestone: Tor: 0.4.4.x-finalTor: unspecified

Bulk-remove tickets from 0.4.4. Add the 044-deferred label to them.

comment:5 Changed 2 months ago by nickm

Milestone: Tor: unspecified

Bulk-move prop311 and prop312 to 0.4.5

Note: See TracTickets for help on using tickets.