Network Working Group Curtis King
Internet-Draft Alexey Melnikov
Intended Status: Proposed Standard Isode Ltd.
Arnt Gulbrandsen
Oryx Mail Systems GmbH
May 2007
The IMAP NOTIFY Extension
draft-gulbrandsen-imap-notify-06.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
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
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-
Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft expires in November 2007.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Abstract
This document defines an IMAP extension which allows a client to
request specific kinds of unsolicited notifications, such as
messages being added to or deleted from mailboxes.
King, et al. Expires November 2007 [Page 1]
Internet-draft April 2007
1. 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 [RFC2119].
Formal syntax is defined by [RFC4234] as extended by [RFC3501] and
[RFC4466].
Example lines prefaced by "C:" are sent by the client and ones
prefaced by "S:" by the server. "[...]" means elision.
2. Overview
The IDLE command (defined in [RFC2177]) provides a way for the
client to go into a mode where the IMAP server pushes notifications
about IMAP mailstore events for the selected mailbox. However, the
IDLE extension doesn't restrict or control which server events can
be sent, or what information the server sends in response to each
event.
This document defines an IMAP extension that allows clients to
express their preferences about unsolicited events generated by the
server. The extension allows clients to only receive events they
are interested in, while servers know that they don't need to go
into effort of generating certain types of untagged responses.
IMAP servers which support this extension advertise the X-DRAFT-
I06-NOTIFY extension.
Comments regarding this draft may be sent either to the
lemonade@ietf.org mailing list or to the authors.
3. The NOTIFY Command
Arguments: Mailboxes to be watched
Events about which to notify the client
Responses: Possibly untagged STATUS responses
Result: OK The server will notify the client as requested.
NO NOTIFY too complex or expensive, lack of permissions.
BAD Command unknown, invalid, unsupported or unknown
arguments.
The NOTIFY command informs the server that the client listens for
King, et al. Expires November 2007 [Page 2]
Internet-draft April 2007
event notifications all the time (even when no command is in
progress) and requests the server to notify it about the specified
set of events.
Until the NOTIFY command is used for the first time, the server only
sends notifications while a command is being processed, and notifies
the client about these events on the selected mailbox: (see section
5 for definitions): NewMessage, ExpungeMessage, FlagChange and (if
[ANNOTATE] is being used) AnnotationChange. By default, the
notification about NewMessage events includes the message's UID and
flags. The server does not notify the client about any events on
other mailboxes.
The effect of NOTIFY lasts until the next NOTIFY command, or until
the IMAP connection is closed.
If the NOTIFY command enables NewMessage, ExpungeMessage,
AnnotationChange or FlagChange notification for a mailbox, the
server MUST send a STATUS response for that mailbox before NOTIFY's
tagged OK. If NewMessage is enabled, the STATUS response MUST
contain MESSAGES, UIDNEXT and UIDVALIDITY. If ExpungeMessage is
enabled, the STATUS response MUST contain MESSAGES. If either
AnnotationChange or FlagChange are included, the STATUS response
MUST contain UIDVALIDITY and HIGHESTMODSEQ.
Clients are advised to limit the number of mailboxes used with
NOTIFY. Particularly, if a client asks for events for all accessible
mailboxes, the server may swamp the client with updates about shared
mailboxes. This wastes both server resources and network traffic,
and the client may have to pay for every byte.
If the client does not have access to the information requested, the
server MUST respond with a tagged NO.
If the notification would be prohibitively expensive for the server
(e.g. "notify me of all flag changes in all mailboxes"), the server
MAY refuse the command with a tagged NO [NOTIFICATIONOVERFLOW]
response.
If the client requests information for events of an unsupported type
(e.g. OverQuota and the server does not advertise the QUOTA
extension defined in [RFC2087]), the server MUST refuse the command
with a tagged BAD response.
Here's an example:
S: * OK [CAPABILITY IMAP4REV1 NOTIFY]
C: a login bob alice
King, et al. Expires November 2007 [Page 3]
Internet-draft April 2007
S: a OK Password matched
C: b notify (selected newmessage (uid body.peek[header.fields
(from to subject)]) (all) expungemessage) (pattern Lists/*
newmessage (uid) (all))
S: * STATUS Lists/Lemonade (UIDVALIDITY 4 UIDNEXT 9999 MESSAGES
500)
S: [...]
S: * STATUS Lists/Im2000 (UIDVALIDITY 901 UIDNEXT 1 MESSAGES 0)
S: b OK done
C: c select inbox
S: [...] (the usual 7-8 responses to SELECT)
S: c OK INBOX selected
(Time passes. A new message is delivered to mailbox
Lists/Lemonade.)
S: * STATUS Lists/Lemonade (UIDVALIDITY 4 UIDNEXT 10000
MESSAGES 501)
(Time passes. A new message is delivered to inbox.)
S: * 127 FETCH (UID 127001 BODY[HEADER.FIELDS (From To
Subject)] {75}
S: Subject: Re: good morning
S: From: alice@example.org
S: To: bob@example.org
S:
S: )
(Time passes. The client decides it wants to know about
one more mailbox.)
C: d notify (selected newmessage (uid body.peek[header.fields
(from to subject)]) (all) expungemessage) (pattern (Lists/*
misc) newmessage (uid) (all))
S: * STATUS misc (UIDVALIDITY 1 UIDNEXT 999)
(This command enables notification on one mailbox and
otherwise changes nothing, so one STATUS response is
sent.)
S: d OK done
4. Interaction with the IDLE Command
If IDLE (as well as this extension) is supported, the server should
send ExpungeMessage while processing IDLE, and otherwise send the
same events as the client instructed using NOTIFY.
NOTIFY makes IDLE unnecessary for some clients. If a client does not
use MSNs and '*' in commands, it can request ExpungeMessage and
NewMessage for the selected mailbox using NOTIFY instead of entering
IDLE mode.
King, et al. Expires November 2007 [Page 4]
Internet-draft April 2007
5. Event Types
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
event.
This section specifies the events of which an IMAP server can notify
an IMAP client, and how.
The server SHOULD omit notifying the client if the event is caused
by this client. For example, if the client issues CREATE and has
requested CreateMailbox event that would cover the newly created
mailbox, the server SHOULD NOT notify the client of the
CreateMailbox change.
5.1. FlagChange and AnnotationChange
If the flag/annotation change happens in the selected mailbox, the
server notifies the client by sending an unsolicited FETCH response,
which MUST include UID and FLAGS/ANNOTATION FETCH data items. It MAY
also send new FLAGS and/or OK [PERMANENTFLAGS ...] responses.
If the change happens in another mailbox, then the response depends
on whether CONDSTORE [RFC4551] is being used. If so, the server
sends a STATUS (HIGHESTMODSEQ) response. (Note that whenever mailbox
UIDVALIDITY changes, the server MUST also include UIDVALIDITY in the
STATUS response.) If not, the server does not notify the client.
FlagChange covers the ReadMessages, TrashMessages, SetFlags and
ClearFlags events in [MSGEVENT].
[[Open Issue: Filip Navara requested for STATUS (UNSEEN) to be sent
for ReadMessages. Arnt considers that unsound, since it involves
processing all messages in a mailbox after an event affecting only
one message, and since it's not reliable anyway.]]
Example in the selected mailbox:
S: * 99 FETCH (UID 9999 FLAGS ($Junk))
And in another, with CONDSTORE in use:
S: * STATUS Lists/Lemonade (HIGHESTMODSEQ 65666665)
5.2. NewMessage
This covers both NewMessage and AppendMessage in [MSGEVENT].
King, et al. Expires November 2007 [Page 5]
Internet-draft April 2007
If the new/appended message is in the selected mailbox, the server
notifies the client by sending an unsolicited EXISTS response,
followed by an unsolicited FETCH response containing the information
requested by the client. The server MAY also send a RECENT response,
if the server marks the message as \Recent.
Note that a single EXISTS response can be returned for multiple
AppendMessage/NewMessage events.
If the new/appended message is in another mailbox, the server sends
an unsolicited STATUS (UIDNEXT MESSAGES) response for the relevant
mailbox. If CONDSTORE (defined in [RFC4551]) is in use, the
HIGHESTMODSEQ status data item MUST be included in the STATUS
response.
The client SHOULD NOT use FETCH attributes that implicitly set the
\seen flag, or that presuppose the existence of a given bodypart.
UID, MODSEQ, FLAGS, ENVELOPE, BODY.PEEK[HEADER.FIELDS... and
BODY/BODYSTRUCTURE may be the most useful attributes.
Note that if a client asks to be notified of NewMessage events, the
number of messages can increase at any time, and therefore the
client cannot refer to a specific message using the MSN/UID '*'.
Example in the selected mailbox:
S: * 444 EXISTS
S: * 444 FETCH (UID 9999)
And in another, without CONDSTORE:
S: * STATUS Lists/Lemonade (UIDNEXT 10002 MESSAGES 503)
5.3. ExpungeMessage
If the expunged message(s) is/are in the selected mailbox, the
server notifies the client using EXPUNGE (or EXPUNGED, if [QRESYNC]
is being used).
If the expunged message(s) is/are in another mailbox, the server
sends an unsolicited STATUS (UIDNEXT MESSAGES) response for the
relevant mailbox. If CONDSTORE is being used, HIGHESTMODSEQ MUST be
included in the STATUS response.
Note that if a client requests ExpungeMessage, the meaning of an MSN
can change at any time, so the client cannot use MSNs in commands
any more. For example, such a client cannot use FETCH (it must only
use UID FETCH). The meaning of '*' can also change when messages are
added or expunged.
King, et al. Expires November 2007 [Page 6]
Internet-draft April 2007
The ExpungeMessage notification covers both ExpungeMessage and
ExpireMessage events from [MSGEVENT].
Example in the selected mailbox, without QRESYNC:
S: * 444 EXPUNGE
And in another:
S: * STATUS misc (UIDNEXT 999 MESSAGES 554)
5.4. OverQuota, UnderQuota and QuotaChange
If the client has permission to perform GETQUOTA (defined in
[RFC2087]), the server sends an unsolicited QUOTA response
containing the new quotas. The server also sends an unsolicited
QUOTAROOT response, so that the client can correlate the affected
mailbox to the quota root.
These notifications are sent if the client has requested
notifications for at least one affected mailbox.
Example:
S: * QUOTAROOT INBOX ""
S: * QUOTA "" (STORAGE 10 512)
5.5. CreateMailbox and DeleteMailbox
The server notifies the client by sending an unsolicited LIST
responses for each affected mailbox name. If the mailbox name does
not refer to a mailbox after the event, the \Nonexistent flag MUST
be included.
These notifications are sent if the client has requested
notifications for at least one affected mailbox. In the case of
CreateMailbox, the mailbox itself and its parent are considered to
be affected. In the case of DeleteMailbox, all deleted mailboxes and
their parent(s) are considered to be affected.
Example of a newly created mailbox:
S: * LIST () "/" "NewMailbox"
And a deleted mailbox:
S: * LIST (\NoSelect) "/" "INBOX.DeletedMailbox"
5.6. RenameMailbox
For each selectable mailbox renamed, the server sends an extended
King, et al. Expires November 2007 [Page 7]
Internet-draft April 2007
LIST response [LISTEXT] for the new mailbox name, containing the
OLDNAME extended data item with the old mailbox name. When a
mailbox is renamed, its children are renamed too. No additional
RenameMailbox events are sent for children in this case. When INBOX
is renamed, a new INBOX is assumed to be created. No CreateMailbox
event must be sent for INBOX in this case.
Example:
S: * LIST () "/" "NewMailbox" ("OLDNAME" ("OldMailbox"))
5.7. SubscriptionChange
The server notifies the client by sending an unsolicited LIST
responses for each affected mailbox name. If and only if the mailbox
is subscribed after the event, the \Subscribed attribute (see
[LISTEXT]) is included.
Example:
S: * LIST (\Subscribed) "/" "SubscribedMailbox"
5.8. MailboxMetadataChange
The server sends an unsolicited LIST response including METADATA. If
possible, only the changed metadata should be included, but if
necessary, all metadata must be included.
Example:
S: * LIST "/" "INBOX" (METADATA (/comment (value.priv "My
comment")))
5.9. AdminMailbox
If the user has the right to perform GETACL (see [RFC4314]) after
the event, the server notifies the client by sending an unsolicited
ACL response with the mailbox' new rights.
If the user loses the right to perform GETACL as a result of this
event, the server MAY also send the ACL response.
In all other cases, the server does not notify the client.
Example:
S: * ACL INBOX Fred rwipslxcetda David lrswideta
King, et al. Expires November 2007 [Page 8]
Internet-draft April 2007
5.10. Notification Overflow
If the server is unable or unwilling to deliver as many
notifications as it is being asked to, it may disable notifications
for some or all clients. It MUST notify these clients by sending an
untagged "OK [NOTIFICATIONOVERFLOW]" response and behave as if no
NOTIFY command had been sent.
Example:
S: * OK [NOTIFICATIONOVERFLOW] CPU overloaded, sorry
5.11. ACL Changes
Even if NOTIFY succeeds, it is still possible to lose access to the
mailboxes monitoried at a later time. If this happens, the server
MUST silently stop monitoring these mailboxes.
[[Open issue: This similar with the GETACL treatment in 5.9, which
noone has complained about, but is it optimal?]]
6. Mailbox Specification.
Mailboxes to be monitored can be specified in several different
ways.
If the client specifies monitoring of the same mailbox several
times, the first specification wins. A common example is asking for
events on the selected mailbox and some named mailboxes.
6.1. Selected
Selected refers to the mailbox selected using either SELECT or
EXAMINE (see [RFC3501] section 6.3.1 and 6.3.2). When the IMAP
connection is not in selected state, selected does not refer to any
mailbox.
6.2. Personal
Personal refers to all selectable mailboxes in the user's personal
namespace(s).
[[Open issue: What about mailboxes owned by the user, but not in
those namespaces? Finding those would be difficult to implement for
some servers.]]
King, et al. Expires November 2007 [Page 9]
Internet-draft April 2007
6.3. Inboxes
Inboxes refers to all selectable mailboxes in the user's personal
namespace(s) to which messages may be delivered by an MDA (see
[EMAIL-ARCH], particularly section 4.3.3).
If the IMAP server cannot easily compute this set, it MUST treat
"inboxes" as equivalent to "personal".
6.4 Subscribed
Subscribed refers to all mailboxes subscribed by the user.
If the subscription list changes, the list MUST be reevaluated.
6.5 Pattern
Pattern refers to all selectable mailboxes which match the specified
pattern.
[[Open Issue: Making this "all selectable mailboxes" makes it easy
to implement this well. The pattern can be evaluated at NOTIFY time
and notification information affixed to the mailboxes in RAM. Fine.
But what about "notify me if any mailboxes are created whose name
contains the letters xxx"? Not useful IMO...? (writes arnt)]]
7. Formal Syntax
The following syntax specification uses the Augmented Backus-Naur
Form (ABNF) notation as specified in [RFC4234]. [RFC3501] defines
the non-terminals "capability", "command-auth", "mailbox", "mailbox-
data", "resp-text-code" and "search-key". [LISTEXT] defines the non-
terminal "mbox-or-pat".
Except as noted otherwise, all alphabetic characters are case-
insensitive. The use of upper or lower case characters to define
token strings is for editorial clarity only. Implementations MUST
accept these strings in a case-insensitive fashion.
capability =/ "X-DRAFT-I06-NOTIFY"
;; [[Note to RFC Editor: change the capability
;; name before publication]]
command-auth =/ notify
King, et al. Expires November 2007 [Page 10]
Internet-draft April 2007
notify = "NOTIFY" SP event-groups
event-groups = event-group *(SP event-group)
event-group = "(" filter-mailboxes SP events ")"
filter-mailboxes = "selected" / "inboxes" / "personal" /
"subscribed" / ( "pattern" SP mbox-or-pat )
events = ( "(" event *(SP event) ")" ) / "NONE"
;; As in draft-ietf-lemonade-msgevent-XX.txt
;; "NONE" means that the client does not wish
;; to receive any events for the specified
;; mailboxes
event = message-event
/ mailbox-event / user-event / event-ext
message-match-criteria = "(" search-key ")"
message-event = ( "NewMessage" SP
"(" fetch-att *(SP fetch-att) ")"
SP message-match-criteria )
/ "ExpungeMessage"
/ "FlagChange" SP message-match-criteria
/ "AnnotationChange" SP message-match-criteria
;; "NewMessage" includes "AppendMessage" from
[MSGEVENT].
;; "FlagChange" is any of "ReadMessages",
;; "TrashMessages", "SetFlags", "ClearFlags"
[MSGEVENT]. ;; "ExpungeMessage" includes
"ExpireMessage" [MSGEVENT].
mailbox-event = "CreateMailbox" / "DeleteMailbox" /
"RenameMailbox" /
"SubscriptionChange" / "MailboxMetadataChange"
/ "QuotaChange" / "AdminMailbox"
;; [[Alexey: Should
"{Create/Delete/Rename}Mailbox" be
;; replaced with a single event?]]
;; [[Alexey: Add "LocationChange" - e.g. mailbox
;; migration between servers?]]
user-event = "OverQuota" / "UnderQuota"
event-ext = atom
;; For future extensions
King, et al. Expires November 2007 [Page 11]
Internet-draft April 2007
oldname-extended-item = "OLDNAME" SP "(" mailbox ")"
;; Extended data item (mbox-list-extended-item)
;; returned in a LIST response when a mailbox is
;; renamed.
;; Note 1: the OLDNAME tag can be returned
;; with and without surrounding quotes, as per
;; mbox-list-extended-item-tag production.
resp-text-code =/ "NOTIFICATIONOVERFLOW"
8. Security considerations
It is very easy for a client to deny itself service using NOTIFY:
Asking for all events on all mailboxes may work on a small server,
but with a big server can swamp the client's network connection or
processing capability. In the worst case, the server's processing
could also degrade the service it offers to other clients.
Servers authors should be aware that if a client issues requests and
does not listen to the resulting responses, the TCP window can
easily fill up, and a careless server might block. This problem
exists in plain IMAP, however this extension magnifies the problem.
This extensions makes it possible to retrieve messages immediately
when they are added to the mailbox. This makes it wholly impractical
to delete sensitive messages using programs like imapfilter. Using
[SIEVE] or similar is much better.
9. IANA considerations
The IANA is requested to add NOTIFY to the list of IMAP extensions,
http://www.iana.org/assignments/imap4-capabilities.
9.1. Initial LIST-EXTENDED extended data item registrations
It is requested that the following entry be added to the LIST-
EXTENDED extended data item registry [LISTEXT]:
To: iana@iana.org Subject: Registration of OLDNAME LIST-EXTENDED
extended data item
LIST-EXTENDED extended data item tag: OLDNAME
LIST-EXTENDED extended data item description: The OLDNAME extended
data item describes the old mailbox name for the mailbox identified
by the LIST response.
King, et al. Expires November 2007 [Page 12]
Internet-draft April 2007
Which LIST-EXTENDED option(s) (and their types) causes this extended
data item to be returned (if any): none
Published specification : RFC XXXX, Section 5.6.
Security considerations: none
Intended usage: COMMON
Person and email address to contact for further information:
Alexey Melnikov <Alexey.Melnikov@isode.com>
Owner/Change controller: iesg@ietf.org
10. Acknowedgements
The authors gratefully acknowledge the help of Peter Coates, Dave
Cridland, Mark Crispin, Cyrus Daboo and Abhijit Menon-Sen. Various
example lines are copied from other RFCs.
This document builds on one published and two unpublished drafts by
the same authors.
11. Normative References
[RFC2087] Myers, "IMAP4 QUOTA extension", RFC 2087, January 1997.
[RFC2119] Bradner, "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, Harvard University, March
1997.
[RFC2177] Leiba, "IMAP4 IDLE Command", RFC 2177, IBM, June 1997.
[RFC3501] Crispin, "Internet Message Access Protocol - Version
4rev1", RFC 3501, University of Washington, June 2003.
[RFC4234] Crocker, Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 4234, Brandenburg
Internetworking, Demon Internet Ltd, October 2005.
[RFC4314] Melnikov, "IMAP4 Access Control List (ACL) Extension",
RFC 4314, December 2005.
[RFC4466] Melnikov, Daboo, "Collected Extensions to IMAP4 ABNF",
RFC 4466, Isode Ltd., April 2006.
King, et al. Expires November 2007 [Page 13]
Internet-draft April 2007
[RFC4551] Melnikov, Hole, "IMAP Extension for Conditional STORE
Operation or Quick Flag Changes Resynchronization", RFC
4551, Isode Ltd., June 2006.
[ANNOTATE] Gellens, Daboo, "IMAP ANNOTATE Extension", draft-ietf-
imapext-annotate-16 (work in progress).
[LISTEXT] Leiba, Melnikov, "IMAP4 List Command Extensions", draft-
ietf-imapext-list-extensions-18 (work in progress), IBM,
September 2006.
[METADATA] Daboo, "IMAP METADATA Extension", draft-daboo-imap-
annotatemore-11 (work in progress), Apple Computer, Inc.,
February 2007.
[MSGEVENT] Newman, "Internet Message Store Events", draft-ietf-
lemonade-msgevent-01.txt (work in progress), Sun, March
2007.
12. Informative References
[SIEVE] Showalter, "Sieve: A Mail Filtering Language", RFC 3028,
Mirapoint Inc, January 2001.
[QRESYNC] Melnikov, Cridland, Wilson, "IMAP4 Extensions for Quick
Mailbox Resynchronization", draft-ietf-lemonade-
reconnect-client-03.txt (work in progress), February
2007.
[EMAIL-ARCH] Crocker, "Internet Mail Architecture", draft-crocker-
email-arch-06 (work in progress), March 2007.
13. Authors' Addresses
Curtis King
Isode Ltd
5 Castle Business Village
36 Station Road
Hampton, Middlesex TW12 2BX
UK
Email: Curtis.King@isode.com
King, et al. Expires November 2007 [Page 14]
Internet-draft April 2007
Alexey Melnikov
Isode Ltd
5 Castle Business Village
36 Station Road
Hampton, Middlesex TW12 2BX
UK
Email: Alexey.Melnikov@isode.com
Arnt Gulbrandsen
Oryx Mail Systems GmbH
Schweppermannstr. 8
D-81671 Muenchen
Germany
Email: arnt@oryx.com
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights 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; nor does it represent that
it has made any independent effort to identify any such rights.
Information on the procedures with respect to rights in RFC
documents can be found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat 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 implementers or users of this
specification can be obtained from the IETF on-line IPR repository
at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
King, et al. Expires November 2007 [Page 15]
Internet-draft April 2007
Full Copyright Statement
Copyright (C) The IETF Trust (2007). This document is subject to
the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on
an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE
ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
King, et al. Expires November 2007 [Page 16]