IETF Logo Mail Archive

Re: draft-ietf-httpbis-jfv: what's next

Willy Tarreau <w@1wt.eu> Sun, 16 October 2016 05:31 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 2CBE812959C for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 15 Oct 2016 22:31:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.332
X-Spam-Level:
X-Spam-Status: No, score=-7.332 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.431, 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 AuJFqgDOedTY for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 15 Oct 2016 22:31:26 -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 53998129408 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sat, 15 Oct 2016 22:31:25 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1bvdyd-00074j-UC for ietf-http-wg-dist@listhub.w3.org; Sun, 16 Oct 2016 05:27:15 +0000
Resent-Date: Sun, 16 Oct 2016 05:27:15 +0000
Resent-Message-Id: <E1bvdyd-00074j-UC@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <w@1wt.eu>) id 1bvdyZ-00073y-Eq for ietf-http-wg@listhub.w3.org; Sun, 16 Oct 2016 05:27:11 +0000
Received: from wtarreau.pck.nerim.net ([62.212.114.60] helo=1wt.eu) by lisa.w3.org with esmtp (Exim 4.80) (envelope-from <w@1wt.eu>) id 1bvdyX-0002NJ-R4 for ietf-http-wg@w3.org; Sun, 16 Oct 2016 05:27:10 +0000
Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id u9G5QfSM029013; Sun, 16 Oct 2016 07:26:41 +0200
Date: Sun, 16 Oct 2016 07:26:41 +0200
From: Willy Tarreau <w@1wt.eu>
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
Cc: Martin Thomson <martin.thomson@gmail.com>, Matt Menke <mmenke@google.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <20161016052641.GA28987@1wt.eu>
References: <CAEK7mvoXqyX3cADJytjU+C158EULgPLbzAb5kiUN=8WWxhi29Q@mail.gmail.com> <78301.1476524467@critter.freebsd.dk> <CABkgnnXw7WacnMf4Nsx-drktn__V4afK61G67A5bT5SSdqaucQ@mail.gmail.com> <79226.1476546544@critter.freebsd.dk> <20161015213519.GA28177@1wt.eu> <80098.1476570364@critter.freebsd.dk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <80098.1476570364@critter.freebsd.dk>
User-Agent: Mutt/1.6.0 (2016-04-01)
Received-SPF: pass client-ip=62.212.114.60; envelope-from=w@1wt.eu; helo=1wt.eu
X-W3C-Hub-Spam-Status: No, score=-5.5
X-W3C-Hub-Spam-Report: AWL=-0.575, BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: lisa.w3.org 1bvdyX-0002NJ-R4 9549785485ae6ee76822fe829828b876
X-Original-To: ietf-http-wg@w3.org
Subject: Re: draft-ietf-httpbis-jfv: what's next
Archived-At: <http://www.w3.org/mid/20161016052641.GA28987@1wt.eu>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/32607
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 Sat, Oct 15, 2016 at 10:26:04PM +0000, Poul-Henning Kamp wrote:
> >And what about #4 consisting in indicating the encoding in the header
> >field *name* instead
> 
> That's quite a hack, isn't it ?

Not that much after all when you think about it, because our parsers
will have to consider the field name to know how to decode the value.
Content-length will remain integer for example. Thus new fields could
be classified by their name using a prefix for easier sorting/testing.

> I'd prefer not to complicate things that way if I can...

Same for me, don't worry, which is why I'm only suggesting :-)

Willy

v2.23.0 | Report a Bug | By Email