IETF Logo Mail Archive

[art] Re: draft-bray-unichars-09 review

"John R. Levine" <johnl@iecc.com> Tue, 08 October 2024 17:18 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 810D7C14CF1C for <art@ietfa.amsl.com>; Tue, 8 Oct 2024 10:18:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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=iecc.com
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 2vKbvj5ruPOC for <art@ietfa.amsl.com>; Tue, 8 Oct 2024 10:17:59 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99F4CC14F6B7 for <art@ietf.org>; Tue, 8 Oct 2024 10:17:58 -0700 (PDT)
Received: (qmail 7202 invoked from network); 8 Oct 2024 17:17:57 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding; s=1c2067056944.k2410; t=1728407866; x=1728753466; bh=4/fnK3AQtivkjWZxTwaTtS/fUpfjSNNjg4d3CIGwTnw=; b=K5rmOHJxVwRm//w5WxKNw1QrF0iXxT2TJY8YXpvCemdKSiaaKSHkJL6fpcgmte7s0rhmpyjdBw42T+uxMGKCNVlKWUk4e177jWrHpIqQWURY4VYbE9HZuOxGaPNu3XzhDh8MxMKEAPjVpfxLAGPzmA/W9HpQrzKTNH+MB5ElM9vr1T6dhACD7PIruUwV+Y6E1ElxAYgwjo4Q3PvlYFmStIjjm6bzB6rtNb7GE3TsVkOLLcfnzTInAfWyPhJ5ov039f7jiWTrL2Tb3jSpr+Egv0ImCqxGP8Q+047Cs52Nc5p5fplkVM8t8AM9IwJO+w+AS4hIgqbjro8lnF4pGsY8Ug==
Received: from ary.local ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA CHACHA20-POLY1305 AEAD) via TCP6; 08 Oct 2024 17:17:56 -0000
Received: by ary.local (Postfix, from userid 501) id EB70F95A4B51; Tue, 8 Oct 2024 13:17:55 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by ary.local (Postfix) with ESMTP id AB30195A4B33; Tue, 8 Oct 2024 13:17:55 -0400 (EDT)
Date: Tue, 08 Oct 2024 13:17:55 -0400
Message-ID: <aa5a3274-2af3-a3f7-6eb8-885bf88e08af@iecc.com>
From: "John R. Levine" <johnl@iecc.com>
To: Tim Bray <tbray@textuality.com>, Orie Steele <orie@transmute.industries>
X-X-Sender: johnl@ary.local
In-Reply-To: <CAHBU6itokOYJb6ZWUfvct7O7AqDsULvYUrtBqm25Wy-7TxOM4Q@mail.gmail.com>
References: <CAN8C-_JkHcer1MbvwSrtFxFu_38JRy-_JstYOmAMdOVCdCe-0g@mail.gmail.com> <CAHBU6itokOYJb6ZWUfvct7O7AqDsULvYUrtBqm25Wy-7TxOM4Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: LGBAAWQ23GAHQXYT7UB4RXZORR5KI2P3
X-Message-ID-Hash: LGBAAWQ23GAHQXYT7UB4RXZORR5KI2P3
X-MailFrom: johnl@iecc.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-art.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-bray-unichars@ietf.org, art@ietf.org
X-Mailman-Version: 3.3.9rc5
Precedence: list
Subject: [art] Re: draft-bray-unichars-09 review
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/LIhPSmYP9mb31A4S46wvRyh7nfQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Owner: <mailto:art-owner@ietf.org>
List-Post: <mailto:art@ietf.org>
List-Subscribe: <mailto:art-join@ietf.org>
List-Unsubscribe: <mailto:art-leave@ietf.org>

On Tue, 8 Oct 2024, Tim Bray wrote:
> UTF-16 is essentially never used on the wire. I for one have never seen it
> in my decades of work in this space.  Does anyone have a counter-example?
> Or even better, does anyone know of an RFC that says “you MUST NOT put
> UTF-16 on the wire.”? Because thankfully, nobody does.
>
> ### Where are legacy codes still used in IETF protocols?

I gather that Javascript is often sent as UTF-16 even if its MIME label 
says UTF-8, which is why it always starts with a BOM.

Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly

v2.46.0 | Report a Bug | By Email | System Status