[tcpm] FW: Call for Adoption: TCP Tuning for HTTP
"Scharf, Michael (Nokia - DE)" <michael.scharf@nokia.com> Wed, 02 March 2016 09:39 UTC
Return-Path: <michael.scharf@nokia.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B266E1AC3F2 for <tcpm@ietfa.amsl.com>; Wed, 2 Mar 2016 01:39:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 OCErOG76Ua8b for <tcpm@ietfa.amsl.com>; Wed, 2 Mar 2016 01:39:51 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpgre-esg-02.alcatel-lucent.com [135.245.210.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F34A1AC3F4 for <tcpm@ietf.org>; Wed, 2 Mar 2016 01:39:50 -0800 (PST)
Received: from fr711umx2.dmz.alcatel-lucent.com (unknown [135.245.210.39]) by Websense Email Security Gateway with ESMTPS id B2E4A25E2AA90 for <tcpm@ietf.org>; Wed, 2 Mar 2016 09:39:46 +0000 (GMT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (fr711usmtp1.zeu.alcatel-lucent.com [135.239.2.122]) by fr711umx2.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u229dmUa002847 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <tcpm@ietf.org>; Wed, 2 Mar 2016 09:39:48 GMT
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id u229dlY7026683 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <tcpm@ietf.org>; Wed, 2 Mar 2016 10:39:48 +0100
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.15]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.03.0195.001; Wed, 2 Mar 2016 10:39:48 +0100
From: "Scharf, Michael (Nokia - DE)" <michael.scharf@nokia.com>
To: "tcpm@ietf.org Extensions" <tcpm@ietf.org>
Thread-Topic: Call for Adoption: TCP Tuning for HTTP
Thread-Index: AQHRdEeh16Gz+pebXEm4eXrhOLtjJZ9F4wxAgAADIxA=
Date: Wed, 02 Mar 2016 09:39:47 +0000
Message-ID: <655C07320163294895BBADA28372AF5D486E00B7@FR712WXCHMBA15.zeu.alcatel-lucent.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.41]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tcpm/_gWnJQ-2wV_Lal7xy9pkO95cPUE>
Subject: [tcpm] FW: Call for Adoption: TCP Tuning for HTTP
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2016 09:39:53 -0000
I assume this could be of interest to the TCPM community. Michael -----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] FW: Call for Adoption: TCP Tuning for HTTP Scharf, Michael (Nokia - DE)
- Re: [tcpm] FW: Call for Adoption: TCP Tuning for … gorry
- Re: [tcpm] FW: Call for Adoption: TCP Tuning for … Joe Touch
- Re: [tcpm] FW: Call for Adoption: TCP Tuning for … Scharf, Michael (Nokia - DE)