Re: Consensus call to include Display Strings in draft-ietf-httpbis-sfbis
Poul-Henning Kamp <phk@phk.freebsd.dk> Fri, 26 May 2023 06:50 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 C69BFC1522CD for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 25 May 2023 23:50:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.65
X-Spam-Level:
X-Spam-Status: No, score=-7.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1lA88_PRtaAV for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 25 May 2023 23:50:53 -0700 (PDT)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62420C1522CB for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 25 May 2023 23:50:53 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.94.2) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1q2RHg-008Wqr-Qq for ietf-http-wg-dist@listhub.w3.org; Fri, 26 May 2023 06:50:44 +0000
Resent-Date: Fri, 26 May 2023 06:50:44 +0000
Resent-Message-Id: <E1q2RHg-008Wqr-Qq@lyra.w3.org>
Received: from titan.w3.org ([128.30.52.76]) by lyra.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <phk@critter.freebsd.dk>) id 1q2RHe-008WpM-6c for ietf-http-wg@listhub.w3.org; Fri, 26 May 2023 06:50:42 +0000
Received: from phk.freebsd.dk ([130.225.244.222]) by titan.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <phk@critter.freebsd.dk>) id 1q2RHc-0093O7-DM for ietf-http-wg@w3.org; Fri, 26 May 2023 06:50:41 +0000
Received: from critter.freebsd.dk (unknown [192.168.55.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by phk.freebsd.dk (Postfix) with ESMTPS id 16D2389334; Fri, 26 May 2023 06:50:35 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.17.1/8.16.1) with ESMTPS id 34Q6oY9N030825 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 26 May 2023 06:50:34 GMT (envelope-from phk@critter.freebsd.dk)
Received: (from phk@localhost) by critter.freebsd.dk (8.17.1/8.16.1/Submit) id 34Q6oYQx030824; Fri, 26 May 2023 06:50:34 GMT (envelope-from phk)
Message-Id: <202305260650.34Q6oYQx030824@critter.freebsd.dk>
To: Mark Nottingham <mnot@mnot.net>
cc: "Julian F. Reschke" <julian.reschke@gmx.de>, ietf-http-wg@w3.org
In-reply-to: <66F56BEF-2691-43F6-842B-EF570F42320B@mnot.net>
From: Poul-Henning Kamp <phk@phk.freebsd.dk>
References: <FC5270AF-509C-4331-AE8F-1F2D51BBC5F2@apple.com> <C687C218-7793-4B74-BB51-B7C34059F9C4@gbiv.com> <202305252223.34PMNecG001082@critter.freebsd.dk> <5a704134-ce9c-2201-62ff-3a70ba6ac775@gmx.de> <202305260547.34Q5lZre026200@critter.freebsd.dk> <66F56BEF-2691-43F6-842B-EF570F42320B@mnot.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <30822.1685083834.1@critter.freebsd.dk>
Date: Fri, 26 May 2023 06:50:34 +0000
Received-SPF: pass client-ip=130.225.244.222; envelope-from=phk@critter.freebsd.dk; helo=phk.freebsd.dk
X-W3C-Hub-Spam-Status: No, score=-4.9
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1q2RHc-0093O7-DM 7f0472e10af2656b744f41e59afea933
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Consensus call to include Display Strings in draft-ietf-httpbis-sfbis
Archived-At: <https://www.w3.org/mid/202305260650.34Q6oYQx030824@critter.freebsd.dk>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/51097
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>
-------- Mark Nottingham writes: > PHK, you could make this argument for *any* of the types already in SF > -- we don't need Integers when you can just stuff them in binary, after > all. Mark, that is a disingenious argument, and you know it better than any. I designed SF, and later you helped, make SF the largest possible union of current HTTP header definitions, while still trying to impose some kind of order. I did not encounter a single RFC which defined a field where integers were transmitted as anything but a sequence of ASCII digits. The information in HTTP fields is almost exclusively for machine-machine communication, and SF is an attempt to make that safer, saner and more resource efficient. There are a few occational "Show this to the human" bits of information at the HTTP field level, and there, and /only/ there, it makes sense to allow UniCode. But those fields have no semantic meaning at the HTTP level, they are not interpreted at the HTTP level, and therefore they should be transferred as opaque data, and the validation of them left to the upper layers of application software. Ie: sf-binary. Adding a "sort-of-human-readable" string encoding of UniCode fields makes things more complex, less safe and adds overhead for everybody, while adding no new functionality. This is a bad idea, and the PR is a bad execution of that bad ide. -- 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.
- Consensus call to include Display Strings in draf… Tommy Pauly
- Re: Consensus call to include Display Strings in … Julian Reschke
- Re: Consensus call to include Display Strings in … Mark Nottingham
- Re: Consensus call to include Display Strings in … Poul-Henning Kamp
- Re: Consensus call to include Display Strings in … Martin Thomson
- Re: Consensus call to include Display Strings in … Mark Thomas
- Re: Consensus call to include Display Strings in … Roy T. Fielding
- Re: Consensus call to include Display Strings in … Poul-Henning Kamp
- Re: Consensus call to include Display Strings in … Mark Nottingham
- Re: Consensus call to include Display Strings in … Poul-Henning Kamp
- Re: Consensus call to include Display Strings in … Julian Reschke
- Re: Consensus call to include Display Strings in … Julian Reschke
- Re: Consensus call to include Display Strings in … Mark Nottingham
- Re: Consensus call to include Display Strings in … Glenn Strauss
- Re: Consensus call to include Display Strings in … Poul-Henning Kamp
- Re: Consensus call to include Display Strings in … Mark Nottingham
- Re: Consensus call to include Display Strings in … Poul-Henning Kamp
- Re: Consensus call to include Display Strings in … Ilari Liusvaara
- Re: Consensus call to include Display Strings in … Roy T. Fielding
- Re: Consensus call to include Display Strings in … Mark Nottingham
- Re: Consensus call to include Display Strings in … David Benjamin
- Re: Consensus call to include Display Strings in … Willy Tarreau
- Re: Consensus call to include Display Strings in … Martin J. Dürst
- Re: Consensus call to include Display Strings in … Julian Reschke
- Re: Consensus call to include Display Strings in … Michael Sweet
- Re: Consensus call to include Display Strings in … Willy Tarreau
- Re: Consensus call to include Display Strings in … Julian Reschke
- Re: Consensus call to include Display Strings in … Mark Nottingham
- Re: Consensus call to include Display Strings in … Willy Tarreau
- Libraries assuming iso-8859-1 (was: Re: Consensus… Martin J. Dürst
- Re: Libraries assuming iso-8859-1 (was: Re: Conse… Poul-Henning Kamp
- Re: Consensus call to include Display Strings in … Martin J. Dürst
- Re: Consensus call to include Display Strings in … Martin J. Dürst
- Re: Consensus call to include Display Strings in … Willy Tarreau
- Re: Libraries assuming iso-8859-1 (was: Re: Conse… Julian Reschke
- Re: Consensus call to include Display Strings in … Julian Reschke
- Re: Consensus call to include Display Strings in … Julian Reschke
- Re: Libraries assuming iso-8859-1 (was: Re: Conse… Mark Nottingham
- Re: Libraries assuming iso-8859-1 (was: Re: Conse… Martin Thomson
- Re: Libraries assuming iso-8859-1 (was: Re: Conse… Mark Nottingham
- Re: Consensus call to include Display Strings in … Kazuho Oku
- Re: Consensus call to include Display Strings in … Tommy Pauly
- Re: Consensus call to include Display Strings in … Mark Nottingham
- Re: Consensus call to include Display Strings in … Poul-Henning Kamp
- Re: Consensus call to include Display Strings in … Ilari Liusvaara
- Re: Consensus call to include Display Strings in … Poul-Henning Kamp
- Re: Consensus call to include Display Strings in … Ilari Liusvaara
- Re: Consensus call to include Display Strings in … Poul-Henning Kamp