Re: p1: Upgrade ordering (possible HTTP/2 impact)
Mark Nottingham <mnot@mnot.net> Wed, 08 May 2013 09:34 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 A785821F901F for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 8 May 2013 02:34:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.582
X-Spam-Level:
X-Spam-Status: No, score=-10.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m-ThzoCJD0DH for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 8 May 2013 02:34:21 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 99FCD21F9023 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 8 May 2013 02:34:21 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1Ua0kE-0006Tz-0h for ietf-http-wg-dist@listhub.w3.org; Wed, 08 May 2013 09:33:06 +0000
Resent-Date: Wed, 08 May 2013 09:33:06 +0000
Resent-Message-Id: <E1Ua0kE-0006Tz-0h@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 1Ua0k2-0006St-Ty for ietf-http-wg@listhub.w3.org; Wed, 08 May 2013 09:32:54 +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 1Ua0jy-00038n-DM for ietf-http-wg@w3.org; Wed, 08 May 2013 09:32:54 +0000
Received: from [192.168.1.80] (unknown [118.209.105.214]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 44F0122E1F3; Wed, 8 May 2013 05:32:27 -0400 (EDT)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <5189E2D7.3070602@ericsson.com>
Date: Wed, 08 May 2013 19:32:23 +1000
Cc: ietf-http-wg@w3.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <C0E7B31D-28D3-4CE1-B553-61AF7EFC5D91@mnot.net>
References: <B49447FF-CB94-43ED-9CA2-0698C64BB554@mnot.net> <5189E2D7.3070602@ericsson.com>
To: Salvatore Loreto <salvatore.loreto@ericsson.com>
X-Mailer: Apple Mail (2.1503)
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.4
X-W3C-Hub-Spam-Report: AWL=-3.395, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1Ua0jy-00038n-DM 7de3d43f3a80c1b432f8a15d38e745c3
X-Original-To: ietf-http-wg@w3.org
Subject: Re: p1: Upgrade ordering (possible HTTP/2 impact)
Archived-At: <http://www.w3.org/mid/C0E7B31D-28D3-4CE1-B553-61AF7EFC5D91@mnot.net>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/17891
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>
Not sure I understand the question; The Upgrade header likely won't be valid in HTTP/2... On 08/05/2013, at 3:29 PM, Salvatore Loreto <salvatore.loreto@ericsson.com> wrote: > On 4/20/13 7:07 AM, Mark Nottingham wrote: >> p1 section 6.7 defines the Upgrade header, but no where does it say anything about relative preference. >> >> Should we define (or at least allow) for the ordering to be semantically significant? It seems to me that if we end up using this, and there are a few different variants of HTTP/2 (e.g., "normal" vs "mobile"), it'd be nice to rely on ordering here. > Mark > do you foresee the possibility HTTP/2 will be (or behave) differently or it is just an example? > > /Sal > > -- Mark Nottingham http://www.mnot.net/
- Re: p1: Upgrade ordering (possible HTTP/2 impact) Mark Nottingham
- Re: p1: Upgrade ordering (possible HTTP/2 impact) Willy Tarreau
- p1: Upgrade ordering (possible HTTP/2 impact) Mark Nottingham
- Re: p1: Upgrade ordering (possible HTTP/2 impact) Willy Tarreau
- Re: p1: Upgrade ordering (possible HTTP/2 impact) Mark Nottingham
- Re: p1: Upgrade ordering (possible HTTP/2 impact) Mark Nottingham
- Re: p1: Upgrade ordering (possible HTTP/2 impact) Willy Tarreau
- Re: p1: Upgrade ordering (possible HTTP/2 impact) Mark Nottingham
- Re: p1: Upgrade ordering (possible HTTP/2 impact) Roberto Peon
- Re: p1: Upgrade ordering (possible HTTP/2 impact) Mark Nottingham
- Re: p1: Upgrade ordering (possible HTTP/2 impact) Roberto Peon
- Re: p1: Upgrade ordering (possible HTTP/2 impact) William Chan (陈智昌)
- Re: p1: Upgrade ordering (possible HTTP/2 impact) Willy Tarreau
- Re: p1: Upgrade ordering (possible HTTP/2 impact) Mark Nottingham
- Re: p1: Upgrade ordering (possible HTTP/2 impact) William Chan (陈智昌)
- Re: p1: Upgrade ordering (possible HTTP/2 impact) Mark Nottingham
- Re: p1: Upgrade ordering (possible HTTP/2 impact) Willy Tarreau
- Re: p1: Upgrade ordering (possible HTTP/2 impact) Mark Nottingham
- Re: p1: Upgrade ordering (possible HTTP/2 impact) Salvatore Loreto
- Re: p1: Upgrade ordering (possible HTTP/2 impact) Peter Occil
- Re: p1: Upgrade ordering (possible HTTP/2 impact) Mark Nottingham
- Re: Upgrade ordering (possible HTTP/2 impact) Peter Occil
- Re: Upgrade ordering (possible HTTP/2 impact) Peter Occil
- Re: Upgrade ordering (possible HTTP/2 impact) Mark Nottingham