IETF Logo Mail Archive

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

Dave Crocker <dhc@dcrocker.net> Tue, 13 October 2020 13:33 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 32D3B3A0FD5 for <ietf-822@ietfa.amsl.com>; Tue, 13 Oct 2020 06:33:54 -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 h6g3wXmz8ZZh for <ietf-822@ietfa.amsl.com>; Tue, 13 Oct 2020 06:33:53 -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 4E22E3A0FD3 for <ietf-822@ietf.org>; Tue, 13 Oct 2020 06:33:53 -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 09DDb6NY025421 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 13 Oct 2020 06:37:06 -0700
Reply-To: dcrocker@bbiw.net
To: Valdis Klētnieks <valdis.kletnieks@vt.edu>, dcrocker@bbiw.net
Cc: Ricardo Signes <rjbs@semiotic.systems>, ietf-822@ietf.org
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> <4be5cd91-6150-80d2-6c9d-e527ab8dee49@dcrocker.net> <80704.1602463779@turing-police>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <85da904b-bf3a-87a4-6473-ce088a372ed9@dcrocker.net>
Date: Tue, 13 Oct 2020 06:33:45 -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: <80704.1602463779@turing-police>
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/XXzViD4Iy7ipmpBMUry57Tx9uGY>
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: Tue, 13 Oct 2020 13:33:54 -0000

On 10/11/2020 5:49 PM, Valdis Klētnieks wrote:
>> 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?
> "associated bytes SHOULD be presented with the system default method
> for denoting an unallocated or undisplayable code point"

Yeah.  That works.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email