This is an automated email from the git hooks/post-receive script.
nickm pushed a commit to branch main in repository torspec.
commit e2f59b2e266785dd0bf2a2ba6ffece69241aa6ee Author: Ian Jackson ijackson@chiark.greenend.org.uk AuthorDate: Fri Jul 8 12:52:47 2022 +0100
specify how to reenable padding
Arti has a "dormant mode" which means that it might need to reenable channel padding after hving disabled it.
How to do this, paarticularly in the face of possibly changing consensus parameters, is an edge case. --- padding-spec.txt | 10 ++++++++++ 1 file changed, 10 insertions(+)
diff --git a/padding-spec.txt b/padding-spec.txt index 511ea01..2ffd33d 100644 --- a/padding-spec.txt +++ b/padding-spec.txt @@ -266,6 +266,16 @@ Table of Contents immediately after sending their NETINFO cell. Recipients SHOULD, however, accept padding negotiation messages at any time.
+ If a client which previously negotiated reduced, or disabled, padding, and + wishes to re-enable default padding (ie padding according to the consensus + parameters), it SHOULD send CELL_PADDING_NEGOTIATE START with zero in the + ito_low_ms and ito_high_ms fields. (It therefore SHOULD NOT copy the values + from its own established consensus into the CELL_PADDING_NEGOTIATE cell.) + This avoids the client needing to send updated padding negotiations if the + consensus parameters should change. The recipient's clamping of the timing + parameters will cause the recipienty to use its notion of the consensus + parameters. + Clients and bridges MUST reject padding negotiation messages from relays, and close the channel if they receive one.