Changes between Initial Version and Version 1 of Ticket #28807, comment 1


Ignore:
Timestamp:
Dec 11, 2018, 3:03:44 AM (6 months ago)
Author:
teor
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #28807, comment 1

    initial v1  
    3232
    3333A. Here's one way we could fix it:
    34 1. Introduce a new consensus method that supports the bwweightscale and maxunmeasuredbw consensus parameters properly (#19011)
    35 2. Convince directory authority operators to set maxunmeasuredbw to:
    36   * 1 (0.34 clients choosing an authority each time every client builds 1 circuit), or
    37   * 0 (no clients choosing authorities for circuits)
     34  1. Introduce a new consensus method that supports the bwweightscale and maxunmeasuredbw consensus parameters properly (#19011)
     35  2. Convince directory authority operators to set maxunmeasuredbw to:
     36    * 1 (0.34 clients choosing an authority each time every client builds 1 circuit), or
     37    * 0 (no clients choosing authorities for circuits)
    3838But this change affects all unmeasured relays, not just authorities.
    3939
    4040B. Here's another way we could fix it:
    41 1. Convince directory authority operators to set `MaxAdvertisedBandwidth 0` in their torrcs
     41  1. Convince directory authority operators to set `MaxAdvertisedBandwidth 0` in their torrcs
    4242
    4343Since authorities are unmeasured, tor will use min(self-reported bandwidth, MaxAdvertisedBandwidth, 20) as their bandwidth. sbws and Torflow never produce results for authorities, so they will always be unmeasured. (sbws 1.0.3 and later will also apply the MaxAdvertisedBandwidth limit if authorities are ever measured. See #28598, #28588.)