Simple Mail Transfer Protocol extension for relaying Metadata
draft-melnikov-smtp-metadata-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Alexey Melnikov | ||
| Last updated | 2015-12-19 (Latest revision 2015-06-17) | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at:
https://www.ietf.org/archive/id/draft-melnikov-smtp-metadata-01.txt
https://www.ietf.org/archive/id/draft-melnikov-smtp-metadata-01.txt
Abstract
This memo defines an extension to the SMTP (Simple Mail Transfer Protocol) service whereby message metadata (such as Trace header fields, IMAP flags, Keying material, etc) can be transferred in separate containers similar to BDAT (RFC 3030, SMTP CHUNKING) command. This allows clean separation of transaction related state from the message itself.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)