netdev - A TLP implementation question

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180214002751.GF28312@strugglingcoder.info>
Date:   Tue, 13 Feb 2018 16:27:51 -0800
From:   hiren panchasara <hiren@...ugglingcoder.info>
To:     netdev@...r.kernel.org
Subject: A TLP implementation question

Looking at current net-next to understand an aspect of TLP (tail loss
probe) implementation.

https://tools.ietf.org/html/draft-ietf-tcpm-rack-02 is the source of
truth now for TLP and 6.2.1.  Phase 1: Scheduling a loss probe
Step 1: Check conditions for scheduling a PTO. has following as one of
the conditions:
(d) The most recently transmitted data was not itself a TLP probe
(i.e. a sender MUST NOT send consecutive TLP probes)

I would appreciate if someone can help me trace how current code is
trying to enforce this requirement. How does it check/track that the
last (re)transmitted packet was a tlp probe.

Thanks in advance,
Hiren

Content of type "application/pgp-signature" skipped