Revision of core Email specifications (emailcore) Internet Drafts

      
 Simple Mail Transfer Protocol
 
 draft-ietf-emailcore-rfc5321bis-27.txt
 Date: 26/02/2024
 Authors: John Klensin
 Working Group: Revision of core Email specifications (emailcore)
 This document is a specification of the basic protocol for Internet electronic mail transport. It (including text carried forward from RFC 5321) consolidates, updates, and clarifies several previous documents, making all or parts of most of them obsolete. It covers the SMTP extension mechanisms and best practices for the contemporary Internet, but does not provide details about particular extensions. The document also provides information about use of SMTP for other than strict mail transport and delivery. This document replaces RFC 5321, the earlier version with the same title, and supersedes RFCs 1846, 7504, and 7505, incorporating all the relevant information in them.
 Applicability Statement for IETF Core Email Protocols
 
 draft-ietf-emailcore-as-09.txt
 Date: 18/12/2023
 Authors: John Klensin, Kenneth Murchison, Ekow Sam
 Working Group: Revision of core Email specifications (emailcore)
 Electronic mail is one of the oldest Internet applications that is still in very active use. While the basic protocols and formats for mail transport and message formats have evolved slowly over the years, events and thinking in more recent years have supplemented those core protocols with additional features and suggestions for their use. This Applicability Statement describes the relationship among many of those protocols and provides guidance and makes recommendations for the use of features of the core protocols.
 Internet Message Format
 
 draft-ietf-emailcore-rfc5322bis-11.txt
 Date: 08/04/2024
 Authors: Pete Resnick
 Working Group: Revision of core Email specifications (emailcore)
 This document specifies the Internet Message Format (IMF), a syntax for text messages that are sent between computer users, within the framework of "electronic mail" messages. This specification is a revision of Request For Comments (RFC) 5322, itself a revision of Request For Comments (RFC) 2822, all of which supersede Request For Comments (RFC) 822, "Standard for the Format of ARPA Internet Text Messages", updating it to reflect current practice and incorporating incremental changes that were specified in other RFCs.

data-group-menu-data-url="/group/groupmenu.json">

Revision of core Email specifications (emailcore)

WG Name Revision of core Email specifications
Acronym emailcore
Area Applications and Real-Time Area (art)
State Active
Charter charter-ietf-emailcore-01 Approved
Status update Show Changed 2020-06-25
Document dependencies
Additional resources Issue Tracker, Zulip stream
Personnel Chairs Alexey Melnikov, Todd Herr
Area Director Murray Kucherawy
Mailing list Address emailcore@ietf.org
To subscribe https://www.ietf.org/mailman/listinfo/emailcore
Archive https://mailarchive.ietf.org/arch/browse/emailcore/
Chat Room address https://zulip.ietf.org/#narrow/stream/emailcore

Charter for Working Group

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 (recommended extensions, transport
security and other issues from the UTA working group's output, and such)
and current email practices. 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

Date Milestone Associated documents
Nov 2024 Submit Applicability Statment to the IESG for publication at Proposed Standard draft-ietf-emailcore-as
Jul 2024 Submit RFC5321bis to the IESG for publication at Internet Standard draft-ietf-emailcore-rfc5321bis
May 2024 Submit RFC5322bis to the IESG for publication at Internet Standard draft-ietf-emailcore-rfc5322bis