Mail Extensions (mailext)
-------------------------
Charter
Last Modified: 06/05/2000
Current Status: Concluded Working Group
Chair(s):
J. Cargille <allan@internetMCI.com>
Applications Area Director(s):
Ned Freed <ned.freed@mrochek.com>
Patrik Faltstrom <paf@cisco.com>
Applications Area Advisor:
Ned Freed <ned.freed@mrochek.com>
Mailing Lists:
General Discussion:mailext@list.cren.net
To Subscribe: listproc@list.cren.net
In Body: subscribe mailext Firstname Lastname
Archive:
Description of Working Group:
The Mail Extensions Working Group will review, refine as
needed, and then make a recommendation on standardization of several
recent proposals for standards-track compatible extensions to SMTP
(via the Service Extensions mechanism), MIME (via new Content
Subtypes), and MIME-MHS (via MIME Content Subtypes and usage rules).
It will also act as the review body for several documents that
clarify and provide applicability statements about the use of
Internet mail: that work will ultimately lead to an update for the
mail-related section of RFC 1123. Part of that effort involves
RARE WG-MSG documents that address the Internet's installed
electronic mail infrastructure. Since such documents should not
be processed in RARE alone, this working group will act as the
IETF focus for reviewing them.
Initial drafts of all of the documents that the working group is
expected to review have already been, or will soon be, published.
The working group will be starting with documents that have been
prepared as individual (or spontaneous design team) contributions.
It is not expected to initiate new work. On the other hand, it is
expected to make explicit ``not ready for standardization'' or
``inappropriate for standardization'' recommendations if that is
appropriate.
The working group will be initialized with the following Internet-
Drafts or their successors, listed alphabetically. A major
purpose
of its first meeting is to prune or add to this list.
draft-freed-ftbp-00.txt
draft-freed-smtp-pipeline-00.txt
draft-houttuin-mailservers-02.txt
draft-rare-msg-a-bombs-00.txt
draft-rare-msg-c-bombs-00.txt
draft-vaudreuil-smtp-binary-04.txt
draft-vaudreuil-smtp-stream-00.txt
Goals and Milestones:
JUL 94 Publish an Internet-Draft on mail transport clarifications.
Done Meet at the Toronto IETF. Review pending Internet-Drafts
and decide for each whether it is ready for processing to
Proposed, should be published as Experimental or
Informational, should be discarded as a working group
effort, or should be a candidate for further working group
development. Refine the charter and work plan.
SEP 94 Revised drafts and IESG processing of any documents that
were concluded in July to be ready for processing.
OCT 94 Revised versions of specification documents identified as
needing further development published as Internet-Drafts
and ready for processing and final review.
OCT 94 Publication of revised versions of any documents that were
concluded in July to be ready to advance onto the standards
track.
DEC 94 Final review of remaining specification documents during
the San Jose IETF. Penultimate review of clarifications and
applicability statements documents.
JAN 95 New Internet-Drafts of clarifications and applicability
statements documents.
JAN 95 Final Internet-Drafts of specification documents ready for
Last Call and IESG processing to Proposed Standard.
APR 95 Final review on clarifications and applicability statements
documents as Internet-Drafts during IETF.
MAY 95 Clarifications and applicability statements documents ready
for Last Call and IESG processing to Proposed Standard.
Internet-Drafts:
No Current Internet-Drafts.
Request For Comments:
RFC Stat Published Title
------- -- ----------- ------------------------------------
RFC1766 PS MAR 95 Tags for the Identification of Languages
RFC1830 E AUG 95 SMTP Service Extensions for Transmission of Large
and Binary MIME Messages
RFC1820 I AUG 95 Multimedia E-mail (MIME) User Agent Checklist
RFC1844 I AUG 95 Multimedia E-mail (MIME) User Agent checklist
RFC1845 E OCT 95 SMTP Service Extension for Checkpoint/Restart
RFC1846 E OCT 95 SMTP 521 reply code
RFC1854 PS OCT 95 SMTP Service Extension for Command Pipelining
RFC2017 PS OCT 96 Definition of the URL MIME External-Body Access-Type
RFC2076 I FEB 97 Common Internet Message Headers