[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-commits] [torspec/master] Add that coords do not communicate
commit ee5491e939cda0a3258c8018db1e2cd90b730bc3
Author: Matt Traudt <sirmatt@xxxxxxx>
Date: Fri Aug 14 10:10:40 2020 -0400
Add that coords do not communicate
---
proposals/316-flashflow.md | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
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
_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits