diff options
| author | Damian Johnson <atagar@torproject.org> | 2015-05-19 08:03:13 -0700 |
|---|---|---|
| committer | Damian Johnson <atagar@torproject.org> | 2015-05-19 08:03:13 -0700 |
| commit | e0e81d078af8c747bf08309c1a0c013d2f98efc3 (patch) | |
| tree | b086bcc40cc04fcbb828b93a48328fc713ada955 | |
| parent | 7ec5d394de1aa1d43e58141de9f6d3cb5822b4ca (diff) | |
Revise NETWORK_LIVENESS specnetwork_liveness
Minor revisions for the new NETWORK_LIVENESS event...
* Include a note about the version when this is being added.
* No need to say new fields are allowed. This is said near the start of
section 4.1...
"Clients MUST tolerate events with arguments and keywords they do not
recognize"
* Rejigger the spec's style a tad to be more like other events.
| -rw-r--r-- | control-spec.txt | 12 |
1 files changed, 5 insertions, 7 deletions
diff --git a/control-spec.txt b/control-spec.txt index c9f871b..5377658 100644 --- a/control-spec.txt +++ b/control-spec.txt @@ -2789,15 +2789,13 @@ 4.1.27. Network liveness has changed Syntax: - "650" SP "NETWORK_LIVENESS" SP Status ... CRLF - Status = "UP" | "DOWN" + "650" SP "NETWORK_LIVENESS" SP Status CRLF + Status = "UP" / ; The network now seems to be reachable. + "DOWN" / ; The network now seems to be unreachable. - The Status values are: - "UP" -- The network now seems to be reachable. - "DOWN" -- The network now seems to be unreachable. + Controllers MUST tolerate unrecognized status types. - Controllers MUST ignore unrecognized Status values, and MUST ignore - unrecognized material at the end of the event line. + [NETWORK_LIVENESS was added in Tor 0.2.7.2-alpha] 5. Implementation notes |