Re: Encouraging a healthy HTTP/2 ecosystem
Mark Nottingham <mnot@mnot.net> Wed, 02 July 2014 10:28 UTC
Return-Path: <ietf-http-wg-request@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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07A2C1B28F4 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 2 Jul 2014 03:28:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.553
X-Spam-Level:
X-Spam-Status: No, score=-7.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, 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 xlitUNeAU2Zt for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 2 Jul 2014 03:28:43 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A508D1B28F0 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 2 Jul 2014 03:28:43 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1X2Hkx-0006Gj-8x for ietf-http-wg-dist@listhub.w3.org; Wed, 02 Jul 2014 10:27:15 +0000
Resent-Date: Wed, 02 Jul 2014 10:27:15 +0000
Resent-Message-Id: <E1X2Hkx-0006Gj-8x@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <mnot@mnot.net>) id 1X2Hkd-0006EN-7h for ietf-http-wg@listhub.w3.org; Wed, 02 Jul 2014 10:26:55 +0000
Received: from mxout-07.mxes.net ([216.86.168.182]) by lisa.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <mnot@mnot.net>) id 1X2Hkb-00084I-Ve for ietf-http-wg@w3.org; Wed, 02 Jul 2014 10:26:55 +0000
Received: from [192.168.1.68] (unknown [118.209.193.75]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 93FF722E257; Wed, 2 Jul 2014 06:26:28 -0400 (EDT)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Content-Type: text/plain; charset="windows-1252"
From: Mark Nottingham <mnot@mnot.net>
X-Priority: 3 (Normal)
In-Reply-To: <0a36eecddce77117dca7a3d0cd5c0188.squirrel@arekh.ddns.net>
Date: Wed, 02 Jul 2014 20:26:25 +1000
Cc: Poul-Henning Kamp <phk@phk.freebsd.dk>, "\"William Chan (陈智昌)\"" <willchan@chromium.org>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <864EB174-B35C-4799-95BD-166CF2797108@mnot.net>
References: <CAA4WUYgqE02o9jftm1ERJGsKBqau9CRAJ4=JF0r3x-11gh5ZXQ@mail.gmail.com> <76400.1404195794@critter.freebsd.dk> <F19D7D32-4264-423A-8B9B-F6F9036ACFEE@mnot.net> <0a36eecddce77117dca7a3d0cd5c0188.squirrel@arekh.ddns.net>
To: Nicolas Mailhot <nicolas.mailhot@laposte.net>
X-Mailer: Apple Mail (2.1878.2)
Received-SPF: pass client-ip=216.86.168.182; envelope-from=mnot@mnot.net; helo=mxout-07.mxes.net
X-W3C-Hub-Spam-Status: No, score=-3.8
X-W3C-Hub-Spam-Report: AWL=-3.064, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1X2Hkb-00084I-Ve 84965a56d7096db4bcc986b60d067c38
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Encouraging a healthy HTTP/2 ecosystem
Archived-At: <http://www.w3.org/mid/864EB174-B35C-4799-95BD-166CF2797108@mnot.net>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/25110
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>
On 2 Jul 2014, at 7:23 pm, Nicolas Mailhot <nicolas.mailhot@laposte.net> wrote: > Le Mar 1 juillet 2014 08:55, Mark Nottingham a écrit : > Mark, > >> I appreciate you're concerned about the CONTINUATION issue, but using it >> to derail other discussions isn't appropriate. > > In the defence of PHK he seems to be the only one defending the http users > at large and not the subset present here Sorry, nobody gets to wear the mantle of “I defend the users." That’s too easy. >> Also, emotive language like "bogus misfeatures" and "blackmail" doesn't >> help make decisions; it's just a distraction. Please refrain. > > Because >> In order to prevent the extension mechanism from failing (due to >> intermediaries whitelisting extensions and disallowing all others, or some >> other sort of brokenness) > > is not emotive and a distraction? Um, yeah. > Do you not understand still that websocket and other attempts to force > some classes of traffic through security equipments didn't fail because of > some technical default in those equipments, but because those equipments > were deployed to block those classes of traffic in the first place? And > that any attempt to force the issue in http2 will result in the same > outcome for this new protocol? I understand that. These arguments are perfectly valid, and indeed may carry the day (in this case particularly, since I can’t see there being any normative outcome agreed upon). What I’m not willing to tolerate is the continuing degradation of the discussion into point-scoring, personal attacks and assumptions of ill intent by one’s opposition. It has no place here. For example, you didn’t need to start that paragraph with “Do you not understand…” That’s needlessly aggressive; just make the argument without impugning my ability to understand it. BTW, the above is not a particular comment on PHK’s participation, BTW — it’s about what seems to be a growing trend in the discussion. > And BTW, in what way PHK's characterisation of >> A vendor that owned both an auto-updating client and popular website >> could enforce this. > > is not perfectly accurate? Yep. Thanks, -- Mark Nottingham http://www.mnot.net/
- Encouraging a healthy HTTP/2 ecosystem William Chan (陈智昌)
- Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
- Re: Encouraging a healthy HTTP/2 ecosystem William Chan (陈智昌)
- Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
- Re: Encouraging a healthy HTTP/2 ecosystem Mark Nottingham
- Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
- Re: Encouraging a healthy HTTP/2 ecosystem Mark Nottingham
- Re: Encouraging a healthy HTTP/2 ecosystem Cory Benfield
- Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
- Re: Encouraging a healthy HTTP/2 ecosystem Patrick McManus
- Re: Encouraging a healthy HTTP/2 ecosystem Jason Greene
- Re: Encouraging a healthy HTTP/2 ecosystem William Chan (陈智昌)
- Re: Encouraging a healthy HTTP/2 ecosystem Willy Tarreau
- Re: Encouraging a healthy HTTP/2 ecosystem Jeff Pinner
- Re: Encouraging a healthy HTTP/2 ecosystem Willy Tarreau
- Re: Encouraging a healthy HTTP/2 ecosystem Jason Greene
- Re: Encouraging a healthy HTTP/2 ecosystem Johnny Graettinger
- Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
- Re: Encouraging a healthy HTTP/2 ecosystem Willy Tarreau
- Re: Encouraging a healthy HTTP/2 ecosystem James Adjamli
- Re: Encouraging a healthy HTTP/2 ecosystem Jeff Pinner
- Re: Encouraging a healthy HTTP/2 ecosystem William Chan (陈智昌)
- Re: Encouraging a healthy HTTP/2 ecosystem Willy Tarreau
- Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
- Re: Encouraging a healthy HTTP/2 ecosystem William Chan (陈智昌)
- Re: Encouraging a healthy HTTP/2 ecosystem Willy Tarreau
- Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
- Re: Encouraging a healthy HTTP/2 ecosystem William Chan (陈智昌)
- Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
- Re: Encouraging a healthy HTTP/2 ecosystem Adrian Cole
- Re: Encouraging a healthy HTTP/2 ecosystem James M Snell
- Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
- Re: Encouraging a healthy HTTP/2 ecosystem Mike Belshe
- Re: Encouraging a healthy HTTP/2 ecosystem Mike Belshe
- Re: Encouraging a healthy HTTP/2 ecosystem Nicolas Mailhot
- Re: Encouraging a healthy HTTP/2 ecosystem Nicolas Mailhot
- Re: Encouraging a healthy HTTP/2 ecosystem Eric J. Bowman
- Re: Encouraging a healthy HTTP/2 ecosystem Nicolas Mailhot
- Re: Encouraging a healthy HTTP/2 ecosystem Mike Belshe
- Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
- Re: Encouraging a healthy HTTP/2 ecosystem Mark Nottingham
- Re: Encouraging a healthy HTTP/2 ecosystem Greg Wilkins
- Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
- Re: Encouraging a healthy HTTP/2 ecosystem Mike Belshe
- Re: Encouraging a healthy HTTP/2 ecosystem Mark Nottingham
- Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
- Re: Encouraging a healthy HTTP/2 ecosystem Greg Wilkins
- Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
- Re: Encouraging a healthy HTTP/2 ecosystem Mike Belshe
- Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
- Re: Encouraging a healthy HTTP/2 ecosystem Peter Ghosh
- Re: Encouraging a healthy HTTP/2 ecosystem Mike Belshe
- Re: Encouraging a healthy HTTP/2 ecosystem Mike Belshe
- RE: Encouraging a healthy HTTP/2 ecosystem Mike Bishop
- Re: Encouraging a healthy HTTP/2 ecosystem William Chan (陈智昌)
- Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
- Re: Encouraging a healthy HTTP/2 ecosystem William Chan (陈智昌)
- Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
- Re: Encouraging a healthy HTTP/2 ecosystem Mike Belshe
- Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
- Changing the Internet was: Encouraging a healthy … Roland Zink
- Re: Encouraging a healthy HTTP/2 ecosystem Yoav Nir
- Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp
- Re: Encouraging a healthy HTTP/2 ecosystem Greg Wilkins
- Re: Encouraging a healthy HTTP/2 ecosystem Poul-Henning Kamp