Opened 7 years ago

Last modified 16 months ago

#4565 assigned project

Enable relays to talk to other relays via IPv6

Reported by: karsten Owned by: ln5
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: ipv6 tor-relay needs-design
Cc: nickm, ln5 Actual Points:
Parent ID: #5788 Points: 5
Reviewer: Sponsor:

Description

We need to extend Tor for relays to talk to other relays via IPv6. This task depends on #4564. The exact steps will be described in the roadmap that comes out of #4556.

This ticket is an optional deliverable for June 30, 2012 for sponsor G.

Child Tickets

TicketStatusOwnerSummaryComponent
#24403assignedPropose and implement IPv6 ORPort reachability checks on relaysCore Tor/Tor

Change History (13)

comment:1 Changed 7 years ago by karsten

Owner: karsten deleted
Status: newassigned

We don't have a person to lead this deliverable yet.

comment:2 Changed 7 years ago by karsten

Milestone: Sponsor G: June 30, 2012Sponsor G: September 30, 2012

Moving to the September milestone, because did not finish everything by end of June.

comment:3 Changed 7 years ago by karsten

Owner: set to ln5

Assigning to ln5 after talking to him, because this ticket is related to #4563 and #4564 which are quite related. The ticket is an optional sponsor deliverable for September 30.

comment:4 Changed 7 years ago by karsten

Keywords: SponsorG20120930 added
Milestone: Sponsor G: September 30, 2012

Switching from using milestones to keywords for sponsor deliverables. See #6365 for details.

comment:5 Changed 7 years ago by ln5

Keywords: ipv6 added

comment:6 Changed 7 years ago by karsten

Keywords: SponsorG20120930 removed

Removing the sponsor keyword. It was always clear that this is an optional sponsor deliverable. We didn't make enough progress here to call it done, which is perfectly fine.

comment:7 Changed 7 years ago by nickm

Milestone: Tor: unspecified

comment:8 Changed 6 years ago by nickm

Keywords: tor-relay added

comment:9 Changed 6 years ago by nickm

Component: Tor RelayTor

comment:10 Changed 2 years ago by arma

Cc: nickm,ln5nickm, ln5
Severity: Normal

The roadmap in #4556 basically says "this relay-to-relay use of ipv6 will happen naturally over time".

Meaning, there isn't any discussion of whether it's a good idea to switch to ipv6 if both relays support it, or leave those tls connections on ipv4 since we still mandate all relays be able to speak ipv4.

So: is there some advantage to moving relay communications to ipv6? Maybe the routing is different and better? (I could imagine the routing being different and worse, in the case of folks who have the more centralized hurricane electric ipv6 connections.)

comment:11 Changed 22 months ago by nickm

Keywords: needs-design added
Points: 5

comment:12 Changed 21 months ago by teor

Parent ID: #5788

comment:13 in reply to:  10 Changed 16 months ago by teor

Replying to arma:

The roadmap in #4556 basically says "this relay-to-relay use of ipv6 will happen naturally over time".

Meaning, there isn't any discussion of whether it's a good idea to switch to ipv6 if both relays support it, or leave those tls connections on ipv4 since we still mandate all relays be able to speak ipv4.

So: is there some advantage to moving relay communications to ipv6? Maybe the routing is different and better? (I could imagine the routing being different and worse, in the case of folks who have the more centralized hurricane electric ipv6 connections.)

We'll try to answer this as part of #24403.
But I think the answer will be: "just use either at random".

Note: See TracTickets for help on using tickets.