Re: [tcpm] TCP Tuning for HTTP - update

"Scharf, Michael (Nokia - DE)" <michael.scharf@nokia.com> Wed, 17 August 2016 18:44 UTC

Return-Path: <michael.scharf@nokia.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66F4812D1A6 for <tcpm@ietfa.amsl.com>; Wed, 17 Aug 2016 11:44:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level:
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 RyNB7gCvbfqT for <tcpm@ietfa.amsl.com>; Wed, 17 Aug 2016 11:44:38 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (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 4404212B014 for <tcpm@ietf.org>; Wed, 17 Aug 2016 11:44:38 -0700 (PDT)
Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id AD3F988F1E10E; Wed, 17 Aug 2016 18:44:32 +0000 (GMT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (fr712usmtp2.zeu.alcatel-lucent.com [135.239.2.42]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u7HIiZHw031411 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 17 Aug 2016 18:44:35 GMT
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id u7HIiXUm010620 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 17 Aug 2016 20:44:34 +0200
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.108]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.03.0195.001; Wed, 17 Aug 2016 20:44:33 +0200
From: "Scharf, Michael (Nokia - DE)" <michael.scharf@nokia.com>
To: Mark Nottingham <mnot@mnot.net>, "tcpm@ietf.org" <tcpm@ietf.org>
Thread-Topic: [tcpm] TCP Tuning for HTTP - update
Thread-Index: AQHR+CudIob/6hMO6kqGYKe7IdcfpKBNdUvA
Date: Wed, 17 Aug 2016 18:44:33 +0000
Message-ID: <655C07320163294895BBADA28372AF5D489E64AF@FR712WXCHMBA15.zeu.alcatel-lucent.com>
References: <0CC24FC1-37E1-4125-9627-05726A9D9406@mnot.net>
In-Reply-To: <0CC24FC1-37E1-4125-9627-05726A9D9406@mnot.net>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/443xfJEVL5jk19T2rV18Gj_iSKc>
Cc: Patrick McManus <pmcmanus@mozilla.com>, Daniel Stenberg <daniel@haxx.se>
Subject: Re: [tcpm] TCP Tuning for HTTP - update
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.17
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, 17 Aug 2016 18:44:40 -0000

Speaking as individual contributor...

* I support an *informational* document in httpbis under the constraint that the document is finally also last called in tcpm. However, I have some doubts that this document has to be a BCP. Apart from the formal aspects that a BCP would have to be carefully reviewed regarding consistency with TCPM documents, I also believe that some of the content can easily get outdated as TCP and operating systems evolve, so "current" seems relative. See below for one example for how fast TCP and its implementations can evolve.

* There is a related discussion on a document currently discussed in LWIP draft-gomez-core-tcp-constrained-node-networks, which focuses quite on the opposite type of TCP deployment. I believe the IETF should handle both documents consistently (but this is a topic for our ADs). In case of LWIP, the current AD guidance is to have a brief readouts in TCPM from time to time (maybe every second meeting or so). Given that a lot if TCP implementers follow TCPM, I believe such a readout would be a good opportunity to get feedback.

* I believe TCP is not only implemented on a single operating system only ;-) I'd actually be interested in the roadmap for adding a more comprehensive coverage of TCP stacks, if stack-specific recommendations should be included e.g. in the appendix. I do not object to OS-specific examples in general. To me this seems doable in an informational document.

* I suggest to reference RFC 7414 for a more complete overview of TCP features 

* There has recently been quite a bit of TCPM discussion on RACK, which is still under design but if the document wants to cover TLP it may be reasonable to consider RACK. Some context can be found e.g. in https://www.ietf.org/proceedings/96/slides/slides-96-tcpm-3.pdf and https://www.ietf.org/proceedings/96/slides/slides-96-tcpm-4.pdf . Others may know more than me.

* I offer to more review the technical content once the document has matured a bit; right now I still see quite a bit of work to be completed

Michael




-----Original Message-----
From: tcpm [mailto:tcpm-bounces@ietf.org] On Behalf Of Mark Nottingham
Sent: Wednesday, August 17, 2016 4:03 AM
To: tcpm@ietf.org
Cc: Patrick McManus; Daniel Stenberg
Subject: [tcpm] TCP Tuning for HTTP - update

Hi TCPM,

Just a quick note; Daniel and Tim have made an update to the TCP Tuning for HTTP draft:
  https://tools.ietf.org/html/draft-stenberg-httpbis-tcp

We've had a Call for Adoption open for this draft for a while, and will likely adopt it soon. However, we'd like to get feedback from this community first -- both about the latest version of the input document, and to see if there's interest in helping out.

You can give feedback on the HTTP WG mailing list <https://lists.w3.org/Archives/Public/ietf-http-wg/>, or  by responding to this e-mail (Please leave the CC line; Patrick and I will try to summarise the feedback to the WG).

Cheers,

--
Mark Nottingham   https://www.mnot.net/




_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm