Re: [ietf-822] A "Reaction" strawman to throw into the mix
Dave Crocker <dhc@dcrocker.net> Tue, 03 November 2020 17:12 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 4783B3A0DF4 for <ietf-822@ietfa.amsl.com>; Tue, 3 Nov 2020 09:12:36 -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 SLSPXzQsIuHB for <ietf-822@ietfa.amsl.com>; Tue, 3 Nov 2020 09:12:33 -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 C3DF83A0DEA for <ietf-822@ietf.org>; Tue, 3 Nov 2020 09:12:33 -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 0A3HFo7D020448 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 3 Nov 2020 09:15:50 -0800
Reply-To: dcrocker@bbiw.net
To: Pete Resnick <resnick@episteme.net>
Cc: ietf-822@ietf.org
References: <B6A2D19C-1790-4ACC-857B-DA4AFD0D4A86@episteme.net> <4457df09-cbf8-f61d-30f0-a7a73f6cd960@dcrocker.net> <F19D70F9-272D-4A4E-8C06-8D3FA1A0EB03@episteme.net>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <c45d75b4-449d-7170-3fa4-8ee43e94464d@dcrocker.net>
Date: Tue, 03 Nov 2020 09:12:18 -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: <F19D70F9-272D-4A4E-8C06-8D3FA1A0EB03@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/4x6sp3meRAw4NPeZwxif_IAqtfk>
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: Tue, 03 Nov 2020 17:12:36 -0000
On 11/2/2020 1:19 PM, Pete Resnick wrote: > On 2 Nov 2020, at 11:24, Dave Crocker wrote: > I don't disagree. However, the semantics provided by MDN is that of > associating a disposition with a particular message, That's what In-Reply-To: does, more generally. > and it has all of > the machinery to do that association. That's what MUA use of In-Reply-To: for threading does. > Associating a reaction with the > original messages seems to me much the same as associating an indication > that a message was "read" or "dispatched" or "deleted". I don't recall seeing a discussion here (or elsewhere) that looked for support of MDNs, that way, in MUAs. > Yes, it > definitely extends the purpose of MDNs, but it doesn't seem like a huge > stretch. Whereas going from a handling semantic to substantive recipient content semantic does seem like quite a basic change to me. >> Adding the ability to have a reply message include content tagged as a >> reaction adds to the semantics of email exchange. > > When I think of reactions, I think of providing a UI to add a "Like" > button or similar. That seems separate to me from replies, and in some That's the problem with focusing on a particular, user-level implementation choice, rather than the underlying semantics -- the 'nature' -- of what is being done. > cases replaces it. Having the the user readable part allows you to do a > reply should you desire, Except that that's not the nature of MDNs. And it's not how they are (typically? Ever?) implemented. > As I said, I agree that this is a change in purpose for MDNs, but I > don't see it as particularly horrible distortion. > > But as I said at the beginning, I can certainly live with Ned's > proposal. MDNs just struck me as cleaner. d/ -- Dave Crocker Brandenburg InternetWorking bbiw.net
- [ietf-822] A "Reaction" strawman to throw into th… Pete Resnick
- Re: [ietf-822] A "Reaction" strawman to throw int… Dave Crocker
- Re: [ietf-822] A "Reaction" strawman to throw int… Dave Crocker
- Re: [ietf-822] A "Reaction" strawman to throw int… John Levine
- Re: [ietf-822] A "Reaction" strawman to throw int… Pete Resnick
- Re: [ietf-822] A "Reaction" strawman to throw int… Alessandro Vesely
- Re: [ietf-822] A "Reaction" strawman to throw int… Dave Crocker