diff options
| author | Nick Mathewson <nickm@torproject.org> | 2017-08-23 10:03:30 -0400 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2017-08-23 10:03:30 -0400 |
| commit | 85d7c57bbdf5492046b64ccb5761547de3ea171d (patch) | |
| tree | 4d9b106b3bf18cad8d968d6330393f5fd8522fc4 /dir-spec.txt | |
| parent | d92fc8b17b207cfb8131f6922a95d022c37c06c8 (diff) | |
| download | torspec-85d7c57bbdf5492046b64ccb5761547de3ea171d.tar.gz torspec-85d7c57bbdf5492046b64ccb5761547de3ea171d.zip | |
document the term "reasonably live"; clarify "live"
Diffstat (limited to 'dir-spec.txt')
| -rw-r--r-- | dir-spec.txt | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/dir-spec.txt b/dir-spec.txt index ade48ae..3c57fb8 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -3295,8 +3295,8 @@ The following methods have incorrect implementations; authorities SHOULD release time.] Clients try to have a live consensus network-status document at all times. - A network-status document is "live" if the time in its valid-until field - has not passed. + A network-status document is "live" if the time in its valid-after field + has passed, and the time in its valid-until field has not passed. When a client has no consensus network-status document, it downloads it from a randomly chosen fallback directory mirror or authority. Clients @@ -3354,6 +3354,10 @@ The following methods have incorrect implementations; authorities SHOULD the same update strategy as for the normal consensus. They should not download more than one consensus flavor. + When a client does not have a live consensus, it will generally use the + most recent consensus it has if that consensus is "reasonably live". A + "reasonably live" consensus is one that expired less than 24 hours ago. + 5.2. Downloading server descriptors or microdescriptors Clients try to have the best descriptor for each router. A descriptor is |