Opened 9 months ago

Last modified 4 months ago

#33263 assigned enhancement

Prop 313: 4. Collect IPv6 Bandwidth Stats on Relays and Bridges

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: prop313, ipv6, 044-deferred
Cc: metrics-team Actual Points:
Parent ID: #33052 Points: 3
Reviewer: Sponsor: Sponsor55-must


We propose that relays (and bridges) collect IPv6 consumed bandwidth

To minimise development and testing effort, we propose re-using the existing
"bw_array" code in rephist.c.

(We might want to move this code into separate relay-only code and header files, because it is relay-specific.)

In particular, tor currently counts these bandwidth statistics:

  • read,
  • write,
  • dir_read, and
  • dir_write.

We propose adding the following bandwidth statistics:

  • ipv6_read, and
  • ipv6_write.

(The IPv4 statistics can be calculated by subtracting the IPv6 statistics
from the existing total consumed bandwidth statistics.)

We believe that collecting IPv6 consumed bandwidth statistics is about as
safe as the existing IPv4+IPv6 total consumed bandwidth statistics.

See proposal 313, section 4:

Child Tickets

Change History (4)

comment:1 Changed 9 months ago by teor

Summary: Prop 313: 4. Collecting IPv6 Consumed Bandwidth StatisticsProp 313: 4. Collect IPv6 Bandwidth Stats on Relays and Bridges

comment:2 Changed 6 months ago by teor

Owner: teor deleted

Un-assign myself from future Sponsor 55 tasks.

comment:3 Changed 6 months ago by teor

Points: 13

Since we've done the detailed design work on this task, I am revising the estimates up.

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