[or-cvs] [tor/master 06/10] In the migration plan, mention how to prevent overloading the bridge authority
arma at torproject.org
arma at torproject.org
Fri Oct 1 02:06:18 UTC 2010
Author: Steven Murdoch <Steven.Murdoch at cl.cam.ac.uk>
Date: Wed, 17 Mar 2010 11:56:59 +0000
Subject: In the migration plan, mention how to prevent overloading the bridge authority
Commit: df3911ded8cc056f4d399d76f2518c69332be4f8
---
.../ideas/xxx-automatic-node-promotion.txt | 11 +++++++++--
1 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/doc/spec/proposals/ideas/xxx-automatic-node-promotion.txt b/doc/spec/proposals/ideas/xxx-automatic-node-promotion.txt
index 8563b47..8cf9350 100644
--- a/doc/spec/proposals/ideas/xxx-automatic-node-promotion.txt
+++ b/doc/spec/proposals/ideas/xxx-automatic-node-promotion.txt
@@ -99,9 +99,16 @@ Target:
3.x New controller message
-4. Related proposals
+4. Migration plan
-5. Open questions:
+ We should start by setting a high bandwidth and uptime requirement
+ in the consensus, so as to avoid overloading the bridge authority
+ with too many bridges. Once we are confident our systems can scale,
+ the criteria can be gradually shifted down to gain more bridges.
+
+5. Related proposals
+
+6. Open questions:
- What user interaction policy should we take?
--
1.7.1
More information about the tor-commits
mailing list