Opened 15 months ago

Closed 12 months ago

Last modified 12 months ago

#27339 closed task (fixed)

Work out a policy for resolving differences between torflow and sbws

Reported by: teor Owned by:
Priority: Medium Milestone: sbws: unspecified
Component: Core Tor/sbws Version:
Severity: Normal Keywords:
Cc: pastly, juga, teor Actual Points:
Parent ID: #27107 Points:
Reviewer: Sponsor:

Description

In #27135, 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 #25459.)
  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.

Child Tickets

TicketStatusOwnerSummaryComponent
#27340closedWork out how to scale sbws to match torflow, when the distributions matchCore Tor/sbws
#28216closedjugaCompare sbws total scaled bandwidth with total consensus bandwidthCore Tor/sbws

Change History (6)

comment:1 Changed 13 months ago by juga

Milestone: sbws 1.0 (MVP must)sbws 1.1

Policy 2 is now implemented. Moving this to 1.1 milestone, to implement 3.

comment:2 Changed 12 months ago by teor

Resolution: fixed
Status: newclosed

We have already opened a lot of tickets to improve sbws in the sbws 1.1 milestone.

comment:3 Changed 12 months ago by teor

Milestone: sbws 1.1sbws 1.2

Milestone renamed

comment:4 Changed 12 months ago by teor

Milestone: sbws 1.2sbws: 1.2.x

Milestone renamed

comment:5 Changed 12 months ago by teor

Milestone: sbws: 1.2.xsbws: 1.2.x-final

Milestone renamed

comment:6 Changed 12 months ago by teor

Milestone: sbws: 1.2.x-finalsbws: unspecified

Milestone renamed

Note: See TracTickets for help on using tickets.