LAST CALL: IMAP base and MULTIAPPEND drafts
Mark Crispin <mrc@cac.washington.edu> Fri, 05 January 2001 03:40 UTC
Received: by ns.secondary.com (8.9.3/8.9.3) id TAA21050 for ietf-imapext-bks; Thu, 4 Jan 2001 19:40:21 -0800 (PST)
Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id TAA21046 for <ietf-imapext@IMC.ORG>; Thu, 4 Jan 2001 19:40:20 -0800 (PST)
Received: from microdol1.cac.washington.edu (microdol1.cac.washington.edu [140.142.112.196]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id TAA07455; Thu, 4 Jan 2001 19:44:55 -0800
Received: from Tomobiki-Cho.CAC.Washington.EDU (localhost [127.0.0.1]) (authenticated) by microdol1.cac.washington.edu (8.11.1+UW00.11/8.11.1+UW00.11) with ESMTP id f053isD25819; Thu, 4 Jan 2001 19:44:54 -0800
Date: Thu, 04 Jan 2001 19:44:53 -0800
From: Mark Crispin <mrc@cac.washington.edu>
To: IMAP Interest List <IMAP@cac.washington.edu>
cc: IMAP Extensions WG <ietf-imapext@imc.org>
Subject: LAST CALL: IMAP base and MULTIAPPEND drafts
Message-ID: <Pine.NXT.4.32.0101041938420.7661-100000@Tomobiki-Cho.CAC.Washington.EDU>
Organization: Networks & Distributed Computing
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: owner-ietf-imapext@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-imapext/mail-archive/>
List-ID: <ietf-imapext.imc.org>
List-Unsubscribe: <mailto:ietf-imapext-request@imc.org?body=unsubscribe>
As discussed in the IMAPEXT meeting in San Diego,... This is a last call for http://www.ietf.org/internet-drafts/draft-crispin-imapv-13.txt which is the latest revision of RFC 2060, correcting all known errors and omissions. It has been 4 years since RFC 2060 was released, and there are a lot of changes and clarifications. This is also a last call for http://www.ietf.org/internet-drafts/draft-crispin-imap-multiappend-02.txt which is a minor (but exceedingly useful) extension. It is unchanged from the -01 draft except for an updated expiration date. Does IMAPEXT want to take on MULTIAPPEND, or just let it advance to Proposed Standard status by itself? I don't forsee any further work being done to MULTIAPPEND, and people have been implementing it... -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate.
- Re: LAST CALL: IMAP base and MULTIAPPEND drafts Mark Crispin
- Re: LAST CALL: IMAP base and MULTIAPPEND drafts Simon Josefsson
- LAST CALL: IMAP base and MULTIAPPEND drafts Mark Crispin
- re: Major error in IMAP base spec: 822/MIME confo… Mark Crispin
- Major error in IMAP base spec: 822/MIME conforman… Chris Newman
- Re: LAST CALL: IMAP base and MULTIAPPEND drafts Mark Crispin
- Re: LAST CALL: IMAP base and MULTIAPPEND drafts Chris Newman