draft-ietf-imapext-annotate-07.txt   draft-ietf-imapext-annotate-08.txt 
IMAP Extensions Working Group R. Gellens IMAP Extensions Working Group R. Gellens
Internet Draft: IMAP ANNOTATE Extension C. Daboo Internet Draft: IMAP ANNOTATE Extension C. Daboo
Document: draft-ietf-imapext-annotate-07.txt May 2003 Document: draft-ietf-imapext-annotate-08.txt October 2003
IMAP ANNOTATE Extension IMAP ANNOTATE Extension
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
skipping to change at page 22, line ? skipping to change at page 22, line ?
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://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 Copyright Notice
Copyright (C) The Internet Society 2003. All Rights Reserved. Copyright (C) The Internet Society 2003. All Rights Reserved.
Gellens & Daboo Expires November 2003 [Page 1] Gellens & Daboo Expires April 2004 [Page 1]
Table of Contents Table of Contents
1 Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1 Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2 Discussion . . . . . . . . . . . . . . . . . . . . . . . . . 2 2 Discussion . . . . . . . . . . . . . . . . . . . . . . . . . 2
3 Conventions Used in This Document . . . . . . . . . . . . . . 2 3 Conventions Used in This Document . . . . . . . . . . . . . . 2
4 Change History . . . . . . . . . . . . . . . . . . . . . . . 3 4 Change History . . . . . . . . . . . . . . . . . . . . . . . 3
5 Introduction and Overview . . . . . . . . . . . . . . . . . . 4 5 Introduction and Overview . . . . . . . . . . . . . . . . . . 4
6 Data Model . . . . . . . . . . . . . . . . . . . . . . . . . 5 6 Data Model . . . . . . . . . . . . . . . . . . . . . . . . . 6
6.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . 5 6.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . 6
6.2 Namespace of Entries and Attributes . . . . . . . . . . 6 6.2 Namespace of Entries and Attributes . . . . . . . . . . 6
6.2.1 Entry Names . . . . . . . . . . . . . . . . . . . . . 6 6.2.1 Entry Names . . . . . . . . . . . . . . . . . . . . . 7
6.2.2 Attribute Names . . . . . . . . . . . . . . . . . . 8 6.2.2 Attribute Names . . . . . . . . . . . . . . . . . . 9
7 Private versus Shared and Access Control . . . . . . . . . . 9 7 Private versus Shared and Access Control . . . . . . . . . . 9
8 IMAP Protocol Changes . . . . . . . . . . . . . . . . . . . 10 8 IMAP Protocol Changes . . . . . . . . . . . . . . . . . . . 10
8.1 General considerations . . . . . . . . . . . . . . . . . 10 8.1 General considerations . . . . . . . . . . . . . . . . . 10
8.2 Optional parameters with the SELECT/EXAMINE commands . . 10 8.2 Optional parameters with the SELECT/EXAMINE commands . . 11
8.3 ANNOTATION Message Data Item in FETCH Command . . . . . . 11 8.3 ANNOTATION Message Data Item in FETCH Command . . . . . . 12
8.4 ANNOTATION Message Data Item in FETCH Response . . . . . 13 8.4 ANNOTATION Message Data Item in FETCH Response . . . . . 13
8.5 ANNOTATION Message Data Item in STORE . . . . . . . . . . 14 8.5 ANNOTATION Message Data Item in STORE . . . . . . . . . . 14
8.6 ANNOTATION interaction with COPY . . . . . . . . . . . . 15 8.6 ANNOTATION interaction with COPY . . . . . . . . . . . . 16
8.7 ANNOTATION Message Data Item in APPEND . . . . . . . . . 16 8.7 ANNOTATION Message Data Item in APPEND . . . . . . . . . 16
8.8 ANNOTATION Criterion in SEARCH . . . . . . . . . . . . . 16 8.8 ANNOTATION Criterion in SEARCH . . . . . . . . . . . . . 16
8.9 ANNOTATION Key in SORT . . . . . . . . . . . . . . . . . 17 8.9 ANNOTATION Key in SORT . . . . . . . . . . . . . . . . . 17
9 Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . 17 9 Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . 18
10 IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 10 IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
10.1 Entry and Attribute Registration Template . . . . . . . 19 10.1 Entry and Attribute Registration Template . . . . . . . 19
11 Security Considerations . . . . . . . . . . . . . . . . . . . 20 11 Security Considerations . . . . . . . . . . . . . . . . . . . 20
12 Normative References . . . . . . . . . . . . . . . . . . . . 20 12 Normative References . . . . . . . . . . . . . . . . . . . . 20
13 Informative References . . . . . . . . . . . . . . . . . . . 21 13 Informative References . . . . . . . . . . . . . . . . . . . 21
14 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 21 14 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 21
15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 21 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 21
16 Full Copyright Statement . . . . . . . . . . . . . . . . . . 21 16 Full Copyright Statement . . . . . . . . . . . . . . . . . . 21
1 Abstract 1 Abstract
skipping to change at page 22, line ? skipping to change at page 22, line ?
list, <ietf-imapext@imc.org>. To subscribe, send a message to list, <ietf-imapext@imc.org>. To subscribe, send a message to
<ietf-imapext-request@imc.org> with the word SUBSCRIBE as the body. <ietf-imapext-request@imc.org> with the word SUBSCRIBE as the body.
Private comments should be sent to the authors. Private comments should be sent to the authors.
3 Conventions Used in This Document 3 Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [KEYWORDS]. document are to be interpreted as described in RFC 2119 [KEYWORDS].
Gellens & Daboo Expires November 2003 [Page 2] Gellens & Daboo Expires April 2004 [Page 2]
Formal syntax is defined using ABNF [ABNF] as modified by [IMAP4]. Formal syntax is defined using ABNF [ABNF] as modified by [IMAP4].
In examples, "C:" and "S:" indicate lines sent by the client and In examples, "C:" and "S:" indicate lines sent by the client and
server respectively. Line breaks not preceded by a "C:" or "S:" are server respectively. Line breaks not preceded by a "C:" or "S:" are
for editorial clarity only. for editorial clarity only.
4 Change History 4 Change History
Changes from -07 to -08:
1. ANNOTATESIZE response changed to use "NIL" for a mailbox that
does not support any type of annotations, and "0" for a mailbox
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.
skipping to change at page 22, line ? skipping to change at page 22, line ?
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.
Gellens & Daboo Expires April 2004 [Page 3]
2. Added missing 'notify' and 'ret' dsn annotations for 2. Added missing 'notify' and 'ret' dsn annotations for
/message/smtp-envelope. /message/smtp-envelope.
3. Added requirement to store data permanently - no 3. Added requirement to store data permanently - no
'session only' annotations. 'session only' annotations.
4. Removed Access Control section. Replaced with comments 4. Removed Access Control section. Replaced with comments
Gellens & Daboo Expires November 2003 [Page 3]
on read-only/read-write mailboxes and storing private or on read-only/read-write mailboxes and storing private or
shared annotations. 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
skipping to change at page 22, line ? skipping to change at page 22, line ?
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 CAPABILITY command response. in 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]
5 Introduction and Overview 5 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.
Gellens & Daboo Expires November 2003 [Page 4]
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
skipping to change at page 22, line ? skipping to change at page 22, line ?
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 other extensions may want to utilise this, so it is not that other extensions may want to utilise this, so it is not
strictly dependent on the ANNOTATE extension being present. strictly 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 6 Data Model
Gellens & Daboo Expires November 2003 [Page 5]
6.1 Overview 6.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
skipping to change at page 22, line ? skipping to change at page 22, line ?
Entry and attribute names are case-insensitive. Entry and attribute names are case-insensitive.
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]
6.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
10.1 for the registration template. 10.1 for the registration template.
Gellens & Daboo Expires November 2003 [Page 6]
/ /
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 entries that start with a numeric character ("0" - "9") All entries that start with a numeric character ("0" - "9")
refer to an annotation on a specific body part. All other refer to an annotation on a specific body part. All other
entries are for annotations on the entire message. entries are for 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.
skipping to change at page 22, line ? skipping to change at page 22, line ?
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 recipient
is addressed to the original author, not the user who performed is addressed to the original author, not the user who performed
the redirection. the redirection.
Gellens & Daboo Expires November 2003 [Page 7]
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 client instead of the original message Subject. the 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 as created by a particular product of some vendor. message as created by a particular product of some vendor.
skipping to change at page 22, line ? skipping to change at page 22, line ?
/<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 Defines flags for a specific body part of a message. The
"value" attribute of these entries must be either "1", "0" or "value" attribute of these entries must be either "1", "0" or
NIL. NIL.
/<section-part>/vendor/<vendor-token> /<section-part>/vendor/<vendor-token>
Gellens & Daboo Expires April 2004 [Page 8]
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.
Gellens & Daboo Expires November 2003 [Page 8]
6.2.2 Attribute Names 6.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 10.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 fetching without using either suffix includes both. The client or fetching without using either suffix includes both. The client
MUST specify either a ".priv" or ".shared" suffix when storing an MUST specify either a ".priv" or ".shared" suffix when storing an
skipping to change at page 22, line ? skipping to change at page 22, line ?
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
Gellens & Daboo Expires April 2004 [Page 9]
shared IMAP folder containing bug reports. Engineers may want to shared IMAP folder containing bug reports. Engineers may want to
use annotations to add information to existing messages, indicate 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 ACL to permit access to a mailbox by other users may an ACL to permit access to a mailbox by other users may
Gellens & Daboo Expires November 2003 [Page 9]
unintentionally expose private information. unintentionally 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 shared annotations on messages in a shared folder, which set shared annotations on messages in a shared folder, which
individual users may wish to supplement with additional notes. individual 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 to differentiate them. Also, it should be as easy as possible way to differentiate them. Also, it should be as easy as possible
for a client to access both and not overlook either. There is also for a client to access both and not overlook either. There is also
skipping to change at page 22, line ? skipping to change at page 22, line ?
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" response. "ANNOTATESIZE" 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. For mailboxes that cannot have mailboxes and not others, or may be able to provide only read-only
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 "0" (zero) during the SELECT "ANNOTATESIZE" response with a value of "NIL" during the SELECT or
or EXAMINE command for that mailbox. Clients MUST NOT attempt to EXAMINE command for that mailbox. Clients MUST NOT attempt to fetch
fetch or store annotations on any messages in a mailbox for which or store annotations on any messages in a mailbox for which the
"ANNOTATESIZE" response was "NIL". For mailboxes that can only have
read-only annotations associated with them, the server MUST return
an "ANNOTATESIZE" response with a value of "0" (zero) during the
SELECT or EXAMINE command for that mailbox. Clients MUST NOT
attempt to store annotations on any messages in a mailbox for which
the "ANNOTATESIZE" response was zero. the "ANNOTATESIZE" response was zero.
Gellens & Daboo Expires November 2003 [Page 10]
8.2 Optional parameters with the SELECT/EXAMINE commands 8.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. It is anticipated that other extensions may
want to use this facility, so a generalised approach is given here. want to use this facility, so a generalised approach is given here.
This facility is not dependent on the presence of the ANNOTATE This facility is not dependent on the presence of the ANNOTATE
extension - other extensions can use it with a server that does not extension - other extensions can use it with a server that does not
implement ANNOTATE. implement ANNOTATE.
skipping to change at page 22, line ? skipping to change at page 22, line ?
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 command. The second parameter consists of two EXAMINE command. The second parameter consists of two
items: an atom followed by a quoted string. items: an atom followed by a quoted string.
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 In the above example, a parameter not supported by the
server is 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 8.4.
8.3 ANNOTATION Message Data Item in FETCH Command 8.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.
Gellens & Daboo Expires November 2003 [Page 11]
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")))
skipping to change at page 22, line ? skipping to change at page 22, line ?
"/subject" ("value.priv" "Rhinoceroses!" "/subject" ("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 "size" In the above example, the contents of the private "value" and "size"
attributes for any entries in the "" hierarchy are requested by the attributes for any entries in the "" hierarchy are requested by the
client and returned by the server. client and returned by the server.
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 "/subject" ("value.shared" "Patches? We don't
need no steenkin patches!"))) need no steenkin patches!")))
S: a OK Fetch complete S: a OK Fetch complete
Gellens & Daboo Expires November 2003 [Page 12]
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 are requested by the client and returned by the hierarchy 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: Examples:
skipping to change at page 22, line ? skipping to change at page 22, line ?
Examples: Examples:
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).
C: a FETCH 1 (ANNOTATION C: a FETCH 1 (ANNOTATION
(("/comment" "/subject") "value")) (("/comment" "/subject") "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" "/subject" ("value.priv" "My subject"
"value.shared" NIL))) "value.shared" NIL)))
S: a OK Fetch complete S: a OK Fetch complete
Gellens & Daboo Expires November 2003 [Page 13]
In the above example, two entries each with a single attribute-value In the above example, two entries each with a single attribute-value
pair are returned by the server. Since the client did not specify a pair are returned by the server. Since the client did not specify a
".shared" or ".priv" suffix, both are returned. Only the private ".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.
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"
skipping to change at page 22, line ? skipping to change at page 22, line ?
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 8.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 for values of attributes it wants to remove from entries. NIL 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 an untagged FETCH in response to the STORE command and generate an untagged FETCH in response to the STORE command and
assumes that the client updates its own cache if the command assumes that 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 number of allowed annotations has already been reached, the maximum number of allowed annotations has already been reached, the
server MUST return a tagged NO response with a "[ANNOTATE TOOMANY]" server MUST return a tagged NO response with a "[ANNOTATE TOOMANY]"
Gellens & Daboo Expires November 2003 [Page 14]
response code. response code.
Examples: 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 to
"My new comment" is created if not already present, or replaced if "My new comment" is created if not already present, or replaced if
skipping to change at page 22, line ? skipping to change at page 22, line ?
In the above example, the entries "/comment" and "/subject" are In the above example, the entries "/comment" and "/subject" 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" C: a STORE 1 ANNOTATION ("/comment"
Gellens & Daboo Expires April 2004 [Page 15]
("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 present) and the private attributes "value" and already present) and the private attributes "value" and
"vendor.foobar" are created if not already present, or replaced if "vendor.foobar" are created if not already present, or replaced if
they exist. they exist.
8.6 ANNOTATION interaction with COPY 8.6 ANNOTATION interaction with COPY
Gellens & Daboo Expires November 2003 [Page 15]
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 copy all the annotation data associated with any
messages being copied via the COPY command. The only exceptions to messages being copied via the COPY command. The only exceptions to
this are if the destination mailbox permissions are such that either this are if the destination mailbox permissions are such that either
the '.priv' or '.shared' annotations are not allowed, or if the the '.priv' or '.shared' annotations are not allowed, or if the
destination mailbox is of a type that does not support annotations destination mailbox is of a type that does not support annotations
(and returns a zero value for its ANNOTATESIZE response code). or does not support storing of annotations (a mailbox that returns a
zero or "NIL" value for its ANNOTATESIZE response code).
8.7 ANNOTATION Message Data Item in APPEND 8.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 Sets the specified list of entries and attributes in the
resulting message. 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
skipping to change at page 22, line ? skipping to change at page 22, line ?
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 8.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 attributes matching <attribute-name> and the specified string and attributes matching <attribute-name> and the specified string
<value> in their values are returned in the SEARCH results. The "*" <value> in their values are returned in the SEARCH results. The "*"
character can be used in the entry or attribute name fields to match character can be used in the entry or attribute name fields to match
any content in those items. The "%" character can be used in the any content in those items. The "%" character can be used in the
entry or attribute name fields to match a single level of hierarchy entry or attribute name fields to match a single level of hierarchy
only. only.
Gellens & Daboo Expires November 2003 [Page 16]
Examples: 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 containing
the string "IMAP4" in the shared or private "value" attribute of the the string "IMAP4" in the shared or private "value" attribute of the
"/comment" entry are returned in the search results. "/comment" entry are returned in the search results.
C: a SEARCH ANNOTATION "*" "*" "IMAP4" C: a SEARCH ANNOTATION "*" "*" "IMAP4"
skipping to change at page 22, line ? skipping to change at page 22, line ?
determines sort order, as specified in the SORT extension determines sort order, as specified in the SORT extension
description.) description.)
Examples: Examples:
C: a SORT (ANNOTATION "/subject" "value.shared") UTF-8 ALL C: a SORT (ANNOTATION "/subject" "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
Gellens & Daboo Expires April 2004 [Page 17]
"/subject" entry. "/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 9 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].
Gellens & Daboo Expires November 2003 [Page 17]
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 case-
insensitive. The use of upper or lower case characters to define 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
skipping to change at page 22, line ? skipping to change at page 22, line ?
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
Gellens & Daboo Expires November 2003 [Page 18]
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 "ANNOTATESIZE" SP (number / "NIL")
; new response codes for STORE failures ; new response codes for STORE failures
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
skipping to change at page 22, line ? skipping to change at page 22, line ?
value = nstring value = nstring
10 IANA Considerations 10 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 track or IESG approved experimental RFC, or fall under the standards track or IESG approved experimental RFC, or fall under the
vendor namespace. Vendor names MUST be registered. vendor namespace. Vendor names MUST be registered.
10.1 Entry and Attribute Registration Template 10.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: _______________________
Gellens & Daboo Expires November 2003 [Page 19]
____________________________________ ____________________________________
____________________________________ ____________________________________
Contact person: ____________________ Contact person: ____________________
email: ____________________ email: ____________________
11 Security Considerations 11 Security Considerations
skipping to change at page 22, line ? skipping to change at page 22, line ?
operation", operation",
<http://www.ietf.org/internet-drafts/draft-ietf-imapext-condstore-01.txt, <http://www.ietf.org/internet-drafts/draft-ietf-imapext-condstore-01.txt,
April 2003. April 2003.
[IMAP4] Crispin, "Internet Message Access Protocol - Version 4rev1", [IMAP4] Crispin, "Internet Message Access Protocol - Version 4rev1",
RFC 3501, March 2003. RFC 3501, March 2003.
[KEYWORDS] Bradner, "Key words for use in RFCs to Indicate [KEYWORDS] Bradner, "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, March 1997. Requirement Levels", RFC 2119, March 1997.
Gellens & Daboo Expires April 2004 [Page 20]
[MDNSENT] Melnikov, "Message Disposition Notification (MDN) profile [MDNSENT] Melnikov, "Message Disposition Notification (MDN) profile
for Internet Message Access Protocol (IMAP)", RFC 3503, March 2003. for Internet Message Access Protocol (IMAP)", RFC 3503, March 2003.
[MULTIAPPEND] Crispin, "Internet Message Access Protocol (IMAP) - [MULTIAPPEND] Crispin, "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 [SMTP-DSN] Moore, "SMTP Service Extension for Delivery Status
Notifications", RFC 1891, January 1996. Notifications", RFC 1891, January 1996.
[SORT] Crispin, Murchison, "Internet Message Access Protocol - Sort [SORT] Crispin, Murchison, "Internet Message Access Protocol - Sort
and Thread Extension", work in progress. and Thread Extension", work in progress.
<http://www.ietf.org/internet-drafts/draft-ietf-imapext-sort-13.txt> <http://www.ietf.org/internet-drafts/draft-ietf-imapext-sort-13.txt>
Gellens & Daboo Expires November 2003 [Page 20]
13 Informative References 13 Informative References
[ACL] Myers, "IMAP4 ACL extension", RFC 2086, January 1997. [ACL] Myers, "IMAP4 ACL extension", RFC 2086, January 1997.
14 Acknowledgments 14 Acknowledgments
Many thanks to Chris Newman for his detailed comments on the first Many thanks to Chris Newman for his detailed comments on the first
draft of this document, and to the participants at the ACAP working draft of this document, and to the participants at the ACAP working
dinner in Pittsburgh. dinner in Pittsburgh.
skipping to change at page 22, line ? skipping to change at page 22, line ?
Email: daboo@cyrusoft.com Email: daboo@cyrusoft.com
16 Full Copyright Statement 16 Full Copyright Statement
Copyright (C) The Internet Society 2003. All Rights Reserved. Copyright (C) The Internet Society 2003. 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
Gellens & Daboo Expires April 2004 [Page 21]
kind, provided that the above copyright notice and this paragraph kind, provided that the above copyright notice and this paragraph
are included on all such copies and derivative works. However, this 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 assigns.
Gellens & Daboo Expires November 2003 [Page 21]
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.
 End of changes. 

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