Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S sbws
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Network Health
  • sbws
  • Issues
  • #27339
Closed
Open
Created Aug 27, 2018 by teor@teor

Work out a policy for resolving differences between torflow and sbws

In legacy/trac#27135 (moved), we talk about how to deal with differences between torflow and sbws.

Here are some options:

  1. Any difference between sbws and torflow is a bug in sbws that should be fixed.
  2. If a sbws deployment is within X% of an existing bandwidth authority, sbws is ok. (The total consensus weights of the existing bandwidth authorities are within 50% of each other, see legacy/trac#25459 (moved).)
  3. Let's choose an ideal bandwidth distribution for the Tor network, and modify sbws until we get that distribution.

Juga suggested that we start with policy 2, and use research to work out when to move to policy 3.

Assignee
Assign to
Time tracking