aboutsummaryrefslogtreecommitdiff
path: root/doc/spec/control-spec.txt
diff options
context:
space:
mode:
Diffstat (limited to 'doc/spec/control-spec.txt')
-rw-r--r--doc/spec/control-spec.txt14
1 files changed, 8 insertions, 6 deletions
diff --git a/doc/spec/control-spec.txt b/doc/spec/control-spec.txt
index 424deea736..cda883e119 100644
--- a/doc/spec/control-spec.txt
+++ b/doc/spec/control-spec.txt
@@ -1200,14 +1200,16 @@ $Id$
CLOCK_SKEW
SKEW="+" / "-" SECONDS
+ MIN_SKEW="+" / "-" SECONDS.
SOURCE="DIRSERV:IP:Port" / "NETWORKSTATUS:IP:PORT" / "CONSENSUS"
If "SKEW" is present, it's an estimate of how far we are from the
- time declared in the source. If the source is a DIRSERV, we got
- the current time from a connection to a dirserver. If the source is
- a NETWORKSTATUS, we decided we're skewed because we got a v2
- networkstatus from far in the future. If the source is
- CONSENSUS, we decided we're skewed because we got a networkstatus
- consensus from the future.
+ time declared in the source. (In other words, if we're an hour in
+ the past, the value is -3600.) "MIN_SKEW" is present, it's a lower
+ bound. If the source is a DIRSERV, we got the current time from a
+ connection to a dirserver. If the source is a NETWORKSTATUS, we
+ decided we're skewed because we got a v2 networkstatus from far in
+ the future. If the source is CONSENSUS, we decided we're skewed
+ because we got a networkstatus consensus from the future.
{Controllers may want to warn the user if the skew is high, or if
multiple skew messages appear at severity WARN. Controllers