RFC - 4466

Collected Extensions to IMAP4 ABNF

Original:	ftp://ftp.isi.edu/in-notes/rfc4466.txt
Authors:	A. Melnikov [Isode Ltd.], C. Daboo []
Date:	April 2006
Category:	Proposed Standard

---

Updates:
RFC-3516prop	IMAP4 Binary Content Extension (Updated by RFC-4466prop)
RFC-3502prop	Internet Message Access Protocol (IMAP) - MULTIAPPEND Extension (Updated by RFC-4469prop, RFC-4466prop)
RFC-3501prop	INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1 (Updated by RFC-4551prop, RFC-4469prop, RFC-4466prop)
RFC-2342prop	IMAP4 Namespace (Updated by RFC-4466prop)
RFC-2088prop	IMAP4 non-synchronizing literals (Updated by RFC-4466prop)

Referred by:	3 RFC
Refers to:	8 RFC

---

Status

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.

Copyright Notice

Copyright (C) The Internet Society (2006).

Abstract

Over the years, many documents from IMAPEXT and LEMONADE working groups, as well as many individual documents, have added syntactic extensions to many base IMAP commands described in RFC 3501. For ease of reference, this document collects most of such ABNF changes in one place.

This document also suggests a set of standard patterns for adding options and extensions to several existing IMAP commands defined in RFC 3501. The patterns provide for compatibility between existing and future extensions.

This document updates ABNF in RFCs 2088, 2342, 3501, 3502, and 3516. It also includes part of the errata to RFC 3501. This document doesn't specify any semantic changes to the listed RFCs.

---