diff options
| author | Matt Traudt <sirmatt@ksu.edu> | 2020-08-14 10:10:40 -0400 |
|---|---|---|
| committer | Matt Traudt <sirmatt@ksu.edu> | 2020-08-21 09:39:06 -0400 |
| commit | ee5491e939cda0a3258c8018db1e2cd90b730bc3 (patch) | |
| tree | 5054a175af9bc60198849fe5339c6014d011803a /proposals/316-flashflow.md | |
| parent | 11ed971dd8ba9609bf67b5387bb3a09af812b823 (diff) | |
| download | torspec-ee5491e939cda0a3258c8018db1e2cd90b730bc3.tar.gz torspec-ee5491e939cda0a3258c8018db1e2cd90b730bc3.zip | |
Add that coords do not communicate
Diffstat (limited to 'proposals/316-flashflow.md')
| -rw-r--r-- | proposals/316-flashflow.md | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/proposals/316-flashflow.md b/proposals/316-flashflow.md index 5caf0e1..db6bc9c 100644 --- a/proposals/316-flashflow.md +++ b/proposals/316-flashflow.md @@ -10,6 +10,9 @@ Status: Draft - `[ ]` hyperlink sources - `[ ]` make section numbers work, or don't use them, or ...? +- `[.]` do coords need to communicate? No. Specify better in Measurement + Scheduling section + - addressed in Intro # Introduction @@ -48,7 +51,8 @@ FlashFlow will run their own FlashFlow deployment consisting of a coordinator that they run and one or more measurers that they trust (e.g. because they run them themselves), similar to how each runs their own Torflow/sbws. Section 5.2 of this proposal describes long term plans -involving multiple FlashFlow deployments. +involving multiple FlashFlow deployments. *FlashFlow coordinators do not need +to communicate with each other*. FlashFlow is more performant than Torflow: FlashFlow takes 5 hours to measure the entire existing Tor network from scratch (with 3 Gbit/s |