diff options
| -rw-r--r-- | dir-spec.txt | 18 | ||||
| -rw-r--r-- | tor-spec.txt | 10 |
2 files changed, 28 insertions, 0 deletions
diff --git a/dir-spec.txt b/dir-spec.txt index 657e95f..d486991 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -2294,6 +2294,24 @@ "id" SP "ed25519" SP "none" NL [vote only, at most once] + "stats" SP [KeyValues] NL + + [At most once. Vote only] + + KeyValue ::= Keyword '=' Number + Number ::= [0-9]+("."[0-9]+)? + KeyValues ::= KeyValue | KeyValues SP KeyValue + + Line containing various statistics that an authority has computed for + this relay. Each stats is represented as a key + value. Reported keys + are: + + "wfu" - Weighted Fractional Uptime + "tk" - Weighted Time Known + "mtbf" - Mean Time Between Failure (stability) + + (As of tor-0.4.6.1-alpha) + The footer section is delineated in all votes and consensuses supporting consensus method 9 and above with the following: diff --git a/tor-spec.txt b/tor-spec.txt index 11a991a..62b7d5d 100644 --- a/tor-spec.txt +++ b/tor-spec.txt @@ -1822,6 +1822,16 @@ see tor-design.pdf. [*] Older versions of Tor also send this reason when connections are reset. + Upon receiving a RELAY_END cell, the recipient may be sure that no further + cells will arrive on that stream, and can treat such cells as a protocol + violation. + + After sending a RELAY_END cell, the sender needs to give the recipient + time to receive that cell. In the meantime, the sender SHOULD remember + how many cells of which types (CONNECTED, SENDME, DATA) that it would have + accepted on that stream, and SHOULD kill the circuit if it receives more + than permitted. + --- [The rest of this section describes unimplemented functionality.] Because TCP connections can be half-open, we follow an equivalent |