Re: [tcpm] TCP Tuning for HTTP - update
Mark Nottingham <mnot@mnot.net> Wed, 17 August 2016 04:43 UTC
Return-Path: <mnot@mnot.net>
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 486F012B057 for <tcpm@ietfa.amsl.com>; Tue, 16 Aug 2016 21:43:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level:
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-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 NIM3IgQdgjO2 for <tcpm@ietfa.amsl.com>; Tue, 16 Aug 2016 21:43:26 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (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 01F7612B040 for <tcpm@ietf.org>; Tue, 16 Aug 2016 21:43:25 -0700 (PDT)
Received: from [192.168.3.100] (unknown [124.189.98.244]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 0756122E1F3; Wed, 17 Aug 2016 00:43:18 -0400 (EDT)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <7fa95741-ac58-3183-1b92-238bd4b4dae6@isi.edu>
Date: Wed, 17 Aug 2016 14:43:15 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <5CD67877-19E3-4E79-BBF2-3E270343A378@mnot.net>
References: <0CC24FC1-37E1-4125-9627-05726A9D9406@mnot.net> <7fa95741-ac58-3183-1b92-238bd4b4dae6@isi.edu>
To: Joe Touch <touch@isi.edu>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/o0AFGHANOG7CqzyeY_rewjNj-YQ>
Cc: tcpm@ietf.org, HTTP Working Group <ietf-http-wg@w3.org>, Daniel Stenberg <daniel@haxx.se>, Patrick McManus <pmcmanus@mozilla.com>
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 04:43:28 -0000
Joe, > On 17 Aug 2016, at 2:21 PM, Joe Touch <touch@isi.edu> wrote: > > Hi, Mark, et al., > > I posted a review of this document to both to TCPM and HTTP WGs. > > This update fails to address the issues I raised - notably that many of > the issues therein are known *and published*. I'm assuming you're talking about <https://lists.w3.org/Archives/Public/ietf-http-wg/2016JanMar/0314.html>. > So first, can we discuss the issue of PLAGIARISM? Sure, let's discuss it. That's a very serious accusation. Are you saying that your material has been intentionally used without proper acknowledgement? Personally, I doubt that. What may have happened is that the text brushes up against things that you've written about in the past, and you feel that you're not adequately acknowledged. 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. On the other hand, if it turns out that directing readers toward other documents (including yours) adds value, a reference might make sense. > Not only of two of my works, but of many others that pointed out most of > the information summarized in this doc. > > Second, the step of "adoption" needs to wait until there's something new > here that wasn't known 20 years ago and the issue of plagiarism is > addressed. Other people in the HTTP *and* TCP communities have commented that such a document would be very useful, whether or not it's something "new that wasn't known 20 years ago". Cheers, > > Joe > > On 8/16/2016 7:02 PM, Mark Nottingham wrote: >> 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 > > <Attached Message.eml><Attached Message.eml> -- Mark Nottingham https://www.mnot.net/
- Re: [tcpm] TCP Tuning for HTTP - update Jana Iyengar
- 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 SALLANTIN Renaud
- Re: [tcpm] TCP Tuning for HTTP - update Kuhn Nicolas
- Re: [tcpm] TCP Tuning for HTTP - update Gorry Fairhurst
- 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 Yuchung Cheng
- Re: [tcpm] TCP Tuning for HTTP - update Gorry Fairhurst
- 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 Adrien de Croy
- 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 Scharf, Michael (Nokia - DE)
- 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 Joe Touch
- Re: [tcpm] TCP Tuning for HTTP - update Mark Nottingham
- [tcpm] TCP Tuning for HTTP - update Mark Nottingham