From: Steven Murdoch Date: Wed, 17 Mar 2010 11:56:59 +0000 (+0000) Subject: In the migration plan, mention how to prevent overloading the bridge authority X-Git-Tag: tor-0.2.3.1-alpha~339 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=df3911ded8cc056f4d399d76f2518c69332be4f8;p=thirdparty%2Ftor.git In the migration plan, mention how to prevent overloading the bridge authority --- diff --git a/doc/spec/proposals/ideas/xxx-automatic-node-promotion.txt b/doc/spec/proposals/ideas/xxx-automatic-node-promotion.txt index 8563b47547..8cf9350a3b 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?