draft-ietf-lemonade-imap-notify-00.txt   draft-ietf-lemonade-imap-notify-01.txt 
Network Working Group Curtis King Network Working Group Curtis King
Internet-Draft Alexey Melnikov Internet-Draft Alexey Melnikov
Intended Status: Proposed Standard Isode Ltd. Intended Status: Proposed Standard Isode Ltd.
Arnt Gulbrandsen Arnt Gulbrandsen
Oryx Mail Systems GmbH Oryx Mail Systems GmbH
August 25, 2007 November 14, 2007
The IMAP NOTIFY Extension The IMAP NOTIFY Extension
draft-ietf-lemonade-imap-notify-00.txt draft-ietf-lemonade-imap-notify-01.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
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 1, line 44 skipping to change at page 1, line 44
This Internet-Draft expires in November 2007. This Internet-Draft expires in November 2007.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document defines an IMAP extension which allows a client to This document defines an IMAP extension which allows a client to
request specific kinds of unsolicited notifications, such as request specific kinds of unsolicited notifications for specified
messages being added to or deleted from mailboxes. mailboxes, such as messages being added to or deleted from
mailboxes.
Internet-draft August 2007 Internet-draft November 2007
1. Conventions Used in This Document 1. 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 [RFC2119]. document are to be interpreted as described in [RFC2119].
Formal syntax is defined by [RFC4234] as extended by [RFC3501] and Formal syntax is defined by [RFC4234] as extended by [RFC3501] and
[RFC4466]. [RFC4466].
skipping to change at page 2, line 29 skipping to change at page 2, line 29
Example lines prefaced by "C:" are sent by the client and ones Example lines prefaced by "C:" are sent by the client and ones
prefaced by "S:" by the server. "[...]" means elision. prefaced by "S:" by the server. "[...]" means elision.
2. Overview 2. Overview
The IDLE command (defined in [RFC2177]) provides a way for the The IDLE command (defined in [RFC2177]) provides a way for the
client to go into a mode where the IMAP server pushes notifications client to go into a mode where the IMAP server pushes notifications
about IMAP mailstore events for the selected mailbox. However, the about IMAP mailstore events for the selected mailbox. However, the
IDLE extension doesn't restrict or control which server events can IDLE extension doesn't restrict or control which server events can
be sent, or what information the server sends in response to each be sent, or what information the server sends in response to each
event. event. Also, IDLE only applies to the selected mailbox, thus
requiring an additional TCP connection per mailbox.
This document defines an IMAP extension that allows clients to This document defines an IMAP extension that allows clients to
express their preferences about unsolicited events generated by the express their preferences about unsolicited events generated by the
server. The extension allows clients to only receive events they server. The extension allows clients to only receive events they
are interested in, while servers know that they don't need to go are interested in, while servers know that they don't need to go
into effort of generating certain types of untagged responses. into effort of generating certain types of untagged responses.
IMAP servers which support this extension advertise the X-DRAFT- IMAP servers which support this extension advertise the X-DRAFT-
W00-NOTIFY extension. W00-NOTIFY extension.
skipping to change at page 3, line 5 skipping to change at page 3, line 5
3. The NOTIFY Command 3. The NOTIFY Command
Arguments: "ADD" or "SET" Arguments: "ADD" or "SET"
optional STATUS indicator optional STATUS indicator
Mailboxes to be watched Mailboxes to be watched
Events about which to notify the client Events about which to notify the client
Or Or
Arguments: "NONE" Arguments: "NONE"
Internet-draft August 2007 Internet-draft November 2007
Responses: Possibly untagged STATUS responses (for ADD/SET) Responses: Possibly untagged STATUS responses (for ADD/SET)
Result: OK - The server will notify the client as requested. Result: OK - The server will notify the client as requested.
NO - NOTIFY too complex or expensive, etc. NO - NOTIFY too complex or expensive, etc.
BAD - Command unknown, invalid, unsupported or unknown BAD - Command unknown, invalid, unsupported or unknown
arguments. arguments.
The NOTIFY command informs the server that the client listens for The NOTIFY command informs the server that the client listens for
event notifications all the time (even when no command is in event notifications all the time (even when no command is in
skipping to change at page 4, line 5 skipping to change at page 4, line 5
MESSAGES, UIDNEXT and UIDVALIDITY. If MessageExpunge is enabled, the MESSAGES, UIDNEXT and UIDVALIDITY. If MessageExpunge is enabled, the
STATUS response MUST contain MESSAGES. If either AnnotationChange or STATUS response MUST contain MESSAGES. If either AnnotationChange or
FlagChange are included, the STATUS response MUST contain FlagChange are included, the STATUS response MUST contain
UIDVALIDITY and HIGHESTMODSEQ. Absence of the STATUS indicator UIDVALIDITY and HIGHESTMODSEQ. Absence of the STATUS indicator
parameter allows the client to avoid the additional STATUS parameter allows the client to avoid the additional STATUS
responses. This might be useful if the client has already retrieved responses. This might be useful if the client has already retrieved
this information before issuing the NOTIFY command. this information before issuing the NOTIFY command.
Clients are advised to limit the number of mailboxes used with Clients are advised to limit the number of mailboxes used with
Internet-draft August 2007 Internet-draft November 2007
NOTIFY. Particularly, if a client asks for events for all accessible NOTIFY. Particularly, if a client asks for events for all accessible
mailboxes, the server may swamp the client with updates about shared mailboxes, the server may swamp the client with updates about shared
mailboxes. This wastes both server resources and network traffic. mailboxes. This wastes both server resources and network traffic.
For each mailbox specified, the server verifies that the client has For each mailbox specified, the server verifies that the client has
access using the following test: access using the following test:
- If the name does not refer to an existing mailbox, the server MUST - If the name does not refer to an existing mailbox, the server MUST
ignore it. ignore it.
skipping to change at page 5, line 5 skipping to change at page 5, line 5
If the client requests information for events of an unsupported type If the client requests information for events of an unsupported type
(e.g. QuotaExceed and the server does not advertise the QUOTA (e.g. QuotaExceed and the server does not advertise the QUOTA
extension defined in [RFC2087]), the server MUST refuse the command extension defined in [RFC2087]), the server MUST refuse the command
with a tagged BAD response. with a tagged BAD response.
Here's an example: Here's an example:
S: * OK [CAPABILITY IMAP4REV1 NOTIFY] S: * OK [CAPABILITY IMAP4REV1 NOTIFY]
C: a login bob alice C: a login bob alice
Internet-draft August 2007 Internet-draft November 2007
S: a OK Password matched S: a OK Password matched
C: b notify set status (selected MessageNew (uid C: b notify set status (selected MessageNew (uid
body.peek[header.fields (from to subject)]) (all) body.peek[header.fields (from to subject)]) (all)
MessageExpunge) (subtree Lists MessageNew (uid) (all)) MessageExpunge) (subtree Lists MessageNew (uid) (all))
S: * STATUS Lists/Lemonade (UIDVALIDITY 4 UIDNEXT 9999 MESSAGES S: * STATUS Lists/Lemonade (UIDVALIDITY 4 UIDNEXT 9999 MESSAGES
500) 500)
S: [...] S: [...]
S: * STATUS Lists/Im2000 (UIDVALIDITY 901 UIDNEXT 1 MESSAGES 0) S: * STATUS Lists/Im2000 (UIDVALIDITY 901 UIDNEXT 1 MESSAGES 0)
S: b OK done S: b OK done
skipping to change at page 6, line 5 skipping to change at page 6, line 5
If IDLE (as well as this extension) is supported, while processing If IDLE (as well as this extension) is supported, while processing
IDLE the server MUST send the same events as instructed by the IDLE the server MUST send the same events as instructed by the
client using the NOTIFY command. client using the NOTIFY command.
NOTIFY makes IDLE unnecessary for some clients. If a client does not NOTIFY makes IDLE unnecessary for some clients. If a client does not
use MSNs and '*' in commands, it can request MessageExpunge and use MSNs and '*' in commands, it can request MessageExpunge and
MessageNew for the selected mailbox using the NOTIFY command instead MessageNew for the selected mailbox using the NOTIFY command instead
of entering the IDLE mode. of entering the IDLE mode.
Internet-draft August 2007 Internet-draft November 2007
5. Event Types 5. Event Types
Only some of the events in [MSGEVENT] can be expressed in IMAP, and Only some of the events in [MSGEVENT] can be expressed in IMAP, and
for some of them there are several possible ways to express the for some of them there are several possible ways to express the
event. event.
This section specifies the events of which an IMAP server can notify This section specifies the events of which an IMAP server can notify
an IMAP client, and how. an IMAP client, and how.
skipping to change at page 7, line 5 skipping to change at page 7, line 5
on whether CONDSTORE [RFC4551] is being used. If so, the server on whether CONDSTORE [RFC4551] is being used. If so, the server
sends a STATUS (HIGHESTMODSEQ) response. (Note that whenever mailbox sends a STATUS (HIGHESTMODSEQ) response. (Note that whenever mailbox
UIDVALIDITY changes, the server MUST also include UIDVALIDITY in the UIDVALIDITY changes, the server MUST also include UIDVALIDITY in the
STATUS response.) If not, the server does not notify the client. STATUS response.) If not, the server does not notify the client.
FlagChange covers the MessageRead, MessageTrash, FlagsSet and FlagChange covers the MessageRead, MessageTrash, FlagsSet and
FlagsClear events in [MSGEVENT]. FlagsClear events in [MSGEVENT].
[[Open Issue: Filip Navara requested for STATUS (UNSEEN) to be sent [[Open Issue: Filip Navara requested for STATUS (UNSEEN) to be sent
Internet-draft August 2007 Internet-draft November 2007
for MessageRead. Arnt considers that unsound, since it involves for MessageRead. Arnt considers that unsound, since it involves
processing all messages in a mailbox after an event affecting only processing all messages in a mailbox after an event affecting only
one message, and since it's not reliable anyway.]] one message, and since it's not reliable anyway.]]
Example in the selected mailbox: Example in the selected mailbox:
S: * 99 FETCH (UID 9999 FLAGS ($Junk)) S: * 99 FETCH (UID 9999 FLAGS ($Junk))
And in another, with CONDSTORE in use: And in another, with CONDSTORE in use:
S: * STATUS Lists/Lemonade (HIGHESTMODSEQ 65666665) S: * STATUS Lists/Lemonade (HIGHESTMODSEQ 65666665)
skipping to change at page 8, line 5 skipping to change at page 8, line 5
Example in the selected mailbox: Example in the selected mailbox:
S: * 444 EXISTS S: * 444 EXISTS
S: * 444 FETCH (UID 9999) S: * 444 FETCH (UID 9999)
And in another, without CONDSTORE: And in another, without CONDSTORE:
S: * STATUS Lists/Lemonade (UIDNEXT 10002 MESSAGES 503) S: * STATUS Lists/Lemonade (UIDNEXT 10002 MESSAGES 503)
5.3. MessageExpunge 5.3. MessageExpunge
Internet-draft August 2007 Internet-draft November 2007
If the expunged message(s) is/are in the selected mailbox, the If the expunged message(s) is/are in the selected mailbox, the
server notifies the client using EXPUNGE (or VANISHED, if [QRESYNC] server notifies the client using EXPUNGE (or VANISHED, if [QRESYNC]
is being used). is being used).
If the expunged message(s) is/are in another mailbox, the server If the expunged message(s) is/are in another mailbox, the server
sends an unsolicited STATUS (UIDNEXT MESSAGES) response for the sends an unsolicited STATUS (UIDNEXT MESSAGES) response for the
relevant mailbox. If CONDSTORE is being used, HIGHESTMODSEQ MUST be relevant mailbox. If CONDSTORE is being used, HIGHESTMODSEQ MUST be
included in the STATUS response. included in the STATUS response.
skipping to change at page 9, line 5 skipping to change at page 9, line 5
These notifications are sent if the client has requested These notifications are sent if the client has requested
notifications for at least one affected mailbox. notifications for at least one affected mailbox.
Example: Example:
S: * QUOTAROOT INBOX "" S: * QUOTAROOT INBOX ""
S: * QUOTA "" (STORAGE 10 512) S: * QUOTA "" (STORAGE 10 512)
In this example the quota root named "" (see [RFC2087] for the In this example the quota root named "" (see [RFC2087] for the
definition of quota root) governs the mailbox INBOX. Note that the definition of quota root) governs the mailbox INBOX. Note that the
server may return the QUOTAROOT and the QUOTA response in any order. server may return the QUOTAROOT and the QUOTA response in any order.
Internet-draft August 2007 Internet-draft November 2007
5.5. MailboxCreate and MailboxDelete 5.5. MailboxCreate and MailboxDelete
The server notifies the client by sending an unsolicited LIST The server notifies the client by sending an unsolicited LIST
responses for each affected mailbox name. If the mailbox name does responses for each affected mailbox name. If the mailbox name does
not refer to a mailbox after the event, the \Nonexistent flag MUST not refer to a mailbox after the event, the \Nonexistent flag MUST
be included. be included.
These notifications are sent if the client has requested These notifications are sent if the client has requested
notifications for at least one affected mailbox. In the case of notifications for at least one affected mailbox. In the case of
MailboxCreate, the mailbox itself and its parent are considered to MailboxCreate, the mailbox itself and its parent are considered to
be affected. In the case of MailboxDelete, all deleted mailboxes and be affected. In the case of MailboxDelete, all deleted mailboxes and
their parent(s) are considered to be affected. their parent(s) are considered to be affected.
Example of a newly created mailbox: Example of a newly created mailbox:
S: * LIST () "/" "NewMailbox" S: * LIST () "/" "NewMailbox"
And a deleted mailbox: And a deleted mailbox:
S: * LIST (\NoSelect) "/" "INBOX.DeletedMailbox" S: * LIST (\NonExistent) "/" "INBOX.DeletedMailbox"
5.6. MailboxRename 5.6. MailboxRename
For each selectable mailbox renamed, the server sends an extended For each selectable mailbox renamed, the server sends an extended
LIST response [LISTEXT] for the new mailbox name, containing the LIST response [LISTEXT] for the new mailbox name, containing the
OLDNAME extended data item with the old mailbox name. When a OLDNAME extended data item with the old mailbox name. When a
mailbox is renamed, its children are renamed too. No additional mailbox is renamed, its children are renamed too. No additional
MailboxRename events are sent for children in this case. When INBOX MailboxRename events are sent for children in this case. When INBOX
is renamed, a new INBOX is assumed to be created. No MailboxCreate is renamed, a new INBOX is assumed to be created. No MailboxCreate
event must be sent for INBOX in this case. event must be sent for INBOX in this case.
skipping to change at page 10, line 5 skipping to change at page 10, line 5
is subscribed after the event, the \Subscribed attribute (see is subscribed after the event, the \Subscribed attribute (see
[LISTEXT]) is included. [LISTEXT]) is included.
Example: Example:
S: * LIST (\Subscribed) "/" "SubscribedMailbox" S: * LIST (\Subscribed) "/" "SubscribedMailbox"
5.8. MailboxMetadataChange 5.8. MailboxMetadataChange
The server sends an unsolicited LIST response including METADATA. If The server sends an unsolicited LIST response including METADATA. If
Internet-draft August 2007 Internet-draft November 2007
possible, only the changed metadata should be included, but if possible, only the changed metadata should be included, but if
necessary, all metadata must be included. necessary, all metadata must be included.
Example: Example:
S: * LIST "/" "INBOX" (METADATA (/comment (value.priv "My S: * LIST "/" "INBOX" (METADATA (/comment (value.priv "My
comment"))) comment")))
5.9. AdminMailbox 5.9. AdminMailbox
skipping to change at page 11, line 5 skipping to change at page 11, line 5
Example: Example:
S: * OK [NOTIFICATIONOVERFLOW] ...A comment can go here... S: * OK [NOTIFICATIONOVERFLOW] ...A comment can go here...
5.11. ACL Changes 5.11. ACL Changes
Even if NOTIFY succeeds, it is still possible to lose access to the Even if NOTIFY succeeds, it is still possible to lose access to the
mailboxes monitoried at a later time. If this happens, the server mailboxes monitoried at a later time. If this happens, the server
MUST silently stop monitoring these mailboxes. If access is later MUST silently stop monitoring these mailboxes. If access is later
Internet-draft August 2007 Internet-draft November 2007
granted, the server MUST restart event monitoring. granted, the server MUST restart event monitoring.
6. Mailbox Specification. 6. Mailbox Specification.
Mailboxes to be monitored can be specified in several different Mailboxes to be monitored can be specified in several different
ways. ways.
If the client specifies monitoring of the same mailbox several If the client specifies monitoring of the same mailbox several
times, the first specification wins. A common example is asking for times, the first specification wins. A common example is asking for
skipping to change at page 12, line 5 skipping to change at page 12, line 5
If the IMAP server cannot easily compute this set, it MUST treat If the IMAP server cannot easily compute this set, it MUST treat
"inboxes" as equivalent to "personal". "inboxes" as equivalent to "personal".
6.4 Subscribed 6.4 Subscribed
Subscribed refers to all mailboxes subscribed by the user. Subscribed refers to all mailboxes subscribed by the user.
If the subscription list changes, the list MUST be reevaluated. If the subscription list changes, the list MUST be reevaluated.
Internet-draft August 2007 Internet-draft November 2007
6.5 Subtree 6.5 Subtree
Subtree is followed by a mailbox name or list of mailbox names. A Subtree is followed by a mailbox name or list of mailbox names. A
subtree refers to all selectable mailboxes which are subordinate to subtree refers to all selectable mailboxes which are subordinate to
the specified mailbox plus the mailbox itself. the specified mailbox plus the mailbox itself.
[[Open Issue: Making this "all selectable mailboxes" makes it easy [[Open Issue: Making this "all selectable mailboxes" makes it easy
to implement this well. The pattern can be evaluated at NOTIFY time to implement this well. The pattern can be evaluated at NOTIFY time
and notification information affixed to the mailboxes in RAM. Fine. and notification information affixed to the mailboxes in RAM. Fine.
skipping to change at page 13, line 5 skipping to change at page 13, line 5
notify = "NOTIFY" SP notify = "NOTIFY" SP
(notify-add / notify-set / notify-none) (notify-add / notify-set / notify-none)
notify-add = "ADD" [status-indicator] SP event-groups notify-add = "ADD" [status-indicator] SP event-groups
; Add (prepend) registered notification ; Add (prepend) registered notification
; events to the list of notification ; events to the list of notification
; events. Newer events override older ; events. Newer events override older
; events. ; events.
[[Alexey: what about "most specific" event [[Alexey: what about "most specific" event
Internet-draft August 2007 Internet-draft November 2007
overriding a pattern?]] overriding a pattern?]]
notify-set = "SET" [status-indicator] SP event-groups notify-set = "SET" [status-indicator] SP event-groups
; Replace registered notification events ; Replace registered notification events
; with the specified list of events ; with the specified list of events
notify-none = "NONE" notify-none = "NONE"
; Cancel all registered notification ; Cancel all registered notification
; events. The client is not interested ; events. The client is not interested
skipping to change at page 14, line 5 skipping to change at page 14, line 5
SP message-match-criteria ) SP message-match-criteria )
/ "MessageExpunge" / "MessageExpunge"
/ "FlagChange" SP message-match-criteria / "FlagChange" SP message-match-criteria
/ "AnnotationChange" SP message-match-criteria / "AnnotationChange" SP message-match-criteria
;; "MessageNew" includes "MessageAppend" from ;; "MessageNew" includes "MessageAppend" from
;; [MSGEVENT]. "FlagChange" is any of ;; [MSGEVENT]. "FlagChange" is any of
;; "MessageRead", "MessageTrash", "FlagsSet", ;; "MessageRead", "MessageTrash", "FlagsSet",
;; "FlagsClear" [MSGEVENT]. "MessageExpunge" ;; "FlagsClear" [MSGEVENT]. "MessageExpunge"
;; includes "MessageExpire" [MSGEVENT]. ;; includes "MessageExpire" [MSGEVENT].
Internet-draft August 2007 Internet-draft November 2007
mailbox-event = "MailboxCreate" / "MailboxDelete" / mailbox-event = "MailboxCreate" / "MailboxDelete" /
"MailboxRename" / "MailboxRename" /
"SubscriptionChange" / "MailboxMetadataChange" "SubscriptionChange" / "MailboxMetadataChange"
/ "QuotaChange" / "AdminMailbox" / "QuotaChange" / "AdminMailbox"
; "SubscriptionChange" includes ; "SubscriptionChange" includes
; MailboxSubscribe and MailboxUnSubscribe ; MailboxSubscribe and MailboxUnSubscribe
user-event = "QuotaExceed" / "QuotaWithin" user-event = "QuotaExceed" / "QuotaWithin"
skipping to change at page 15, line 5 skipping to change at page 15, line 5
to delete sensitive messages using programs like imapfilter. Using to delete sensitive messages using programs like imapfilter. Using
[SIEVE] or similar is much better. [SIEVE] or similar is much better.
9. IANA considerations 9. IANA considerations
The IANA is requested to add NOTIFY to the list of IMAP extensions, The IANA is requested to add NOTIFY to the list of IMAP extensions,
http://www.iana.org/assignments/imap4-capabilities. http://www.iana.org/assignments/imap4-capabilities.
9.1. Initial LIST-EXTENDED extended data item registrations 9.1. Initial LIST-EXTENDED extended data item registrations
Internet-draft August 2007 Internet-draft November 2007
It is requested that the following entry be added to the LIST- It is requested that the following entry be added to the LIST-
EXTENDED extended data item registry [LISTEXT]: EXTENDED extended data item registry [LISTEXT]:
To: iana@iana.org Subject: Registration of OLDNAME LIST-EXTENDED To: iana@iana.org Subject: Registration of OLDNAME LIST-EXTENDED
extended data item extended data item
LIST-EXTENDED extended data item tag: OLDNAME LIST-EXTENDED extended data item tag: OLDNAME
LIST-EXTENDED extended data item description: The OLDNAME extended LIST-EXTENDED extended data item description: The OLDNAME extended
skipping to change at page 16, line 5 skipping to change at page 16, line 5
[RFC2087] Myers, "IMAP4 QUOTA extension", RFC 2087, January 1997. [RFC2087] Myers, "IMAP4 QUOTA extension", RFC 2087, January 1997.
[RFC2119] Bradner, "Key words for use in RFCs to Indicate [RFC2119] Bradner, "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, Harvard University, March Requirement Levels", RFC 2119, Harvard University, March
1997. 1997.
[RFC2177] Leiba, "IMAP4 IDLE Command", RFC 2177, IBM, June 1997. [RFC2177] Leiba, "IMAP4 IDLE Command", RFC 2177, IBM, June 1997.
[RFC3501] Crispin, "Internet Message Access Protocol - Version [RFC3501] Crispin, "Internet Message Access Protocol - Version
Internet-draft August 2007 Internet-draft November 2007
4rev1", RFC 3501, University of Washington, June 2003. 4rev1", RFC 3501, University of Washington, June 2003.
[RFC4234] Crocker, Overell, "Augmented BNF for Syntax [RFC4234] Crocker, Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 4234, Brandenburg Specifications: ABNF", RFC 4234, Brandenburg
Internetworking, Demon Internet Ltd, October 2005. Internetworking, Demon Internet Ltd, October 2005.
[RFC4314] Melnikov, "IMAP4 Access Control List (ACL) Extension", [RFC4314] Melnikov, "IMAP4 Access Control List (ACL) Extension",
RFC 4314, December 2005. RFC 4314, December 2005.
skipping to change at page 17, line 5 skipping to change at page 17, line 5
Mirapoint Inc, January 2001. Mirapoint Inc, January 2001.
[QRESYNC] Melnikov, Cridland, Wilson, "IMAP4 Extensions for Quick [QRESYNC] Melnikov, Cridland, Wilson, "IMAP4 Extensions for Quick
Mailbox Resynchronization", draft-ietf-lemonade- Mailbox Resynchronization", draft-ietf-lemonade-
reconnect-client-05.txt (work in progress), February reconnect-client-05.txt (work in progress), February
2007. 2007.
[EMAIL-ARCH] Crocker, "Internet Mail Architecture", draft-crocker- [EMAIL-ARCH] Crocker, "Internet Mail Architecture", draft-crocker-
email-arch-09 (work in progress), March 2007. email-arch-09 (work in progress), March 2007.
Internet-draft August 2007 Internet-draft November 2007
13. Authors' Addresses 13. Authors' Addresses
Curtis King Curtis King
Isode Ltd Isode Ltd
5 Castle Business Village 5 Castle Business Village
36 Station Road 36 Station Road
Hampton, Middlesex TW12 2BX Hampton, Middlesex TW12 2BX
UK UK
skipping to change at page 18, line 5 skipping to change at page 18, line 5
Email: Alexey.Melnikov@isode.com Email: Alexey.Melnikov@isode.com
Arnt Gulbrandsen Arnt Gulbrandsen
Oryx Mail Systems GmbH Oryx Mail Systems GmbH
Schweppermannstr. 8 Schweppermannstr. 8
D-81671 Muenchen D-81671 Muenchen
Germany Germany
Email: arnt@oryx.com Email: arnt@oryx.com
Internet-draft August 2007 Internet-draft November 2007
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed Intellectual Property Rights or other rights that might be claimed
to pertain to the implementation or use of the technology described to pertain to the implementation or use of the technology described
in this document or the extent to which any license under such in this document or the extent to which any license under such
rights might or might not be available; nor does it represent that rights might or might not be available; nor does it represent that
it has made any independent effort to identify any such rights. it has made any independent effort to identify any such rights.
Information on the procedures with respect to rights in RFC Information on the procedures with respect to rights in RFC
 End of changes. 22 change blocks. 
23 lines changed or deleted 25 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/