diff options
author | Paul Syverson <syverson@itd.nrl.navy.mil> | 2005-01-28 05:13:37 +0000 |
---|---|---|
committer | Paul Syverson <syverson@itd.nrl.navy.mil> | 2005-01-28 05:13:37 +0000 |
commit | d44dcdebf53e9cb11e30bf41b593d62203880922 (patch) | |
tree | 09f23f4e5d20bff755f674faffbdb80ad5dbccca | |
parent | 083b67cda564d3ad8896f0ad6fe3332911088f33 (diff) | |
download | tor-d44dcdebf53e9cb11e30bf41b593d62203880922.tar tor-d44dcdebf53e9cb11e30bf41b593d62203880922.tar.gz |
Just a few more topology scaling notes before bed
svn:r3440
-rw-r--r-- | doc/design-paper/challenges.tex | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/doc/design-paper/challenges.tex b/doc/design-paper/challenges.tex index 6dc84e57e..f58da8266 100644 --- a/doc/design-paper/challenges.tex +++ b/doc/design-paper/challenges.tex @@ -760,7 +760,15 @@ can address them with witness connections or other means. (E.g., does it make sense to favor the nodes that are listed by more than one node at the top?) - +Been making this too hard. Save elegant answers for another venue. +Just assume 50 node clique (center). Assume these can each handle 125 +connections to other nodes. Assume everyone else connects to 3 nodes +in the center and anyone out of the center that they want to. All +3-node paths choose a center node for their second hop. Then the +network easily scales to c. 1300 nodes with commensurate increase in +bandwidth. Distribute the center hardwired to new nodes or publicize. +Let directories tell about other nodes in the network. 50-50 that +path goes whatever-center-center. \section{The Future} |