Re: [ietf-822] What about doing more?

Dave Crocker <dhc@dcrocker.net> Sun, 11 October 2020 01: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 4EF3C3A0D7E for <ietf-822@ietfa.amsl.com>; Sat, 10 Oct 2020 18:24:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.113
X-Spam-Level:
X-Spam-Status: No, score=-2.113 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.213, 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 weQ4exftZpw3 for <ietf-822@ietfa.amsl.com>; Sat, 10 Oct 2020 18:24:51 -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 4F97C3A0D82 for <ietf-822@ietf.org>; Sat, 10 Oct 2020 18:24:47 -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 09B1Rr5w026699 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 10 Oct 2020 18:27:53 -0700
Reply-To: dcrocker@bbiw.net
To: Brandon Long <blong@google.com>, Dave Crocker <dcrocker@bbiw.net>
Cc: 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> <9dc5c8ab-3389-a5cf-aaa2-c26895c9350c@dcrocker.net> <CABa8R6vK+movetP6AjX+fVNCLAiH4kLi97qhQa0+kTF+vz__zA@mail.gmail.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <f9181f88-9d59-0e96-d0ee-270752d1f985@dcrocker.net>
Date: Sat, 10 Oct 2020 18:24:33 -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: <CABa8R6vK+movetP6AjX+fVNCLAiH4kLi97qhQa0+kTF+vz__zA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-822/H8RGchakHSW8_cDPf4XszF0mW-M>
Subject: Re: [ietf-822] What about doing more?
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: Sun, 11 Oct 2020 01:24:56 -0000

On 10/8/2020 11:58 PM, Brandon Long wrote:
> So, I don't have extensive usage of these other systems or ones beyond 
> these, but the simple spec seems to satisfy
> the majority of the examples.  Hopefully others will speak up if other 
> systems do more than this.


Thanks for the review of existing practice.  It's good to have something 
like that in the list archive and even better to have it discussed.

There are a number of directions extensibility could take, here.  Each 
one will have some appeal. Maybe a lot.

The danger in any exercise like this is trying to guess which 
capabilities are best to include or -- much worse -- trying to include 
all of them -- or at least, someone's guess at what all of them are 
(is?)  Possibly demonstrating a bit of cultural bias, on my part, I tend 
to call that the OSI approach...

However there is quite a bit of history suggesting that it is best to 
start with something that is distinctly simple -- and even simplistic -- 
at first, to make it easy to develop and deploy, getting basic field 
experience.  Typically, that means starting with the smallest capability 
that is deemed useful.

Best of all is to start with something that is already established, 
while leaving room for /future/ extensions, based on actual demand. For 
the current draft, I tossed in a simple, non-normative rule with a set 
of emojis that already have an established base of experience.

If this gets deployed and used, and there is a community outcry -- or at 
least a polite, cohesive request -- for one particular kind of 
enhancement or another, that enhancement is likely to be easy.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net