IETF Logo Mail Archive

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

"John Levine" <johnl@taugh.com> Mon, 03 February 2020 17:34 UTC

Return-Path: <johnl@iecc.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 B1F0F120BB0 for <i18ndir@ietfa.amsl.com>; Mon, 3 Feb 2020 09:34:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=M4dZxSjp; dkim=pass (1536-bit key) header.d=taugh.com header.b=UJAPPepq
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 HRIv_yTmeZ-p for <i18ndir@ietfa.amsl.com>; Mon, 3 Feb 2020 09:34:06 -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 2FE2A120072 for <i18ndir@ietf.org>; Mon, 3 Feb 2020 09:34:06 -0800 (PST)
Received: (qmail 21613 invoked from network); 3 Feb 2020 17:34:04 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=546a.5e38598c.k2002; bh=9/G+iO7zoeKVClgaDdRXeUr+yQmhFhqlfL/sK5U7IwM=; b=M4dZxSjpzILG9visc0Hwy49XzC3yzvFZWOF+PAIk+3bULKE73f5JB0VRpRGX03XW6YA/oteg7ucsJtz85wi3154UoHb6Ti+BrVR7BCmonf7x4ybPDQR5TfcNyWSHYSkJnt5CXvaRB0aQNQG6vschv3op4Qx7+ZV+9lyTJHxii33lO8aZiAHFaSIWXS7PVaAS4GuOPhFR0GdZ1IuTiss2FixVPWCtzH1sXQBJ4F/YOWRWlWk4igmHqiEqw/4A9a7w
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=546a.5e38598c.k2002; bh=9/G+iO7zoeKVClgaDdRXeUr+yQmhFhqlfL/sK5U7IwM=; b=UJAPPepqCn2taCN3KwLLdH3enzEAEkj4drXajLpTu2bP9eQxvCcOxizRsc4DcSHVv+ybWqbEqiTnjTsq17motzIimHtjAgBM+Lj0jf5zQX7a+BQuqdHPyeL7vpOeeaI/v/ah+W0gAGf/7g2hWRggxj45rWkw+xlW1ZrsgGjnjkT2Vjk9xN/7qSTXcEpTgUGbn5AS32Ul4GWxMNsODph/udryJGj1wbxFb9KLZLgiKQzpr5SvpYVDD3zjm+rgxZtv
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 03 Feb 2020 17:34:04 -0000
Received: by ary.qy (Postfix, from userid 501) id 88EE813AA055; Mon, 3 Feb 2020 12:34:04 -0500 (EST)
Date: Mon, 03 Feb 2020 12:34:04 -0500
Message-Id: <20200203173404.88EE813AA055@ary.qy>
From: John Levine <johnl@taugh.com>
To: i18ndir@ietf.org
Cc: john-ietf@jck.com
In-Reply-To: <7D2D294BBAD6BC06F09142E3@JcK-HP5.jck.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/m5l2w_JXVE6dRSdgI6S-9MT9UoM>
Subject: Re: [I18ndir] Fwd: 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: Mon, 03 Feb 2020 17:34:08 -0000

In article <7D2D294BBAD6BC06F09142E3@JcK-HP5.jck.com> you write:
>Because HTTP is not supposed to be visible to users, if the
>Directorate is going to get involved, we will probably need to
>have the usual discussion about protocol elements versus
>user-visible strings, noting that one could easily have:
>
>   Foo-Header: "Unicode in UTF-8 and NFKD"
>
>Which is an all-ASCII description of a potentially non-ASCII
>payload. ...

HTTP headers and mail headers share the same namespace.  Mail software
does not expect non-ASCII header names and Bad Things(tm) would happen
if we started sending mail with UTF-8 names.  EAI keeps ASCII field
names while allowing UTF-8 contents in headers intended to be shown to
people.

Keeping in mind that these names are all intended to be read by
computers, not by people, I don't see what problem they would solve,
but I can see a lot of problems they would cause.

R's,
John

v2.23.0 | Report a Bug | By Email