[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-commits] [torspec/main] Clarify behavior on out-of-bounds link padding parameters.
commit 315ce4fc3b6677cd76bd8c303a5b72377dc25649
Author: Nick Mathewson <nickm@xxxxxxxxxxxxxx>
Date: Mon Aug 16 11:12:17 2021 -0400
Clarify behavior on out-of-bounds link padding parameters.
---
tor-spec.txt | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/tor-spec.txt b/tor-spec.txt
index 8d345fb..7e76562 100644
--- a/tor-spec.txt
+++ b/tor-spec.txt
@@ -1954,9 +1954,11 @@ see tor-design.pdf.
field is either 1 (stop padding) or 2 (start padding). For the start
padding command, a pair of timeout values specifying a low and a high
range bounds for randomized padding timeouts may be specified as unsigned
- integer values in milliseconds. The ito_low_ms field must not be lower than
- the current consensus parameter value for nf_ito_low (default: 1500).
- ito_high_ms must be greater than ito_low_ms.
+ integer values in milliseconds. The ito_low_ms field should not be lower
+ than the current consensus parameter value for nf_ito_low (default:
+ 1500). The ito_high_ms field must should not be lower than ito_low_ms.
+ (If any party receives an out-of-range value, they clamp it so
+ that it is in-range.)
For more details on padding behavior, see padding-spec.txt.
_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits