Propose and implement IPv6 ORPort reachability checks on relays

This is the top-level task for relay IPv6 ORPort reachability checks.

See: https://trac.torproject.org/projects/tor/wiki/org/roadmaps/Tor/IPv6Features#ReachabilityChecks

Check the child tickets for details.

changed milestone to %Tor: unspecified

added 034-removed-20180328 034-triage-20180328 044-deferred component::core tor/tor ipv6 milestone::Tor: unspecified parent::33048 priority::medium severity::normal status::new tor-relay type::task labels

Trac:
Parent: N/A to #4565 (moved)

I am happy to coordinate this, please feel free to help out with child tickets.

Trac:
Status: new to assigned
Owner: N/A to teor

The 0.3.3 feature freeze deadline has passed

Trac:
Milestone: Tor: 0.3.3.x-final to Tor: 0.3.4.x-final

Trac:
Keywords: N/A deleted, 034-triage-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

Trac:
Keywords: N/A deleted, 034-removed-20180328 added

These tickets, tagged with 034-removed-*, are no longer in-scope for 0.3.4. We can reconsider any of them, if time permits.

Trac:
Milestone: Tor: 0.3.4.x-final to Tor: unspecified

Not on any roadmap yet.

Trac:
Owner: teor to N/A

Removing sponsor V as we do not have more time to include this tickets in the sponsor.

Removing sponsor from tickets that we do not have time to fit in the remain of this sponsorship.

Trac:
Sponsor: SponsorV-can to N/A

Trac:
Parent: #4565 (moved) to #5940 (moved)

Trac:
Points: N/A to 48

If we get funding for this ticket, we should triage the child tickets as our first step.

Trac:
Points: 48 to N/A
Milestone: Tor: unspecified to Tor: 0.4.4.x-final

Trac:
Parent: #5940 (moved) to #33048 (moved)

Change tickets that are assigned to nobody to "new".

Trac:
Status: assigned to new

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

Trac:
Milestone: Tor: 0.4.4.x-final to Tor: unspecified
Keywords: N/A deleted, 044-deferred added

mentioned in issue #24404 (moved)

mentioned in issue #24405 (moved)