Re: Libraries assuming iso-8859-1 (was: Re: Consensus call to include Display Strings in draft-ietf-httpbis-sfbis)
Martin Thomson <mt@lowentropy.net> Mon, 29 May 2023 19:07 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 D8C17C151B37 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 29 May 2023 12:07:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.046
X-Spam-Level:
X-Spam-Status: No, score=-5.046 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b="oQn0CF0p"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="fGUt/DQ0"
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 2r-pjca_8UGS for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 29 May 2023 12:07:25 -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 5334CC151B02 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 29 May 2023 12:07:24 -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 1q3iAZ-00FmV3-EM for ietf-http-wg-dist@listhub.w3.org; Mon, 29 May 2023 19:04:39 +0000
Resent-Date: Mon, 29 May 2023 19:04:39 +0000
Resent-Message-Id: <E1q3iAZ-00FmV3-EM@lyra.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by lyra.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <mt@lowentropy.net>) id 1q3iAX-00FmU5-Vb for ietf-http-wg@listhub.w3.org; Mon, 29 May 2023 19:04:37 +0000
Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by mimas.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <mt@lowentropy.net>) id 1q3iAX-003pWd-NW for ietf-http-wg@w3.org; Mon, 29 May 2023 19:04:37 +0000
Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 9774C5C010B for <ietf-http-wg@w3.org>; Mon, 29 May 2023 15:04:32 -0400 (EDT)
Received: from imap41 ([10.202.2.91]) by compute6.internal (MEProxy); Mon, 29 May 2023 15:04:32 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm2; t= 1685387072; x=1685473472; bh=fEUiZP1JNcvKjjClp9dxvr4ko7UiZMkE2ZD Kv28R6H0=; b=oQn0CF0pXpocVY72dxp7n9mZCefSNOouu5bv5yNmrKrk6kT9+Be G7bomdWnrgePJM4A0ajz8M2b3A2SOk+6gDEFZhBssp7KV7B2LrQXCYdQGKt9658X x7RvgzAkLD72xp7ITJv6FIk4omhj+YOoS41U0O57aU6RW1I1qg8iEDXSoB9kJ4XE J1flWdeoQfMK6tVYENaPucheICOVshPsjqN94fceKqInqWnBl9nriaie5tQQJZnF O+fdjR8IRHkDK2JFP6nvFbcUDH2OuIoVL9RA4d4H7mL3RjQUMK1XbzwKn3gPush4 iWoHJkN5KceKKpEUyJ7SQxkVI+5F1pyj4+w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1685387072; x= 1685473472; bh=fEUiZP1JNcvKjjClp9dxvr4ko7UiZMkE2ZDKv28R6H0=; b=f GUt/DQ04l23YlsQarJ9veUgP7fllN1s9jxD6WOvXLeo+7bnR/45Y6MBYUs0PHJfe OJseZ1UB3iH1+yi4wi7syGnAnGog2AJ9z3Ph3jL70kA+KHLfoehuMz+0EieToF2h pTFkRzXa9B/DuvTSKnumrvYrQwoASUJTwsDsp+SVJchF0U42jNojDIxTiZC06Nar 38rClaVP2G0a7xGVpsALLzcltyYiG8aE8zq8U7vce2kf+oXCULKtkJT0CLiR3L88 KIT/BBLKdptW4Y+GnAI1Ks5nXTVjBP9oio3wBc7mmNX51zFUbqclwePmdl2brHqo 0fTdLmyMEGFhRrsxgwPTg==
X-ME-Sender: <xms:QPd0ZPgwTQbDoj1wo348xwbrHdBWwhgjRXpYzuZXAb2DV-VmLPGWYQ> <xme:QPd0ZMDFcoWchy9KzZ5jzQeh4imVCNPX33CG-Gzizx0GI3mugv86OCD7OBYo9AKZw JpugPlfc4NI58hXOOM>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeekhedgudefudcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgfgse htqhertderreejnecuhfhrohhmpedfofgrrhhtihhnucfvhhhomhhsohhnfdcuoehmthes lhhofigvnhhtrhhophihrdhnvghtqeenucggtffrrghtthgvrhhnpefgjeeuudeiffeltd egleehjedvtedtjeduudehgfegfefgkefgueeiteegffdttdenucevlhhushhtvghrufhi iigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmtheslhhofigvnhhtrhhophihrd hnvght
X-ME-Proxy: <xmx:QPd0ZPEK6bOEVwWFPd8hGUp_klsb-fQl21jLvsxVWZ_CkjyN8IalWg> <xmx:QPd0ZMSaHVMHqRNaQwSzdOzextU6FKfBcpNJFMnDDwBu9WBmq-jhxQ> <xmx:QPd0ZMzBmt12XfBdHegqK5R-HWJkktGD7sEdmVKQDff2dHlWlRkDMQ> <xmx:QPd0ZL_ChWnCEMwnxJDrcMd49Qp5-pV3V_77ikAKaixdn8FsYUw-Tw>
Feedback-ID: ic129442d:Fastmail
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 531412340080; Mon, 29 May 2023 15:04:32 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.9.0-alpha0-441-ga3ab13cd6d-fm-20230517.001-ga3ab13cd
Mime-Version: 1.0
Message-Id: <72ddfd05-4fbe-410d-8dd2-6abcc0410917@app.fastmail.com>
In-Reply-To: <E80E63C6-639E-41CC-BD40-6EA698092C14@mnot.net>
References: <FC5270AF-509C-4331-AE8F-1F2D51BBC5F2@apple.com> <C687C218-7793-4B74-BB51-B7C34059F9C4@gbiv.com> <F84B0780-7710-4F74-9830-ECBD4A926C3D@mnot.net> <c81e6562-7927-a342-9032-df69aba4ad43@it.aoyama.ac.jp> <E80E63C6-639E-41CC-BD40-6EA698092C14@mnot.net>
Date: Mon, 29 May 2023 20:04:11 +0100
From: Martin Thomson <mt@lowentropy.net>
To: ietf-http-wg@w3.org
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Received-SPF: pass client-ip=66.111.4.27; envelope-from=mt@lowentropy.net; helo=out3-smtp.messagingengine.com
X-W3C-Hub-DKIM-Status: validation passed: (address=mt@lowentropy.net domain=lowentropy.net), signature is good
X-W3C-Hub-DKIM-Status: validation passed: (address=mt@lowentropy.net domain=messagingengine.com), signature is good
X-W3C-Hub-Spam-Status: No, score=-6.8
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1q3iAX-003pWd-NW ced25c6bfc8426dbb0661a143cfb8425
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Libraries assuming iso-8859-1 (was: Re: Consensus call to include Display Strings in draft-ietf-httpbis-sfbis)
Archived-At: <https://www.w3.org/mid/72ddfd05-4fbe-410d-8dd2-6abcc0410917@app.fastmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/51123
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>
On Mon, May 29, 2023, at 02:16, Mark Nottingham wrote: > So, while I think it would be great if we could use UTF-8 in HTTP > fields directly, I agree with Julian's characterisation of this as > appropriate for an experiment, not something that we should include in > infrastructure like SF -- implying that it has to be very highly > reliable. I'm inclined to agree. But, if we proceed with %"..%xx." now, what would UTF-8 look like? "ε", %"∝", or something new like '§'? I would like to run that experiment: it would be the most efficient and most natural thing to do, but I share at least some of your concern about the risks (which are largely a function of middleware: CDNs, stacks, WAFs, etc...). That is tempered by Roy's points about the feature being introduced alongside a feature. Upgrading software should be justifiable if the feature provides enough incentive; but would we want to deploy a new valuable feature with something like this that might add deployment hurdles? What might we also do to prepare for such an experiment? Preparation can make success more likely. It seems to me like maybe specifying the new type now is how you get the new type recognized ahead of the time that you run the experiment. Keep in mind that %"" doesn't have an immediate customer either.
- 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