IETF Logo Mail Archive

Re: http/2 prioritization/fairness bug with proxies

Albert Lunde <atlunde@panix.com> Mon, 04 February 2013 15:58 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D525E21F88A3 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 4 Feb 2013 07:58:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q5ikYeinNfhI for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 4 Feb 2013 07:58:11 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 6EE3021F882F for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 4 Feb 2013 07:58:11 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1U2OPC-0001jQ-6L for ietf-http-wg-dist@listhub.w3.org; Mon, 04 Feb 2013 15:56:26 +0000
Resent-Date: Mon, 04 Feb 2013 15:56:26 +0000
Resent-Message-Id: <E1U2OPC-0001jQ-6L@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <atlunde@panix.com>) id 1U2OP6-0001il-HY for ietf-http-wg@listhub.w3.org; Mon, 04 Feb 2013 15:56:20 +0000
Received: from mailbackend.panix.com ([166.84.1.89]) by lisa.w3.org with esmtp (Exim 4.72) (envelope-from <atlunde@panix.com>) id 1U2OP5-00014Z-Jm for ietf-http-wg@w3.org; Mon, 04 Feb 2013 15:56:20 +0000
Received: from [192.168.15.4] (unknown [184.78.58.209]) by mailbackend.panix.com (Postfix) with ESMTP id 72F562EC04; Mon, 4 Feb 2013 10:55:58 -0500 (EST)
Message-ID: <510FDA11.7040708@panix.com>
Date: Mon, 04 Feb 2013 09:56:01 -0600
From: Albert Lunde <atlunde@panix.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf-http-wg@w3.org
References: <CAA4WUYjiBZpShKKFfHQnixc94aOLrck0oR4ykARB=hF5h8nkfA@mail.gmail.com> <3430.1359961022@critter.freebsd.dk> <510F72CE.8030003@treenet.co.nz> <CDFC6823-BC3E-4F53-A9FA-9F0E7AAF0C12@mnot.net> <510FB175.9030805@treenet.co.nz>
In-Reply-To: <510FB175.9030805@treenet.co.nz>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass client-ip=166.84.1.89; envelope-from=atlunde@panix.com; helo=mailbackend.panix.com
X-W3C-Hub-Spam-Status: No, score=-4.2
X-W3C-Hub-Spam-Report: AWL=-1.910, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1U2OP5-00014Z-Jm bf3939f9e16dc1918973c225eee40325
X-Original-To: ietf-http-wg@w3.org
Subject: Re: http/2 prioritization/fairness bug with proxies
Archived-At: <http://www.w3.org/mid/510FDA11.7040708@panix.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/16353
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/4/2013 7:02 AM, Amos Jeffries wrote:
  Which goes to show why specifying an algorithm for handling opaque
> client-selected prioritization is the wrong way to go about this.
>
> You have presented a good argument for specifying a set of standardized
> priority labels with criterion for setting each label.

One possible gotcha there is that not everything is a browser. A server 
application issuing, say, web service requests may have different 
pasterns of usage than a browser client used by an typical human user.

On another hand, the example of multiple TCP connections in HTTP/1.1 and 
in particular, "download accelerators", illustrates that some client 
software will be developed to "game the system" any way it can; it's 
going to be hard to be fair.

v2.23.0 | Report a Bug | By Email