aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2017-05-16 09:20:26 -0400
committerNick Mathewson <nickm@torproject.org>2017-05-16 09:20:26 -0400
commitcbe17dfc88f753fa0a98acb6851fe5783e39bfc8 (patch)
tree12fd3f4c18c8373fa4bc3d51146e80da8a98c034
parent607dabf60772d152f9b9edcae3993fdc6c90a5ae (diff)
downloadtorspec-cbe17dfc88f753fa0a98acb6851fe5783e39bfc8.tar.gz
torspec-cbe17dfc88f753fa0a98acb6851fe5783e39bfc8.zip
Note the part of prop#275 that got implemented.
-rw-r--r--dir-spec.txt13
-rw-r--r--proposals/275-md-published-time-is-silly.txt6
2 files changed, 14 insertions, 5 deletions
diff --git a/dir-spec.txt b/dir-spec.txt
index 60efdc0..d6ad9d8 100644
--- a/dir-spec.txt
+++ b/dir-spec.txt
@@ -2070,11 +2070,14 @@
identity key, encoded in base64, with trailing equals sign(s)
removed. "Digest" is a hash of its most recent descriptor as
signed (that is, not including the signature), encoded in base64.
- "Publication" is the
- publication time of its most recent descriptor, in the form
- YYYY-MM-DD HH:MM:SS, in UTC. "IP" is its current IP address;
- ORPort is its current OR port, "DirPort" is its current directory
- port, or "0" for "none".
+
+ "Publication" is the publication time of its most recent descriptor,
+ in the form YYYY-MM-DD HH:MM:SS, in UTC. Implementations MAY base
+ decisions on publication times in the past, but MUST NOT reject
+ publication times in the future.
+
+ "IP" is its current IP address; ORPort is its current OR port,
+ "DirPort" is its current directory port, or "0" for "none".
"a" SP address ":" port NL
diff --git a/proposals/275-md-published-time-is-silly.txt b/proposals/275-md-published-time-is-silly.txt
index 0a01fe5..b38ee97 100644
--- a/proposals/275-md-published-time-is-silly.txt
+++ b/proposals/275-md-published-time-is-silly.txt
@@ -5,6 +5,12 @@ Created: 20-Feb-2017
Status: Open
Target: 0.3.1.x-alpha
+0. Status:
+
+ As of 0.2.9.11 / 0.3.0.7 / 0.3.1.1-alpha, Tor no longer takes any
+ special action on "future" published times, as proposed in section 4.
+
+
1. Overview
This document proposes that, in order to limit the bandwidth needed