draft-ietf-imapext-annotate-08.txt   draft-ietf-imapext-annotate-09.txt 
IMAP Extensions Working Group R. Gellens IMAP Extensions Working Group R. Gellens
Internet Draft: IMAP ANNOTATE Extension C. Daboo Internet-Draft QUALCOMM Incorporated
Document: draft-ietf-imapext-annotate-08.txt October 2003 Expires: October 18, 2004 C. Daboo
Cyrusoft International, Inc.
April 19, 2004
IMAP ANNOTATE Extension IMAP ANNOTATE Extension
draft-ietf-imapext-annotate-09
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that other
other groups may also distribute working documents as groups may also distribute working documents as Internet-Drafts.
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six months
months and may be updated, replaced, or obsoleted by other documents and may be updated, replaced, or obsoleted by other documents at any
at any time. It is inappropriate to use Internet-Drafts as time. It is inappropriate to use Internet-Drafts as reference
reference material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at http://
http://www.ietf.org/ietf/1id-abstracts.txt. www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet- Draft Shadow Directories can be accessed at The list of Internet- Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Copyright Notice This Internet-Draft will expire on October 18, 2004.
Copyright (C) The Internet Society 2003. All Rights Reserved. Copyright Notice
Gellens & Daboo Expires April 2004 [Page 1] Copyright (C) The Internet Society (2004). All Rights Reserved.
Table of Contents
1 Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2 Discussion . . . . . . . . . . . . . . . . . . . . . . . . . 2
3 Conventions Used in This Document . . . . . . . . . . . . . . 2
4 Change History . . . . . . . . . . . . . . . . . . . . . . . 3
5 Introduction and Overview . . . . . . . . . . . . . . . . . . 4
6 Data Model . . . . . . . . . . . . . . . . . . . . . . . . . 6
6.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . 6
6.2 Namespace of Entries and Attributes . . . . . . . . . . 6
6.2.1 Entry Names . . . . . . . . . . . . . . . . . . . . . 7
6.2.2 Attribute Names . . . . . . . . . . . . . . . . . . 9
7 Private versus Shared and Access Control . . . . . . . . . . 9
8 IMAP Protocol Changes . . . . . . . . . . . . . . . . . . . 10
8.1 General considerations . . . . . . . . . . . . . . . . . 10
8.2 Optional parameters with the SELECT/EXAMINE commands . . 11
8.3 ANNOTATION Message Data Item in FETCH Command . . . . . . 12
8.4 ANNOTATION Message Data Item in FETCH Response . . . . . 13
8.5 ANNOTATION Message Data Item in STORE . . . . . . . . . . 14
8.6 ANNOTATION interaction with COPY . . . . . . . . . . . . 16
8.7 ANNOTATION Message Data Item in APPEND . . . . . . . . . 16
8.8 ANNOTATION Criterion in SEARCH . . . . . . . . . . . . . 16
8.9 ANNOTATION Key in SORT . . . . . . . . . . . . . . . . . 17
9 Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . 18
10 IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
10.1 Entry and Attribute Registration Template . . . . . . . 19
11 Security Considerations . . . . . . . . . . . . . . . . . . . 20
12 Normative References . . . . . . . . . . . . . . . . . . . . 20
13 Informative References . . . . . . . . . . . . . . . . . . . 21
14 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 21
15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 21
16 Full Copyright Statement . . . . . . . . . . . . . . . . . . 21
1 Abstract Abstract
The ANNOTATE extension to the Internet Message Access Protocol The ANNOTATE extension to the Internet Message Access Protocol
[IMAP4] permits clients and servers to maintain "metadata" for [IMAP4] permits clients and servers to maintain "metadata" for
messages stored in an IMAP4 mailbox. messages stored in an IMAP4 mailbox.
2 Discussion Change History (to be removed prior to publication as an RFC)
Public comments can be sent to the IETF IMAP Extensions mailing
list, <ietf-imapext@imc.org>. To subscribe, send a message to
<ietf-imapext-request@imc.org> with the word SUBSCRIBE as the body.
Private comments should be sent to the authors.
3 Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [KEYWORDS].
Gellens & Daboo Expires April 2004 [Page 2]
Formal syntax is defined using ABNF [ABNF] as modified by [IMAP4].
In examples, "C:" and "S:" indicate lines sent by the client and
server respectively. Line breaks not preceded by a "C:" or "S:" are
for editorial clarity only.
4 Change History Changes from -08 to -09:
1. Fix formatting, ID nits etc.
2. Fix subject -> altsubject in examples.
3. Added text to SELECT/EXAMINE optional parameter definition to
indicate that the option could trigger a global state change or a
mailbox specific change.
4. Changed entry/attribute names to be case-sensitive to avoid case
mapping issues with utf8 text.
5. Clarify COPY interaction to indicate that only the current user's
'.priv's are copied, not the '.priv's of other users.
Changes from -07 to -08: Changes from -07 to -08:
1. ANNOTATESIZE response changed to use "NIL" for a mailbox that 1. ANNOTATESIZE response changed to use "NIL" for a mailbox that
does not support any type of annotations, and "0" for a mailbox does not support any type of annotations, and "0" for a mailbox
that only supports read-only annotations. that only supports read-only annotations.
Changes from -06 to -07: Changes from -06 to -07:
1. Added text to state entry and attribute names are always 1. Added text to state entry and attribute names are always
case-insensitive. case-insensitive.
2. Removed top-level entry namespace. 2. Removed top-level entry namespace.
3. Added server accept minima for annotation size and count. 3. Added server accept minima for annotation size and count.
4. Added [ANNOTATE TOOBIG] & [ANNOTATE TOOMANY] response codes. 4. Added [ANNOTATE TOOBIG] & [ANNOTATE TOOMANY] response codes.
5. Added [ANNOTATESIZE <<n>>] response code. 5. Added [ANNOTATESIZE <<n>>] response code.
6. Added comment on suggested CONDSTORE support. 6. Added comment on suggested CONDSTORE support.
7. Modified append behaviour to account for MULTIAPPEND. 7. Modified append behaviour to account for MULTIAPPEND.
8. Tweaked ABNF. 8. Tweaked ABNF.
Changes from -05 to -06: Changes from -05 to -06:
1. Split references into Normative and Informative. 1. Split references into Normative and Informative.
2. Reworked flags to allow IMAP4 flag prefix to appear in annotation name. 2. Reworked flags to allow IMAP4 flag prefix to appear in annotation
3. Removed smtp-envelope annotation - a future extension can add this. name.
3. Removed smtp-envelope annotation - a future extension can add
this.
4. Changed subject to altsubject. 4. Changed subject to altsubject.
5. Added $MDNSent flag and reference to document. 5. Added $MDNSent flag and reference to document.
6. Cleaned up formal syntax to use IMAP string type for entry 6. Cleaned up formal syntax to use IMAP string type for entry and
and attributes, with requirements on how the string is formatted. attributes, with requirements on how the string is formatted.
7. Use of ACAP vendor subtree registry for vendor tokens. 7. Use of ACAP vendor subtree registry for vendor tokens.
8. Fixed STORE syntax. 8. Fixed STORE syntax.
Changes from -04 to -05: Changes from -04 to -05:
1. Fixed examples to match formal syntax for FETCH responses where 1. Fixed examples to match formal syntax for FETCH responses where
parenthesis do not appear around entry-att items. parenthesis do not appear around entry-att items.
Changes from -03 to -04: Changes from -03 to -04:
1. Fixed attrib/attrib-match grammar to use "." instead of "/". 1. Fixed attrib/attrib-match grammar to use "." instead of "/".
2. Add text for server to reject unknown <part-specifier>. 2. Add text for server to reject unknown <part-specifier>.
skipping to change at page 22, line ? skipping to change at page 3, line 4
parenthesis do not appear around entry-att items. parenthesis do not appear around entry-att items.
Changes from -03 to -04: Changes from -03 to -04:
1. Fixed attrib/attrib-match grammar to use "." instead of "/". 1. Fixed attrib/attrib-match grammar to use "." instead of "/".
2. Add text for server to reject unknown <part-specifier>. 2. Add text for server to reject unknown <part-specifier>.
3. Do not allow empty part-specifier. 3. Do not allow empty part-specifier.
4. Store NIL to value to delete. 4. Store NIL to value to delete.
5. Comment on COPY interaction with ANNOTATE. 5. Comment on COPY interaction with ANNOTATE.
6. Added comment that IMAP flags are mapped one-to-one with their 6. Added comment that IMAP flags are mapped one-to-one with their
corresponding FLAGS items. corresponding FLAGS items.
7. Added comment that the recent flag annotation is read-only. 7. Added comment that the recent flag annotation is read-only.
Changes from -02 to -03: Changes from -02 to -03:
1. Removed reference to status modtime item. 1. Removed reference to status modtime item.
2. Added missing 'notify' and 'ret' dsn annotations for /message/
Gellens & Daboo Expires April 2004 [Page 3] smtp-envelope.
2. Added missing 'notify' and 'ret' dsn annotations for 3. Added requirement to store data permanently - no 'session only'
/message/smtp-envelope. annotations.
3. Added requirement to store data permanently - no 4. Removed Access Control section. Replaced with comments on
'session only' annotations. read-only/read-write mailboxes and storing private or shared
4. Removed Access Control section. Replaced with comments annotations.
on read-only/read-write mailboxes and storing private or
shared annotations.
5. Removed STORE to default .priv or .shared. 5. Removed STORE to default .priv or .shared.
6. Added section on optional select parameters. 6. Added section on optional select parameters.
Changes from -01 to -02: Changes from -01 to -02:
1. Now require .priv or .shared on store operations. 1. Now require .priv or .shared on store operations.
Changes from -00 to -01: Changes from -00 to -01:
1. MODTIME moved to its own draft, which this draft now 1. MODTIME moved to its own draft, which this draft now depends on.
depends on. Thus, Conditional Annotation STORE and Thus, Conditional Annotation STORE and related items deleted from
related items deleted from this draft. this draft.
2. Private versus Shared Annotations: both are possible 2. Private versus Shared Annotations: both are possible (separately
(separately addressable using ".priv" and ".shared" addressable using ".priv" and ".shared" suffixes). There is a
suffixes). There is a per-mailbox setting for the per-mailbox setting for the default. It is an open issue how this
default. It is an open issue how this is viewed or is viewed or changed by the client.
changed by the client. 3. In ACLs, the "w" right is needed to updated shared state; the "s"
3. In ACLs, the "w" right is needed to updated shared state; right is needed to update private state.
the "s" right is needed to update private state.
4. Various clarifications and text modifications. 4. Various clarifications and text modifications.
5. Added 'forwarded' flag for message parts. 5. Added 'forwarded' flag for message parts.
Changes from pre-imapext to -00: Changes from pre-imapext to -00:
1. Clarified text describing attributions, entries, and 1. Clarified text describing attributions, entries, and attributes.
attributes.
2. Changed 'modifiedsince' to 'modtime'; referenced ACAP spec. 2. Changed 'modifiedsince' to 'modtime'; referenced ACAP spec.
3. Deleted 'queued' flag. 3. Deleted 'queued' flag.
4. Expanded and explained smtp-envelope entry. 4. Expanded and explained smtp-envelope entry.
5. Restricted including ANNOTATION data in unsolicited responses 5. Restricted including ANNOTATION data in unsolicited responses
until the client uses it first. (Open issue as to if needed). until the client uses it first. (Open issue as to if needed).
6. Examples now only use valid entries and attributes. 6. Examples now only use valid entries and attributes.
7. Updated Security Considerations. 7. Updated Security Considerations.
8. Content-Type now defaults to text/plain. 8. Content-Type now defaults to text/plain.
9. Open Issue: Shared vs. private annotations. 9. Open Issue: Shared vs. private annotations.
10. Open issue: Annotation Modtime untagged response or VALIDTIME 10. Open issue: Annotation Modtime untagged response or VALIDTIME
FETCH data. FETCH data.
11. Open issue: Conditional annotation STORE. 11. Open issue: Conditional annotation STORE.
12. ANNOTATION criterion available if both "ANNOTATE" and "SORT" 12. ANNOTATION criterion available if both "ANNOTATE" and "SORT" in
in CAPABILITY command response. CAPABILITY command response.
13. Prohibition on annotations in lieu of base spec functionality. 13. Prohibition on annotations in lieu of base spec functionality.
14. Specified required ACL rights. 14. Specified required ACL rights.
15. ANNOTATION message data item in APPEND. 15. ANNOTATION message data item in APPEND.
16. ANNOTATION-MODTIME message data item in STATUS. 16. ANNOTATION-MODTIME message data item in STATUS.
17. Replaced ATOM_CHAR with utf8-char. 17. Replaced ATOM_CHAR with utf8-char.
18. Updated other ABNF entries. 18. Updated other ABNF entries.
Gellens & Daboo Expires April 2004 [Page 4] Table of Contents
5 Introduction and Overview 1. Introduction and Overview . . . . . . . . . . . . . . . . . 5
2. Data Model . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 Namespace of entries and attributes . . . . . . . . . . . . 6
2.2.1 Entry Names . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2.2 Attribute Names . . . . . . . . . . . . . . . . . . . . . . 9
2.3 Private versus Shared and Access Control . . . . . . . . . . 10
3. IMAP Protocol Changes . . . . . . . . . . . . . . . . . . . 11
3.1 General Considerations . . . . . . . . . . . . . . . . . . . 11
3.2 Optional parameters with the SELECT/EXAMINE commands . . . . 11
3.3 ANNOTATION Message Data Item in FETCH Command . . . . . . . 13
3.4 ANNOTATION Message Data Item in FETCH Response . . . . . . . 15
3.5 ANNOTATION Message Data Item in STORE . . . . . . . . . . . 16
3.6 ANNOTATION interaction with COPY . . . . . . . . . . . . . . 18
3.7 ANNOTATION Message Data Item in APPEND . . . . . . . . . . . 18
3.8 ANNOTATION Criterion in SEARCH . . . . . . . . . . . . . . . 18
3.9 ANNOTATION Key in SORT . . . . . . . . . . . . . . . . . . . 19
4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . 20
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . 22
5.1 Entry and Attribute Registration Template . . . . . . . . . 22
6. Security Considerations . . . . . . . . . . . . . . . . . . 22
Normative References . . . . . . . . . . . . . . . . . . . . 22
Informative References . . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 23
A. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 24
Intellectual Property and Copyright Statements . . . . . . . 25
1. Introduction and Overview
The ANNOTATE extension is present in any IMAP4 implementation which The ANNOTATE extension is present in any IMAP4 implementation which
returns "ANNOTATE" as one of the supported capabilities in the returns "ANNOTATE" as one of the supported capabilities in the
CAPABILITY response. CAPABILITY response.
The ANNOTATE extension adds a new message data item to the FETCH and The ANNOTATE extension adds a new message data item to the FETCH and
STORE commands, as well as adding SEARCH and SORT keys and an APPEND STORE commands, as well as adding SEARCH and SORT keys and an APPEND
modifier. modifier.
This extension makes the following changes to the IMAP4 protocol: This extension makes the following changes to the IMAP4 protocol:
a) adds a new ANNOTATION message data item for use in FETCH a. adds a new ANNOTATION message data item for use in FETCH
b) adds a new ANNOTATION message data item for use in STORE b. adds a new ANNOTATION message data item for use in STORE
c) adds a new ANNOTATION search criterion for use in SEARCH c. adds a new ANNOTATION search criterion for use in SEARCH
d) adds a new ANNOTATION sort key for use in SORT extension d. adds a new ANNOTATION sort key for use in SORT extension
e) adds a new ANNOTATION data item for use in APPEND e. adds a new ANNOTATION data item for use in APPEND
f) adds a new requirement on the COPY command f. adds a new requirement on the COPY command
g) adds a extension mechanism for adding parameters to the g. adds a extension mechanism for adding parameters to the SELECT/
SELECT/EXAMINE commands and defines the ANNOTATE parameter EXAMINE commands and defines the ANNOTATE parameter
h) adds two new response codes to indicate store failures of h. adds two new response codes to indicate store failures of
annotations. annotations.
i) adds a new untagged response codes for the SELECT or EXAMINE i. adds a new untagged response codes for the SELECT or EXAMINE
commands to indicate the maximum size. commands to indicate the maximum size.
The data model used for the storage of annotations is based on that The data model used for the storage of annotations is based on that
of the Application Configuration Access Protocol [ACAP]. Note that of the Application Configuration Access Protocol [ACAP]. Note that
there is no inheritance in annotations. there is no inheritance in annotations.
Clients MUST NOT use annotations in lieu of equivalent IMAP base Clients MUST NOT use annotations in lieu of equivalent IMAP base
specification facilities. For example, use of a "seen" flag in the specification facilities. For example, use of a "seen" flag in the
vendor namespace together with ".PEEK" in fetches. Such behaviour vendor namespace together with ".PEEK" in fetches. Such behaviour
would significantly reduce IMAP interoperability. would significantly reduce IMAP interoperability.
If a server supports annotations, then it MUST store all annotation If a server supports annotations, then it MUST store all annotation
data permanently, i.e. there is no concept of 'session only' data permanently, i.e. there is no concept of 'session only'
annotations that would correspond to the behaviour of 'session' annotations that would correspond to the behaviour of 'session' flags
flags as defined in the IMAP base specification. The exception to as defined in the IMAP base specification. The exception to this is
this is IMAP flags (which are accessible directly through IMAP flags (which are accessible directly through annotations) which
annotations) which may be 'session only' as determined by the FLAGS may be 'session only' as determined by the FLAGS and PERMANENTFLAGS
and PERMANENTFLAGS responses to a SELECT or EXAMINE command. responses to a SELECT or EXAMINE command.
This extension also introduces a generalised mechanism for adding This extension also introduces a generalised mechanism for adding
parameters to the SELECT or EXAMINE commands. It is anticipated parameters to the SELECT or EXAMINE commands. It is anticipated that
that other extensions may want to utilise this, so it is not other extensions may want to utilise this, so it is not strictly
strictly dependent on the ANNOTATE extension being present. dependent on the ANNOTATE extension being present.
In order to provide optimum support for a disconnected client (one In order to provide optimum support for a disconnected client (one
that needs to synchronise annotations for use when offline), servers that needs to synchronise annotations for use when offline), servers
SHOULD also support the Conditional STORE [CONDSTORE] extension. SHOULD also support the Conditional STORE [CONDSTORE] extension.
Gellens & Daboo Expires April 2004 [Page 5]
The rest of this document describes the data model and protocol The rest of this document describes the data model and protocol
changes more rigorously. changes more rigorously.
6 Data Model 2. Data Model
6.1 Overview 2.1 Overview
The data model used in ANNOTATE is that of a uniquely named entry The data model used in ANNOTATE is that of a uniquely named entry
which contains a set of standard attributes. A single coherent unit which contains a set of standard attributes. A single coherent unit
of "metadata" for a message is stored as a single entry, made up of of "metadata" for a message is stored as a single entry, made up of
several attributes. several attributes.
For example, a comment added to a message has an entry name of For example, a comment added to a message has an entry name of "/
"/comment". This entry is composed of several attributes such as comment". This entry is composed of several attributes such as
"value", "size", etc. which contain the properties and data of the "value", "size", etc. which contain the properties and data of the
entry. entry.
The protocol changes to IMAP described below allow a client to The protocol changes to IMAP described below allow a client to access
access or change the values of any attributes in any entries in a or change the values of any attributes in any entries in a message
message annotation, assuming it has sufficient access rights to do annotation, assuming it has sufficient access rights to do so (see
so (see Section 7 for specifics). Section 2.3 for specifics).
6.2 Namespace of Entries and Attributes 2.2 Namespace of entries and attributes
Each message annotation is made up of a set of entries. Each entry Each message annotation is made up of a set of entries. Each entry
has a hierarchical name in UTF-8, with each component of the name has a hierarchical name in UTF-8, with each component of the name
separated by a slash ("/"). separated by a slash ("/").
Each entry is made up of a set of attributes. Each attribute has a Each entry is made up of a set of attributes. Each attribute has a
hierarchical name in UTF-8, with each component of the name hierarchical name in UTF-8, with each component of the name separated
separated by a period ("."). by a period (".").
The value of an attribute is NIL (has no value), or is a string of The value of an attribute is NIL (has no value), or is a string of
zero or more octets. zero or more octets.
Entry and attribute names MUST NOT contain asterisk ("*") or percent Entry and attribute names MUST NOT contain asterisk ("*") or percent
("%") characters and MUST be valid UTF-8 strings which do not ("%") characters and MUST be valid UTF-8 strings which do not contain
contain the NULL octet. Invalid entry or attribute names result in the NULL octet. Invalid entry or attribute names result in a BAD
a BAD response in any IMAP commands where they are used. response in any IMAP commands where they are used.
Entry and attribute names are case-insensitive. Entry and attribute names are case-sensitive.
Use of non-visible UTF-8 characters in entry and attribute names is Use of non-visible UTF-8 characters in entry and attribute names is
strongly discouraged. strongly discouraged.
This specification defines an initial set of entry and attribute This specification defines an initial set of entry and attribute
names available for use in message annotations. In addition, an names available for use in message annotations. In addition, an
extension mechanism is described to allow additional names to be extension mechanism is described to allow additional names to be
added for extensibility. added for extensibility.
Gellens & Daboo Expires April 2004 [Page 6] 2.2.1 Entry Names
6.2.1 Entry Names
Entry names MUST be specified in a standards track or IESG approved Entry names MUST be specified in a standards track or IESG approved
experimental RFC, or fall under the vendor namespace. See Section experimental RFC, or fall under the vendor namespace. See Section 5.1
10.1 for the registration template. for the registration template.
/ /
Defines the top-level of entries associated with an entire Defines the top-level of entries associated with an entire
message. This entry itself does not contain any attributes. message. This entry itself does not contain any attributes. All
All entries that start with a numeric character ("0" - "9") entries that start with a numeric character ("0" - "9") refer to
refer to an annotation on a specific body part. All other an annotation on a specific body part. All other entries are for
entries are for annotations on the entire message. annotations on the entire message.
/comment /comment
Defines a comment or note associated with an entire message. Defines a comment or note associated with an entire message.
/flags /flags
Defines the top-level of entries for flags associated with an Defines the top-level of entries for flags associated with an
entire message. The "value" attribute of each of the entries entire message. The "value" attribute of each of the entries
described below must be either "1", "0" or NIL. "1" corresponds described below must be either "1", "0" or NIL. "1" corresponds to
to the flag being set. the flag being set.
Standard [IMAP4] flags always have a '\' prefix character. Standard [IMAP4] flags always have a '\' prefix character. Other
Other standard flags have a '$' prefix. The annotation names standard flags have a '$' prefix. The annotation names used for
used for all flags uses the complete name for that flag, all flags uses the complete name for that flag, including the
including the prefix character. prefix character.
The set of standard IMAP flags annotations are: The set of standard IMAP flags annotations are:
/flags/\answered /flags/\answered
/flags/\flagged /flags/\flagged
/flags/\deleted /flags/\deleted
/flags/\seen /flags/\seen
/flags/\draft /flags/\draft
/flags/\recent /flags/\recent
Changes to these annotations are reflected in the standard IMAP Changes to these annotations are reflected in the standard IMAP
flags. The \recent attribute is read only, clients MUST NOT flags. The \recent attribute is read only, clients MUST NOT
attempt to change it. attempt to change it.
Note that entry names are sent as [IMAP4] string elements which Note that entry names are sent as [IMAP4] string elements which
requires that '\' characters be escaped if sent as a quoted requires that '\' characters be escaped if sent as a quoted string
string as opposed to a literal. as opposed to a literal.
Note that flag and keyword names in [IMAP4] are case-insensitive,
however the entry names for the corresponding annotations are
case-sensitive. Thus the [IMAP4] flag and keyword names MUST be
mapped to lowercase characters before being used as entry names
for annotations.
Additional standard flags are: Additional standard flags are:
/flags/$mdnsent /flags/$mdnsent
/flags/$redirected /flags/$redirected
/flags/$forwarded /flags/$forwarded
The '$mdnsent' flag is used to indicate message disposition The '$mdnsent' flag is used to indicate message disposition
notification processing state [MDNSENT]. notification processing state [MDNSENT].
Gellens & Daboo Expires April 2004 [Page 7]
The '$redirected' flag indicates that a message has been handed The '$redirected' flag indicates that a message has been handed
off to someone else, by resending the message with minimal off to someone else, by resending the message with minimal
alterations, and in such a way that a reply by the new recipient alterations, and in such a way that a reply by the new
is addressed to the original author, not the user who performed recipient is addressed to the original author, not the user who
the redirection. performed the redirection.
The '$forwarded' flag indicates the message was resent to The '$forwarded' flag indicates the message was resent to
another user, embedded within or attached to a new message. another user, embedded within or attached to a new message.
/altsubject /altsubject
Contains text supplied by the message recipient, to be used by Contains text supplied by the message recipient, to be used by the
the client instead of the original message Subject. client instead of the original message Subject.
/vendor/<vendor-token> /vendor/<vendor-token>
Defines the top-level of entries associated with an entire Defines the top-level of entries associated with an entire message
message as created by a particular product of some vendor. as created by a particular product of some vendor. These
These sub-entries can be used by vendors to provide sub-entries can be used by vendors to provide client-specific
client-specific attributes. The vendor-token MUST be registered attributes. The vendor-token MUST be registered with IANA, using
with IANA, using the [ACAP] vendor subtree registry. the [ACAP] vendor subtree registry.
/<section-part> /<section-part>
Defines the top-level of entries associated with a specific body Defines the top-level of entries associated with a specific body
part of a message. This entry itself does not contain any part of a message. This entry itself does not contain any
attributes. The section-part uses the same numeric part attributes. The section-part uses the same numeric part specifier
specifier syntax as the BODY message data item in the FETCH syntax as the BODY message data item in the FETCH command [IMAP4].
command [IMAP4]. The server MUST return a BAD response if the The server MUST return a BAD response if the client uses an
client uses an incorrect part specifier (either incorrect syntax incorrect part specifier (either incorrect syntax or a specifier
or a specifier referring to a non-existent part). The server referring to a non-existent part). The server MUST return a BAD
MUST return a BAD response if the client uses an empty part response if the client uses an empty part specifier (which is used
specifier (which is used in [IMAP4] to represent the entire in [IMAP4] to represent the entire message).
message).
/<section-part>/comment /<section-part>/comment
Defines a comment or note associated with a specific body part Defines a comment or note associated with a specific body part of
of a message. a message.
/<section-part>/flags /<section-part>/flags
Defines the top-level of entries associated with flag state for Defines the top-level of entries associated with flag state for a
a specific body part of a message. All sub-entries are specific body part of a message. All sub-entries are maintained
maintained entirely by the client. There is no implicit change entirely by the client. There is no implicit change to any flag by
to any flag by the server. the server.
/<section-part>/flags/seen /<section-part>/flags/seen
/<section-part>/flags/answered /<section-part>/flags/answered
/<section-part>/flags/flagged /<section-part>/flags/flagged
/<section-part>/flags/forwarded /<section-part>/flags/forwarded
Defines flags for a specific body part of a message. The
"value" attribute of these entries must be either "1", "0" or
NIL.
/<section-part>/vendor/<vendor-token> Defines flags for a specific body part of a message. The "value"
attribute of these entries must be either "1", "0" or NIL.
Gellens & Daboo Expires April 2004 [Page 8] /<section-part>/vendor/<vendor-token>
Defines the top-level of entries associated with a specific body Defines the top-level of entries associated with a specific body
part of a message as created by a particular product of some part of a message as created by a particular product of some
vendor. This entry can be used by vendors to provide client vendor. This entry can be used by vendors to provide client
specific attributes. The vendor-token MUST be registered with specific attributes. The vendor-token MUST be registered with
IANA. IANA.
6.2.2 Attribute Names 2.2.2 Attribute Names
Attribute names MUST be specified in a standards track or IESG Attribute names MUST be specified in a standards track or IESG
approved experimental RFC, or fall under the vendor namespace. See approved experimental RFC, or fall under the vendor namespace. See
Section 10.1 for the registration template. Section 5.1 for the registration template.
All attribute names implicitly have a ".priv" and a ".shared" suffix All attribute names implicitly have a ".priv" and a ".shared" suffix
which maps to private and shared versions of the entry. Searching which maps to private and shared versions of the entry. Searching or
or fetching without using either suffix includes both. The client fetching without using either suffix includes both. The client MUST
MUST specify either a ".priv" or ".shared" suffix when storing an specify either a ".priv" or ".shared" suffix when storing an
annotation. annotation.
value value
A UTF8 string representing the data value of the attribute. To A UTF8 string representing the data value of the attribute. To
delete an annotation, the client can store NIL into the value. delete an annotation, the client can store NIL into the value.
size size
The size of the value, in octets. Set automatically by the The size of the value, in octets. Set automatically by the server,
server, read-only to clients. read-only to clients.
content-type content-type
A MIME [MIME] content type and subtype that describes the nature A MIME [MIME] content type and subtype that describes the nature
of the content of the "value" attribute. If not present, a of the content of the "value" attribute. If not present, a value
value of "text/plain; charset=utf8" is assumed. of "text/plain; charset=utf8" is assumed.
vendor.<vendor-token> vendor.<vendor-token>
Defines an attribute associated with a particular product of Defines an attribute associated with a particular product of some
some vendor. This attribute can be used by vendors to provide vendor. This attribute can be used by vendors to provide client
client specific attributes. The vendor-token MUST be registered specific attributes. The vendor-token MUST be registered with
with IANA, using the [ACAP] vendor subtree registry. IANA, using the [ACAP] vendor subtree registry.
7 Private versus Shared and Access Control 2.3 Private versus Shared and Access Control
Some IMAP mailboxes are private, accessible only to the owning user. Some IMAP mailboxes are private, accessible only to the owning user.
Other mailboxes are not, either because the owner has set an ACL Other mailboxes are not, either because the owner has set an ACL
[ACL] which permits access by other users, or because it is a shared [ACL] which permits access by other users, or because it is a shared
mailbox. mailbox.
This raises the issue of shared versus private annotations. This raises the issue of shared versus private annotations.
If all annotations are private, it is impossible to set annotations If all annotations are private, it is impossible to set annotations
in a shared or otherwise non-private mailbox that are visible to in a shared or otherwise non-private mailbox that are visible to
other users. This eliminates what could be a useful aspect of other users. This eliminates what could be a useful aspect of
annotations in a shared environment. An example of such use is a annotations in a shared environment. An example of such use is a
shared IMAP folder containing bug reports. Engineers may want to use
Gellens & Daboo Expires April 2004 [Page 9] annotations to add information to existing messages, indicate
shared IMAP folder containing bug reports. Engineers may want to
use annotations to add information to existing messages, indicate
assignments, status, etc. This use requires shared annotations. assignments, status, etc. This use requires shared annotations.
If all annotations are shared, it is impossible to use annotations If all annotations are shared, it is impossible to use annotations
for private notes on messages in shared mailboxes. Also, modifying for private notes on messages in shared mailboxes. Also, modifying an
an ACL to permit access to a mailbox by other users may ACL to permit access to a mailbox by other users may unintentionally
unintentionally expose private information. expose private information.
There are also situations in which both shared and private There are also situations in which both shared and private
annotations are useful. For example, an administrator may want to annotations are useful. For example, an administrator may want to set
set shared annotations on messages in a shared folder, which shared annotations on messages in a shared folder, which individual
individual users may wish to supplement with additional notes. users may wish to supplement with additional notes.
If shared and private annotations are to coexist, we need a clear If shared and private annotations are to coexist, we need a clear way
way to differentiate them. Also, it should be as easy as possible to differentiate them. Also, it should be as easy as possible for a
for a client to access both and not overlook either. There is also client to access both and not overlook either. There is also a danger
a danger in allowing a client to store an annotation without knowing in allowing a client to store an annotation without knowing if it is
if it is shared or private. shared or private.
This document proposes two standard suffixes for all attributes: This document proposes two standard suffixes for all attributes:
".shared" and ".priv". A search, fetch, or sort which specifies ".shared" and ".priv". A search, fetch, or sort which specifies
neither uses both. Store operations MUST explicitly use .priv or neither uses both. Store operations MUST explicitly use .priv or
.shared suffixes. .shared suffixes.
A user can only store and fetch private annotations on messages in A user can only store and fetch private annotations on messages in
any mailbox which they can SELECT or EXAMINE, including ones which any mailbox which they can SELECT or EXAMINE, including ones which
only open READ-ONLY. A user can only store and fetch shared only open READ-ONLY. A user can only store and fetch shared
annotations on messages in any mailbox that they can SELECT and annotations on messages in any mailbox that they can SELECT and which
which opens READ-WRITE. If a client attempts to store or fetch a opens READ-WRITE. If a client attempts to store or fetch a shared
shared annotation on a READ-ONLY mailbox, the server MUST respond annotation on a READ-ONLY mailbox, the server MUST respond with a NO
with a NO response. response.
8 IMAP Protocol Changes 3. IMAP Protocol Changes
8.1 General considerations 3.1 General Considerations
The server is allowed to impose limitations on the size of any one The server is allowed to impose limitations on the size of any one
annotation or the total number of annotations for a single message. annotation or the total number of annotations for a single message.
However, the server MUST accept a minimum annotation data size of at However, the server MUST accept a minimum annotation data size of at
least 1024 bytes, and a minimum annotation count per message of at least 1024 bytes, and a minimum annotation count per message of at
least 10. least 10.
The server SHOULD indicate the maximum size for an annotation value The server SHOULD indicate the maximum size for an annotation value
by sending an untagged "ANNOTATESIZE" response during a SELECT or by sending an untagged "ANNOTATESIZE" response during a SELECT or
EXAMINE command. Clients MUST NOT store annotation values of a size EXAMINE command. Clients MUST NOT store annotation values of a size
greater than the amount indicated by the server in the greater than the amount indicated by the server in the "ANNOTATESIZE"
"ANNOTATESIZE" response. response.
In some cases, servers may be able to offer annotations on some In some cases, servers may be able to offer annotations on some
mailboxes and not others, or may be able to provide only read-only mailboxes and not others, or may be able to provide only read-only
annotations on some mailboxes. For mailboxes that cannot have annotations on some mailboxes. For mailboxes that cannot have
Gellens & Daboo Expires April 2004 [Page 10]
annotations associated with them, the server MUST return an annotations associated with them, the server MUST return an
"ANNOTATESIZE" response with a value of "NIL" during the SELECT or "ANNOTATESIZE" response with a value of "NIL" during the SELECT or
EXAMINE command for that mailbox. Clients MUST NOT attempt to fetch EXAMINE command for that mailbox. Clients MUST NOT attempt to fetch
or store annotations on any messages in a mailbox for which the or store annotations on any messages in a mailbox for which the
"ANNOTATESIZE" response was "NIL". For mailboxes that can only have "ANNOTATESIZE" response was "NIL". For mailboxes that can only have
read-only annotations associated with them, the server MUST return read-only annotations associated with them, the server MUST return an
an "ANNOTATESIZE" response with a value of "0" (zero) during the "ANNOTATESIZE" response with a value of "0" (zero) during the SELECT
SELECT or EXAMINE command for that mailbox. Clients MUST NOT or EXAMINE command for that mailbox. Clients MUST NOT attempt to
attempt to store annotations on any messages in a mailbox for which store annotations on any messages in a mailbox for which the
the "ANNOTATESIZE" response was zero. "ANNOTATESIZE" response was zero.
8.2 Optional parameters with the SELECT/EXAMINE commands 3.2 Optional parameters with the SELECT/EXAMINE commands
This extension adds the ability to include one or more parameters This extension adds the ability to include one or more parameters
with the IMAP SELECT or EXAMINE commands, to turn on or off certain with the IMAP SELECT or EXAMINE commands, to turn on or off certain
standard behaviour, or to add new optional behaviours required for a standard behaviour, or to add new optional behaviours required for a
particular extension. It is anticipated that other extensions may particular extension.
want to use this facility, so a generalised approach is given here.
This facility is not dependent on the presence of the ANNOTATE There are two possible modes of operation:
extension - other extensions can use it with a server that does not
implement ANNOTATE. o A global state change where a single use of the optional parameter
will effect the session state from that time on, irrespective of
subsequent SELECT/EXAMINE commands.
o A per-mailbox state change that will effect the session only for
the duration of the new selected state. A subsequent SELECT/
EXAMINE without the optional parameter will cancel its effect for
the newly selected mailbox.
It is anticipated that other extensions may want to use this
facility, so a generalised approach is given here. This facility is
not dependent on the presence of the ANNOTATE extension - other
extensions can use it with a server that does not implement ANNOTATE.
Optional parameters to the SELECT or EXAMINE commands are added as a Optional parameters to the SELECT or EXAMINE commands are added as a
parenthesised list of atoms or strings, and appear after the mailbox parenthesised list of atoms or strings, and appear after the mailbox
name in the standard SELECT or EXAMINE command. The order of name in the standard SELECT or EXAMINE command. The order of
individual parameters is arbitrary. Individual parameters may individual parameters is arbitrary. Individual parameters may consist
consist of one or more atoms or strings in a specific order. If a of one or more atoms or strings in a specific order. If a parameter
parameter consists of more than one atom or string, it MUST appear consists of more than one atom or string, it MUST appear in its own
in its own parenthesised list. Any parameter not defined by parenthesised list. Any parameter not defined by extensions that the
extensions that the server supports MUST be rejected with a NO server supports MUST be rejected with a NO response.
response.
Example: Example:
C: a SELECT INBOX (ANNOTATE) C: a SELECT INBOX (ANNOTATE)
S: ... S: ...
S: a OK SELECT complete S: a OK SELECT complete
In the above example, a single parameter is used with the In the above example, a single parameter is used with the SELECT
SELECT command. command.
C: a EXAMINE INBOX (ANNOTATE (RESPONSES "UID Responses") MODTIME) Example:
C: a EXAMINE INBOX (ANNOTATE (RESPONSES "UID Responses") CONDSTORE)
S: ... S: ...
S: a OK EXAMINE complete S: a OK EXAMINE complete
In the above example, three parameters are used with the In the above example, three parameters are used with the EXAMINE
EXAMINE command. The second parameter consists of two command. The second parameter consists of two items: an atom
items: an atom followed by a quoted string. followed by a quoted string.
Example:
C: a SELECT INBOX (BLURDYBLOOP) C: a SELECT INBOX (BLURDYBLOOP)
S: a NO Unknown parameter in SELECT command S: a NO Unknown parameter in SELECT command
Gellens & Daboo Expires April 2004 [Page 11] In the above example, a parameter not supported by the server is
In the above example, a parameter not supported by the incorrectly used.
server is incorrectly used.
The ANNOTATE extension defines a single optional select parameter The ANNOTATE extension defines a single optional select parameter
"ANNOTATE", which is used to turn on unsolicited responses for "ANNOTATE", which is used to turn on unsolicited responses for
annotations as described in Section 8.4. annotations as described in Section 3.4. This option al parameter is
results in a per-mailbox state change, i.e. it must be used in each
SELECT/EXAMINE command in order to be effective, irrespective of
whether it was used in a previous SELECT/EXAMINE during the same
session.
8.3 ANNOTATION Message Data Item in FETCH Command 3.3 ANNOTATION Message Data Item in FETCH Command
This extension adds an ANNOTATION message data item to the FETCH This extension adds an ANNOTATION message data item to the FETCH
command. This allows clients to retrieve annotations for a range of command. This allows clients to retrieve annotations for a range of
messages in the currently selected mailbox. messages in the currently selected mailbox.
ANNOTATION <entry-specifier> <attribute-specifier> ANNOTATION <entry-specifier> <attribute-specifier>
The ANNOTATION message data item, when used by the client in the The ANNOTATION message data item, when used by the client in the
FETCH command, takes an entry specifier and an attribute FETCH command, takes an entry specifier and an attribute
specifier. specifier.
Example: Example:
C: a FETCH 1 (ANNOTATION ("/comment" "value")) C: a FETCH 1 (ANNOTATION ("/comment" "value"))
S: * 1 FETCH (ANNOTATION ("/comment" S: * 1 FETCH (ANNOTATION ("/comment"
("value.priv" "My comment" ("value.priv" "My comment"
"value.shared" "Group note"))) "value.shared" "Group note")))
S: a OK Fetch complete S: a OK Fetch complete
In the above example, the content of the "value" attribute In the above example, the content of the "value" attribute for the
for the "/comment" entry is requested by the client and "/comment" entry is requested by the client and returned by the
returned by the server. Since neither ".shared" nor ".priv" server. Since neither ".shared" nor ".priv" was specified, both
was specified, both are returned. are returned.
"*" and "%" wildcard characters can be used in either specifier to "*" and "%" wildcard characters can be used in either specifier to
match one or more characters at that position, with the exception match one or more characters at that position, with the exception
that "%" does not match the hierarchy delimiter for the specifier it that "%" does not match the hierarchy delimiter for the specifier it
appears in (that is, "/" for an entry specifier or "." for an appears in (that is, "/" for an entry specifier or "." for an
attribute specifier). Thus an entry specifier of "/%" matches attribute specifier). Thus an entry specifier of "/%" matches entries
entries such as "/comment" and "/subject", but not such as "/comment" and "/altsubject", but not "/flags/$redirected".
"/flags/$redirected".
Example:
Examples:
C: a FETCH 1 (ANNOTATION ("/*" ("value.priv" "size.priv"))) C: a FETCH 1 (ANNOTATION ("/*" ("value.priv" "size.priv")))
S: * 1 FETCH (ANNOTATION S: * 1 FETCH (ANNOTATION
("/comment" ("value.priv" "My comment" ("/comment" ("value.priv" "My comment"
"size.priv" "10") "size.priv" "10")
"/subject" ("value.priv" "Rhinoceroses!" "/altsubject" ("value.priv" "Rhinoceroses!"
"size.priv" "13") "size.priv" "13")
"/vendor/foobar/label.priv" "/vendor/foobar/label.priv"
("value.priv" "label43" ("value.priv" "label43"
"size.priv" "7") "size.priv" "7")
"/vendor/foobar/personality" "/vendor/foobar/personality"
("value.priv" "Tallulah Bankhead" ("value.priv" "Tallulah Bankhead"
"size.priv" "17"))) "size.priv" "17")))
S: a OK Fetch complete S: a OK Fetch complete
Gellens & Daboo Expires April 2004 [Page 12] In the above example, the contents of the private "value" and
In the above example, the contents of the private "value" and "size" "size" attributes for any entries in the "" hierarchy are
attributes for any entries in the "" hierarchy are requested by the requested by the client and returned by the server.
client and returned by the server.
Example:
C: a FETCH 1 (ANNOTATION ("/%" "value.shared")) C: a FETCH 1 (ANNOTATION ("/%" "value.shared"))
S: * 1 FETCH (ANNOTATION S: * 1 FETCH (ANNOTATION
("/comment" ("value.shared" "Patch Mangler") ("/comment" ("value.shared" "Patch Mangler")
"/subject" ("value.shared" "Patches? We don't "/altsubject" ("value.shared" "Patches? We don't
need no steenkin patches!"))) need no steenkin patches!")))
S: a OK Fetch complete S: a OK Fetch complete
In the above example, the contents of the shared "value" In the above example, the contents of the shared "value"
attributes for entries at the top level only of the "" attributes for entries at the top level only of the "" hierarchy
hierarchy are requested by the client and returned by the are requested by the client and returned by the server.
server.
Entry and attribute specifiers can be lists of atomic specifiers, so Entry and attribute specifiers can be lists of atomic specifiers, so
that multiple items of each type may be returned in a single FETCH that multiple items of each type may be returned in a single FETCH
command. command.
Examples: Example:
C: a FETCH 1 (ANNOTATION C: a FETCH 1 (ANNOTATION
(("/comment" "/subject") "value.priv")) (("/comment" "/altsubject") "value.priv"))
S: * 1 FETCH (ANNOTATION S: * 1 FETCH (ANNOTATION
("/comment" ("value.priv" "What a chowder-head") ("/comment" ("value.priv" "What a chowder-head")
"/subject" ("value.priv" "How to crush beer cans"))) "/altsubject" ("value.priv" "How to crush beer cans")))
S: a OK Fetch complete S: a OK Fetch complete
In the above example, the contents of the private "value" attributes In the above example, the contents of the private "value"
for the two entries "/comment" and "/subject" are requested by the attributes for the two entries "/comment" and "/altsubject" are
client and returned by the server. requested by the client and returned by the server.
8.4 ANNOTATION Message Data Item in FETCH Response 3.4 ANNOTATION Message Data Item in FETCH Response
The ANNOTATION message data item in the FETCH response displays The ANNOTATION message data item in the FETCH response displays
information about annotations in a message. information about annotations in a message.
ANNOTATION parenthesised list ANNOTATION parenthesised list
The response consists of a list of entries, each of which has a The response consists of a list of entries, each of which has a
list of attribute-value pairs. list of attribute-value pairs.
Examples: Example:
C: a FETCH 1 (ANNOTATION ("/comment" "value")) C: a FETCH 1 (ANNOTATION ("/comment" "value"))
S: * 1 FETCH (ANNOTATION ("/comment" S: * 1 FETCH (ANNOTATION ("/comment"
("value.priv" "My comment" ("value.priv" "My comment"
"value.shared" NIL))) "value.shared" NIL)))
S: a OK Fetch complete S: a OK Fetch complete
In the above example, a single entry with a single attribute-value In the above example, a single entry with a single attribute-value
pair is returned by the server. Since the client did not specify a pair is returned by the server. Since the client did not specify a
Gellens & Daboo Expires April 2004 [Page 13]
".shared" or ".priv" suffix, both are returned. Only the private ".shared" or ".priv" suffix, both are returned. Only the private
attribute has a value (the shared value is NIL). attribute has a value (the shared value is NIL).
Example:
C: a FETCH 1 (ANNOTATION C: a FETCH 1 (ANNOTATION
(("/comment" "/subject") "value")) (("/comment" "/altsubject") "value"))
S: * 1 FETCH (ANNOTATION S: * 1 FETCH (ANNOTATION
("/comment" ("value.priv" "My comment" ("/comment" ("value.priv" "My comment"
"value.shared" NIL) "value.shared" NIL)
"/subject" ("value.priv" "My subject" "/altsubject" ("value.priv" "My subject"
"value.shared" NIL))) "value.shared" NIL)))
S: a OK Fetch complete S: a OK Fetch complete
In the above example, two entries each with a single attribute-value In the above example, two entries each with a single
pair are returned by the server. Since the client did not specify a attribute-value pair are returned by the server. Since the client
".shared" or ".priv" suffix, both are returned. Only the private did not specify a ".shared" or ".priv" suffix, both are returned.
attributes have values; the shared attributes are NIL. Only the private attributes have values; the shared attributes are
NIL.
Example:
C: a FETCH 1 (ANNOTATION C: a FETCH 1 (ANNOTATION
("/comment" ("value" "size"))) ("/comment" ("value" "size")))
S: * 1 FETCH (ANNOTATION S: * 1 FETCH (ANNOTATION
("/comment" ("/comment"
("value.priv" "My comment" ("value.priv" "My comment"
"value.shared" NIL "value.shared" NIL
"size.priv" "10" "size.priv" "10"
"size.shared" "0"))) "size.shared" "0")))
S: a OK Fetch complete S: a OK Fetch complete
In the above example, a single entry with two attribute-value pairs In the above example, a single entry with two attribute-value
is returned by the server. Since the client did not specify a pairs is returned by the server. Since the client did not specify
".shared" or ".priv" suffix, both are returned. Only the private a ".shared" or ".priv" suffix, both are returned. Only the private
attributes have values; the shared attributes are NIL. attributes have values; the shared attributes are NIL.
Servers MUST NOT include ANNOTATION data in unsolicited responses Servers MUST NOT include ANNOTATION data in unsolicited responses
unless the client used the ANNOTATE select parameter when it issued unless the client used the ANNOTATE select parameter when it issued
the last SELECT or EXAMINE command. This restriction avoids sending the last SELECT or EXAMINE command. This restriction avoids sending
ANNOTATION data to a client unless the client explicitly asks for ANNOTATION data to a client unless the client explicitly asks for it.
it.
Servers SHOULD send ANNOTATION message data items in unsolicited Servers SHOULD send ANNOTATION message data items in unsolicited
FETCH responses if an annotation entry is changed by a third-party, FETCH responses if an annotation entry is changed by a third-party,
and the ANNOTATE select parameter was used. This allows servers to and the ANNOTATE select parameter was used. This allows servers to
keep clients updated with changes to annotations by other clients. keep clients updated with changes to annotations by other clients.
8.5 ANNOTATION Message Data Item in STORE 3.5 ANNOTATION Message Data Item in STORE
ANNOTATION <parenthesised entry-attribute-value list> ANNOTATION <parenthesised entry-attribute-value list>
Sets the specified list of entries by adding or replacing the Sets the specified list of entries by adding or replacing the
specified attributes with the values provided. Clients can use specified attributes with the values provided. Clients can use NIL
NIL for values of attributes it wants to remove from entries. for values of attributes it wants to remove from entries.
Gellens & Daboo Expires April 2004 [Page 14]
The ANNOTATION message data item used with the STORE command has an The ANNOTATION message data item used with the STORE command has an
implicit ".SILENT" behaviour. This means the server does not implicit ".SILENT" behaviour. This means the server does not generate
generate an untagged FETCH in response to the STORE command and an untagged FETCH in response to the STORE command and assumes that
assumes that the client updates its own cache if the command the client updates its own cache if the command succeeds.
succeeds.
If the server is unable to store an annotation because the size of If the server is unable to store an annotation because the size of
its value is too large, the server MUST return a tagged NO response its value is too large, the server MUST return a tagged NO response
with a "[ANNOTATE TOOBIG]" response code. with a "[ANNOTATE TOOBIG]" response code.
If the server is unable to store a new annotation because the If the server is unable to store a new annotation because the maximum
maximum number of allowed annotations has already been reached, the number of allowed annotations has already been reached, the server
server MUST return a tagged NO response with a "[ANNOTATE TOOMANY]" MUST return a tagged NO response with a "[ANNOTATE TOOMANY]" response
response code. code.
Example:
Examples:
C: a STORE 1 ANNOTATION ("/comment" C: a STORE 1 ANNOTATION ("/comment"
("value.priv" "My new comment")) ("value.priv" "My new comment"))
S: a OK Store complete S: a OK Store complete
In the above example, the entry "/comment" is created (if not In the above example, the entry "/comment" is created (if not
already present) and the private attribute "value" with data set to already present) and the private attribute "value" with data set
"My new comment" is created if not already present, or replaced if to "My new comment" is created if not already present, or replaced
it exists. if it exists.
Example:
C: a STORE 1 ANNOTATION ("/comment" C: a STORE 1 ANNOTATION ("/comment"
("value.shared" NIL)) ("value.shared" NIL))
S: a OK Store complete S: a OK Store complete
In the above example, the shared "value" attribute of the entry In the above example, the shared "value" attribute of the entry "/
"/comment" is removed by storing NIL into the attribute. comment" is removed by storing NIL into the attribute.
Multiple entries can be set in a single STORE command by listing Multiple entries can be set in a single STORE command by listing
entry-attribute-value pairs in the list. entry-attribute-value pairs in the list.
Example: Example:
C: a STORE 1 ANNOTATION ("/comment" C: a STORE 1 ANNOTATION ("/comment"
("value.priv" "Get tix Tuesday") ("value.priv" "Get tix Tuesday")
"/subject" "/altsubject"
("value.priv" "Wots On")) ("value.priv" "Wots On"))
S: a OK Store complete S: a OK Store complete
In the above example, the entries "/comment" and "/subject" are In the above example, the entries "/comment" and "/altsubject" are
created (if not already present) and the private attribute "value" created (if not already present) and the private attribute "value"
is created for each entry if not already present, or replaced if is created for each entry if not already present, or replaced if
they exist. they exist.
Multiple attributes can be set in a single STORE command by listing Multiple attributes can be set in a single STORE command by listing
multiple attribute-value pairs in the entry list. multiple attribute-value pairs in the entry list.
Example: Example:
C: a STORE 1 ANNOTATION ("/comment"
Gellens & Daboo Expires April 2004 [Page 15] C: a STORE 1 ANNOTATION ("/comment"
("value.priv" "My new comment" ("value.priv" "My new comment"
"vendor.foobar.priv" "foo's bar")) "vendor.foobar.priv" "foo's bar"))
S: a OK Store complete S: a OK Store complete
In the above example, the entry "/comment" is created (if not In the above example, the entry "/comment" is created (if not already
already present) and the private attributes "value" and present) and the private attributes "value" and "vendor.foobar" are
"vendor.foobar" are created if not already present, or replaced if created if not already present, or replaced if they exist.
they exist.
8.6 ANNOTATION interaction with COPY 3.6 ANNOTATION interaction with COPY
The COPY command can be used to move messages from one mailbox to The COPY command can be used to move messages from one mailbox to
another on the same server. Servers that support the ANNOTATION another on the same server. Servers that support the ANNOTATION
extension MUST copy all the annotation data associated with any extension MUST, for each message being copied, copy all '.priv'
messages being copied via the COPY command. The only exceptions to annotation data for the current user only, and all '.shared'
this are if the destination mailbox permissions are such that either annotation data along with the message to the new mailbox. The only
the '.priv' or '.shared' annotations are not allowed, or if the exceptions to this are if the destination mailbox permissions are
destination mailbox is of a type that does not support annotations such that either the '.priv' or '.shared' annotations are not
or does not support storing of annotations (a mailbox that returns a allowed, or if the destination mailbox is of a type that does not
zero or "NIL" value for its ANNOTATESIZE response code). support annotations or does not support storing of annotations (a
mailbox that returns a zero or "NIL" value for its ANNOTATESIZE
response code). Servers MUST NOT copy '.priv' annotation data for
users other than the current user.
8.7 ANNOTATION Message Data Item in APPEND 3.7 ANNOTATION Message Data Item in APPEND
ANNOTATION <parenthesised entry-attribute-value list> ANNOTATION <parenthesised entry-attribute-value list>
Sets the specified list of entries and attributes in the
resulting message. Sets the specified list of entries and attributes in the resulting
message.
The APPEND command can include annotations for the message being The APPEND command can include annotations for the message being
appended via the addition of a new append data item. The new data appended via the addition of a new append data item. The new data
item can also be used with the multi-append [MULTIAPPEND] extension item can also be used with the multi-append [MULTIAPPEND] extension
that allows multiple messages to be appended via a single APPEND that allows multiple messages to be appended via a single APPEND
command. command.
Examples: Example:
C: a APPEND drafts ANNOTATION ("/comment" C: a APPEND drafts ANNOTATION ("/comment"
("value.priv" "Don't send until we hear from Sally")) {310} ("value.priv" "Don't send until we hear from Sally")) {310}
S: + Ready for literal data S: + Ready for literal data
C: MIME-Version: 1.0 C: MIME-Version: 1.0
... ...
C: C:
S: a OK APPEND completed S: a OK APPEND completed
In the above example, a comment with a private value is added to a In the above example, a comment with a private value is added to a
new message appended to the mailbox. The ellipsis represents the new message appended to the mailbox. The ellipsis represents the
bulk of the message. bulk of the message.
8.8 ANNOTATION Criterion in SEARCH 3.8 ANNOTATION Criterion in SEARCH
ANNOTATION <entry-name> <attribute-name> <value> ANNOTATION <entry-name> <attribute-name> <value>
Gellens & Daboo Expires April 2004 [Page 16]
The ANNOTATION criterion for the SEARCH command allows a client to The ANNOTATION criterion for the SEARCH command allows a client to
search for a specified string in the value of an annotation entry of search for a specified string in the value of an annotation entry of
a message. a message.
Messages that have annotations with entries matching <entry-name> Messages that have annotations with entries matching <entry-name> and
and attributes matching <attribute-name> and the specified string attributes matching <attribute-name> and the specified string <value>
<value> in their values are returned in the SEARCH results. The "*" in their values are returned in the SEARCH results. The "*" character
character can be used in the entry or attribute name fields to match can be used in the entry or attribute name fields to match any
any content in those items. The "%" character can be used in the content in those items. The "%" character can be used in the entry or
entry or attribute name fields to match a single level of hierarchy attribute name fields to match a single level of hierarchy only.
only.
Example:
Examples:
C: a SEARCH ANNOTATION "/comment" "value" "IMAP4" C: a SEARCH ANNOTATION "/comment" "value" "IMAP4"
S: * SEARCH 2 3 5 7 11 13 17 19 23 S: * SEARCH 2 3 5 7 11 13 17 19 23
S: a OK Search complete S: a OK Search complete
In the above example, the message numbers of any messages containing In the above example, the message numbers of any messages
the string "IMAP4" in the shared or private "value" attribute of the containing the string "IMAP4" in the shared or private "value"
"/comment" entry are returned in the search results. attribute of the "/comment" entry are returned in the search
results.
Example:
C: a SEARCH ANNOTATION "*" "*" "IMAP4" C: a SEARCH ANNOTATION "*" "*" "IMAP4"
S: * SEARCH 1 2 3 5 8 13 21 34 S: * SEARCH 1 2 3 5 8 13 21 34
S: a OK Search complete S: a OK Search complete
In the above example, the message numbers of any messages containing In the above example, the message numbers of any messages
the string "IMAP4" in any attribute (public or private) of any entry containing the string "IMAP4" in any attribute (public or private)
are returned in the search results. of any entry are returned in the search results.
8.9 ANNOTATION Key in SORT 3.9 ANNOTATION Key in SORT
ANNOTATION <entry-name> <attribute-name> ANNOTATION <entry-name> <attribute-name>
The ANNOTATION criterion for the SORT command [SORT] instructs the The ANNOTATION criterion for the SORT command [SORT] instructs the
server to return the message numbers or UIDs of a mailbox, sorted server to return the message numbers or UIDs of a mailbox, sorted
using the values of the specified annotations. The ANNOTATION using the values of the specified annotations. The ANNOTATION
criterion is available if the server returns both "ANNOTATE" and criterion is available if the server returns both "ANNOTATE" and
"SORT" as supported capabilities in the CAPABILITY command response. "SORT" as supported capabilities in the CAPABILITY command response.
Messages are sorted using the values of the <attribute-name> Messages are sorted using the values of the <attribute-name>
attributes in the <entry-name> entries. (The charset argument attributes in the <entry-name> entries. (The charset argument
determines sort order, as specified in the SORT extension determines sort order, as specified in the SORT extension
description.) description.)
Examples: Example:
C: a SORT (ANNOTATION "/subject" "value.shared") UTF-8 ALL
C: a SORT (ANNOTATION "/altsubject" "value.shared") UTF-8 ALL
S: * SORT 2 3 4 5 1 11 10 6 7 9 8 S: * SORT 2 3 4 5 1 11 10 6 7 9 8
S: a OK Sort complete S: a OK Sort complete
In the above example, the message numbers of all messages are In the above example, the message numbers of all messages are
returned, sorted according to the shared "value" attribute of the returned, sorted according to the shared "value" attribute of the
"/altsubject" entry.
Gellens & Daboo Expires April 2004 [Page 17]
"/subject" entry.
Note that the ANNOTATION sort key must include a fully specified Note that the ANNOTATION sort key must include a fully specified
entry and attribute -- wildcards are not allowed. entry and attribute -- wildcards are not allowed.
9 Formal Syntax 4. Formal Syntax
The following syntax specification uses the Augmented Backus-Naur The following syntax specification uses the Augmented Backus-Naur
Form (ABNF) notation as specified in [ABNF]. Form (ABNF) notation as specified in [ABNF].
Non-terminals referenced but not defined below are as defined by Non-terminals referenced but not defined below are as defined by
[IMAP4]. [IMAP4].
Except as noted otherwise, all alphabetic characters are case- Except as noted otherwise, all alphabetic characters are
insensitive. The use of upper or lower case characters to define case-insensitive. The use of upper or lower case characters to define
token strings is for editorial clarity only. Implementations MUST token strings is for editorial clarity only. Implementations MUST
accept these strings in a case-insensitive fashion. accept these strings in a case-insensitive fashion.
annotate-param = "ANNOTATE" annotate-param = "ANNOTATE"
; defines the select parameter used with ; defines the select parameter used with
; ANNOTATE extension ; ANNOTATE extension
append = "APPEND" SP mailbox [SP flag-list] [SP date-time] append = "APPEND" SP mailbox [SP flag-list] [SP date-time]
[SP "ANNOTATION" SP att-annotate] SP literal [SP "ANNOTATION" SP att-annotate] SP literal
; modifies original IMAP4 APPEND command ; modifies original IMAP4 APPEND command
skipping to change at page 22, line ? skipping to change at page 21, line 13
attribs = att-match / attribs = att-match /
"(" att-match *(SP att-match) ")" "(" att-match *(SP att-match) ")"
entries = entry-match / entries = entry-match /
"(" entry-match *(SP entry-match) ")" "(" entry-match *(SP entry-match) ")"
entry = string entry = string
; slash-separated path to entry ; slash-separated path to entry
; MUST NOT contain "*" or "%" ; MUST NOT contain "*" or "%"
Gellens & Daboo Expires April 2004 [Page 18]
entry-att = entry SP "(" att-value *(SP att-value) ")" entry-att = entry SP "(" att-value *(SP att-value) ")"
entry-match = string entry-match = string
; slash-separated path to entry ; slash-separated path to entry
; MAY contain "*" or "%" for use as wildcards ; MAY contain "*" or "%" for use as wildcards
examine =/ *(SP "(" select-param *(SP select-param) ")" examine =/ *(SP "(" select-param *(SP select-param) ")"
; modifies the original IMAP4 examine command to ; modifies the original IMAP4 examine command to
; accept optional parameters ; accept optional parameters
fetch-ann-resp = "ANNOTATION" SP "(" entry-att *(SP entry-att) ")" fetch-ann-resp = "ANNOTATION" SP "(" entry-att *(SP entry-att) ")"
fetch-att =/ "ANNOTATION" SP "(" entries SP attribs ")" fetch-att =/ "ANNOTATION" SP "(" entries SP attribs ")"
; modifies original IMAP4 fetch-att ; modifies original IMAP4 fetch-att
resp-text-code =/ "ANNOTATE" SP "TOOBIG" / resp-text-code =/ "ANNOTATE" SP "TOOBIG" /
"ANNOTATE" SP "TOOMANY" / "ANNOTATE" SP "TOOMANY" /
"ANNOTATESIZE" SP (number / "NIL") "ANNOTATESIZE" SP (number / "NIL")
; new response codes for STORE failures ; new response codes
search-key =/ "ANNOTATION" SP entry-match SP att-match search-key =/ "ANNOTATION" SP entry-match SP att-match
SP value SP value
; modifies original IMAP4 search-key ; modifies original IMAP4 search-key
select =/ *(SP "(" select-param *(SP select-param) ")" select =/ *(SP "(" select-param *(SP select-param) ")"
; modifies the original IMAP4 select command to ; modifies the original IMAP4 select command to
; accept optional parameters ; accept optional parameters
select-param = astring / "(" astring SP astring *(SP astring) ")" select-param = astring / "(" astring SP astring *(SP astring) ")"
skipping to change at page 22, line ? skipping to change at page 22, line 4
select-param = astring / "(" astring SP astring *(SP astring) ")" select-param = astring / "(" astring SP astring *(SP astring) ")"
; parameters to SELECT may contain one or ; parameters to SELECT may contain one or
; more atoms or strings - multiple items ; more atoms or strings - multiple items
; are always parenthesised ; are always parenthesised
sort-key =/ "ANNOTATION" SP entry SP attrib sort-key =/ "ANNOTATION" SP entry SP attrib
; modifies original sort-key [SORT] ; modifies original sort-key [SORT]
store-att-flags =/ att-annotate store-att-flags =/ att-annotate
; modifies original IMAP4 STORE command ; modifies original IMAP4 STORE command
value = nstring value = nstring
10 IANA Considerations 5. IANA Considerations
Both entry names and attribute names MUST be specified in a Both entry names and attribute names MUST be specified in a standards
standards track or IESG approved experimental RFC, or fall under the track or IESG approved experimental RFC, or fall under the vendor
vendor namespace. Vendor names MUST be registered. namespace. Vendor names MUST be registered.
10.1 Entry and Attribute Registration Template 5.1 Entry and Attribute Registration Template
Gellens & Daboo Expires April 2004 [Page 19]
To: iana@iana.org To: iana@iana.org
Subject: IMAP Annotate Registration Subject: IMAP Annotate Registration
Please register the following IMAP Annotate item: Please register the following IMAP Annotate item:
[] Entry [] Attribute [] Entry [] Attribute
Name: ______________________________ Name: ______________________________
Description: _______________________ Description: _______________________
____________________________________ ____________________________________
____________________________________ ____________________________________
Contact person: ____________________ Contact person: ____________________
email: ____________________ email: ____________________
11 Security Considerations 6. Security Considerations
The ANNOTATE extension does not raise any security considerations The ANNOTATE extension does not raise any security considerations
that are not present in the base [IMAP4] protocol, and these issues that are not present in the base [IMAP4] protocol, and these issues
are discussed in [IMAP4]. are discussed in [IMAP4].
Care must be taken to ensure that annotations whose values are Care must be taken to ensure that annotations whose values are
intended to remain private are not stored in mailboxes which are intended to remain private are not stored in mailboxes which are
accessible to other users. This includes mailboxes owned by the accessible to other users. This includes mailboxes owned by the user
user by whose ACLs permit access by others as well as any shared by whose ACLs permit access by others as well as any shared
mailboxes. mailboxes.
12 Normative References Normative References
[ABNF] Crocker, Overell, "Augmented BNF for Syntax Specifications:
ABNF", RFC 2234, November 1997.
[ACAP] Newman, Myers, "ACAP -- Application Configuration Access [RFC1891] Moore, K., "SMTP Service Extension for Delivery Status
Protocol", RFC 2244, November 1997. Notifications", RFC 1891, January 1996.
[CONDSTORE] Melnikov, Hole, "IMAP Extension for Conditional STORE [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
operation", Requirement Levels", BCP 14, RFC 2119, March 1997.
<http://www.ietf.org/internet-drafts/draft-ietf-imapext-condstore-01.txt,
April 2003.
[IMAP4] Crispin, "Internet Message Access Protocol - Version 4rev1", [RFC2234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
RFC 3501, March 2003. Specifications: ABNF", RFC 2234, November 1997.
[KEYWORDS] Bradner, "Key words for use in RFCs to Indicate [RFC2244] Newman, C. and J. Myers, "ACAP -- Application
Requirement Levels", RFC 2119, March 1997. Configuration Access Protocol", RFC 2244, November 1997.
Gellens & Daboo Expires April 2004 [Page 20] [RFC3501] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION
[MDNSENT] Melnikov, "Message Disposition Notification (MDN) profile 4rev1", RFC 3501, March 2003.
for Internet Message Access Protocol (IMAP)", RFC 3503, March 2003.
[MULTIAPPEND] Crispin, "Internet Message Access Protocol (IMAP) - [RFC3502] Crispin, M., "Internet Message Access Protocol (IMAP) -
MULTIAPPEND Extension", RFC 3502, March 2003. MULTIAPPEND Extension", RFC 3502, March 2003.
[SMTP-DSN] Moore, "SMTP Service Extension for Delivery Status [RFC3503] Melnikov, A., "Message Disposition Notification (MDN)
Notifications", RFC 1891, January 1996. profile for Internet Message Access Protocol (IMAP)", RFC
3503, March 2003.
[SORT] Crispin, Murchison, "Internet Message Access Protocol - Sort
and Thread Extension", work in progress.
<http://www.ietf.org/internet-drafts/draft-ietf-imapext-sort-13.txt>
13 Informative References [SORT] Crispin, M. and K. Murchison, "Internet Message Access
Protocol - Sort and Thread Extension",
draft-ietf-imapext-sort-15.txt, April 2004.
[ACL] Myers, "IMAP4 ACL extension", RFC 2086, January 1997. Informative References
14 Acknowledgments [CONDSTORE]
Melnikov, A. and S. Hole, "IMAP Extension for Conditional
STORE operation", draft-ietf-imapext-condstore-05.txt,
April 2004.
Many thanks to Chris Newman for his detailed comments on the first [RFC2086] Myers, J., "IMAP4 ACL extension", RFC 2086, January 1997.
draft of this document, and to the participants at the ACAP working
dinner in Pittsburgh.
15 Authors' Addresses Authors' Addresses
Randall Gellens Randall Gellens
QUALCOMM Incorporated QUALCOMM Incorporated
5775 Morehouse Dr. 5775 Morehouse Dr.
San Diego, CA 92121-2779 San Diego, CA 92121-2779
U.S.A. US
Email: randy@qualcomm.com
EMail: randy@qualcomm.com
Cyrus Daboo Cyrus Daboo
Cyrusoft International, Inc. Cyrusoft International, Inc.
Suite 780, 5001 Baum Blvd. 5001 Baum Blvd.
Suite 650
Pittsburgh, PA 15213 Pittsburgh, PA 15213
U.S.A. US
Email: daboo@cyrusoft.com EMail: daboo@cyrusoft.com
16 Full Copyright Statement Appendix A. Acknowledgments
Copyright (C) The Internet Society 2003. All Rights Reserved. Many thanks to Chris Newman for his detailed comments on the first
draft of this document, and to the participants at the ACAP working
dinner in Pittsburgh.
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
Full Copyright Statement
Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
Gellens & Daboo Expires April 2004 [Page 21] included on all such copies and derivative works. However, this
kind, provided that the above copyright notice and this paragraph
are included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/