W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2016

Re: Fwd: Re: [tcpm] FW: Call for Adoption: TCP Tuning for HTTP

From: Joe Touch <touch@isi.edu>
Date: Thu, 3 Mar 2016 12:18:21 -0800
To: Willy Tarreau <w@1wt.eu>
Cc: touch@isi.edu, ietf-http-wg@w3.org
Message-ID: <56D89C0D.6030601@isi.edu>

On 3/3/2016 11:15 AM, Joe Touch wrote:
>>>> A TIME_WAIT on the client is not recyclable. That's why
>>>> TIME_WAIT is a problem for the client and not for the server.
>>> See above; TW is *never* recyclable.
>> Yes it definitely is on the server side, which is the point. When you
>> receive a SYN whose ISN is higher than the end of the current window,
>> it's a new one by definition (as indicated in RFC1122).
> RFC1122's statement on TIME-WAIT has nothing to do with the ISN the
> server receives; it has to do with the ISN the server assigns. You don't
> "recycle" the TIME-WAIT; you effectively reopen the connection with the
> same port pair. But that then requires keeping more state in the TW.

And while we're at it, this rule is nearly completely defeated if ISNs
are randomized or treated as a single resource throughout a machine
(rather than being specific to a socket pair).

Received on Thursday, 3 March 2016 20:19:57 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 22 March 2016 12:47:11 UTC