Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC4549
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 4549
This document attempts to address some of the issues involved in buildinga disconnected IMAP4 client. In particular, it deals with theissues of what might be called the "driver" portion of the synchronizationtool: the portion of the code responsible for issuing the correct setof IMAP4 commands to synchronize the disconnected client in the waythat is most likely to make the human who uses the disconnectedclient happy.
This note describes different strategies that can be used by disconnectedclients and shows how to use IMAP protocol in order to minimize thetime of the synchronization process.
This note also lists IMAP extensions that a server should implement inorder to provide better synchronization facilities to disconnected clients. This memo provides information for the Internet community.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.