Opened 9 months ago

Last modified 5 months ago

#33264 assigned enhancement

Prop 313: 5. Collect IPv6 Connection Stats on Relays

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: 5
Reviewer: Sponsor: Sponsor55-must


We propose that relays (but not bridges) collect IPv6 connection statistics.

Bridges refuse to collect the existing ConnDirectionStatistics, so we do not
believe it is safe to collect the smaller IPv6 totals on bridges.

To minimise development and testing effort, we propose re-using the existing
"bidi" code in rephist.c. (This code may require some refactoring, because
the "bidi" totals are globals, rather than a struct.)

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

In particular, tor currently counts these connection statistics:

  • below threshold,
  • mostly read,
  • mostly written, and
  • both read and written.

We propose adding IPv6 variants of all these statistics. (The IPv4
statistics can be calculated by subtracting the IPv6 statistics from the
existing total connection statistics.)

See proposal 313, section 5:

Child Tickets

Change History (4)

comment:1 Changed 9 months ago by teor

Summary: Prop 313: 5. Collect IPv6 Connection Statistics on RelaysProp 313: 5. Collect IPv6 Connection Stats on Relays

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: 25

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

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