aboutsummaryrefslogtreecommitdiffstats
path: root/link/crypto.c
diff options
context:
space:
mode:
authoreunhhu <[email protected]>2026-09-29 13:55:09 +0100
committereunhhu <[email protected]>2026-09-29 13:55:09 +0100
commit315c1f970c2ae482bceec2a9cc8666e6cb380a81 (patch)
tree69401194de07e72049929793af76127c64fa65d6 /link/crypto.c
parent19ebac6e3cd5e48e16a73c78342fa676dc905db9 (diff)
downloadpure-315c1f970c2ae482bceec2a9cc8666e6cb380a81.tar.gz
pure-315c1f970c2ae482bceec2a9cc8666e6cb380a81.zip
Send no packet only to probe the path or say a challenge back
M2 (ten thousand devices, a record each every 5 s) sent 118k packets for 80k records. A link whose packets were never full still probed for a 1,452-byte path: nothing larger would have been carried. And a sender said a receiver's challenge back in a packet of its own, one for each device each time the receiver started. Now a link probes once a packet of its was full, and a challenge rides in the next packet that goes (records, or a probe). Until then the receiver's answers there are at most three times what came, which the answers to one packet are not; when they are held back, the sender's probe or record sent again says it back. M2 sends 80,036 again (docs/research/099-link-epochs.md).
Diffstat (limited to 'link/crypto.c')
0 files changed, 0 insertions, 0 deletions