Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
T
Tor Specifications
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
George Kadianakis
Tor Specifications
Commits
b92dd338
Commit
b92dd338
authored
4 years ago
by
Nick Mathewson
Browse files
Options
Downloads
Patches
Plain Diff
Update dirspec to reflect REASONABLY_LIVE_TIME.
parent
61b5da17
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
dir-spec.txt
+10
-3
10 additions, 3 deletions
dir-spec.txt
with
10 additions
and
3 deletions
dir-spec.txt
+
10
−
3
View file @
b92dd338
...
...
@@ -362,7 +362,10 @@
(See note above: clients guess that the next consensus's FU will be
two intervals after the current VA.)
VU: The consensus is no longer valid.
VU: The consensus is no longer valid; clients should continue to try to
download a new consensus if they have not done so already.
VU + 24 hours: Clients will no longer use the consensus at all.
VoteSeconds and DistSeconds MUST each be at least 20 seconds; FU-VA and
VU-FU MUST each be at least 5 minutes.
...
...
@@ -1770,10 +1773,14 @@
[Exactly once.]
The end of the Interval for this vote. After this time,
the
c
onsensus produced by this vote should not be used.
See section 1.4
The end of the Interval for this vote. After this time,
all
c
lients should try to find a more recent consensus.
See section 1.4
for voting timeline information.
In practice, clients continue to use the consensus for up to 24 hours
after it is no longer valid, if no more recent consensus can be
downloaded.
"voting-delay" SP VoteSeconds SP DistSeconds NL
[Exactly once.]
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment