Re: Empty lists in Structured Headers (#781)

Willy Tarreau <w@1wt.eu> Tue, 14 May 2019 18:22 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 7FB54120046 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 14 May 2019 11:22:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, MAILING_LIST_MULTI=-1, 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 OCa6gJo945Rt for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 14 May 2019 11:22:49 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [IPv6:2603:400a:ffff:804:801e:34:0:38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC05012003F for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 14 May 2019 11:22:48 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1hQc2u-0007xq-ON for ietf-http-wg-dist@listhub.w3.org; Tue, 14 May 2019 18:21:00 +0000
Resent-Date: Tue, 14 May 2019 18:21:00 +0000
Resent-Message-Id: <E1hQc2u-0007xq-ON@frink.w3.org>
Received: from mimas.w3.org ([2603:400a:ffff:804:801e:34:0:4f]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <w@1wt.eu>) id 1hQc2q-0007x3-Tl for ietf-http-wg@listhub.w3.org; Tue, 14 May 2019 18:20:56 +0000
Received: from wtarreau.pck.nerim.net ([62.212.114.60] helo=1wt.eu) by mimas.w3.org with esmtp (Exim 4.89) (envelope-from <w@1wt.eu>) id 1hQc2p-0003tR-Jl for ietf-http-wg@w3.org; Tue, 14 May 2019 18:20:56 +0000
Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id x4EIKMjJ017161; Tue, 14 May 2019 20:20:22 +0200
Date: Tue, 14 May 2019 20:20:22 +0200
From: Willy Tarreau <w@1wt.eu>
To: Tommy Pauly <tpauly@apple.com>
Cc: "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>, Poul-Henning Kamp <phk@phk.freebsd.dk>, Mark Nottingham <mnot@mnot.net>
Message-ID: <20190514182022.GA17146@1wt.eu>
References: <D99820F1-D169-468E-BA31-68AA710C3CC4@mnot.net> <B3BF258C-ECB2-4F07-83EF-2D491E236718@apple.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <B3BF258C-ECB2-4F07-83EF-2D491E236718@apple.com>
User-Agent: Mutt/1.6.1 (2016-04-27)
Received-SPF: pass client-ip=62.212.114.60; envelope-from=w@1wt.eu; helo=1wt.eu
X-W3C-Hub-Spam-Status: No, score=-6.8
X-W3C-Hub-Spam-Report: AWL=1.084, BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1hQc2p-0003tR-Jl 0b34302de9f701172e70b4587b23b508
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Empty lists in Structured Headers (#781)
Archived-At: <https://www.w3.org/mid/20190514182022.GA17146@1wt.eu>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/36641
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: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

Hello Tommy,

On Tue, May 14, 2019 at 10:46:11AM -0700, Tommy Pauly wrote:
> I'd like to ask everyone to reply with which option they prefer of the of
> following, so we can get a sense of the group's opinion:
> 
> A. Leave the document as is, not defining empty header values for SH (as requested by the editors). As noted on the list, this can allow future revisions to add support.
> B. Define empty header values for SH (as the issue requests).
> C. Do not allow empty header values for SH, but add formal text to the document explaining how to handle empty values.
> 
> Please evaluate these based on what you think will help us converge and ship
> this document, and note that this is deciding how we define formal Structured
> Headers, not all or previous HTTP headers.

I'd prefer B first, then C as a fallback. I'm not strong on this, I just
find it too bad to purposely not support a single feature which already
works even if seldom used. But I won't make a fuss if we don't have it,
this will only leave me with a feeling of half-finished work.

Thanks,
Willy