aboutsummaryrefslogtreecommitdiff
path: root/proposals/324-rtt-congestion-control.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2022-08-11 11:05:46 -0400
committerNick Mathewson <nickm@torproject.org>2022-08-15 11:22:36 -0400
commit05b9bacc4c166f310a673a86ff1b5e92e6f6a6b4 (patch)
treeeda02e91cf5695e95e683b81592ec78b2567b485 /proposals/324-rtt-congestion-control.txt
parentcb4ae84a20793a00f35a70aad5df47d4e4c7da7c (diff)
downloadtorspec-05b9bacc4c166f310a673a86ff1b5e92e6f6a6b4.tar.gz
torspec-05b9bacc4c166f310a673a86ff1b5e92e6f6a6b4.zip
xon/xoff: specify behavior on weird values.
Diffstat (limited to 'proposals/324-rtt-congestion-control.txt')
-rw-r--r--proposals/324-rtt-congestion-control.txt6
1 files changed, 6 insertions, 0 deletions
diff --git a/proposals/324-rtt-congestion-control.txt b/proposals/324-rtt-congestion-control.txt
index c46fd4e..d529d5c 100644
--- a/proposals/324-rtt-congestion-control.txt
+++ b/proposals/324-rtt-congestion-control.txt
@@ -747,6 +747,12 @@ struct xon_cell {
u32 kbps_ewma;
}
+Parties SHOULD treat XON or XOFF cells with unrecognized versions as a
+protocol violation.
+
+In `xon_cell`, a zero value for `kbps_ewma` means that the stream's rate is
+unlimited. Parties should therefore not send "0" to mean "do not send data".
+
4.1.1. XON/XOFF behavior
If the length of an edge outbuf queue exceeds the size provided in the