Fwd: Re: [tcpm] FW: Call for Adoption: TCP Tuning for HTTP
Joe Touch <touch@isi.edu> Wed, 02 March 2016 22:40 UTC
Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2158E1B3341 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 2 Mar 2016 14:40:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.908
X-Spam-Level:
X-Spam-Status: No, score=-6.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.006, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id woj89ZepDpCo for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 2 Mar 2016 14:40:21 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A22B1B3346 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 2 Mar 2016 14:40:15 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1abFMd-0003ga-QZ for ietf-http-wg-dist@listhub.w3.org; Wed, 02 Mar 2016 22:35:27 +0000
Resent-Date: Wed, 02 Mar 2016 22:35:27 +0000
Resent-Message-Id: <E1abFMd-0003ga-QZ@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <touch@isi.edu>) id 1abFMY-0003fk-5e for ietf-http-wg@listhub.w3.org; Wed, 02 Mar 2016 22:35:22 +0000
Received: from vapor.isi.edu ([128.9.64.64]) by maggie.w3.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <touch@isi.edu>) id 1abFMV-0006dq-Qg for ietf-http-wg@w3.org; Wed, 02 Mar 2016 22:35:21 +0000
Received: from [128.9.184.68] ([128.9.184.68]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id u22MYfIv005024 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 2 Mar 2016 14:34:42 -0800 (PST)
Cc: touch@isi.edu
References: <56D74C23.5010705@isi.edu>
From: Joe Touch <touch@isi.edu>
To: ietf-http-wg@w3.org
X-Forwarded-Message-Id: <56D74C23.5010705@isi.edu>
Message-ID: <56D76A7E.7090507@isi.edu>
Date: Wed, 02 Mar 2016 14:34:38 -0800
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <56D74C23.5010705@isi.edu>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Received-SPF: none client-ip=128.9.64.64; envelope-from=touch@isi.edu; helo=vapor.isi.edu
X-W3C-Hub-Spam-Status: No, score=-6.4
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, W3C_NW=0.5
X-W3C-Scan-Sig: maggie.w3.org 1abFMV-0006dq-Qg 3aa169c406e76c6cf3dfdf9e61bc6e37
X-Original-To: ietf-http-wg@w3.org
Subject: Fwd: Re: [tcpm] FW: Call for Adoption: TCP Tuning for HTTP
Archived-At: <http://www.w3.org/mid/56D76A7E.7090507@isi.edu>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/31154
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
Hi, all, This doc was noted on the TCPM list. See my observations below. Joe -------- Forwarded Message -------- Subject: Re: [tcpm] FW: Call for Adoption: TCP Tuning for HTTP Date: Wed, 2 Mar 2016 12:25:07 -0800 From: Joe Touch <touch@isi.edu> To: Scharf, Michael (Nokia - DE) <michael.scharf@nokia.com>, tcpm@ietf.org Extensions <tcpm@ietf.org> CC: touch@isi.edu On 3/2/2016 1:39 AM, Scharf, Michael (Nokia - DE) wrote: > I assume this could be of interest to the TCPM community. I have doubts: - it reads like a Linux manual page All Linux-specific references and commands would need to be moved to an appendix to be useful as an RFC. - this repeats (sometimes correctly, sometimes in error) existing advice J. Heidemann, K. Obraczka, J. Touch, “Modeling the Performance of HTTP Over Several Transport Protocols,” IEEE/ACM Transactions on Networking, V5, N5, Oct. 1997, pp.616-630. T. Faber, J. Touch, and W. Yue, “The TIME-WAIT state in TCP and Its Effect on Busy Servers,” in Proc. IEEE Infocom, 1999, pp. 1573-1583. - it has significant errors TIME-WAIT issues apply to servers, not clients. Nagle has been known to perform poorly for multibyte interactive traffic for a very long time, including not only web traffic but also multi-byte character or keyboard signals. Disabling slow-start after idle is safe only with pacing. Without pacing, the resulting traffic can generate a burst that was never experienced and result in both poor performance for the current connection and potential impact to competing traffic. (those are just a few) Overall, I think a man page might be useful, but this summary isn't useful for the IETF. Joe > -----Original Message----- > From: Scharf, Michael (Nokia - DE) > Sent: Wednesday, March 02, 2016 10:37 AM > To: 'Mark Nottingham'; HTTP WG > Cc: amankin@verisign.com; Daniel Stenberg > Subject: RE: Call for Adoption: TCP Tuning for HTTP > > The document refers to several TCPM RFCs with experimental status, e.g., in Section 3. That may have to be taken into account when heading towards BCP status. > > Michael > (TCPM co-chair) > > > -----Original Message----- > From: Mark Nottingham [mailto:mnot@mnot.net] > Sent: Wednesday, March 02, 2016 6:47 AM > To: HTTP WG > Cc: amankin@verisign.com; Daniel Stenberg > Subject: Call for Adoption: TCP Tuning for HTTP > > [ copying Alison as our Transport Tech Advisor ] > > Daniel has kindly started a document about how HTTP uses TCP, both for /1 and /2: > <https://tools.ietf.org/html/draft-stenberg-httpbis-tcp> > > We haven't explicitly discussed this at a meeting, but I have heard interest in this topic from a variety of folks. > > What do people think about adopting this with a target of Best Current Practice? > > Please comment on-list. > > Regards, > > -- > Mark Nottingham https://www.mnot.net/ > > > _______________________________________________ > tcpm mailing list > tcpm@ietf.org > https://www.ietf.org/mailman/listinfo/tcpm >
- Call for Adoption: TCP Tuning for HTTP Mark Nottingham
- Re: Call for Adoption: TCP Tuning for HTTP Willy Tarreau
- Re: Call for Adoption: TCP Tuning for HTTP Tim Wicinski
- Re: Call for Adoption: TCP Tuning for HTTP Cory Benfield
- Re: Call for Adoption: TCP Tuning for HTTP Thomas Mangin
- Re: Fwd: Re: [tcpm] FW: Call for Adoption: TCP Tu… Willy Tarreau
- Re: Call for Adoption: TCP Tuning for HTTP Scharf, Michael (Nokia - DE)
- Fwd: Re: [tcpm] FW: Call for Adoption: TCP Tuning… Joe Touch
- Re: Fwd: Re: [tcpm] FW: Call for Adoption: TCP Tu… Joe Touch
- Re: Fwd: Re: [tcpm] FW: Call for Adoption: TCP Tu… Willy Tarreau
- Re: Fwd: Re: [tcpm] FW: Call for Adoption: TCP Tu… Joe Touch
- Re: Fwd: Re: [tcpm] FW: Call for Adoption: TCP Tu… Willy Tarreau
- Re: Fwd: Re: [tcpm] FW: Call for Adoption: TCP Tu… Joe Touch
- Re: Fwd: Re: [tcpm] FW: Call for Adoption: TCP Tu… Joe Touch
- Re: Fwd: Re: [tcpm] FW: Call for Adoption: TCP Tu… Patrick McManus
- Re: Fwd: Re: [tcpm] FW: Call for Adoption: TCP Tu… Willy Tarreau
- Re: Fwd: Re: [tcpm] FW: Call for Adoption: TCP Tu… Willy Tarreau
- Re: Fwd: Re: [tcpm] FW: Call for Adoption: TCP Tu… Joe Touch
- Re: Fwd: Re: [tcpm] FW: Call for Adoption: TCP Tu… Willy Tarreau
- Re: Fwd: Re: [tcpm] FW: Call for Adoption: TCP Tu… Joe Touch
- Re: Fwd: Re: [tcpm] FW: Call for Adoption: TCP Tu… Patrick McManus
- Re: Fwd: Re: [tcpm] FW: Call for Adoption: TCP Tu… Willy Tarreau
- Re: [tcpm] Call for Adoption: TCP Tuning for HTTP Mark Nottingham
- Re: [tcpm] Call for Adoption: TCP Tuning for HTTP Tim Wicinski
- Re: [tcpm] Call for Adoption: TCP Tuning for HTTP Willy Tarreau
- [Reposted to list] Re: Fwd: Re: [tcpm] FW: Call f… Kari Hurtta
- Re: [tcpm] Call for Adoption: TCP Tuning for HTTP Ben Niven-Jenkins
- Re: Fwd: Re: [tcpm] FW: Call for Adoption: TCP Tu… Yoshifumi Nishida
- Re: [tcpm] Call for Adoption: TCP Tuning for HTTP Willy Tarreau
- Re: Fwd: Re: [tcpm] FW: Call for Adoption: TCP Tu… Willy Tarreau
- Re: Fwd: Re: [tcpm] FW: Call for Adoption: TCP Tu… Yoshifumi Nishida
- RE: Call for Adoption: TCP Tuning for HTTP Salvatore Loreto
- RE: Call for Adoption: TCP Tuning for HTTP Daniel Stenberg
- Re: Call for Adoption: TCP Tuning for HTTP Leif Hedstrom
- Re: Call for Adoption: TCP Tuning for HTTP Amos Jeffries
- Re: Fwd: Re: [tcpm] FW: Call for Adoption: TCP Tu… Willy Tarreau
- Re: Call for Adoption: TCP Tuning for HTTP Leif Hedstrom
- Re: Call for Adoption: TCP Tuning for HTTP Joe Touch
- Re: Call for Adoption: TCP Tuning for HTTP Matthew Kerwin
- RE: Call for Adoption: TCP Tuning for HTTP Daniel Stenberg
- RE: Call for Adoption: TCP Tuning for HTTP Daniel Stenberg