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 update (last changed 2020-06-25)
Dependencies Document dependency graph (SVG)
Additional Resources
- Issuer Tracker
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/
Jabber chat Room address xmpp:emailcore@jabber.ietf.org?join
Logs https://jabber.ietf.org/logs/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.