IETF Logo Mail Archive

Re: Empty lists in Structured Headers (#781)

"Poul-Henning Kamp" <phk@phk.freebsd.dk> Thu, 02 May 2019 19:04 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 2AB15120075 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 2 May 2019 12:04:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.899
X-Spam-Level:
X-Spam-Status: No, score=-2.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=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 j_ZWn9NjuZwy for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 2 May 2019 12:04:09 -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 ED02E120072 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 2 May 2019 12:04:08 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1hMGxd-00058K-BP for ietf-http-wg-dist@listhub.w3.org; Thu, 02 May 2019 19:01:37 +0000
Resent-Date: Thu, 02 May 2019 19:01:37 +0000
Resent-Message-Id: <E1hMGxd-00058K-BP@frink.w3.org>
Received: from titan.w3.org ([2603:400a:ffff:804:801e:34:0:4c]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <phk@critter.freebsd.dk>) id 1hMGxb-00056s-5y for ietf-http-wg@listhub.w3.org; Thu, 02 May 2019 19:01:35 +0000
Received: from phk.freebsd.dk ([130.225.244.222]) by titan.w3.org with esmtp (Exim 4.89) (envelope-from <phk@critter.freebsd.dk>) id 1hMGxZ-0000MC-4D for ietf-http-wg@w3.org; Thu, 02 May 2019 19:01:34 +0000
Received: from critter.freebsd.dk (v-critter.freebsd.dk [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id 754F12025654; Thu, 2 May 2019 19:01:10 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTPS id x42J1A4u008589 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 2 May 2019 19:01:10 GMT (envelope-from phk@critter.freebsd.dk)
Received: (from phk@localhost) by critter.freebsd.dk (8.15.2/8.15.2/Submit) id x42J19Yw008588; Thu, 2 May 2019 19:01:09 GMT (envelope-from phk)
To: Julian Reschke <julian.reschke@gmx.de>
cc: Willy Tarreau <w@1wt.eu>, "Roy T. Fielding" <fielding@gbiv.com>, Martin Thomson <mt@lowentropy.net>, ietf-http-wg@w3.org
In-reply-to: <4d86289c-26fb-5add-5734-f4aff8cdb7fd@gmx.de>
From: Poul-Henning Kamp <phk@phk.freebsd.dk>
References: <D99820F1-D169-468E-BA31-68AA710C3CC4@mnot.net> <1645485d-84da-4b74-8fb1-d487394ba89a@www.fastmail.com> <627257EE-FE78-40A6-AA91-9E488C53A8FC@gbiv.com> <8113.1556816199@critter.freebsd.dk> <20190502174129.GF32325@1wt.eu> <8403.1556819980@critter.freebsd.dk> <4d86289c-26fb-5add-5734-f4aff8cdb7fd@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8586.1556823669.1@critter.freebsd.dk>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 02 May 2019 19:01:09 +0000
Message-ID: <8587.1556823669@critter.freebsd.dk>
Received-SPF: none client-ip=130.225.244.222; envelope-from=phk@critter.freebsd.dk; helo=phk.freebsd.dk
X-W3C-Hub-Spam-Status: No, score=-5.7
X-W3C-Hub-Spam-Report: AWL=-0.833, BAYES_00=-1.9, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1hMGxZ-0000MC-4D 0641163d2c252306b87e14d609344c71
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Empty lists in Structured Headers (#781)
Archived-At: <https://www.w3.org/mid/8587.1556823669@critter.freebsd.dk>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/36594
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>

--------
In message <4d86289c-26fb-5add-5734-f4aff8cdb7fd@gmx.de>, Julian Reschke writes
:

>> If a documented use case appears and a concensus for how to meet
>> its needs can be found, publishing a SHbis will not hurt anybody,
>> or create any compatibility issues since the specs that references
>> SHorig are not changed by SHbiss mere existence.
>
>So do yo envision implementers to have multiple code paths for SH,
>SHbis, SHbisbis???

No.

But if implementers want to support the FooBar: header which requires
SHter, they will have to upgrade their SH parser to SHter.

Doing so will not change the parsing or validation of headers specified
against SH or SHbis.

-- 
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.

v2.23.0 | Report a Bug | By Email