The Internet Message Action Protocol (IMAP4) Child Mailbox Extension
draft-gahrns-imap-child-mailbox-04
The information below is for an old version of the document that is already published as an RFC.
Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 3348.
|
|
---|---|---|---|
Authors | Raymond Cheng , Mike Gahrns | ||
Last updated | 2020-01-21 (Latest revision 2002-02-21) | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | Informational | ||
Formats | |||
Stream | WG state | (None) | |
Document shepherd | (None) | ||
IESG | IESG state | Became RFC 3348 (Informational) | |
Action Holders |
(None)
|
||
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | Ned Freed | ||
IESG note | |||
Send notices to | (None) |
draft-gahrns-imap-child-mailbox-04
A new Request for Comments is now available in online RFC libraries. RFC 3348 Title: The Internet Message Action Protocol (IMAP4) Child Mailbox Extension Author(s): M. Gahrns, R. Cheng Status: Informational Date: July 2002 Mailbox: mikega@microsoft.com, raych@microsoft.com Pages: 6 Characters: 11868 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-gahrns-imap-child-mailbox-04.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3348.txt The Internet Message Action Protocol (IMAP4) CHILDREN extension provides a mechanism for a client to efficiently determine if a particular mailbox has children, without issuing a LIST "" * or a LIST "" % for each mailbox. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information.