[tor-commits] [torspec/master] Correct the description of when to disable a node as a likely sybil.

[nickm@xxxxxxxxxxxxxx]

commit 49db7e0de3f3dc6acbc9016e3cb9068a6f8c9407
Author: Nick Mathewson <nickm@xxxxxxxxxxxxxx>
Date:   Tue Apr 16 12:13:24 2013 -0400

    Correct the description of when to disable a node as a likely sybil.
---
 dir-spec.txt |    9 +++++----
 1 files changed, 5 insertions(+), 4 deletions(-)

diff --git a/dir-spec.txt b/dir-spec.txt
index e1e85f7..5a84250 100644
--- a/dir-spec.txt
+++ b/dir-spec.txt
@@ -1766,10 +1766,11 @@
    Directory server administrators may label some relays or IPs as
    blacklisted, and elect not to include them in their network-status lists.
 
-   Authorities SHOULD 'disable' any relays in excess of 3 on any single IP.
-   When there are more than 3 to choose from, authorities should first prefer
-   authorities to non-authorities, then prefer Running to non-Running, and
-   then prefer high-bandwidth to low-bandwidth[*].  To 'disable' a relay, the
+   Authorities SHOULD 'disable' any relays in excess of 2 on any single
+   IP.  When there are more than 2 (or AuthDirMaxServersPerAddr) to
+   choose from, authorities should first prefer authorities to
+   non-authorities, then prefer Running to non-Running, and then prefer
+   high-bandwidth to low-bandwidth[*].  To 'disable' a relay, the
    authority *should* advertise it without the Running or Valid flag.
 
       [*] In this comparison, measured bandwidth is used unless it is not



_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits