wiki:org/teams/NetworkHealthTeam

Network Health Team

Overview

The network health team doesn't quite exist yet, in the sense that it has no people funded to work on it, but when it does, it will work on these five areas:

(1) track community standards about what makes a good relay

  • publish up-to-date expectations for relay operators
  • set best practices for how to set relay families
  • detect and resolve bad relays
    • exitmap, sybil detection, hsdir traps

(2) anomaly analysis / network health engineer [with network team]

  • establish baselines of expected network behavior
  • look for and resolve denial of service issues
  • track connectivity issues between relays
  • look for relays hitting resource limits

(3) make sure usage/growth stats are collected and accurate

  • track network performance, relay diversity by various metrics
  • count users [with network team and metrics team]
  • monitor bridge growth and usage [with censorship team]

(4) relay advocacy [with community team]

  • maintain docs for setting up and running relays and bridges
  • grow a cohesive community of relay operators so they have peers
    • keep relays on the right tor versions
  • relaunch a gamification / badge system for lauding good relay progress
  • strengthen relationships with non-profit orgs that run relays
  • help companies that want to offset their tor network load

(5) maintain the components of the network

  • maintain directory authority relationships
  • keep bandwidth authorities working (including setting the right balance between speed and location diversity)
  • have enough tor browser default bridges, and keep them running smoothly [with censorship team]
  • update the fallbackdirs list

People

Roger, David, and Georg have expressed enthusiasm about having this team.

Communication

Other teams have weekly irc meetings, but we're not there yet.

We do have a public and archived mailing list though: https://lists.torproject.org/cgi-bin/mailman/listinfo/network-health

Resources

In Stockholm we met to begin planning: notes

Tickets

So far there is no own network health component in our Trac system and we likely won't create a new one as we are about to migrate to an own Gitlab instance. For now we use the network-health keyword on tickets that should be on the radar of the network health team. All of those tickets can be found below:

Owner: cohosh (1 match)

Ticket Summary Status Owner Reviewer Priority Severity Modified
#32545 Perform measurements to concretely understand snowflake throughput and network health assigned cohosh Medium Normal 37 hours ago

Owner: ggus (1 match)

Ticket Summary Status Owner Reviewer Priority Severity Modified
#32934 EFF Legal FAQ review - 2020 edition assigned ggus Medium Normal 10 days ago

Owner: gk (2 matches)

Ticket Summary Status Owner Reviewer Priority Severity Modified
#32864 Reproduce Arthur's exit failures and then contact or badexit the relays assigned gk Medium Normal 10 hours ago
#20969 Detect relays that don't update their onion keys every 7 days. assigned gk Medium Normal 8 days ago

Owner: metrics-team (11 matches)

Ticket Summary Status Owner Reviewer Priority Severity Modified
#33010 Monitor cloudflare captcha rate: do a periodic onionperf-like query to a cloudflare-hosted static site new metrics-team Medium Normal 28 hours ago
#29343 Run arthur's DNS timeout scanner, archive it in CollecTor, and add it to Onionoo new metrics-team Medium Normal 2 days ago
#23509 Implement family-level pages showing aggregated graphs assigned metrics-team Medium Normal 6 days ago
#26124 Bring​ back Tor​ Weather new metrics-team Medium Normal 8 days ago
#12131 Measure connectivity patterns between relays assigned metrics-team Medium Normal 8 days ago
#26089 collect and archive DNS resolver data of tor exits new metrics-team Medium Normal 8 days ago
#29344 Consider heartbeat frequency, logging and extra-info statistics new metrics-team Very High Normal 8 days ago
#27235 add route_origin_rpki_validity field new metrics-team Medium Normal 9 days ago
#27155 Include BGP prefix information in details documents new metrics-team Medium Normal 9 days ago
#26585 improve AS number and name coverage (switch maxmind to RIPE Stat) new metrics-team Medium Normal 9 days ago
#28529 Confirm that the strange onionoo flood is resolved new metrics-team Medium Normal 8 months ago

Owner: neel (2 matches)

Ticket Summary Status Owner Reviewer Priority Severity Modified
#32672 Reject 0.2.9 and 0.4.0 in dirserv_rejects_tor_version() [DO NOT MERGE BEFORE FEB 2020] merge_ready neel teor Medium Normal 14 hours ago
#26769 We should make HSv3 desc upload less frequent needs_information neel asn Medium Normal 11 months ago

Owner: tbb-team (1 match)

Ticket Summary Status Owner Reviewer Priority Severity Modified
#19119 Repurpose block-malicious-sites-checkbox on TLS error page in Tor Browser new tbb-team Medium Normal 3 months ago

Owner: (none) (20 matches)

Ticket Summary Status Owner Reviewer Priority Severity Modified
#5565 MyFamily should provide an alternate non-idhex subscription mechanism reopened Medium Normal 8 days ago
#7193 Tor's sybil protection doesn't consider IPv6 new Medium Normal 8 days ago
#33018 Dir auths using an unsustainable 400+ mbit/s, need to diagnose and fix new Medium Normal 3 hours ago
#25884 add support for exitmap requirements assigned Medium Normal 8 days ago
#31223 Research approaches for improving the availability of services under DoS new Medium Normal 8 days ago
#15060 Decide the fate of MyFamily new Medium Normal 8 days ago
#28860 Increased DNS failure rate when using ServerDNSResolvConfFile with tor 0.3.4.9 (as opposed to 0.3.3.x) new Medium Normal 8 days ago
#26691 add 'working DNS' to the list of mandatory requirements for the 'exit' flag new Medium Normal 8 days ago
#24014 Make exits check DNS periodically, and disable exit traffic if it fails new Medium Normal 8 days ago
#26094 increase minimal bandwidth requirements, update the manpage, relay guide and FAQ assigned arma Medium Normal 8 days ago
#12389 Should we warn when exit nodes are using opendns or google dns? needs_revision High Normal 11 days ago
#20055 Remove relays that fail to rotate onion keys from the consensus new Medium Normal 2 weeks ago
#28969 Onion Service v3 connection status update event new Medium Normal 7 weeks ago
#28968 Onion Service v2 connection status update event new Medium Normal 7 weeks ago
#28967 Tor control command to connect to Onion Service new Medium Normal 7 weeks ago
#19068 Write and run a clique reachability test. new Medium Normal 3 months ago
#31291 non-public relay health metrics for operators new Medium Normal 5 months ago
#31290 provide DNS health metrics for tor exit relay operators new Medium Normal 6 months ago
#30487 dirmngr goes berserk making tor requests after gpg --recv-key attempt ends new Medium Normal 8 months ago
#30420 Should we recommend that relay operators turn on tcp bbr? new Medium Normal 9 months ago

Last modified 41 hours ago Last modified on Jan 21, 2020, 3:12:02 PM