netdev - Re: rtt metric only for incoming connections?

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: <483C58B2.8080100@hp.com>
Date:	Tue, 27 May 2008 11:53:38 -0700
From:	Rick Jones <rick.jones2@...com>
To:	Stephen Hemminger <stephen.hemminger@...tta.com>
CC:	Stephane Chazelas <Stephane_Chazelas@...oo.fr>,
	Stephen Hemminger <shemminger@...tta.com>,
	David Miller <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: rtt metric only for incoming connections?

>>Also, it seems we can't lower the initial RTO below the RFC 1122
>>default of 3 seconds. 3 seconds may be appropriate for a host
>>for which we don't know how many hops, links, satellites are
>>needed to reach it, but what about local/corporate networks
>>where it's possible to administratively know the rtt so that it
>>can be hardcoded in the routing table.
> 
> 
> Violating RFC's is not really that useful. 

Yet the RFC's are not stone tablets, and they often represent a 
"compromise" between things desirable for the great big internet and 
those someone with a bounded network might have.

> If you have a network dropping SYN packets regularly than there are
> worse problems.

That is entirely plausible.

> Relying on TCP to overcome wireless network problems is not
> a good idea.

How is it any worse than relying on TCP to overcome network congestion 
problems?-)

rick jones
--
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