Opened 16 months ago

Last modified 11 months ago

#24405 new enhancement

Implement relay IPv6 extends with proposed protover

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: needs-proposal, ipv6, tor-relay, 034-triage-20180328, 034-removed-20180328
Cc: Actual Points:
Parent ID: #24403 Points: 1
Reviewer: Sponsor: SponsorV-can

Description

Make relays with IPv6 ORPorts start attempting to connect to IPv6 ORPorts in response to EXTEND2 cells containing IPv6 addresses. (Relays always prefer existing canonical connections, which may be over IPv4.)

Make these relays declare the protover from #24404.

Make them implement the IPv4/IPv6 Extend behviour from #24404.

Child Tickets

Change History (5)

comment:1 Changed 14 months ago by nickm

Milestone: Tor: 0.3.3.x-finalTor: 0.3.4.x-final

Deferring various "new"-status enhancement tickets to 0.3.4

comment:2 Changed 14 months ago by teor

The 0.3.3 freeze deadline has passed, all these children of #24403 belong in 0.3.4

comment:3 Changed 12 months ago by nickm

Keywords: 034-triage-20180328 added

comment:4 Changed 12 months ago by nickm

Keywords: 034-removed-20180328 added

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

comment:5 Changed 11 months ago by nickm

Milestone: Tor: 0.3.4.x-finalTor: unspecified

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

Note: See TracTickets for help on using tickets.