diff options
| author | Isis Lovecruft <isis@torproject.org> | 2017-08-03 18:20:22 +0000 |
|---|---|---|
| committer | Isis Lovecruft <isis@torproject.org> | 2017-08-03 18:20:22 +0000 |
| commit | db17344f15a9e02d041e9d51ff325133cc07007e (patch) | |
| tree | 7bfb22946082e85f1ed9f78645c483b2b0d81359 /proposals/271-another-guard-selection.txt | |
| parent | 28a8208232cac218b9bbbd95521ad7bd3c266b37 (diff) | |
| download | torspec-db17344f15a9e02d041e9d51ff325133cc07007e.tar.gz torspec-db17344f15a9e02d041e9d51ff325133cc07007e.zip | |
prop271: Clarify when guards may be added to {CONFIRMED_GUARDS}.
Diffstat (limited to 'proposals/271-another-guard-selection.txt')
| -rw-r--r-- | proposals/271-another-guard-selection.txt | 5 |
1 files changed, 4 insertions, 1 deletions
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}. |