diff options
| author | JeremyRand <biolizard89@gmail.com> | 2019-10-09 22:56:51 +0000 |
|---|---|---|
| committer | JeremyRand <biolizard89@gmail.com> | 2019-10-11 00:11:57 +0000 |
| commit | cd916518f3e3ea5f8a390d24727eadf68cb8271f (patch) | |
| tree | c862bf20fcf5be9cb433fee7319b4dc8e7d11cd1 /control-spec.txt | |
| parent | c5d276cfb9192e95862ece77c35c104946d87634 (diff) | |
| download | torspec-cd916518f3e3ea5f8a390d24727eadf68cb8271f.tar.gz torspec-cd916518f3e3ea5f8a390d24727eadf68cb8271f.zip | |
Bug 19859: Note that client protocols might be extended later
Diffstat (limited to 'control-spec.txt')
| -rw-r--r-- | control-spec.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/control-spec.txt b/control-spec.txt index 03439eb..d7c7cc9 100644 --- a/control-spec.txt +++ b/control-spec.txt @@ -2215,7 +2215,7 @@ The "CLIENT_PROTOCOL" field indicates the protocol that was used by a client to initiate this stream. (Streams for clients connected with different protocols are isolated on separate circuits if the IsolateClientProtocol - flag is active.) + flag is active.) Controllers MUST tolerate unrecognized client protocols. The "NYM_EPOCH" field indicates the nym epoch that was active when a client initiated this stream. The epoch increments when the NEWNYM signal is |