Re: [Last-Call] Benjamin Kaduk's Discuss on draft-crocker-inreply-react-08: (with DISCUSS and COMMENT)

Kjetil Torgrim Homme <kjetilho@ifi.uio.no> Thu, 04 March 2021 08:41 UTC

Return-Path: <kjetilho@ifi.uio.no>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11E573A167B; Thu, 4 Mar 2021 00:41:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 RKSC0IshFY3d; Thu, 4 Mar 2021 00:41:40 -0800 (PST)
Received: from mail-out01.uio.no (mail-out01.uio.no [IPv6:2001:700:100:10::50]) (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 7A8F73A1675; Thu, 4 Mar 2021 00:41:40 -0800 (PST)
Received: from mail-mx10.uio.no ([129.240.10.27]) by mail-out01.uio.no with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93.0.4) (envelope-from <kjetilho@ifi.uio.no>) id 1lHjY2-0003Va-6T; Thu, 04 Mar 2021 09:41:30 +0100
Received: from wireguard.i.bitbit.net ([87.238.42.12] helo=comm.ms.redpill-linpro.com) by mail-mx10.uio.no with esmtpsa (TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256) user kjetilho (Exim 4.93.0.4) (envelope-from <kjetilho@ifi.uio.no>) id 1lHjY1-0002X9-DJ; Thu, 04 Mar 2021 09:41:30 +0100
Message-ID: <f66e48607d89190f341ed31f5d39201b72c661ba.camel@ifi.uio.no>
From: Kjetil Torgrim Homme <kjetilho@ifi.uio.no>
To: Benjamin Kaduk <kaduk@mit.edu>, Dave Crocker <dcrocker@bbiw.net>
Cc: last-call@ietf.org, todd.herr@valimail.com, Barry Leiba <barryleiba@computer.org>, The IESG <iesg@ietf.org>, draft-crocker-inreply-react@ietf.org
Date: Thu, 04 Mar 2021 09:41:24 +0100
In-Reply-To: <20210304015015.GL56617@kduck.mit.edu>
References: <dbb0a7b2-07fc-348b-4e39-f5b3ff92a2c9@gmail.com> <20210225191159.GU21@kduck.mit.edu> <ef24bc92-b869-3882-d704-a44e4872c5f2@gmail.com> <CAC4RtVDRj_v2Jv9wixGtaLqVr+Q0Qg-z8rSQvRruJyhvVK9dFw@mail.gmail.com> <20210303191115.GG56617@kduck.mit.edu> <0e2a50e5-6f7d-a5c2-acf4-2be4fe34605c@bbiw.net> <20210303200117.GH56617@kduck.mit.edu> <13aca853-9466-81ae-9b8a-d403b49ecc79@bbiw.net> <20210303202035.GI56617@kduck.mit.edu> <9caa51e9-17e9-cb0e-dbba-79b148d40553@bbiw.net> <20210304015015.GL56617@kduck.mit.edu>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.5 (3.36.5-2.fc32)
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-UiO-SPF-Received: Received-SPF: neutral (mail-mx10.uio.no: 87.238.42.12 is neither permitted nor denied by domain of ifi.uio.no) client-ip=87.238.42.12; envelope-from=kjetilho@ifi.uio.no; helo=comm.ms.redpill-linpro.com;
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, AWL=0.019, UIO_MAIL_IS_INTERNAL=-5)
X-UiO-Scanned: B14F082B94F8640A177AE0110C2ECDA4905AF823
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/wvsurlZyn70ZMbHL33o6mt3uW_8>
Subject: Re: [Last-Call] Benjamin Kaduk's Discuss on draft-crocker-inreply-react-08: (with DISCUSS and COMMENT)
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Mar 2021 08:41:43 -0000

On Wed, 2021-03-03 at 17:50 -0800, Benjamin Kaduk wrote:
> I would be happy to suggest better wording ... if I knew which to things
> are indicated by the "both" in "both are present".  I think it's two of:
> emoji as the content of a message part, the In-Reply-To header field, the
> Content-Disposition: Reaction header field, the message being responded to,
> and the message conveying the response.  But which two?

Let me take a stab at it.  First the current text in the tracker:

  2.  Reaction Content-Disposition

     A message sent as a reply MAY include a part containing:

     Content-Disposition: Reaction
[...]
     The emoji(s) express a recipient's summary reaction to the
specific
     message referenced by the accompanying In-Reply-To header field,
for
     the message in which they both are present.  [Mail-Fmt].  For
     processing details, see Section 3.

First I'd like to say - whenever there is a ambiguity in such
introductory text, read the detailed processing instructions to resolve
them.  But I think we can resolve this by replacing "both" with "both
the Reaction part and the In-Reply-To header field".

Sort of unrelated - from the processing instructions:

   2.  If R's In-Reply-To: does reference one, then check R's message
       content for a part with a "reaction" Content-Disposition header
       field, at either the outermost level or as part of a multipart
at
       the outermost level.

This means a forwarded message will *not* get its embedded reactions
processed.  Well, forwarded messages will typically not have I-R-T set,
but if a message includes previous correspondence as an attached MIME
document.  However, In-reply-to in messages in the attached
correspondence will get their reactions processed if they are at the
correct relative level in the structure.

Please correct me if I am wrong, Dave.  If this is *not* the intention,
I think step 1 in the processing instructions need to state this only
applies to I-R-T found at the top level of the message.

-- 
venleg helsing,
Kjetil T.