Re: [tcpm] TCP Tuning for HTTP - update

Alexey Melnikov <> Wed, 17 August 2016 15:34 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5328A12D567 for <>; Wed, 17 Aug 2016 08:34:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.268
X-Spam-Status: No, score=-8.268 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.247, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id sItjDEMmMOWU for <>; Wed, 17 Aug 2016 08:34:15 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0B0FA12D1CA for <>; Wed, 17 Aug 2016 08:34:15 -0700 (PDT)
Received: from lists by with local (Exim 4.80) (envelope-from <>) id 1ba2mj-0007pR-A5 for; Wed, 17 Aug 2016 15:29:41 +0000
Resent-Date: Wed, 17 Aug 2016 15:29:41 +0000
Resent-Message-Id: <>
Received: from ([]) by with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <>) id 1ba2md-0007o7-Rm for; Wed, 17 Aug 2016 15:29:35 +0000
Received: from ([]) by with esmtp (Exim 4.80) (envelope-from <>) id 1ba2mZ-0007Sc-Jn for; Wed, 17 Aug 2016 15:29:34 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1471447745;; s=june2016;; bh=CWf1klbjaRPeCp7NuHMfSMOeiR0RZrj7+m8IslesOw4=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=r4r66WkJEqI5rkt3AEspT2hLg2LzqUaAGPrbOWvNKZceeHmCdkov9IfHp/P2R4XgUgC9Lz TeUWpP5Vu8ykh+JcXlEIzqR4fVWoHpXOYGVw8B6jFR0nJrjGe5pKBo9jZ9zt30YvbiIaTK gf07M774BQUGcs9tVtmP8g2boJeP/tk=;
Received: from [] ( []) by (submission channel) via TCP with ESMTPSA id <>; Wed, 17 Aug 2016 16:29:05 +0100
To: Joe Touch <>, Mark Nottingham <>
References: <> <> <> <> <> <>
Cc:, HTTP Working Group <>, Patrick McManus <>, Daniel Stenberg <>
From: Alexey Melnikov <>
Message-ID: <>
Date: Wed, 17 Aug 2016 16:28:45 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
In-Reply-To: <>
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass client-ip=;;
X-W3C-Hub-Spam-Status: No, score=-4.9
X-W3C-Hub-Spam-Report: AWL=0.650, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: 1ba2mZ-0007Sc-Jn 00346203ebb1e792c39514d573e4db77
Subject: Re: [tcpm] TCP Tuning for HTTP - update
Archived-At: <>
X-Mailing-List: <> archive/latest/32283
Precedence: list
List-Id: <>
List-Help: <>
List-Post: <>
List-Unsubscribe: <>


On 17/08/2016 16:08, Joe Touch wrote:
> On 8/16/2016 11:42 PM, Mark Nottingham wrote:
>>> On 17 Aug 2016, at 3:23 PM, Joe Touch <> wrote:
>>>> If that's the case, I'd observe that the IETF isn't an academic publisher, and acknowledging all prior work in an area is neither practical, nor required, nor current practice.
>>> Plagiarism isn't an issue limited to academic environments. Publication
>>> of a document on the web is still publication.
>> Sure. It also isn't a legal issue in this form (unless you're asserting copyright?). Effectively, it's a cultural norm. Again, I will point out that in the culture of the IETF, we historically have not cited the complete provenance of every idea, both because it's impractical and because it doesn't benefit the reader.
> Although that's true in the smallest cases, the IETF does have two
> concepts that support this norm: an author list and a set of references.
> Can you explain how it helps the reader to not cite two documents that
> are both squarely in the same area as this doc (interaction between HTTP
> and TCP and the impact of running many small connections closed at the
> client as for HTTP)?
Instead of starting your discussion with words like "plagiarism", you 
could have just asked for information to be clarified and a 
citation/acknowledgement added? With your current introduction you 
pissed off lots of people.
>> As far as I know, the IETF does not have a stated position about what you regard as PLAGIARISM. Hopefully we can get some clarity about that from the ADs, as well as some definitive evidence of what you're asserting.
> You can if you want, but my primary point here is to have this work
> corrected - and to stop the myth that "it doesn't matter" whether
> *reasonable* citations are included.