From 05b9bacc4c166f310a673a86ff1b5e92e6f6a6b4 Mon Sep 17 00:00:00 2001 From: Nick Mathewson Date: Thu, 11 Aug 2022 11:05:46 -0400 Subject: xon/xoff: specify behavior on weird values. --- proposals/324-rtt-congestion-control.txt | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'proposals/324-rtt-congestion-control.txt') 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 -- cgit v1.2.3-54-g00ecf