diff options
| author | Nick Mathewson <nickm@torproject.org> | 2022-05-23 14:31:38 -0400 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2022-05-27 14:25:03 -0400 |
| commit | 9aad630153d8bb7c9c3b07b47855700705595059 (patch) | |
| tree | f4a1551be924c51c796bb9ec16aecbb773d803b0 | |
| parent | e35a77088220314b7fcb4053033f131d1357dac6 (diff) | |
| download | torspec-9aad630153d8bb7c9c3b07b47855700705595059.tar.gz torspec-9aad630153d8bb7c9c3b07b47855700705595059.zip | |
Clarify who sends padding negotiation and when.
Also explain what should happen if those assumptions are violated.
| -rw-r--r-- | padding-spec.txt | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/padding-spec.txt b/padding-spec.txt index 0a45e8b..9806b2a 100644 --- a/padding-spec.txt +++ b/padding-spec.txt @@ -252,6 +252,13 @@ Table of Contents CELL_PADDING_NEGOTIATE to instruct the relay not to pad, and then does not send any further padding itself. + Currently, clients negotiate padding only when a channel is created, + immediately after sending their NETINFO cell. Recipients SHOULD, however, + accept padding negotiation messages at any time. + + Clients and bridges MUST reject padding negotiation messages from relays, + and close the channel if they receive one. + 2.6. Consensus Parameters Governing Behavior Connection-level padding is controlled by the following consensus parameters: |