IETF Logo Mail Archive

[ietf-822] More encoding (was Re: Fwd: New Version Notification for draft-crocker-inreply-react-02.txt)

Dave Crocker <dhc@dcrocker.net> Sun, 18 October 2020 19:39 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 B65533A0ACD for <ietf-822@ietfa.amsl.com>; Sun, 18 Oct 2020 12:39:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[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 Qt9H6g8lne3e for <ietf-822@ietfa.amsl.com>; Sun, 18 Oct 2020 12:39:19 -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 BBFAB3A0AD3 for <ietf-822@ietf.org>; Sun, 18 Oct 2020 12:39:17 -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 09IJgYi4002561 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <ietf-822@ietf.org>; Sun, 18 Oct 2020 12:42:35 -0700
Reply-To: dcrocker@bbiw.net
To: ietf-822@ietf.org
References: <8e06bde3-b344-466f-8ac8-313d70436cb4@dcrocker.net> <20201016223329.CD0202388361@ary.qy> <01RQVRJMP1T2005PTU@mauve.mrochek.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <5504edd0-57c2-ed94-07a0-402a655e9ad8@dcrocker.net>
Date: Sun, 18 Oct 2020 12:39:12 -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: <01RQVRJMP1T2005PTU@mauve.mrochek.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/PTzjge-CTjVlWKlI2tsShRcPVvM>
Subject: [ietf-822] More encoding (was Re: Fwd: New Version Notification for draft-crocker-inreply-react-02.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: Sun, 18 Oct 2020 19:39:21 -0000

On 10/16/2020 4:01 PM, Ned Freed wrote:
>>     In messages that are not Internationalized [RFC6532], emoji and any
>>     other non-ASCII characters MUST be encoded using [MIME-Enc].
> +1

Drat.  Thought I'd included the text for this.


However, I just got an offlist suggestion I'd like to get reactions to:

> ... consider allowing the emoji to be specified (one option) as
> "U+1F44D", so:
>    In-Reply-React: U+1F44D U+1F622


The plus is that it's extremely simple, and works nicely for short 
sequences like this.

The minus is that it's not 'standard'.

Thoughts?

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email