Opened 9 months ago

Last modified 5 months ago

#33229 assigned task

Prop 311: 6.1. Test IPv6 ORPort Reachability on the Tor Network

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

Description (last modified by teor)

Test the IPv6 ORPort Reachability and Extends changes in proposal 311, on the public tor network, with a small number of relays and bridges.

We can do public tests after each major feature is merged. We can
also wait for multiple features to merge, and test them all.

Here are some useful features that we can test:

#33222 / #33226 IPv6 ORPort Reachability Self-Tests / Relay=3 Protocol
#33223 Don't Publish Descriptor if IPv6 ORPort is Unreachable

See proposal 311, section 6.1, initial public test part:

Child Tickets

Change History (5)

comment:1 Changed 9 months ago by teor

Description: modified (diff)

comment:2 Changed 7 months ago by gaba

Keywords: network-team-roadmap-2020Q2 added
Sponsor: Sponsor55-must

comment:3 Changed 6 months ago by teor

Description: modified (diff)

comment:4 Changed 6 months ago by teor

Owner: teor deleted

Un-assign myself from future Sponsor 55 tasks.

comment:5 Changed 5 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.

Note: See TracTickets for help on using tickets.