[tor-commits] [torspec] branch main updated: xon/xoff: specify behavior on weird values.

[gitolite role]

This is an automated email from the git hooks/post-receive script.

ahf pushed a commit to branch main
in repository torspec.

The following commit(s) were added to refs/heads/main by this push:
     new 05b9bac  xon/xoff: specify behavior on weird values.
     new e5cd03e  Merge remote-tracking branch 'nickm/xon_xoff_edgecases'
05b9bac is described below

commit 05b9bacc4c166f310a673a86ff1b5e92e6f6a6b4
Author: Nick Mathewson <nickm at torproject.org>
AuthorDate: Thu Aug 11 11:05:46 2022 -0400

    xon/xoff: specify behavior on weird values.
---
 proposals/324-rtt-congestion-control.txt | 6 ++++++
 1 file changed, 6 insertions(+)

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

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.