aboutsummaryrefslogtreecommitdiff
path: root/guard-spec.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2021-10-13 17:05:59 -0400
committerNick Mathewson <nickm@torproject.org>2021-10-13 17:05:59 -0400
commita96f2f70cabb17867f8de72be5db3fc09013e6ac (patch)
treefdee4cdcaab48eaff7aee47cabb2b7c8e5464d2f /guard-spec.txt
parent01ab7bd92502bbf8c3725a15de538757b3b6bc76 (diff)
downloadtorspec-a96f2f70cabb17867f8de72be5db3fc09013e6ac.tar.gz
torspec-a96f2f70cabb17867f8de72be5db3fc09013e6ac.zip
guard-spec: Clarify how the list of primary guards can change.
Diffstat (limited to 'guard-spec.txt')
-rw-r--r--guard-spec.txt4
1 files changed, 4 insertions, 0 deletions
diff --git a/guard-spec.txt b/guard-spec.txt
index 32c4faf..267ad1c 100644
--- a/guard-spec.txt
+++ b/guard-spec.txt
@@ -426,6 +426,10 @@ Table of Contents
Once an element has been added to {PRIMARY_GUARDS}, we do not remove it
until it is replaced by some element from {CONFIRMED_GUARDS}.
+ That is: if a non-primary guard becomes confirmed and not every primary
+ guard is confirmed, then the list of primary guards list is regenerated,
+ first from the confirmed guards (as before), and then from any
+ non-confirmed primary guards guards.
Note that {PRIMARY_GUARDS} do not have to be in
{USABLE_FILTERED_GUARDS}: they might be unreachable.