Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #33051
Closed (moved) (moved)
Open
Created Jan 24, 2020 by Gaba@gaba

O1.4 - Measure the number of Tor relays that support IPv6 reachability checks

See Proposal 313: Relay IPv6 Statistics: https://gitweb.torproject.org/torspec.git/tree/proposals/313-relay-ipv6-stats.txt

Tor's IPv6 reachability checks are described in: Proposal 311: Tor Relay IPv6 Reachability: https://gitweb.torproject.org/torspec.git/tree/proposals/311-relay-ipv6-reachability.txt

The child tickets are in proposal section order, but they will probably be implemented in this order:

Dependencies:

  • Prop 311: 5. Declare Support for Subprotocol Version "Relay=3" (O1.1, #33226 (moved))

Implementation:

  • Write a Script that Counts IPv6 Relays in the Consensus

Metrics Review:

  • Check IPv6 Relay Consensus Counts Script

Internal Testing:

  • Test IPv6 Relay Consensus Counts using Chutney (O1.3, #33267 (moved))

Public Tor Network Testing:

  • Test IPv6 Relay Consensus Counts on the Tor Network

Monitoring:

  • Monitor IPv6 Relay Counts in the Consensus
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking