aboutsummaryrefslogtreecommitdiff
path: root/proposals/109-no-sharing-ips.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2007-07-29 05:20:31 +0000
committerNick Mathewson <nickm@torproject.org>2007-07-29 05:20:31 +0000
commit3b0b185a62e6ae0d9015ff5d6dc3ab06be7dd3c5 (patch)
tree088032692e711ee87470210d32107bb2b913a2ce /proposals/109-no-sharing-ips.txt
parentfeb59d9c380f505078006e7bb4982ad6cb1a92e7 (diff)
downloadtorspec-3b0b185a62e6ae0d9015ff5d6dc3ab06be7dd3c5.tar.gz
torspec-3b0b185a62e6ae0d9015ff5d6dc3ab06be7dd3c5.zip
r13979@catbus: nickm | 2007-07-29 01:20:20 -0400
Implement proposal 109: As an authority, never call more than 3 servers per IP Running and Valid. Prefer Running servers to non-running ones; then prefer high-bandwidth to low-bandwidth. Needs testing. svn:r10968
Diffstat (limited to 'proposals/109-no-sharing-ips.txt')
-rw-r--r--proposals/109-no-sharing-ips.txt17
1 files changed, 11 insertions, 6 deletions
diff --git a/proposals/109-no-sharing-ips.txt b/proposals/109-no-sharing-ips.txt
index 4a5f1a8..483b8b5 100644
--- a/proposals/109-no-sharing-ips.txt
+++ b/proposals/109-no-sharing-ips.txt
@@ -4,7 +4,7 @@ Version: $Revision$
Last-Modified: $Date$
Author: Kevin Bauer & Damon McCoy
Created: 9-March-2007
-Status: Accepted
+Status: Closed
Overview:
This document describes a solution to a Sybil attack vulnerability in the
@@ -34,14 +34,19 @@ Specification:
For each IP address, each directory authority tracks the number of routers
using that IP address, along with their total observed bandwidth. If there
are more than MAX_SERVERS_PER_IP servers at some IP, the authority should
- "disable" all but MAX_SERVERS_PER_IP servers. If the total observed
+ "disable" all but MAX_SERVERS_PER_IP servers. When choosing which servers
+ to disable, the authority should first disable non-Running servers in
+ increasing order of observed bandwidth, and then should disable Running
+ servers in increasing order of bandwidth.
+
+ [[ We don't actually do this part here. -NM
+
+ If the total observed
bandwidth of the remaining non-"disabled" servers exceeds MAX_BW_PER_IP,
the authority should "disable" some of the remaining servers until only one
server remains, or until the remaining observed bandwidth of non-"disabled"
- servers is under MAX_BW_PER_IP. When choosing which servers to disable,
- the authority should first disable non-Running servers in increasing order
- of observed bandwidth, and then should disable Running servers in
- increasing order of bandwidth.
+ servers is under MAX_BW_PER_IP.
+ ]]
Servers that are "disabled" MUST be marked as non-Valid and non-Running.