Changes
Page history
Adds comments about arti milestones, from meeting.
authored
Feb 05, 2021
by
Gaba
Show whitespace changes
Inline
Side-by-side
home.md
View page @
469fe53b
...
@@ -200,7 +200,27 @@ Security Releases
...
@@ -200,7 +200,27 @@ Security Releases
*
what could be a reasonable timeline?
*
what could be a reasonable timeline?
*
by the end of the year have a client (milestones B and C completed)
*
by the end of the year have a client (milestones B and C completed)
*
MILESTONE B: Secure minimal client
*
MILESTONE B: Secure minimal client
*
Guard nodes <--- first thing to work on
*
Correct path selection <-- important but current restrictions have issues
*
Timeouts
*
Circuit timeout logic
*
Connection timeout logic.
*
What other kinds of timeouts?
*
Connection padding <-- not necessary
*
Circuit padding (with padding machines)
*
Build preemptive circuits <-- very important
*
Change behavior depending on network parameters
*
CBT logic?
*
Pathbias logic <-- it can be dropped
*
Figure out where to put a specific async executor and/or TLS implementation in our stack.
*
MILESTONE C: Client feature parity
*
MILESTONE C: Client feature parity
*
V3 onion services
*
Fairness on circuits/streams?
*
Support for using bridges
*
Pluggable transport support
*
Controller API?
*
Dormant mode?
*
Transparent proxy mode(s)
*
Technical debt
*
Technical debt
*
Tooling: CI
*
Tooling: CI
*
Transition to arti is the best way to tackle technical debt right now.
*
Transition to arti is the best way to tackle technical debt right now.
...
...
...
...