netdev - Re: [PATCH] RFC2988bis + taking RTT sample from 3WHS for the passive open side

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]

Date:	Wed, 08 Jun 2011 16:57:50 -0700
From:	Rick Jones <rick.jones2@...com>
To:	David Miller <davem@...emloft.net>
Cc:	eric.dumazet@...il.com, hkchu@...gle.com, hagen@...u.net,
	tsunanet@...il.com, netdev@...r.kernel.org
Subject: Re: [PATCH] RFC2988bis + taking RTT sample from 3WHS for the
 passive open side

On Wed, 2011-06-08 at 16:44 -0700, David Miller wrote:
> From: Eric Dumazet <eric.dumazet@...il.com>
> Date: Thu, 09 Jun 2011 01:39:21 +0200
> 
> > Le mercredi 08 juin 2011 à 15:26 -0700, Jerry Chu a écrit :
> >> It just occurred to me now that initRTO is being reduced, both TCP_SYN_RETRIES
> >> and TCP_SYNACK_RETRIES should be bumped up a bit, to e.g., 7 (?) to meet the
> >> 3 minutes R2 requirement per RFC1122.
> >> 
> >> If you agree, I will submit another patch.
> > 
> > Good catch, but no RFC lowered yet this 3 minutes requirement ?
> 
> I host my email on other planets, please do not break this.

As the RTT to Mars is a minimum of 500 seconds and a maximum of 2500,
and a minimum of 276 seconds for Venus, your software must already be
successfully dealing with TCP connection timeouts less than the RTT to
the planets nearest to Earth, so there should be no need to maintain 3
minutes anyway :)

rick jones
http://c2.com/cgi/wiki?LightSpeedLag
http://ase.tufts.edu/cosmos/print_chapter.asp?id=1

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