Re: [ietf-822] A "Reaction" strawman to throw into the mix

Dave Crocker <dhc@dcrocker.net> Mon, 02 November 2020 17:24 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 0D2613A0D2F for <ietf-822@ietfa.amsl.com>; Mon, 2 Nov 2020 09:24:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.147
X-Spam-Level:
X-Spam-Status: No, score=-2.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.247, 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 jw081Qn5SarX for <ietf-822@ietfa.amsl.com>; Mon, 2 Nov 2020 09:24:09 -0800 (PST)
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 051343A0D37 for <ietf-822@ietf.org>; Mon, 2 Nov 2020 09:24:08 -0800 (PST)
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 0A2HRXKs019039 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <ietf-822@ietf.org>; Mon, 2 Nov 2020 09:27:33 -0800
Reply-To: dcrocker@bbiw.net
To: ietf-822@ietf.org
References: <B6A2D19C-1790-4ACC-857B-DA4AFD0D4A86@episteme.net>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <4457df09-cbf8-f61d-30f0-a7a73f6cd960@dcrocker.net>
Date: Mon, 02 Nov 2020 09:24:02 -0800
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: <B6A2D19C-1790-4ACC-857B-DA4AFD0D4A86@episteme.net>
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/CPiei_Y-rpoGQDwXe35reMlQ2R0>
Subject: Re: [ietf-822] A "Reaction" strawman to throw into the mix
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: Mon, 02 Nov 2020 17:24:12 -0000

On 10/29/2020 10:49 PM, Pete Resnick wrote:
> it reuses existing pieces of infrastructure that seem to fit this use,

Except that, really, this use is semantically quite different from the 
intended use of MDN (RFC 8098):

>    "...used by a Mail User
>    Agent (MUA) or electronic mail gateway to report the disposition of a
>    message after it has been successfully delivered to a recipient."



The goal of indicating a recipient's reaction is quite different from 
indicating disposition of a message.  The term "laying violation" comes 
to mind, in spite of this not quite being a matter of layers.


In structural terms, the MDN is also a more constrained environment than 
a general email message.  Hence, using it for reactions limits the 
context for including reactions.


Adding the ability to have a reply message include content tagged as a 
reaction adds to the semantics of email exchange.

Having a message designed for signaling information, about message 
handling, be modified to include end-user reactions distorts its 
original purpose and limits the added function.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net