Re: [tcpm] TCP Tuning for HTTP - update
Tim Wicinski <tjw.ietf@gmail.com> Wed, 17 August 2016 17:05 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC0BC12DBF1 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 17 Aug 2016 10:05:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.268
X-Spam-Level:
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: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 2RrwbUjVpVuJ for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 17 Aug 2016 10:05:22 -0700 (PDT)
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 A4A8712DBD6 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 17 Aug 2016 10:05:22 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1ba4Cs-0001hC-Gt for ietf-http-wg-dist@listhub.w3.org; Wed, 17 Aug 2016 17:00:46 +0000
Resent-Date: Wed, 17 Aug 2016 17:00:46 +0000
Resent-Message-Id: <E1ba4Cs-0001hC-Gt@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 <tjw.ietf@gmail.com>) id 1ba4Cm-0001gD-64 for ietf-http-wg@listhub.w3.org; Wed, 17 Aug 2016 17:00:40 +0000
Received: from mail-qt0-f195.google.com ([209.85.216.195]) by maggie.w3.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <tjw.ietf@gmail.com>) id 1ba4Ck-00035P-Je for ietf-http-wg@w3.org; Wed, 17 Aug 2016 17:00:39 +0000
Received: by mail-qt0-f195.google.com with SMTP id c52so5750290qte.1 for <ietf-http-wg@w3.org>; Wed, 17 Aug 2016 10:00:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=VlUDqdozY179jb4qlqjHyCuh5A4ucchuua6SlhqRImM=; b=DmR1rXnwqZXM/OgDYjvspu5DI8PZ1GTn+5+69V9fMR0ZAEfCLiksK+XeDwOZSIjYIw ZCaS2N3qKxJFXYwPaErktF2LYy2vLf8IeFwiWdcLu1cTV4Ayp+DiA23HECWEbJpye6is LLr/r09ALQjNMIVdiaTUvo3CO8O8u63PHx5S3wy0tU783Rw2Gb9YYl3U1I8UcRSrovlK L5c7VW/u17to1205kNn3l6vZ4mjbhxxuwXpOLUgcqBjvG+iEX/OtiYskLnBTsnSq++QQ mKL0qE6ZswhqDEnQvuTgyv8VVyyjb7w/Ees68kUbDuxbPIUUXsDVC++HZQ5Wh8z6TjbB NHqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=VlUDqdozY179jb4qlqjHyCuh5A4ucchuua6SlhqRImM=; b=cGWJvhk5WRSoAwrFeFhKXR63FIpD9yRI0q8O9edUkvI6lWrlVCNqYKE71x8ZslnKBs D6em+vTVALqCl2L/LFCbCJ03ZUkydfb1cLQneSLIdxytnMFdNc6tWkm2dp5xEGTEI9C1 dV1uODc8z5FYflC/uHAIGlLbhcVaGboKMkpVW2D2wmV57nTbRD3Eo+VWFuXcdGutAMM1 plapM35K3TU0fNmPQuhMw9KemFg3yAStHBPqHvG95Til05hgZA1oeI6IJf/IPMuYCsus g/S5sq1mz//ocnhk0RCUbiT48STNiy8sTBtFby2vaEghDA1KdSnqmRWyOTIEwkTFbFPO rmYw==
X-Gm-Message-State: AEkooutqMiEOymXr2Z0zBYcBn4l9LMzIBpGIlXlPZ1a2G2SGRAugoFZtsRNwZdWaKs7z2w==
X-Received: by 10.200.54.185 with SMTP id a54mr46301673qtc.63.1471453212363; Wed, 17 Aug 2016 10:00:12 -0700 (PDT)
Received: from twicinski-ltm.internal.salesforce.com ([204.14.236.152]) by smtp.googlemail.com with ESMTPSA id p26sm16957153qkh.28.2016.08.17.10.00.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 17 Aug 2016 10:00:11 -0700 (PDT)
To: Eliot Lear <lear@cisco.com>, Alexey Melnikov <alexey.melnikov@isode.com>, Joe Touch <touch@isi.edu>, Mark Nottingham <mnot@mnot.net>
References: <0CC24FC1-37E1-4125-9627-05726A9D9406@mnot.net> <7fa95741-ac58-3183-1b92-238bd4b4dae6@isi.edu> <5CD67877-19E3-4E79-BBF2-3E270343A378@mnot.net> <2197232f-10d7-28cb-fcc9-05bd495e3c22@isi.edu> <87D56B16-B091-4E9C-9B88-D136ED4BC819@mnot.net> <b1fe8ceb-c48c-8d89-1026-1fbed8d31d62@isi.edu> <2f276fc8-45d9-50e3-08bf-d712bc94302d@isode.com> <ebb0ae0e-8590-b02e-b8c8-1caa4f1435a0@cisco.com>
Cc: tcpm@ietf.org, HTTP Working Group <ietf-http-wg@w3.org>, Daniel Stenberg <daniel@haxx.se>, Patrick McManus <pmcmanus@mozilla.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Message-ID: <23743483-d4aa-9800-eda8-84edb4bf9053@gmail.com>
Date: Wed, 17 Aug 2016 13:00:12 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <ebb0ae0e-8590-b02e-b8c8-1caa4f1435a0@cisco.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass client-ip=209.85.216.195; envelope-from=tjw.ietf@gmail.com; helo=mail-qt0-f195.google.com
X-W3C-Hub-Spam-Status: No, score=-4.7
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: maggie.w3.org 1ba4Ck-00035P-Je 283f147287896b98aca67528cb27a82d
X-Original-To: ietf-http-wg@w3.org
Subject: Re: [tcpm] TCP Tuning for HTTP - update
Archived-At: <http://www.w3.org/mid/23743483-d4aa-9800-eda8-84edb4bf9053@gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/32286
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>
That sounds like a fine idea. I'll be glad to go through those. tim On 8/17/16 12:26 PM, Eliot Lear wrote: > Perhaps we can agree that the reasonable course of action here is for > Joe to (re)-recommend a compact set of citations to the authors, perhaps > even in some easily consumable form to them (kramdown-2629 or XML)? > > Eliot > > > On 8/17/16 5:28 PM, Alexey Melnikov wrote: >> Joe, >> >> 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 <touch@isi.edu> wrote: >>>>> >> [snip] >>>>>> 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. >> Noted. >> >> >> > > > > > _______________________________________________ > tcpm mailing list > tcpm@ietf.org > https://www.ietf.org/mailman/listinfo/tcpm >
- Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
- Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
- Re: [tcpm] TCP Tuning for HTTP - update Eliot Lear
- Re: [tcpm] TCP Tuning for HTTP - update Willy Tarreau
- Re: [tcpm] TCP Tuning for HTTP - update Jeremy Harris
- Re: [tcpm] TCP Tuning for HTTP - update Mark Nottingham
- Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
- Re: [tcpm] TCP Tuning for HTTP - update Willy Tarreau
- Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
- Re: [tcpm] TCP Tuning for HTTP - update Willy Tarreau
- Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
- Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
- Re: [tcpm] TCP Tuning for HTTP - update Willy Tarreau
- Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
- Re: [tcpm] TCP Tuning for HTTP - update Mark Nottingham
- Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
- Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
- Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
- Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
- Re: [tcpm] TCP Tuning for HTTP - update Mark Nottingham
- Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
- Re: [tcpm] TCP Tuning for HTTP - update Matthew Kerwin
- Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
- Re: [tcpm] TCP Tuning for HTTP - update Adrien de Croy
- Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
- Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
- Re: [tcpm] TCP Tuning for HTTP - update Adrien de Croy
- Re: [tcpm] TCP Tuning for HTTP - update Willy Tarreau
- Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
- Re: [tcpm] TCP Tuning for HTTP - update Willy Tarreau
- Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
- Re: [tcpm] TCP Tuning for HTTP - update Tim Wicinski
- Re: [tcpm] TCP Tuning for HTTP - update Eliot Lear
- Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
- Re: [tcpm] TCP Tuning for HTTP - update Alexey Melnikov
- Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
- Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
- Re: [tcpm] TCP Tuning for HTTP - update Willy Tarreau
- Re: [tcpm] TCP Tuning for HTTP - update Mark Nottingham
- Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
- Re: [tcpm] TCP Tuning for HTTP - update Mark Nottingham
- Re: [tcpm] TCP Tuning for HTTP - update Joe Touch
- Re: [tcpm] TCP Tuning for HTTP - update Jana Iyengar