diff options
| author | Steven Murdoch <Steven.Murdoch@cl.cam.ac.uk> | 2010-03-17 11:56:59 +0000 |
|---|---|---|
| committer | Roger Dingledine <arma@torproject.org> | 2010-09-30 22:04:52 -0400 |
| commit | df3911ded8cc056f4d399d76f2518c69332be4f8 (patch) | |
| tree | c4ec858feb8851792fc670dff62528f64fe1bb30 | |
| parent | ac552473501c8c56f0b6a653528ca0879bb20bdd (diff) | |
| download | tor-df3911ded8cc056f4d399d76f2518c69332be4f8.tar.gz tor-df3911ded8cc056f4d399d76f2518c69332be4f8.zip | |
In the migration plan, mention how to prevent overloading the bridge authority
| -rw-r--r-- | doc/spec/proposals/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 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? |