enable TCP timestamps on outgoing ORcon
Make use of TCP timestamps, enable it via socks options on outgoing connections. Defined in RFC 1323. Tor could benefit from some better TCP congestion flow control? The Client or relay does not know what TCP congestion algorithm the other peer may use.
TCP timestamps are enabled by default In Linux kernel.
It was once disabled in some distros, because the bad implementation of timestamp start time was your system uptime and this fingerprinting could leak your uptime on every connection. This was fixed 2 decades ago. So why not use it now for all and not only some? All Tor Connection should look most identical for fingerprinting reasons.
Why not use it? Worst thing to happen is, that it could add 8 extra bytes of TCP header in total.
What is the expected behavior?
TCP connections should be always enabling timestamps, to make fingerprinting harder.