|
|
# Bandwidth Authority
|
|
|
## Tasks/Tickets
|
|
|
|
|
|
### Initially planned SoP tasks
|
|
|
|
|
|
- [ ] implement features we wanted in torflow in sbws instead (1 week)
|
|
|
- [ ] bwauth code needs to be smarter about failed circuits #16559
|
|
|
- [X] assign the 10-second client timeout as the time for failed circuits? (this was fixed by pastly)
|
|
|
- [ ] at least publish failure rates #7281
|
|
|
- [ ] Understand how accurate the bandwidth authority estimates are #7177
|
|
|
- [ ] integration tests (1 week)
|
|
|
- [X] a practice transition in the test network (1 week, but split up)
|
|
|
- [X] set up torflow
|
|
|
- [X] set up sbws
|
|
|
- [X] compare and switch
|
|
|
- [ ] work little-t tor needs (3 weeks)
|
|
|
- [X] report version of bwscanners in votes #3723
|
|
|
- [ ] stop relays reporting zero observed bandwidths #24250
|
|
|
- [ ] relays should regularly do a larger bandwidth self-test #22453
|
|
|
- [ ] bandwidth testing circuits should use guards sometimes #19009
|
|
|
- [ ] report bandwidth more often on test networks #17036
|
|
|
- [X] report bandwidth less often on large, public relays #24104
|
|
|
- [ ] non-essential tickets like https://github.com/pastly/simple-bw-scanner/issues/77 and https://github.com/pastly/simple-bw-scanner/issues/48 (2 weeks) - [ ] if time and motivation
|
|
|
- [X] Have sbws client launch tor itself https://github.com/pastly/simple-bw-scanner/77 (this was solved by pastly)
|
|
|
- [X] Evaluate using [not threads, but twisted instead (probably)] https://github.com/pastly/simple-bw-scanner/48 (pastly marked this as wontfix)
|
|
|
|
|
|
We created and worked on other tickets since this list was proposed.
|
|
|
|
|
|
```
|
|
|
SoP parent Ticket:
|
|
|
[[TicketQuery(status=!closed,order=milestone|changetime,desc=1,format=table,col=resolution|summary|component|milestone|modified|owner|reporter|cc|parent,parent=#25925)]]
|
|
|
```
|
|
|
|
|
|
[sbws PRs/issues from 2018/05/14 to 2018/08/31](https://github.com/pastly/simple-bw-scanner/issues?utf8=%E2%9C%93&q=involves%3Ajuga0++is%3Aissue%7Cpr+updated%3A%3E2018-05-14+)
|
|
|
|
|
|
```
|
|
|
[[TicketQuery(status=!closed,order=milestone|changetime,desc=1,format=table,col=resolution|summary|component|milestone|modified|owner|reporter|cc|parent|changetime,component=Core Tor/sbws)]]
|
|
|
```
|
|
|
|
|
|
[Tickets changed from 2018/05/14 to 2018/08/31 in sbws component or with bwauth keyword](https://trac.torproject.org/projects/tor/query?changetime=May+14%2C+2018..Aug+31%2C+2018&component=^Core+Tor%2Fsbws&or&keywords=~bwauth&changetime=May+14%2C+2018..Aug+31%2C+2018&component=^Core+Tor%2FTor&group=milestone&col=id&col=summary&col=component&col=owner&col=milestone&col=parent&col=reporter&order=milestone)
|
|
|
|
|
|
### PF
|
|
|
|
|
|
Initially planned:
|
|
|
|
|
|
- [ ] compared total consensus weights across bandwidth authorities (#25459)
|
|
|
- [ ] understand how accurate bandwidth authority measurements are (#7177)
|
|
|
- [ ] find over-weighted relays (#24045, #10791)
|
|
|
- [ ] map consensus weight vs bandwidth in votes (#24834)
|
|
|
- [ ] provide bwauth votes via the directory protocol (#21377)
|
|
|
- [ ] make authorities without bandwidth scanners vote flags based on measured bandwidths (#11327)
|
|
|
- [ ] reset uptimes / bandwidths when a relay changes IP address (#22308 / sbws #154)
|
|
|
- [ ] analyse and fix a bug in authority time known (#19162)
|
|
|
- [ ] some bandwidth weight cases not matching the spec (#20284)
|
|
|
- [ ] fix DirAuth weights for other relays, or stop them using other relays (#13297)
|
|
|
|
|
|
[Tickets changed from 1 Oct, 2018 to 21 Mar, 2019 in sbws component or with bwauth keyword](https://trac.torproject.org/projects/tor/query?changetime=Oct+1%2C+2018..Mar+31%2C+2019&component=^Core+Tor%2Fsbws&or&keywords=~bwauth&changetime=Oct+1%2C+2018..Mar+31%2C+2018&component=^Core+Tor%2FTor&group=milestone&col=id&col=summary&col=component&col=owner&col=milestone&col=parent&col=reporter&order=milestone&order=parent&order=status&order=changetime)
|
|
|
|
|
|
### Pending sbws work
|
|
|
|
|
|
[[org/teams/NetworkTeam/BandwidthAuthority/sbws|sbws]]
|
|
|
|
|
|
### Pending Tor tickets with bwauth keyword or scanner or bandwidth in description
|
|
|
|
|
|
[Tickets open with bwauth keyword or scanner or bandwidth in description](https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=merge_ready&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&keywords=~bwauth&or&status=accepted&status=assigned&status=merge_ready&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&description=~scanner%7Cbandwidth&group=milestone&col=id&col=summary&col=component&col=owner&col=milestone&col=parent&col=reporter&order=priority)
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
|
last two queries do not work with change time, but changetime should be added to see tickets only during sop period
|
|
|
,changetime=May+14%2C+2018..Aug+31%2C+2018
|
|
|
```
|
|
|
|
|
|
## Related pages
|
|
|
|
|
|
* [How to Run Torflow](./doc/BandwidthAuthority)
|
|
|
* [Does a Bandwidth Authority Really Matter?](./doc/BandwidthAuthorityMeasurements)
|
|
|
* [Meeting - 2018 Rome - Bandwidth Auhtority Requirements notes](./org/meetings/2018Rome/Notes/BandwidthAuthorityRequirements) |