Re: [ietf-smtp] Proposed Charter for EMAILCORE WG-to-be

Dave Crocker <dhc@dcrocker.net> Wed, 22 July 2020 12:32 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EFF53A0B35 for <ietf-smtp@ietfa.amsl.com>; Wed, 22 Jul 2020 05:32:05 -0700 (PDT)
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, NICE_REPLY_A=-0.001, 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 TlvZ7EAwF9GD for <ietf-smtp@ietfa.amsl.com>; Wed, 22 Jul 2020 05:32:04 -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 12DC83A0B4D for <ietf-smtp@ietf.org>; Wed, 22 Jul 2020 05:32:04 -0700 (PDT)
Received: from [192.168.1.67] (108-226-162-63.lightspeed.sntcca.sbcglobal.net [108.226.162.63]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1.1) with ESMTP id 06MCYa2A020057 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 22 Jul 2020 05:34:36 -0700
To: Tim Wicinski <tjw.ietf@gmail.com>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Seth Blank <seth@valimail.com>, ietf-smtp <ietf-smtp@ietf.org>
References: <ead2de74-68be-144c-1a6a-4d55e3ab59c2@isode.com> <d9373795-7119-1ada-acc5-d564bf7ff793@dcrocker.net> <CADyWQ+F+Q_-9fQfSr2MAieLi82PTGr0r+jPPWs5LLygYHROzcA@mail.gmail.com>
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <27410164-6b23-7623-4255-b7306b6d41da@dcrocker.net>
Date: Wed, 22 Jul 2020 05:31:55 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <CADyWQ+F+Q_-9fQfSr2MAieLi82PTGr0r+jPPWs5LLygYHROzcA@mail.gmail.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-smtp/Q28actjnb50xJ6kVlK5C2ixqzJc>
Subject: Re: [ietf-smtp] Proposed Charter for EMAILCORE WG-to-be
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jul 2020 12:32:09 -0000

On 7/22/2020 5:23 AM, Tim Wicinski wrote:
> In the paragraph Dave edited, I for some reason find the word "that" as 
> feeling out of place. I need to read it a few more times.

Just to confirm, I assume you mean:

 > This working group will conduct that limited review and revision, ...

I was trying to preserve as much of the original text as I could and 
didn't even think about this.  In context it works, given the paragraph 
that precedes it.  But it certainly isn't essential.  Also, it's worth 
making the paragraph stand on its own.

So, perhaps...

      This working group will conduct a limited review and revision to 
the base email specifications, and will publish new versions of these 
documents at Internet Standard status, per RFC 6410. The limited review 
is restricted to corrections and clarifications only. In addition to 
processing existing, verified errata and errata marked as "held for 
document update", the WG may address newly-offered errata.  However, no 
new protocol extensions or amendments will be considered for inclusion 
into 5321bis and 5322bis documents, unless they are already published as 
RFCs.


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net