IETF Logo Mail Archive

Re: [ietf-822] What about doing more?

Dave Crocker <dhc@dcrocker.net> Sun, 11 October 2020 12:07 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 BDE1C3A0B0A for <ietf-822@ietfa.amsl.com>; Sun, 11 Oct 2020 05:07:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.113
X-Spam-Level:
X-Spam-Status: No, score=-2.113 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.213, 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 gcDowb0Ysvhf for <ietf-822@ietfa.amsl.com>; Sun, 11 Oct 2020 05:07:24 -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 415153A0B02 for <ietf-822@ietf.org>; Sun, 11 Oct 2020 05:07:24 -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 09BCAaus007343 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 11 Oct 2020 05:10:37 -0700
Reply-To: dcrocker@bbiw.net
To: Ricardo Signes <rjbs@semiotic.systems>
References: <160200472484.32429.1941119190733112214@ietfa.amsl.com> <15666874-46f5-8c01-8ee1-88c5b54f793f@dcrocker.net> <4b3b771d-b47a-4f24-9cc7-35830391c239@www.fastmail.com> <9dc5c8ab-3389-a5cf-aaa2-c26895c9350c@dcrocker.net> <106aecda-a406-4fc5-8d3d-66c3c364edaa@www.fastmail.com>
Cc: ietf-822@ietf.org
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <4be5cd91-6150-80d2-6c9d-e527ab8dee49@dcrocker.net>
Date: Sun, 11 Oct 2020 05:07:18 -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: <106aecda-a406-4fc5-8d3d-66c3c364edaa@www.fastmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-822/SBC_kXSeZy-RnzRnI0ZCk7VyzH0>
Subject: Re: [ietf-822] What about doing more?
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: Sun, 11 Oct 2020 12:07:26 -0000

On 10/8/2020 6:35 PM, Ricardo Signes wrote:
> The Unicode Emoji List is revised more or less annually.  This means 
> that releasing software that validates this header against the contents 
> of UTS #51 is liable to fall out of date.

The RFC series come with an up-pointer reference mechanism for 
replacement versions.  It appears that The Unicode Consortium does not. 
I'd guess the best we can do is to have some generic language associated 
with the reference that says "or a successor".


> ...some system attempts to decode the
> IDN, finds that it contains unallocated code points

How about:

    Reference to unallocated code points SHOULD NOT be treated as an 
error; the associated bytes SHOULD be presented in numeric form.

or some such?

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email