diff options
| author | eunhhu <[email protected]> | 2026-09-29 15:41:03 +0100 |
|---|---|---|
| committer | eunhhu <[email protected]> | 2026-09-29 15:41:03 +0100 |
| commit | ccf35df074bcb450ebdc56eb27762a9096252a3f (patch) | |
| tree | 38a30ef8a6a05ad7548c8758a2e3b3fd01a3995a /tests/check.py | |
| parent | 5aa976a63da05874eff34dcb34380fc15f1c9afa (diff) | |
| download | pure-ccf35df074bcb450ebdc56eb27762a9096252a3f.tar.gz pure-ccf35df074bcb450ebdc56eb27762a9096252a3f.zip | |
See a path that stops carrying larger datagrams, and go back to the first size
A link that found the path carries 1,452 bytes kept sending them when a
route changed and larger packets were dropped with nothing said (a
black hole): it lost them one after another and stood still (test-link:
8 of 3,000 records in ten minutes). Now, as RFC 8899 ยง4.3 has it, it goes
back to 1,200 bytes when three larger packets in a row are lost while an
acknowledgment covers only smaller ones, or when two probes in a row go
unanswered, and tries the larger size again a second on (three tries,
then ten minutes). The case completes in 1.2 s of virtual time; the M6
simulator's results are the same to the byte in eight paths of loss,
reordering and a bottleneck.
Diffstat (limited to 'tests/check.py')
0 files changed, 0 insertions, 0 deletions
