Skip to main content

Internet Message Access Protocol - ANNOTATE Extension
RFC 5257

Revision differences

Document history

Date By Action
2021-12-06
Amy Vezza Downref to RFC 5257 approved by Last Call for draft-ietf-extra-quota-10
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'The ANNOTATE extension to the Internet Message Access Protocol permits clients and servers to maintain "meta …
Received changes through RFC Editor sync (changed abstract to 'The ANNOTATE extension to the Internet Message Access Protocol permits clients and servers to maintain "meta data" for messages, or individual message parts, stored in a mailbox on the server. For example, this can be used to attach comments and other useful information to a message. It is also possible to attach annotations to specific parts of a message, so that, for example, they could be marked as seen, or important, or a comment added.

Note that this document was the product of a WG that had good consensus on how to approach the problem. Nevertheless, the WG felt it did not have enough information on implementation and deployment hurdles to meet all of the requirements of a Proposed Standard. The IETF solicits implementations and implementation reports in order to make further progress.

Implementers should be aware that this specification may change in an incompatible manner when going to Proposed Standard status. However, any incompatible changes will result in a new capability name being used to prevent problems with any deployments of the experimental extension. This memo defines an Experimental Protocol for the Internet community.')
2015-10-14
(System) Notify list changed from , cyrus@daboo.name to (None)
2008-06-17
Cindy Morgan State Changes to RFC Published from RFC Ed Queue by Cindy Morgan
2008-06-17
Cindy Morgan [Note]: 'RFC 5257' added by Cindy Morgan
2008-06-13
(System) RFC published