This is an automated email from the git hooks/post-receive script.
nickm pushed a commit to branch main in repository torspec.
commit 9aad630153d8bb7c9c3b07b47855700705595059 Author: Nick Mathewson nickm@torproject.org AuthorDate: Mon May 23 14:31:38 2022 -0400
Clarify who sends padding negotiation and when.
Also explain what should happen if those assumptions are violated. --- padding-spec.txt | 7 +++++++ 1 file changed, 7 insertions(+)
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: