* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Emailcore Status Pages

Revision of core Email specifications (Active WG)
Art Area: Barry Leiba, Murray Kucherawy | 2020-Sep-25 —  

2021-01-26 charter

Revision of core Email specifications (emailcore)


 Current Status: Active

     Alexey Melnikov <alexey.melnikov@isode.com>
     Todd Herr <todd.herr@valimail.com>

 Applications and Real-Time Area Directors:
     Murray Kucherawy <superuser@gmail.com>
     Barry Leiba <barryleiba@computer.org>

 Applications and Real-Time Area Advisor:
     Barry Leiba <barryleiba@computer.org>

 Mailing Lists:
     General Discussion: emailcore@ietf.org
     To Subscribe:       https://www.ietf.org/mailman/listinfo/emailcore
     Archive:            ​https://mailarchive.ietf.org/arch/browse/emailcore/

Description of 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

  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

  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

Goals and Milestones:

All charter page changes, including changes to draft-list, rfc-list and milestones:

Generated from PyHt script /wg/emailcore/charters.pyht Latest update: 24 Oct 2012 16:51 GMT -