aboutsummaryrefslogtreecommitdiff
path: root/guard-spec.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2017-02-02 08:51:18 -0500
committerNick Mathewson <nickm@torproject.org>2017-02-02 08:51:18 -0500
commitd9e76007acb3935c49778f01a858a4b84cf2bf00 (patch)
tree1f7c594556af57dec70952ea10350773c838a6d5 /guard-spec.txt
parent65e24ed3f1255b0b836af1a3cefbb16e414c4ab8 (diff)
downloadtorspec-d9e76007acb3935c49778f01a858a4b84cf2bf00.tar.gz
torspec-d9e76007acb3935c49778f01a858a4b84cf2bf00.zip
Tweak description
Diffstat (limited to 'guard-spec.txt')
-rw-r--r--guard-spec.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/guard-spec.txt b/guard-spec.txt
index a1e8e93..731ad97 100644
--- a/guard-spec.txt
+++ b/guard-spec.txt
@@ -473,11 +473,11 @@
random from {USABLE_FILTERED_GUARDS}. Set its {is_pending}
field to true. The circuit is <usable_if_no_better_guard>.
- If during the above algorithm we exhaust all sampled guards before finding a
- reachable one, then we proceed by marking all guards as <maybe> reachable so
- that we can keep on sampling.
+ * Otherwise, if USABLE_FILTERED_GUARDS is empty, we have exhausted
+ all the sampled guards. In this case we proceed by marking all guards
+ as <maybe> reachable so that we can keep on sampling.
- When we finally connect to a guard, we update the {last_tried_connect} time
+ Whenever we yield a guard, we update the {last_tried_connect} time
for the guard to 'now.'
In some cases (for example, when we need a certain directory feature,