IETF Logo Mail Archive

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

"John R Levine" <johnl@taugh.com> Tue, 04 February 2020 01:32 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 1CA1212004A for <i18ndir@ietfa.amsl.com>; Mon, 3 Feb 2020 17:32:49 -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=MtgM28KP; dkim=pass (1536-bit key) header.d=taugh.com header.b=Y2lYHx3d
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 lhdmZob0uRSf for <i18ndir@ietfa.amsl.com>; Mon, 3 Feb 2020 17:32:47 -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 4F5B112001A for <i18ndir@ietf.org>; Mon, 3 Feb 2020 17:32:47 -0800 (PST)
Received: (qmail 37987 invoked from network); 4 Feb 2020 01:32:46 -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=9460.5e38c9be.k2002; i=johnl-iecc.com@submit.iecc.com; bh=OOs08bQy1zKnSAHRG4KulR2328ML/lGxSDSMaScVUCc=; b=MtgM28KP1QgVgDOVu3d4bd4eovrUV/pEjdf9dUVK9mWqfmec3sor0FzOqmYXhdYjNJDLGwWYdH50JfMU72IX6pjj52IxTN1HsQmiYuJo+qaPIsWFkhINQc7ehS2CQi6TrLi5a8LkqvPR65vHWYYg7Xfjv5a+v5h7BzwFzaimVy6BaHCVkbqH/meZvQuQk8S+WTEUSX4LJRYCRqsX0nmgUKWrkXzxcahiVm1p9oamIKZmadb8RKBYmDNqWPK8epq+
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=9460.5e38c9be.k2002; olt=johnl-iecc.com@submit.iecc.com; bh=OOs08bQy1zKnSAHRG4KulR2328ML/lGxSDSMaScVUCc=; b=Y2lYHx3daZ1l48DafZ+nUaG/Re5HKLPMjngJNS/SFXl2QW/5kqVa4z0B/2csx+q3Djqzi2ULCCqn3/8+I3DNJ9FuCCrjlgUtgudqc/jtv3008p18nY5EThTPoszb+heuBoLa5fOVuJ9tvvN1gDez71zplM9dW1jT0jHCrLcdAcxcxDPezVfxTrrlAgFv8Pjc5F3cq41oY20zY9WAoE3BFlU83GHWuqVJYFSYNDrXhJ7ILWrqlReybVov9M+8fFA4
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 01:32:46 -0000
Date: Mon, 03 Feb 2020 20:32:45 -0500
Message-ID: <alpine.OSX.2.21.99999.374.2002032032270.32304@ary.qy>
From: John R Levine <johnl@taugh.com>
To: John C Klensin <john-ietf@jck.com>
Cc: i18ndir@ietf.org
In-Reply-To: <D03AE38116EF15538E10CFAF@PSB>
References: <20200203173404.88EE813AA055@ary.qy> <E2361F8BA970A15043416C2D@PSB> <alpine.OSX.2.21.99999.374.2002031653540.31381@ary.qy> <D03AE38116EF15538E10CFAF@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/_64miDA9h04GWn88xbR7iQjVcDA>
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: Tue, 04 Feb 2020 01:32:49 -0000

>> In section 3.3.3 it says that non-ASCII text is to be encoded
>> as base64, which seems reasonable, "along with a character
>> encoding (preferably UTF-8)" but it doesn't have any
>> convention for where the encoding goes. Experience with MIME
>> suggests that life is simpler if there's a standard form for
>> an encoded text blob so libraries can decode and if need be
>> transliterate in one go.
>
> And omission of a clear model for specifying what is really what
> we call a "charset" elsewhere (not just an encoding) is the one
> clear defect in that particular discussion in the document.
>
> Seems to me that, unless there is a desire to reinvent the
> wheel, using the encoded word model of RFC 2231 (or something
> very much like it)  but strictly with Base64, would be the right
> way to go.

Agreed.  Anyone offering to tell them?

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

v2.23.0 | Report a Bug | By Email