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

John C Klensin <john@jck.com> Wed, 22 July 2020 16:54 UTC

Return-Path: <john@jck.com>
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 29C973A0B0E for <ietf-smtp@ietfa.amsl.com>; Wed, 22 Jul 2020 09:54:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 ber36T6XSmEU for <ietf-smtp@ietfa.amsl.com>; Wed, 22 Jul 2020 09:54:12 -0700 (PDT)
Received: from bsa3.jck.com (bsa3.jck.com [65.175.133.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 022DE3A0B10 for <ietf-smtp@ietf.org>; Wed, 22 Jul 2020 09:54:11 -0700 (PDT)
Received: from hp5.int.jck.com ([198.252.137.153] helo=JcK-HP5.jck.com) by bsa3.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john@jck.com>) id 1jyI0O-0002cq-At; Wed, 22 Jul 2020 12:54:08 -0400
Date: Wed, 22 Jul 2020 11:42:01 -0400
From: John C Klensin <john@jck.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>, dcrocker@bbiw.net
cc: Seth Blank <seth@valimail.com>, ietf-smtp <ietf-smtp@ietf.org>
Message-ID: <2B53C8F2BD584FE507D9B4FB@JcK-HP5>
In-Reply-To: <f750a1ff-a341-090e-048c-d78ab077e4a4@isode.com>
References: <ead2de74-68be-144c-1a6a-4d55e3ab59c2@isode.com> <d9373795-7119-1ada-acc5-d564bf7ff793@dcrocker.net> <f750a1ff-a341-090e-048c-d78ab077e4a4@isode.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/AGK-yxPMGwPb_lbRC5u8_6ehZ9A>
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 16:54:13 -0000


--On Wednesday, 22 July, 2020 13:22 +0100 Alexey Melnikov
<alexey.melnikov@isode.com> wrote:

> On 22/07/2020 13:16, Dave Crocker wrote:
> 
>> On 7/22/2020 5:07 AM, Alexey Melnikov wrote:
>>> This working group will conduct that limited review and
>>> revision, and  publish new versions of these documents at
>>> Internet Standard status,  per RFC 6410. The limited review
>>> is restricted to include corrections  and clarifications
>>> only, such as verified errata and errata marked as  "held
>>> for document update", however the WG is not limited to only 
>>> addressing submitted errata. No new protocol extensions or
>>> amendments  will be considered for inclusion into 5321bis
>>> and 5322bis documents,  unless they are already published as
>>> RFCs.
>> 
>> 
>> Possible refinement to the wording of this paragraph:
>> 
>> This working group will conduct that limited review and
>> revision, 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.
> 
> I think this is a good suggestion. So I like your version.

If you use that, two suggestions (one a repeat of one made
earlier):

(1) In the last few words, change to "published as standards
track RFCs", because that is what 2026/6410, AFAICT, require.

(2) Be careful about newly-offered errata.  The obvious (at
least to me) reading of that is that the way to get something
onto the WG agenda is to submit an erratum through the RFC
Editor system and have author(s) and AD(s) evaluate it and agree
on a status before the WG can proceed to decide whether to
consider the item.  Seems to me that would be a considerable
waste of time for no good purpose (unless, of course, the
submitter gets points somewhere for posting errata).  So some
clarification to the effect that newly-discovered errors in the
document can be brought to the WG mailing list for review may be
in order.

best,
   john