[tor-commits] [torspec/master] prop271: Clarify when guards may be added to {CONFIRMED_GUARDS}.
isis at torproject.org
isis at torproject.org
Thu Aug 3 18:21:35 UTC 2017
commit db17344f15a9e02d041e9d51ff325133cc07007e
Author: Isis Lovecruft <isis at torproject.org>
Date: Thu Aug 3 18:20:22 2017 +0000
prop271: Clarify when guards may be added to {CONFIRMED_GUARDS}.
---
proposals/271-another-guard-selection.txt | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/proposals/271-another-guard-selection.txt b/proposals/271-another-guard-selection.txt
index a0fba19..38da000 100644
--- a/proposals/271-another-guard-selection.txt
+++ b/proposals/271-another-guard-selection.txt
@@ -389,7 +389,10 @@ marking guards as confirmed. —isis]
Randomized as RAND(now, {GUARD_LIFETIME}/10).
We add new members to {CONFIRMED_GUARDS} when we mark a circuit
- built through a guard as "for user traffic."
+ built through a guard as "for user traffic." That is, a circuit is
+ considered for use for client traffic when we have decided that we
+ could attach a stream to it; at that point the guard for that
+ circuit SHOULD be added to {CONFIRMED_GUARDS}.
Whenever we remove a member from {SAMPLED_GUARDS}, we also remove
it from {CONFIRMED_GUARDS}.
More information about the tor-commits
mailing list