Nils Andreas Svee cab1fd1aab docs: scope server kernel-timestamp claim to this crate's server ...

irtt-client can talk to any IRTT-compatible peer, not only this
repo's own irtt-server, and has no way to know what clock source
produced a peer-reported wall-clock endpoint. Restrict the
kernel-receive-timestamp-preference claim to when the peer is
this crate's own Linux irtt-server; state plainly that another
peer's reported value is used as-is otherwise.

2026-08-20 15:18:48 +07:00

..

src

docs: scope server kernel-timestamp claim to this crate's server

2026-08-20 15:18:48 +07:00

AGENTS.md

fix(stats): clamp loss windowing timestamp to its own sent_at

2026-08-15 19:46:19 +07:00

Cargo.toml

test(client): model SessionMachine open-session operation sequences

2026-08-20 10:07:20 +07:00