140's 10, RFC 6298's retransmission timer, written in aup with no new opcode (aup's examples/rto.aup, the timer a deadline in the state seen at each periodic tick): 20 scenarios (10 seeds, ticks every 10 and 100 ms; a closed loop: first sendings lost one in five, the receiver acknowledging cumulatively) and their 241,612 events right against rto.py, the model of the same rules (no known implementation takes given events), on the three paths, the paths the same; module_specs in make check: one scenario at both periods (tests/specs/rto, 2,297 events); bars: one workaround (the periodic tick: 2,795.8 ticks a timeout at 10 ms, 281.6 at 100, seen 4.27 and 49.23 ms late on average; ticks 93% and 57% of the counted work), 56 lines against Python's 30, three frictions (an input's period not readable, no abs, send a keyword); the one-shot timer's shape as a decision point, one spec needing it: noted, not made; the suite table's row 10

1 files changed, 7 insertions, 0 deletions

diff --git a/tests/specs/rto/README.md b/tests/specs/rto/README.md
new file mode 100644
index 0000000..e090586
--- /dev/null
+++ b/tests/specs/rto/README.md
@@ -0,0 +1,7 @@
+# RFC 6298's retransmission timer: two scenarios
+
+`scenarios.json` holds one scenario (seed 2, 20 segments, five timeouts) of `research/experiments/044-specs/rto_check.py`
+at tick periods of 10 and 100 ms: the events an app is given (time in ms, kind, segment) and, after each, the state the
+model of the same rules (`rto.py`) has (SRTT, RTTVAR, RTO, deadline, segments outstanding, retransmissions).
+`tests/check.py`'s `module_specs` gives the events to aup's `examples/rto.aup` (its tick and G made the period's) on
+Pure's three paths.