Opened 8 months ago

Closed 8 months ago

Last modified 6 months ago

#33159 closed task (fixed)

Write a proposal for monitoring IPv6

Reported by: teor Owned by: teor
Priority: Medium Milestone: Tor: 0.4.4.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: ipv6, network-team-roadmap-2020Q1
Cc: metrics-team Actual Points: 1
Parent ID: #33052 Points: 2
Reviewer: Sponsor: Sponsor55-must


For sponsor 55, I need to write a proposal that covers these objectives:

  • O1.4 - Measure the number of Tor relays that support IPv6 reachability checks (#33051)
  • O1.5 - Measure the number of connections, and consumed bandwidth, using IPv4 and IPv6 (#33052)

My current thinking is that:

  • tor should log the number and consensus weight of relays that support IPv6 reachability checks, because we will need those numbers during testing
  • these numbers are available in the consensus

Here's what the proposal requires:

  • calculate relay IPv6 reachability numbers a few times during the project (we may as well use the tor logs)
  • collect IPv6 connection and bandwidth statistics on tor relays
  • calculate the IPv6 connection and bandwidth amounts a few times during the project

Here are some other useful things we might do:

  • split the collected IPv6 statistics by client/relay
  • calculate the guard-but-not-exit relays that support IPv6 client connections
  • log IPv6 statistics in tor's heartbeat logs (we can't use these logs for our project reports, because they only show the local relay's statistics)
  • calculate IPv6 reachability relay count and consensus weight on consensus-health
  • add a pseudo-flag for relay IPv6 reachability support in Relay Search
  • add metrics graphs that shows our progress on
    • IPv6 reachability
    • client IPv6 support on relays
    • IPv6 connections and bandwidth

We definitely won't have time to do all of these optional things, so we should priorise, once the essential work is done.

Child Tickets

Change History (6)

comment:1 Changed 8 months ago by teor

We should also consider changes to Relay Search, consensus-health, or the metrics graphs, to encourage IPv6 deployment, and improve the KPIs for this sponsor.

comment:2 Changed 8 months ago by teor

Actual Points: 0.7
Status: assignedneeds_review

See my PR here:

I'll also send a copy of proposal 313 to the tor-dev mailing list.

comment:4 Changed 8 months ago by teor

Actual Points: 0.70.8

comment:5 Changed 8 months ago by teor

Actual Points: 0.81
Resolution: fixed
Status: needs_reviewclosed

We've been though one round of reviews on this proposal, and I need to create tickets for Sponsor 55 now.

I merged the proposal to master, and updated the proposals index.

comment:6 Changed 6 months ago by gaba

Keywords: network-team-roadmap-2020Q1 added

Add all the tickets from sponsor 55 that are done and being worked on to the keyword #network-team-roadmap-2020Q1 so I can look at them in the wiki page...

Note: See TracTickets for help on using tickets.