Re: [I18ndir] Working Group Last Call: Structured Headers for HTTP

"John R Levine" <johnl@taugh.com> Tue, 04 February 2020 16:51 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: i18ndir@ietfa.amsl.com
Delivered-To: i18ndir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D11D1200F5 for <i18ndir@ietfa.amsl.com>; Tue, 4 Feb 2020 08:51:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=R1ii/1qd; dkim=pass (1536-bit key) header.d=taugh.com header.b=lfh5+M/o
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 Pgw2je5SEjhe for <i18ndir@ietfa.amsl.com>; Tue, 4 Feb 2020 08:51:46 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 86D3A12011A for <i18ndir@ietf.org>; Tue, 4 Feb 2020 08:51:46 -0800 (PST)
Received: (qmail 86699 invoked from network); 4 Feb 2020 16:51:45 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=152a9.5e39a121.k2002; i=johnl-iecc.com@submit.iecc.com; bh=enjQUs9sNJs/0vsUZ1IBhOeJv54TnRIOhzy1xZ4D0b4=; b=R1ii/1qdQ0yTlem8Gpwi9VBKiaDCHMA6giLqceSB1Bmqda0gLRrFS1qfwV9f3n+Ejsp6sZB0H5DhL5VsJLZpY/pI+gtORqlZNgySCHa87K6jeexF+OHBNoBhPqXFgIpcl6TqlpSOfBXuVDDQi7Ve88t6AOfQ/ybSWDDgOiiW2PCMM3GkdMBEFZJxMjafPyTDGgA+AfR9I7SteyOKvShVny+HW89YZZ6f8a5ED2XGY78Ynei44zsX160Dp0/cHEI5
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=152a9.5e39a121.k2002; olt=johnl-iecc.com@submit.iecc.com; bh=enjQUs9sNJs/0vsUZ1IBhOeJv54TnRIOhzy1xZ4D0b4=; b=lfh5+M/ovUkjWmdxZ2NEv5f0sZi89UnEuvJ9ypofsvfa89ixDkDEZ1Eb3rO+UQOJfF0dDQUa6RiA8OG0YLfSoOCoWljizWeXL69WWsk3SV4wvUEOT+dlESZpaFfRdGFXdVKG80zQTjFt2wWq5Pyel5+4/1gMON1/bPeBcUz7aOTDjdX38IDFQcQ+oJ37JQEDJveEqm65CFXtZyXDIpxN/0RLD/TRpkH1HPq19FULuEcseBlYCyMMZILLr2mEYVKo
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.3 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 04 Feb 2020 16:51:44 -0000
Date: Tue, 04 Feb 2020 11:51:44 -0500
Message-ID: <alpine.OSX.2.21.99999.374.2002041149130.34062@ary.qy>
From: John R Levine <johnl@taugh.com>
To: John C Klensin <john@jck.com>
Cc: i18ndir@ietf.org
In-Reply-To: <47AEE7D582019051ACF36647@PSB>
References: <20200203173404.88EE813AA055@ary.qy> <E2361F8BA970A15043416C2D@PSB> <alpine.OSX.2.21.99999.374.2002031653540.31381@ary.qy> <D03AE38116EF15538E10CFAF@PSB> <7D31FE0A-D4EC-4096-83FE-97D2BF4908F5@frobbit.se> <alpine.OSX.2.21.99999.374.2002041007110.33467@ary.qy> <47AEE7D582019051ACF36647@PSB>
User-Agent: Alpine 2.21.99999 (OSX 374 2019-10-27)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/_YBLq2jrLnxab_l-4Ufqk_ElM2U>
Subject: Re: [I18ndir] Working Group Last Call: Structured Headers for HTTP
X-BeenThere: i18ndir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Internationalization Directorate <i18ndir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18ndir/>
List-Post: <mailto:i18ndir@ietf.org>
List-Help: <mailto:i18ndir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2020 16:51:48 -0000

On Tue, 4 Feb 2020, John C Klensin wrote:
>> NFC is specific to UTF-8.  MIME doesn't have that as far as I
>> know so I don't think it makes sense here.
>
> Huh?   NFC is certainly specific to Unicode, but there is
> nothing specific to UTF-8 (or any other encoding form) about it.

Sorry, I meant specific to Unicode.  If there is some old page in big5 or 
ISO-2022-x, there aren't any normalization rules I'm aware of.

I think we agree, normalization is a level up from what they're describing 
here.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly