Opened 6 months ago

Last modified 8 weeks ago

#33242 assigned defect

Prop 312: 3.2.5. Make Relays do IPv4 and IPv6 Directory Fetches

Reported by: teor Owned by:
Priority: Medium Milestone:
Component: Core Tor/Tor Version:
Severity: Normal Keywords: prop312, ipv6, 044-deferred
Cc: Actual Points:
Parent ID: #33241 Points: 1
Reviewer: Sponsor: Sponsor55-can


Relays should start fetching directory documents over IPv4 and IPv6, so they can use X-Your-Address-Is HTTP headers to find their IPv6 addresses.

Bridges must only fetch directory documents over IPv4, because they try to imitate clients. (So they can't find their IPv6 addresses in this way.)

We propose to use a simple load balancing scheme for IPv4 and IPv6
directory requests:

  • choose between IPv4 and IPv6 directory requests at random.

We do not expect this change to have any load-balancing impact on the public
tor network, because the number of relays is much smaller than the number
of clients. However, the 6 directory authorities with IPv6 enabled may see
slightly more directory load, particularly over IPv6.

See proposal 312, section 3.2.5, directory fetch part:

Child Tickets

Change History (4)

comment:1 Changed 3 months ago by teor

Owner: teor deleted

Un-assign myself from future Sponsor 55 tasks.

comment:2 Changed 3 months ago by teor

Sponsor: Sponsor55-mustSponsor55-can

I've made all the IPv6 directory fetch tasks optional, because they could take a lot of work, and they are high-risk.

When we finish the required tasks, we can prioritise the optional tasks.

comment:3 Changed 8 weeks 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:4 Changed 8 weeks ago by nickm

Milestone: Tor: unspecified

Bulk-move prop311 and prop312 to 0.4.5

Note: See TracTickets for help on using tickets.