RFC 3348 on The Internet Message Action Protocol (IMAP4) Child Mailbox Extension
rfc-editor@rfc-editor.org Wed, 24 July 2002 00:01 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07962; Tue, 23 Jul 2002 20:01:43 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id TAA13438 for ietf-123-outbound.10@ietf.org; Tue, 23 Jul 2002 19:55:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id TAA13376 for <all-ietf@loki.ietf.org>; Tue, 23 Jul 2002 19:51:59 -0400 (EDT)
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07711 for <all-ietf@ietf.org>; Tue, 23 Jul 2002 19:50:56 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g6NNpvE06720; Tue, 23 Jul 2002 16:51:57 -0700 (PDT)
Message-Id: <200207232351.g6NNpvE06720@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3348 on The Internet Message Action Protocol (IMAP4) Child Mailbox Extension
Cc: rfc-editor@rfc-editor.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 23 Jul 2002 16:51:57 -0700
Sender: rfc-ed@ISI.EDU
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. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.