An extension to IMAP BODYSTRUCTURE for returning
Content-Location information
draft-melnikov-imap-content-location-00
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Mark Crispin , Steve Hole , Alexey Melnikov | ||
Last updated | 2013-10-18 (Latest revision 2002-06-05) | ||
Replaced by | draft-crispin-imapv | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-crispin-imapv | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The [IMAP4] BODYSTRUCTURE FETCH data item allows a client to learn about the MIME structure of a message without the need to download the entire message. This document extends the syntax of the [IMAP4] BODYSTRUCTURE FETCH response data item to include information from the Content-Location header field described in [MHTML]. This extension helps MHTML-aware IMAP clients to save both the number of round trips and the amount of information sent across the network. Fallback strategies are also discussed when an IMAP server doesn't support this extension.
Authors
Mark Crispin
Steve Hole
Alexey Melnikov
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)