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

Alexey Melnikov <alexey.melnikov@isode.com> Wed, 22 July 2020 12:07 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 6E00B3A0AB3 for <ietf-smtp@ietfa.amsl.com>; Wed, 22 Jul 2020 05:07:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id mihHj7aIdTuL for <ietf-smtp@ietfa.amsl.com>; Wed, 22 Jul 2020 05:07:36 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com []) by ietfa.amsl.com (Postfix) with ESMTP id 4D5213A0AB0 for <ietf-smtp@ietf.org>; Wed, 22 Jul 2020 05:07:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1595419655; d=isode.com; s=june2016; i=@isode.com; bh=DXAR0x5GROLDRyehlN+/Xzwl1FUsPmPv9wubn2rlbA0=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=ew4tD4Ibj7v5FEpK5d9uoJzMElyPmI01/+90DhF/aXpMBxwJYUOHKl9ytHtpMnC3RFsxW9 wV6PDNmxpBjR5+Sxz2gyLJZGoBT9byPWqPBxEbjFWUXXW7IZCl1+uWimBEl0G0SwAgcU3i E2pEqFyALyX/4wgm38GLWnwOQ1UA1j8=;
Received: from [] (connect.isode.net []) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <XxgsBgAkBpZR@waldorf.isode.com>; Wed, 22 Jul 2020 13:07:35 +0100
To: ietf-smtp <ietf-smtp@ietf.org>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: Seth Blank <seth@valimail.com>
Message-ID: <ead2de74-68be-144c-1a6a-4d55e3ab59c2@isode.com>
Date: Wed, 22 Jul 2020 13:07:19 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/AxeI3FvFmkBz3rSBz-LiclT-tJc>
Subject: [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:07:41 -0000

Hi all,

My apologies for not sending this earlier.

This is the draft charter I propose for EMAILCORE WG-to-be:


The base documents defining Internet messaging — colloquially, email -- 
are RFC 5321 (protocol) and RFC 5322 (format). These are revisions and 
consolidations of prior documents and were last published in 2008. They 
currently sit at Draft Standard status, a status that actually no longer 
exists according to current IETF procedure.

Since then some errata have accumulated (both submitted to IETF and 
reported directly to editors), as well as comments made about these 
documents not necessarily describing best email practices. There is now 
exists sufficient critical mass to undertake a limited review and 
revision of these documents for the purpose of advancing them to 
Internet Standard status.

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.

The working group will also work on Applicability Statement/BCP in 
parallel with 5321bis and 5322bis, to capture relationships to other 
widely deployed work (for example recommended extensions) and current 
email practices.

Upon completion of these three milestones, and assuming the participants 
still have the momentum to do so, the working group may undertake 
similar review and revision of other email specifications. Such future 
work will require rechartering.


The current plan for the EMAILCORE BOF is to triage existing errata on 
RFC 5321/5322 (to see what kind of issues were raised), discuss exact 
scope of the effort and finish with reviewing the above proposal at the 
end of the EMAILCORE BOF.

Please let me know your comments/thoughts.

Best Regards,