IETF Logo Mail Archive

Re: [ietf-822] Fwd: New Version Notification for draft-crocker-inreply-react-02.txt

Ned Freed <ned.freed@mrochek.com> Fri, 16 October 2020 23:08 UTC

Return-Path: <ned.freed@mrochek.com>
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 8565D3A083A for <ietf-822@ietfa.amsl.com>; Fri, 16 Oct 2020 16:08:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-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 (1024-bit key) header.d=mrochek.com
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 0rtX6Z3tJavl for <ietf-822@ietfa.amsl.com>; Fri, 16 Oct 2020 16:07:58 -0700 (PDT)
Received: from plum.mrochek.com (plum.mrochek.com [172.95.64.195]) (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 5210D3A082C for <ietf-822@ietf.org>; Fri, 16 Oct 2020 16:07:58 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RQVRJOFF5C002JGY@mauve.mrochek.com> for ietf-822@ietf.org; Fri, 16 Oct 2020 16:02:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mrochek.com; s=201712; t=1602889374; bh=rscQPRe+pocErjH1+Q0toJT42YuOSloIlMhWAvO3ZDE=; h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=gLCPBg5MtZepUvjKszKDMkQrG1RsSQTgok8wkMVc1BHbbJzQuZ0BQJnlb86ZaxWIy xNcv3vnGnuB1NcEBzbaXVK+whFxdmum6d5VWZ/mUfGw9yibABZzIg6F8wCVFzWBndy 08D7qbTFvceVX6mb/oYa74m2M2OGwl/VdGxfSE88=
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: TEXT/PLAIN; CHARSET="us-ascii"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RQN4TDY6V4005PTU@mauve.mrochek.com>; Fri, 16 Oct 2020 16:02:52 -0700 (PDT)
Cc: ietf-822@ietf.org, dcrocker@bbiw.net
Message-id: <01RQVRJMP1T2005PTU@mauve.mrochek.com>
Date: Fri, 16 Oct 2020 16:01:38 -0700
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Fri, 16 Oct 2020 18:33:29 -0400" <20201016223329.CD0202388361@ary.qy>
References: <8e06bde3-b344-466f-8ac8-313d70436cb4@dcrocker.net> <20201016223329.CD0202388361@ary.qy>
To: John Levine <johnl@taugh.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-822/bWL2YTGIPgbLuNAon6xIZnE02r4>
Subject: Re: [ietf-822] 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: Fri, 16 Oct 2020 23:08:02 -0000

> In article <8e06bde3-b344-466f-8ac8-313d70436cb4@dcrocker.net> you write:
> >Note -- Diff:
> >
> >      https://www.ietf.org/rfcdiff?url2=draft-crocker-inreply-react-02

> Looks better but this part is still wrong:

>    Fully interoperable email uses 7-bit ASCII, although some email
>    handling paths directly support 8-bit data.  Emoji characters are
>    drawn from the space outside of 7-bit ASCII.  For email handling
>    paths that are 8-bit clean, the an emoji character does not need
>    special encoding. If the path from author to recipients is not known
>    to be 8-bit clean, The emoji character SHOULD be encoded using
>    [MIME-Enc].

> In non-EAI mail there is no rule about interpreting 8-bit stuff other
> than that it is invalid, and definitely no rule that assumes it is
> encoded as UTF-8. I have no idea whether there are other character
> sets that have emoji, and I don't think any of us want to waste time
> finding out.

UTF-EBCDIC is one such.

   <ducks and runs>

>  Ergo:

>    In messages that are not Internationalized [RFC6532], emoji and any
>    other non-ASCII characters MUST be encoded using [MIME-Enc].

+1

				Ned

v2.23.0 | Report a Bug | By Email