aboutsummaryrefslogtreecommitdiff
path: root/spec
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2023-11-15 20:49:50 -0500
committerNick Mathewson <nickm@torproject.org>2023-11-15 20:49:50 -0500
commitfef5d8f1e44b3c6594ecf6d766904b73e0d6a1b4 (patch)
treea32ccfcb51a9dc4ccfbf0a874a1a0821923121c1 /spec
parentc3b8483ab6ce6486293b91e8340f7534b3366e45 (diff)
downloadtorspec-fef5d8f1e44b3c6594ecf6d766904b73e0d6a1b4.tar.gz
torspec-fef5d8f1e44b3c6594ecf6d766904b73e0d6a1b4.zip
OPE: T is based on seconds since start of _time period_.
Previously it claimed to be "since the descriptor became valid", which doesn't make sense.
Diffstat (limited to 'spec')
-rw-r--r--spec/rend-spec/revision-counter-mgt.md5
1 files changed, 3 insertions, 2 deletions
diff --git a/spec/rend-spec/revision-counter-mgt.md b/spec/rend-spec/revision-counter-mgt.md
index bd41071..627a268 100644
--- a/spec/rend-spec/revision-counter-mgt.md
+++ b/spec/rend-spec/revision-counter-mgt.md
@@ -28,8 +28,9 @@ This scheme is what we recommend for situations when multiple
service instances need to coordinate their revision counters,
without an actual coordination mechanism.
-Let T be the number of seconds that have elapsed since the descriptor
-became valid, plus 1. (T must be at least 1.) Implementations can use the
+Let T be the number of seconds that have elapsed
+since the beginning of the time period,
+plus 1. (T must be at least 1.) Implementations can use the
number of seconds since the start time of the shared random protocol run
that corresponds to this descriptor.