RFC 5819 on IMAP4 Extension for Returning STATUS Information in Extended LIST

rfc-editor@rfc-editor.org Wed, 10 March 2010 06:00 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 478DA3A6C00; Tue, 9 Mar 2010 22:00:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.175
X-Spam-Level:
X-Spam-Status: No, score=-2.175 tagged_above=-999 required=5 tests=[AWL=-0.175, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w9O5yOSBKIm1; Tue, 9 Mar 2010 22:00:44 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 708E63A6BF3; Tue, 9 Mar 2010 22:00:44 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id A2590E0767; Tue, 9 Mar 2010 22:00:49 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5819 on IMAP4 Extension for Returning STATUS Information in Extended LIST
From: rfc-editor@rfc-editor.org
Message-Id: <20100310060049.A2590E0767@rfc-editor.org>
Date: Tue, 09 Mar 2010 22:00:49 -0800
Cc: morg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 06:00:45 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5819

        Title:      IMAP4 Extension for Returning STATUS 
                    Information in Extended LIST 
        Author:     A. Melnikov, T. Sirainen
        Status:     Standards Track
        Date:       March 2010
        Mailbox:    Alexey.Melnikov@isode.com, 
                    tss@iki.fi
        Pages:      6
        Characters: 10584
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-morg-status-in-list-01.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5819.txt

Many IMAP clients display information about total number of
messages / total number of unseen messages in IMAP mailboxes.  In order 
to do that, they are forced to issue a LIST or LSUB command and to list all
available mailboxes, followed by a STATUS command for each mailbox
found.  This document provides an extension to LIST command that
allows the client to request STATUS information for mailboxes
together with other information typically returned by the LIST
command.  [STANDARDS TRACK]

This document is a product of the Message Organization Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC