[ietf-822] What about doing more? (was: Re: Fwd: New Version Notification for draft-crocker-inreply-react-01.txt)
Dave Crocker <dhc@dcrocker.net> Thu, 08 October 2020 18:13 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 525273A0BBC for <ietf-822@ietfa.amsl.com>; Thu, 8 Oct 2020 11:13:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 bbch3oG7Xrz7 for <ietf-822@ietfa.amsl.com>; Thu, 8 Oct 2020 11:13:13 -0700 (PDT)
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 B622C3A0BB3 for <ietf-822@ietf.org>; Thu, 8 Oct 2020 11:13:13 -0700 (PDT)
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 098IGQJI007223 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <ietf-822@ietf.org>; Thu, 8 Oct 2020 11:16:26 -0700
Reply-To: dcrocker@bbiw.net
To: ietf-822@ietf.org
References: <160200472484.32429.1941119190733112214@ietfa.amsl.com> <15666874-46f5-8c01-8ee1-88c5b54f793f@dcrocker.net> <4b3b771d-b47a-4f24-9cc7-35830391c239@www.fastmail.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <9dc5c8ab-3389-a5cf-aaa2-c26895c9350c@dcrocker.net>
Date: Thu, 08 Oct 2020 11:13:08 -0700
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: <4b3b771d-b47a-4f24-9cc7-35830391c239@www.fastmail.com>
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/tmFa_umR27G4YF8xk3hxSkhLckA>
Subject: [ietf-822] What about doing more? (was: Re: 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 18:13:15 -0000
(this is an open note, not directed at anyone in particular.) <rant> The draft specifies a simple header field, to be added to a regular email message. There have been a number of suggestions looking to make enhancements to this basic model. Thee suggestions are all predicated on reasonable thoughts, but they wind up altering the nature of the basic proposal. They create basic limitations to extensibility or usability, such as by not having this be a regular email message. Or they start the slide down a slope of complexity by what really is the start of an effort to replicate functions that are likely to be useful -- or already are -- but which are separate from signalling a reaction. The basic proposal is intentionally simplistic and incremental. Just add a place for signaling a reaction. Everything else about the message is left unspecified because... it's a regular email message. Add or don't add whatever would be in a regular email message. A regular email message might or might not have a Subject line. It might or might not have a body. The body might or might not be complex, such as including an entire survey form. It's regular email. </rant> <plea> What will make the basic mechanism useful to its specific goal, sufficient as a specification, reasonable to implement, and as simple as possible without defeating its other goals? </plea> d/ ps. besides the encoding issue, which certainly satisfies the plea, another one in the works modifies the emoji details a bit. A useful bit. But only a bit. -- Dave Crocker Brandenburg InternetWorking bbiw.net
- [ietf-822] Fwd: New Version Notification for draf… Dave Crocker
- Re: [ietf-822] Fwd: New Version Notification for … Dave Crocker
- Re: [ietf-822] Fwd: New Version Notification for … John Levine
- Re: [ietf-822] Fwd: New Version Notification for … Dave Crocker
- Re: [ietf-822] Fwd: New Version Notification for … John Levine
- Re: [ietf-822] Fwd: New Version Notification for … Keith Moore
- Re: [ietf-822] Fwd: New Version Notification for … John Levine
- Re: [ietf-822] Fwd: New Version Notification for … Keith Moore
- Re: [ietf-822] Fwd: New Version Notification for … Ricardo Signes
- [ietf-822] What about doing more? (was: Re: Fwd: … Dave Crocker
- Re: [ietf-822] What about doing more? (was: Re: F… Ricardo Signes
- Re: [ietf-822] What about doing more? (was: Re: F… Brandon Long
- Re: [ietf-822] What about doing more? Dave Crocker
- Re: [ietf-822] What about doing more? Dave Crocker
- Re: [ietf-822] What about doing more? Valdis Kl ē tnieks
- Re: [ietf-822] What about doing more? (was: Re: F… John Levine
- Re: [ietf-822] What about doing more? (was: Re: F… Ricardo Signes
- Re: [ietf-822] What about doing more? Dave Crocker
- Re: [ietf-822] What about doing more? (was: Re: F… Dave Crocker
- Re: [ietf-822] What about doing more? (was: Re: F… John Levine
- Re: [ietf-822] What about doing more? Hector Santos