Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updates:

RFC 2088,RFC 2342,RFC 3501,RFC 3502,RFC 3516

Updated by:

RFC 6237,RFC 7377

Authors:

A. Melnikov
C. Daboo

Stream:

IETF

Source:

NON WORKING GROUP

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC4466

Discuss this RFC: Send questions or comments to the mailing listiesg@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 4466

Abstract

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

This document also suggests a set of standard patterns for addingoptions and extensions to several existing IMAP commands defined inRFC 3501. The patterns provide for compatibility between existingand future extensions.

This document updates ABNF in RFCs 2088, 2342, 3501, 3502, and 3516. Italso includes part of the errata to RFC 3501. This document doesn'tspecify any semantic changes to the listed RFCs. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.