netdev - Re: [PATCH 2.6.22] TCP: Make TCP_RTO

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 for Android: free password hash cracker in your pocket

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

Message-ID: <46D4419B.50204@psc.edu>
Date:	Tue, 28 Aug 2007 11:39:07 -0400
From:	John Heffner <jheffner@....edu>
To:	OBATA Noboru <noboru.obata.ar@...achi.com>
CC:	davem@...emloft.net, shemminger@...ux-foundation.org,
	yoshfuji@...ux-ipv6.org, netdev@...r.kernel.org
Subject: Re: [PATCH 2.6.22] TCP: Make TCP_RTO_MAX a variable (take 2)

OBATA Noboru wrote:
> Is it correct that you think my problem can be addressed either
> by the followings?
> 
> (1) Make the application timeouts longer.  (Steve has shown that
>     making an application timeouts twice the failover detection
>     timeout would be a solution.)

Right.  Is there something wrong with this approach?

> (2) Let TCP have a notification of some kind.

There was some work on this in the IETF a while back (google trigtran 
linkup), but it never went anywhere to my knowledge.  In principle it's 
possible, but it's not clear that it's worth doing.  It's really just an 
optimization anyway.  Imaging the link that's failing over is one hop or 
more away from the endpoint.  You're back to the same problem again.

   -John
-
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