netdev - Re: [PATCH] make _minimum_ TCP retransmission timeout configurable

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-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070829.152059.48818008.davem@davemloft.net>
Date:	Wed, 29 Aug 2007 15:20:59 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	rick.jones2@...com
Cc:	ian.mcdonald@...di.co.nz, netdev@...r.kernel.org
Subject: Re: [PATCH] make _minimum_ TCP retransmission timeout configurable

From: Rick Jones <rick.jones2@...com>
Date: Wed, 29 Aug 2007 15:09:58 -0700

> If nothing else, 200 ms is a "principle of least surprise" thing since 
> that is the current value (in MS) for TCP_RTO_MIN.

And Solaris and MacOS-X and...

In fact this is a great example why we don't treat RFCs as dictations
from the gods.  They are often wrong, impractical, or full of fatal
flaws.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html