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

Ricardo Signes <rjbs@semiotic.systems> Thu, 08 October 2020 12:19 UTC

Return-Path: <rjbs@semiotic.systems>
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 7D8B73A0D98 for <ietf-822@ietfa.amsl.com>; Thu, 8 Oct 2020 05:19:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=semiotic.systems header.b=1Y5anN5A; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=jMKWV+ol
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 lq3nILZLFBTp for <ietf-822@ietfa.amsl.com>; Thu, 8 Oct 2020 05:19:25 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 916823A0D96 for <ietf-822@ietf.org>; Thu, 8 Oct 2020 05:19:25 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id AA33A5C0221 for <ietf-822@ietf.org>; Thu, 8 Oct 2020 08:19:24 -0400 (EDT)
Received: from imap35 ([10.202.2.85]) by compute5.internal (MEProxy); Thu, 08 Oct 2020 08:19:24 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= semiotic.systems; h=mime-version:message-id:in-reply-to :references:date:from:to:subject:content-type; s=fm2; bh=gsaUcRX 22P5x8qhPOdEU0D6tg8kg8o2lcyrdmaqj/y0=; b=1Y5anN5Apls2I/ePTXwS7g7 v7/0I+AXgm27LlShzcCiDjA/keITArdwq/h2BOSLwmLNtHkPJZWq3fcnXzIff1+9 cgcFBqdl2DuPh0ADNYhahwFhQbYx6uM1i73AEHa74hEn9HDcGraEAF0v18iHEp+i rtIneJL4Qlk93qqaTmId2BlABaXJ5USE8p8RkeQHtITdlbkgJr239Jv5/j1ba0CR svFvJLQ1q7Van64d4k1UZrtOOmOTsS9mKUPY5V/jNnAeKfxWUQeoXIowz3PVgD6o c6qRlCOTQb2tMKf6hmmnVa8vjApEO+F9zNTxY7NGNrjsIj6yQ9I+zN8gjd97iNw= =
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=gsaUcR X22P5x8qhPOdEU0D6tg8kg8o2lcyrdmaqj/y0=; b=jMKWV+ol5t4IlS436utGZ+ yOCXpDYsmcF3Tfb3c3NOvjdzaxljcrRYRXf956PDJk/iUorOCAYXuSaCR4bJaK18 3zFBu2DVS63jYqR+lyYS2Rcd01tzRObEB6XtXcovAfXJNwOrEA1uycKZj9QFE7Lh GlSwNYYmlInIl5z97WUjEruR3v9wH8XLMWgU7o6rW/CZkSGBhLQR4leFFwq3BrZ9 230KplG5MYhZ68Z/VMCxZYqJcCzkKI8EyadbDyt8d4NsV3ksdfgBosZVt49opnGC iPYdLxmKlCkaMtWPxwcPtDU1xbg54sqxxxsywRpg8fFkOaGAYnbgGlG9c6XKkD7Q ==
X-ME-Sender: <xms:zAN_X96JHQ8OG8fvyf6Q0RC7InSJZTkOB0CrpM1Z_C7hz8gNbkcAaA> <xme:zAN_X65DD95x5GrAu-0xMzGkSWy6xMQXAGEwhIqr7ESJyBiQwcKTPVI6lFqNRnFCG UbEzuqP3w2A33ANie4>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrgeelgddvfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrgdtre erreerjeenucfhrhhomhepfdftihgtrghrughoucfuihhgnhgvshdfuceorhhjsghssehs vghmihhothhitgdrshihshhtvghmsheqnecuggftrfgrthhtvghrnhepgeejffduueekhf ffgfdvtedvhfefkeegieduleduueelkefhkefgveefueehvddunecuffhomhgrihhnpehi vghtfhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehrjhgsshesshgvmhhiohhtihgtrdhshihsthgvmhhs
X-ME-Proxy: <xmx:zAN_X0d9FoNiUP4DgEAuRP9vVtFHhS-LC-M86Z5SluO-MWG0MGZB1g> <xmx:zAN_X2KNeFlUeNfFwSzcSNPfe7Bn3rFs8EjPP2XnpmPLs9Y_qowm_w> <xmx:zAN_XxID9vVk3JNEmlbza60U0UMwP5c1CpFalNDHbwGFkC0kT1FT7A> <xmx:zAN_X2US1qa5tAQ1nqFdkxZhauCjW5bMZbbuKDAmRciZKk4wzI3hfw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 365F714C09B3; Thu, 8 Oct 2020 08:19:24 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-407-g461656c-fm-20201004.001-g461656c6
Mime-Version: 1.0
Message-Id: <4b3b771d-b47a-4f24-9cc7-35830391c239@www.fastmail.com>
In-Reply-To: <15666874-46f5-8c01-8ee1-88c5b54f793f@dcrocker.net>
References: <160200472484.32429.1941119190733112214@ietfa.amsl.com> <15666874-46f5-8c01-8ee1-88c5b54f793f@dcrocker.net>
Date: Thu, 08 Oct 2020 08:19:03 -0400
From: Ricardo Signes <rjbs@semiotic.systems>
To: ietf-822@ietf.org
Content-Type: multipart/alternative; boundary="b430cf85693d484180b46932a4d4e82e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-822/8UPbJox7FGQYCiexyxKrWcI2ZiI>
Subject: Re: [ietf-822] 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: Thu, 08 Oct 2020 12:19:28 -0000

On Tue, Oct 6, 2020, at 1:23 PM, Dave Crocker wrote:
> Note:
> 
> Diff:  https://www.ietf.org/rfcdiff?url2=draft-crocker-inreply-react-01

A coworker and I had -just- been discussing a nearly identical idea.  I mentioned it to Bron, who mentioned this draft to me.

I just had two things I thought might be worth chiming in on:

First:  This one is a bit tedious, but since I was going to post here anyway:  the definition of emoji should refer to emoji characters *and sequences*, lest it omit lots of non-single-character emoji.  (Even the humble red heart is more than one character.)

The other thought was about the question of what goes in the body.  Specifically, we discussed a means to distinguish "Look, I just want to send 👍🏽 and nothing else" from "I would like to write a treatise on the ways in which I agree, but if you are not prepared to bask in the glory of my prose, I guess you can summarize it as 👍🏽".  This would allow (for example) a means to count up reactions of a type, even when there's content, and would also allow user agents to avoid drawing whole messages when the content was trivial.  Something like "Header-Contains-Whole-Message: yes" would sum that up, meaning "reaction if provided, otherwise subject".  It's out of scope for this draft as written, but I think multiplies the draft's value.

-- 
rjbs