WG Review: Revision of core Email specifications (emailcore)
The IESG <email@example.com> Fri, 11 September 2020 16:41 UTC
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B58FE3A1404; Fri, 11 Sep 2020 09:41:17 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
From: The IESG <firstname.lastname@example.org>
To: "IETF-Announce" <email@example.com>
Subject: WG Review: Revision of core Email specifications (emailcore)
Content-Type: text/plain; charset="utf-8"
Date: Fri, 11 Sep 2020 09:41:17 -0700
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:firstname.lastname@example.org?subject=unsubscribe>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:email@example.com?subject=subscribe>
X-List-Received-Date: Fri, 11 Sep 2020 16:41:18 -0000
A new IETF WG has been proposed in the Applications and Real-Time Area. The IESG has not made any determination yet. The following draft charter was submitted, and is provided for informational purposes only. Please send your comments to the IESG mailing list (firstname.lastname@example.org) by 2020-09-21. Revision of core Email specifications (emailcore) ----------------------------------------------------------------------- Current status: Proposed WG Chairs: Alexey Melnikov <email@example.com> Seth Blank <firstname.lastname@example.org> Assigned Area Director: Barry Leiba <email@example.com> Applications and Real-Time Area Directors: Barry Leiba <firstname.lastname@example.org> Murray Kucherawy <email@example.com> Mailing list: Address: firstname.lastname@example.org To subscribe: https://www.ietf.org/mailman/listinfo/emailcore Archive: https://mailarchive.ietf.org/arch/browse/emailcore/ Group page: https://datatracker.ietf.org/group/emailcore/ Charter: https://datatracker.ietf.org/doc/charter-ietf-emailcore/ 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 no longer exists according to the current IETF procedure. Since then some errata have accumulated (both submitted to IETF and reported directly to editors), as have comments made about these documents not necessarily describing best email practices. There is now 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 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, with a strong emphasis on keeping these minimal and avoiding broader changes to terminology or document organization. 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 IETF Stream RFCs and are at sufficient maturity level to move to Internet Standard. The working group will also work on an Applicability Statement in parallel with 5321bis and 5322bis, to capture relationships to other documented and widely deployed work (such as recommended extensions) and current email practices, including transport security and other issues from the UTA working group's output. 5321bis and 5322bis will be submitted for publication before this document is finalized, and the "bis" documents will have priority for the working group's attention until they are finished. Upon completion of these three milestones, and assuming there is still the momentum to do so, the working group may undertake similar review and revision of other email specifications. Such future work will require rechartering. Milestones: TBD