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

"Poul-Henning Kamp" <phk@phk.freebsd.dk> Sat, 15 October 2016 22:30 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 35C86129499 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 15 Oct 2016 15:30:44 -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 Rg6Dv8JiWJ2R for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 15 Oct 2016 15:30:42 -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 2258E129401 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sat, 15 Oct 2016 15:30:41 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1bvXPW-0001Fe-R8 for ietf-http-wg-dist@listhub.w3.org; Sat, 15 Oct 2016 22:26:34 +0000
Resent-Date: Sat, 15 Oct 2016 22:26:34 +0000
Resent-Message-Id: <E1bvXPW-0001Fe-R8@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <phk@phk.freebsd.dk>) id 1bvXPS-0001Ec-Tw for ietf-http-wg@listhub.w3.org; Sat, 15 Oct 2016 22:26:30 +0000
Received: from phk.freebsd.dk ([130.225.244.222]) by maggie.w3.org with esmtp (Exim 4.80) (envelope-from <phk@phk.freebsd.dk>) id 1bvXPR-0003Rl-Ah for ietf-http-wg@w3.org; Sat, 15 Oct 2016 22:26:30 +0000
Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id 7FA8927375; Sat, 15 Oct 2016 22:26:06 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id u9FMQ4G0080099; Sat, 15 Oct 2016 22:26:04 GMT (envelope-from phk@phk.freebsd.dk)
To: Willy Tarreau <w@1wt.eu>
cc: Martin Thomson <martin.thomson@gmail.com>, Matt Menke <mmenke@google.com>, HTTP Working Group <ietf-http-wg@w3.org>
In-reply-to: <20161015213519.GA28177@1wt.eu>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <80097.1476570364.1@critter.freebsd.dk>
Date: Sat, 15 Oct 2016 22:26:04 +0000
Message-ID: <80098.1476570364@critter.freebsd.dk>
Received-SPF: none client-ip=130.225.244.222; envelope-from=phk@phk.freebsd.dk; helo=phk.freebsd.dk
X-W3C-Hub-Spam-Status: No, score=-5.6
X-W3C-Hub-Spam-Report: AWL=-1.227, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.425, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: maggie.w3.org 1bvXPR-0003Rl-Ah b9c393cf644f10fd8b5215686426b760
X-Original-To: ietf-http-wg@w3.org
Subject: Re: draft-ietf-httpbis-jfv: what's next
Archived-At: <http://www.w3.org/mid/80098.1476570364@critter.freebsd.dk>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/32606
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>

--------
In message <20161015213519.GA28177@1wt.eu>eu>, Willy Tarreau writes:

>And it also helps when headers are duplicated. Below it's becoming
>obvious what type of duplication happened, and where :
>
>     Foo1: >blah<, >bar<
>     Foo2: >blah, bar<

True, but that doesn't make me any more well disposed towards
header split/concatenation.

>> We have three options:
>> 
>> 1. Keep using RFC7230::token for 'identifier'
>(...)
>> 2. Restrict 'identifier'
>(...)
>> 3. Let the semantic layer sort it out.
>(...)
>
>> I picked 3 based on 'minimum intrusiveness', but I can live with
>> all three.
>
>And what about #4 consisting in indicating the encoding in the header
>field *name* instead

That's quite a hack, isn't it ?

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

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.