... | ... | @@ -176,6 +176,42 @@ Security Releases |
|
|
|
|
|
* [NetworkTeam/TROVE](NetworkTeam/TROVE)
|
|
|
|
|
|
|
|
|
## Plans for 2021
|
|
|
|
|
|
* [Making the Tor network faster & more reliable for users in Internet-repressive places ](https://gitlab.torproject.org/tpo/core/tor/-/issues/40143)
|
|
|
* Main large things:
|
|
|
* Proposal 325 (packed relay cells) [possibly join with prop319]
|
|
|
* Proposal 324 (congestion control)
|
|
|
* Proposal 329 (conflux)
|
|
|
* Reach item: Re-do floodflow experiment; provide relays way to specify shared machine/link
|
|
|
* Smaller things:
|
|
|
* Proposal 328 (Relay overload reporting)
|
|
|
* Proposal 291 (Two guards - ensuring it works; it seems to in CBT experiments)
|
|
|
* Long tail of bugfixes/likely issues:
|
|
|
* EWMA/KIST
|
|
|
* OOMkiller issues wrt conflux and congestion control
|
|
|
* Shadow vs live network discrepancies
|
|
|
* Refactoring ancient pieces of circuit timeouts? (seems not needed)
|
|
|
* [Arti](https://gitlab.torproject.org/tpo/core/arti/-/blob/main/TODO)
|
|
|
* what do we need to have it ready for replacement of C code? Is that possible?
|
|
|
* more involvement. maybe funding.
|
|
|
* define scope for MVP
|
|
|
* what could be a reasonable timeline?
|
|
|
* by the end of the year have a client (milestones B and C completed)
|
|
|
* MILESTONE B: Secure minimal client
|
|
|
* MILESTONE C: Client feature parity
|
|
|
* Technical debt
|
|
|
* Tooling: CI
|
|
|
* Transition to arti is the best way to tackle technical debt right now.
|
|
|
* Preparation for future work:
|
|
|
* Proposal 319 (fragmented cells) [may be needed for proof-of-work, will be needed for pq or walking onions]
|
|
|
* Proposal 321 (happy families)
|
|
|
* Walking onions (if funded)
|
|
|
* Authority contact decentralization
|
|
|
* Evaluating potential next-step cryptography (tagging + pq)
|
|
|
* Prototype of Proposal 327 (PoW over intro)
|
|
|
|
|
|
## Active Sponsors and Contracts
|
|
|
|
|
|
### Roadmap
|
... | ... | |