[tor-commits] [torspec/master] Update dirspec to reflect REASONABLY_LIVE_TIME.

[nickm@xxxxxxxxxxxxxx]

commit b92dd338887ac023da4b5d1aa27b7b3c8ad552bd
Author: Nick Mathewson <nickm@xxxxxxxxxxxxxx>
Date:   Thu Sep 17 13:31:42 2020 -0400

    Update dirspec to reflect REASONABLY_LIVE_TIME.
---
 dir-spec.txt | 13 ++++++++++---
 1 file changed, 10 insertions(+), 3 deletions(-)

diff --git a/dir-spec.txt b/dir-spec.txt
index 47a4ee7..6b0f438 100644
--- a/dir-spec.txt
+++ b/dir-spec.txt
@@ -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
-        consensus produced by this vote should not be used.  See section 1.4
+        The end of the Interval for this vote.  After this time, all
+        clients 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.]



_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits