Protocol Action: 'Contexts for IMAP4' to Proposed Standard

The IESG <> Mon, 09 June 2008 20:03 UTC

Return-Path: <>
Received: from [] (localhost []) by (Postfix) with ESMTP id D0A4028C1CB; Mon, 9 Jun 2008 13:03:51 -0700 (PDT)
Received: by (Postfix, from userid 30) id CEE0D28C1C1; Mon, 9 Jun 2008 13:03:50 -0700 (PDT)
X-idtracker: yes
From: The IESG <>
To: IETF-Announce <>
Subject: Protocol Action: 'Contexts for IMAP4' to Proposed Standard
Message-Id: <>
Date: Mon, 9 Jun 2008 13:03:50 -0700 (PDT)
Cc: Internet Architecture Board <>, RFC Editor <>
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Announcements <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

The IESG has approved the following document:

- 'Contexts for IMAP4 '
   <draft-cridland-imap-context-05.txt> as a Proposed Standard

This document has been reviewed in the IETF but is not the product of an
IETF Working Group. 

The IESG contact person is Chris Newman.

A URL of this Internet-Draft is:

Technical Summary
   The IMAP4rev1 protocol has powerful search facilities as part of the
   core protocol, but lacks the ability to create live, updated results
   which can be easily handled.  This memo provides such an extension,
   and shows how it can be used to provide a facility similar to virtual
Working Group Summary
   This is an individual submission but was discussed by the Lemonade
   WG and has been added to the Lemonade WG profile bis specification.
Protocol Quality
   This was reviewed for the IESG by Chris Newman.  The document
   received at least 5 positive reviews. All issues raised
   so far were fixed.  At least 2 server implementors and 1 client
   implementor are working on implementations.  One more client
   implementor is thinking about implementing this extension.

Note to RFC Editor

   Please ask for approval from the document shepherd, during AUTH48.

IETF-Announce mailing list