IETF Logo Mail Archive

Re: [ietf-822] What about doing more? (was: Re: Fwd: New Version Notification for draft-crocker-inreply-react-01.txt)

Dave Crocker <dhc@dcrocker.net> Tue, 13 October 2020 13:38 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf-822@ietfa.amsl.com
Delivered-To: ietf-822@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAE0A3A0FE4 for <ietf-822@ietfa.amsl.com>; Tue, 13 Oct 2020 06:38:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.112
X-Spam-Level:
X-Spam-Status: No, score=-2.112 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.213, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 3do4dajKIl9W for <ietf-822@ietfa.amsl.com>; Tue, 13 Oct 2020 06:38:01 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 45EFB3A0FD6 for <ietf-822@ietf.org>; Tue, 13 Oct 2020 06:38:01 -0700 (PDT)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net [24.130.62.181]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1.1) with ESMTP id 09DDfGLA025942 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <ietf-822@ietf.org>; Tue, 13 Oct 2020 06:41:16 -0700
Reply-To: dcrocker@bbiw.net
To: ietf-822@ietf.org
References: <20201012024430.EBB4F23493C8@ary.qy> <7f40d841-b42e-46b9-a085-63ff4858623f@www.fastmail.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <3795a81a-d13d-8e4a-2ba7-20bc987f1a1d@dcrocker.net>
Date: Tue, 13 Oct 2020 06:37:56 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1
MIME-Version: 1.0
In-Reply-To: <7f40d841-b42e-46b9-a085-63ff4858623f@www.fastmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-822/Ht8PyMWo9Sk_17bM2CkiPom59Dk>
Subject: Re: [ietf-822] What about doing more? (was: Re: Fwd: New Version Notification for draft-crocker-inreply-react-01.txt)
X-BeenThere: ietf-822@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Internet Message Format \[RFC 822, RFC 2822, RFC 5322\]" <ietf-822.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-822/>
List-Post: <mailto:ietf-822@ietf.org>
List-Help: <mailto:ietf-822-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Oct 2020 13:38:03 -0000

On 10/11/2020 8:49 PM, Ricardo Signes wrote:
> On Sun, Oct 11, 2020, at 10:44 PM, John Levine wrote:
>> If they haven't already figured out that it's a fool's errand to
>> validate Unicode beyond broad rules like don't allow surrogates in
>> UTF-8, they're not going to figure it out for this tiny hack.
> 
> I believe this says "It is not worth including that."

This thread seems to be about a concern that an implementor will not 
know how to properly deal with Unicode.  No doubt that's a valid issue, 
but this specification isn't the place to fix this.  Unicode is a 
discrete (and complex) topic.

Basic tutorials or cautions about it don't belong in a specification 
like this.

If there is a statement to include, it should be a very general, 
non-normative pointer to background information about Unicode or Unicode 
technical issues.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email