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 8563b4754747b58a3b2b65812fff05d70cad2d2e..8cf9350a3b0705099e4cef826372783cb3b84141 100644 (file)
--- 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?