draft-ietf-simple-pres-filter-reqs-02.txt   draft-ietf-simple-pres-filter-reqs-03.txt 
SIMPLE WG H. Khartabil SIMPLE WG T. Moran
Internet-Draft E. Leppanen Internet-Draft
Expires: February 12, 2004 Nokia Expires: July 26, 2004 H. Khartabil
T. Moran E. Leppanen
August 14, 2003 Nokia
January 26, 2004
Requirements for Presence Specific Event Notification Filtering Requirements for Presence Specific Event Notification Filtering
draft-ietf-simple-pres-filter-reqs-02 draft-ietf-simple-pres-filter-reqs-03
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 other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 1, line 32 skipping to change at page 1, line 33
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at http:// The list of current Internet-Drafts can be accessed at http://
www.ietf.org/ietf/1id-abstracts.txt. www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on February 12, 2004. This Internet-Draft will expire on July 26, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
This document defines a set of structured requirements whereby a This document defines a set of structured requirements whereby a
presence information subscriber may select specific information to be presence information subscriber may select specific information to be
received in the presence information notification sent by the received in the presence information notification sent by the
notifier. The purpose is to limit the content and frequency of notifier. The purpose is to limit the content and frequency of
notifications so that only essential information on a need basis is notifications so that only essential information on a need basis is
delivered by the server. delivered by the server.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Event Filtering Model . . . . . . . . . . . . . . . . . . . 3
3. Requirements for Specification of Filters . . . . . . . . . 4 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1 Package Identification . . . . . . . . . . . . . . . . . . . 4 4. Requirements for Specification of Filters . . . . . . . . . 4
3.2 Target URI . . . . . . . . . . . . . . . . . . . . . . . . . 4 4.1 Package Identification . . . . . . . . . . . . . . . . . . . 4
3.3 Notification Triggering . . . . . . . . . . . . . . . . . . 4 4.2 Target URI . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.4 Notification Content . . . . . . . . . . . . . . . . . . . . 5 4.3 Notification Triggering . . . . . . . . . . . . . . . . . . 5
4. Requirements for Uploading Filter Criteria (Operational 4.4 Notification Content . . . . . . . . . . . . . . . . . . . . 5
Rules) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 5. Requirements for Uploading Filters (Operational Rules) . . . 6
4.1 Subscription . . . . . . . . . . . . . . . . . . . . . . . . 5 5.1 Subscription . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1.1 Maintaining a Filter . . . . . . . . . . . . . . . . . . . . 5 5.1.1 Maintaining a Filter . . . . . . . . . . . . . . . . . . . . 6
4.1.2 Changing a Filter . . . . . . . . . . . . . . . . . . . . . 6 5.1.2 Changing a Filter . . . . . . . . . . . . . . . . . . . . . 6
4.2 Server Support For Filters . . . . . . . . . . . . . . . . . 6 5.2 Server Support For Filters . . . . . . . . . . . . . . . . . 6
5. Interaction with Other Features . . . . . . . . . . . . . . 6 6. Interaction with Other Features . . . . . . . . . . . . . . 7
5.1 Resource Lists . . . . . . . . . . . . . . . . . . . . . . . 6 6.1 Resource Lists . . . . . . . . . . . . . . . . . . . . . . . 7
5.2 Partial Notifications . . . . . . . . . . . . . . . . . . . 7 6.2 Partial Notifications . . . . . . . . . . . . . . . . . . . 7
5.3 Authorization . . . . . . . . . . . . . . . . . . . . . . . 7 6.3 Authorization . . . . . . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . 7 7. Security Considerations . . . . . . . . . . . . . . . . . . 7
7. Example Applications for Notification Filtering . . . . . . 8 8. Example Applications for Notification Filtering . . . . . . 8
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
9. Main changes from version 01 . . . . . . . . . . . . . . . . 8 10. Changes from previous versions . . . . . . . . . . . . . . . 9
10. Main changes from version 00 . . . . . . . . . . . . . . . . 9 10.1 Main changes from version 02 . . . . . . . . . . . . . . . . 9
References . . . . . . . . . . . . . . . . . . . . . . . . . 9 10.2 Main changes from version 01 . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 10 10.3 Main changes from version 00 . . . . . . . . . . . . . . . . 10
Intellectual Property and Copyright Statements . . . . . . . 11 References . . . . . . . . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 11
Intellectual Property and Copyright Statements . . . . . . . 12
1. Introduction 1. Introduction
SIP event notification is described in [6]. It defines a general SIP event notification is described in [6]. It defines a general
framework for subscriptions and notifications for SIP event packages. framework for subscriptions and notifications for SIP event packages.
Concrete applications of the general event framework to a specific Concrete applications of the general event framework to a specific
group of events are described in [5] (user presence) and [7] (watcher group of events are described in [5] (user presence) and [7] (watcher
information). information).
The presence information refers to a set of presence attributes The presence information refers to a set of presence attributes
skipping to change at page 3, line 25 skipping to change at page 3, line 25
for communication. The user makes his presence information available for communication. The user makes his presence information available
for other users (watchers). for other users (watchers).
As the inherent usage of event packages grows, the client needs some As the inherent usage of event packages grows, the client needs some
mechanisms for controlling the event notifications at the source. mechanisms for controlling the event notifications at the source.
Evidence of this need is found in [4]. Evidence of this need is found in [4].
The document describing the Presence event package [5] mentions the The document describing the Presence event package [5] mentions the
possibility for filtering. Accordingly, the SUBSCRIBE request may possibility for filtering. Accordingly, the SUBSCRIBE request may
contain a body for filtering the presence information subscription. contain a body for filtering the presence information subscription.
However, the definition of filtering was considered out of scope was However, the definition of filtering was considered out of scope and
left as future work. was left as future work.
These mechanisms are expected to be particularly valuable to users of These mechanisms are expected to be particularly valuable to users of
wireless devices. The characteristics of these devices typically wireless devices. The characteristics of these devices typically
include low bandwidth, low data processing capabilities, small include low bandwidth, low data processing capabilities, small
display and limited battery power. Such devices can benefit from the display and limited battery power. Such devices can benefit from the
ability to filter the amount of information generated at the source ability to filter the amount of information generated at the source
of the event notifications. of the event notifications.
However, it is expected that the control mechanisms for event However, it is expected that the control mechanisms for event
notifications add value for all users irrespectively of their device notifications add value for all users irrespectively of their device
or network access characteristics. or network access characteristics.
Section 3 and Section 4 of this draft propose a set of requirements Section 4 and Section 5 of this draft propose a set of requirements
whereby a client may specify which notifications it is interested in. whereby a client may specify which notifications it is interested in.
That is, a means to specify filtering rules to be executed by the That is, a means to specify filtering rules to be executed by the
server. Section 7 provides a few example applications of notification server. Section 8 provides a few example applications of notification
filtering. filtering.
2. Conventions 2. Event Filtering Model
There are two parts to the event filtering model. From a Presence
service view point, presence information is collected by a Presence
Agent and is published by one or more Presence User Agents. The first
part of the model enables the watcher to limit the presence
information delivered to it. Allowing the watcher to select the
information of interest to it results in the ability to limit the
contents of a presence information document, therefore reducing the
size of a notification message.
+--+
--| |PUA
PA --- +--+
Watcher +---------+ ----
+-----+ | | ---
| | | |-- +--+
| |--------------| |--------------| |PUA
| | | |-- +--+
+-----+ | | ---
+---------+ ----
--- +--+
--| |PUA
+--+
The second part of the model defines the triggering. In a filter-less
subscription, it might be a Presence Agent's default policy to
deliver a notification message every time there is a change to the
presence information of a presentity or whenever a PUA publishes new
and updated presence information from its own point of view. This
model enables the watcher to select the events or changes in presents
information that trigger notifications to be sent. Other changes that
are not defined as triggers in a filter do not result in a
notification message being delivered to the watcher.
3. Conventions
In this document, the key words 'MUST', 'MUST NOT', 'REQUIRED', In this document, the key words 'MUST', 'MUST NOT', 'REQUIRED',
'SHALL', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', 'SHALL', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY',
and 'OPTIONAL' are to be interpreted as described in RFC 2119 [1] and 'OPTIONAL' are to be interpreted as described in RFC 2119 [1]
and indicate requirement levels for compliant implementations. and indicate requirement levels for compliant implementations.
3. Requirements for Specification of Filters 4. Requirements for Specification of Filters
The following requirements relate to the creation of filter criteria. The following requirements relate to the creation of filters.
3.1 Package Identification 4.1 Package Identification
REQ xx: It MUST be possible for the creator of the filter to specify REQ A1: It MUST be possible for the creator of the filter to specify
the package the filter applies to. the package the filter applies to.
3.2 Target URI 4.2 Target URI
REQ xx: It MUST be possible for the watcher to indicate, in the REQ A2: It MUST be possible for the watcher to indicate, in the
filter, the target presentity whose presence information a certain filter, the target presentity whose presence information a certain
filter is applied to. filter is applied to.
REQ xx: It MUST be possible for the watcher to indicate, in the REQ A3: It MUST be possible for the watcher to indicate, in the
filter criteria, the target presentity list whose presence filter, the target domain that a certain filter is applied to. For
information a certain filter is applied to. example an event list might have many resources from different
domains, a watcher needs to be able to set a filter for one of those
REQ xx: It MUST be possible for the watcher to indicate, in the domains.
filter criteria, the target presentity sub-list whose presence
information a certain filter is applied to.
REQ xx: It MUST be possible for the watcher to indicate, in the
filter criteria, the target domain that contains presentities whose
presence information a certain filter is applied to.
3.3 Notification Triggering 4.3 Notification Triggering
This chapter presents requirements for specifying the triggering This chapter presents requirements for specifying the triggering
conditions that result in notifications to be sent to the client. conditions that result in notifications to be sent to the watcher.
REQ xx: It MUST NOT be possible to break any server side policy
constraints when applying the triggering conditions. For example, it
must not be possible for a watcher to request a notification when the
<status> element value of a certain presentity has changed from OPEN
to CLOSED when there is a local server policy constraining the
delivery of any tuple with a <status> element value of CLOSED.
REQ xx: The triggering conditions MUST be based on the presence REQ B1: The triggering conditions MUST be based on the presence
information. For example, the change of value of the <status> information. For example, the change of value of the <status>
element. element.
REQ xx: It MUST be possible to specify logical expressions based on REQ B2:It MUST be possible to define a set of conditions for the
the value of elements defined in the package for the purpose of values of certain elements in a presence document that determine when
triggering. This covers expressions (tests) related to the change of to send notifications.
an element's value, and reaching a certain value of an element.
REQ xx: It MUST be possible to construct one filter that combine REQ B3: It MUST be possible to construct one filter that combines
multiple triggering conditions. multiple triggering conditions.
3.4 Notification Content 4.4 Notification Content
This chapter presents requirements for specifying the filter for This chapter presents requirements for specifying the filter for
choosing content to be sent in the notifications. choosing content to be sent in the notifications.
REQ xx: It MUST NOT be possible to break any server side policy REQ C1: It MUST NOT be possible to break any server side policy
constraints when applying the content filter. For example, it must constraints when applying the content filter. For example, it must
not be possible for a watcher to request a notification to contain not be possible for a watcher to request a notification to contain
the <contact> element of a certain presentity when there is a local the <contact> element of a certain presentity when there is a local
server policy constraining the delivery of the <contact> element. server policy constraining the delivery of the <contact> element.
REQ xx: It MUST be possible for the watcher to specify the presence REQ C2: It MUST be possible for the watcher to specify the presence
information elements (XML elements and/or attributes) in [2] to be information elements (XML elements and/or attributes) in [2] to be
delivered in the notification. delivered in the notification.
REQ xx: It MUST be possible for the watcher to specify presence REQ C3: It MUST be possible for the watcher to specify presence
information in any extension to PIDF to be delivered in the information in any extension to PIDF to be delivered in the
notifications, based on XML elements and/or attributes. See for notifications, based on XML elements and/or attributes. See for
example [3]. example [3].
REQ xx: It MUST be possible for the watcher to specify presence REQ C4: It MUST be possible for the watcher to specify presence
information in any extension to be delivered in the notifications, information in any extension to be delivered in the notifications,
based on namespaces. based on namespaces.
REQ xx: It MUST be possible to construct one filter that combine REQ C5: It MUST be possible to construct one filter that combine
multiple elements and attributes to be included the notifications. multiple elements and attributes to be included the notifications.
4. Requirements for Uploading Filter Criteria (Operational Rules) REQ C6: It MUST be possible for the watcher to specify presence
information in PIDF or any any extension to it to be excluded from
the notifications, based on elements and/or attributes.
REQ xx: It MUST be possible for the watcher to upload filter criteria 5. Requirements for Uploading Filters (Operational Rules)
to the server (notifier) and know the status - accepted or rejected.
4.1 Subscription REQ D1: It MUST be possible for the watcher to upload filters to the
server (notifier) and know the status - accepted or rejected, if the
server policy allows.
REQ xx: It MUST be possible to place a filter in the body of the 5.1 Subscription
REQ D2: It MUST be possible to place a filter in the body of the
SUBSCRIBE request. SUBSCRIBE request.
REQ xx: It MAY be possible to deliver a filter to a server using REQ D3: It MAY be possible to deliver a filter to a server using
other means. For example, it may be possible for the filter to be other means. For example, it may be possible for the filter to be
(permanently) stored in the server. (permanently) stored in the server.
4.1.1 Maintaining a Filter 5.1.1 Maintaining a Filter
REQ xx: The watcher MUST NOT be required to re-set a filter at any
time during the subscription, once the filter has been set.
REQ xx: The watcher SHOULD NOT be required to re-set a filter when REQ D4: The watcher MUST NOT be required to re-set a filter at any
refreshing a subscription, once the filter has been set. time during the subscription, once the filter has been set. This
includes subscription refreshes
REQ xx: Maintaining a filter across subscription refreshes SHOULD be REQ D5: modifying a filter across subscription refreshes SHOULD be
bandwidth efficient. bandwidth efficient.
4.1.2 Changing a Filter REQ D6: It MUST NOT be required for a watcher to explicitly remove a
filter if the subscription was terminated or has expired. I.e. The
filter is automatically removed with the subscription.
REQ xx: It MUST be possible to change the filter during a 5.1.2 Changing a Filter
REQ E1: It MUST be possible to change the filter during a
subscription. subscription.
REQ xx: It MUST be possible for the watcher to remove a set filter, REQ E2: It MUST be possible for the watcher to remove a set filter,
reverting back to a server defined default. reverting back to a server defined default.
4.2 Server Support For Filters 5.2 Server Support For Filters
REQ xx: It MUST be possible for a server not supporting filtering to REQ F1: It MUST be possible for a server not supporting filtering to
inform the watcher of the failure. inform the watcher of the failure.
REQ xx: It MUST be possible for a server not understanding a REQ F2: It MUST be possible for a server not understanding a
filtering to inform the watcher of the failure. filtering to inform the watcher of the failure.
REQ xx: It MUST be possible for a server not accepting a filter to REQ F3: It MUST be possible for a server not accepting a filter to
inform the watcher of the reasons for not accepting the filter. inform the watcher of the reasons for not accepting the filter.
REQ xx: It MUST be possible for a server to terminate a subscription REQ F4: It MUST be possible for the server to terminate a
based on a filter becoming invalid due to sever local policy change. subscription if a filter is no longer acceptable, e.g., due to policy
(How do I word this in a requirement text?) change or server load.
5. Interaction with Other Features 6. Interaction with Other Features
5.1 Resource Lists 6.1 Resource Lists
REQ xx: It MUST be possible to support filtering for subscriptions to REQ G1: It MUST be possible to support filtering for subscriptions to
resource lists [8]. event lists [8].
REQ xx: It MUST be possible for a watcher to specify filter criteria REQ G2: It MUST be possible for the watcher to indicate, in the
for a resource list and/or any nested sub list of the resource list. filter, the target event list that a certain filter is applied to by
the Resource List Server.
REQ xx: It MUST be possible for a watcher to specify different filter REQ G3: It MUST be possible for a watcher to specify individual
for any individual member of a resource list in a resource list filters for any resource in an event list if the subscription is for
subscription. an event list.
REQ xx: It MUST be possible for a watcher to specify different filter REQ G4: It MUST be possible to specify a filter for an event list and
criteria for individual members of any of nested sub lists of a a filters for resources within that list in the same subscription
resource list in a resource list subscription. Any of the nested sub request.
lists may be located in a different domain from the parent list.
REQ xx: It MUST be possible for each watcher to define own filter REQ G5: Some event lists may contain an other event list as a
criteria within resource list subscription if there are several resource. I.e. nested lists. It MUST be possible for the watcher to
indicate, in the filter, a nested event list that a certain filter is
applied to.
REQ G6: It MUST be possible for a watcher to specify different filter
for resources within any nested list of an event list, if the
subscription is for an event list.
REQ G7: It MUST be possible for each watcher to define his/her own
filters within an event list subscription if there are several
simultaneous watchers using the same list. simultaneous watchers using the same list.
5.2 Partial Notifications 6.2 Partial Notifications
REQ xx: It MUST be possible to use filtering along with the partial REQ H1: It MUST be possible to use filtering along with the partial
notification [9] within the same subscription. notification [9] within the same subscription.
5.3 Authorization 6.3 Authorization
REQ xx: Authorization SHOULD occur irrespective of the filtering.
6. Security Considerations 7. Security Considerations
Security requirements specified for [5] also applies to the presence Security requirements specified for [5] also applies to presence
filtering. Additional security considerations related to the presence filtering. Additional security considerations are described as
filtering are described as follows. follows.
REQ xx: It SHOULD be possible for the server to hide the fact that a REQ I1: It SHOULD be possible for the server to hide the fact that a
filter was not acceptable. filter was not acceptable.
REQ xx: The presence of filter criteria in the body in a SIP message REQ I2: The presence of filters in the body in a SIP message has a
has a significant effect on the way in which the request is handled significant effect on the way in which the request is handled at a
at a server. As a result, it is especially important that messages server. As a result, it MUST be possible to authenticate messages
containing filter criteria are authenticated and authorized. carrying filters and authorise the watcher to upload filters.
REQ xx: Modification to the Filter Criteria by an intermediary could REQ I3: Modification to filters by an intermediary could also result
also result in the watcher either not receiving notifications of in the watcher either not receiving notifications of presence
presence information they are interested in or receiving a very large information they are interested in or receiving a very large presence
presence document. Therefore the filter criteria SHOULD be integrity document. Therefore the filters SHOULD be integrity protected between
protected between those nodes that are authorised to modify it (e.g., those nodes that are authorised to modify it (e.g., the resource list
the resource list servers). servers).
REQ xx: Processing of requests and looking up filter criteria REQ I4: Processing of requests and looking up filters requires some
requires some amount of computation. This enables a DoS attack amount of computation. This enables a DoS attack whereby a user can
whereby a user can send requests with substantial numbers messages send requests with substantial numbers messages with large contents,
with large contents, in the hopes of overloading the server. To in the hopes of overloading the server. To prevent this the number of
prevent this the number of filter criteria allowed in a request filters allowed in a request should be limited.
should be limited.
REQ xx: Requests containing filter criteria can reveal sensitive REQ I5: Requests containing filters can reveal sensitive information
information about a UA's capabilities. If this information is about a UA's capabilities. If this information is sensitive, it
sensitive, it SHOULD be encrypted using methods that allow it to be SHOULD be encrypted using methods that allow it to be read by those
read by those nodes that need to do so (e.g., the resource list nodes that need to do so (e.g., the resource list servers).
servers).
REQ xx: The resource list servers SHOULD convey only those parts of REQ I6: The resource list servers SHOULD NOT forward filters targeted
filter information targeted to the same destination as the fanned out to a different domain than a fanned out subscription request.
individual subscriptions, if the filter information is conveyed
further within the subscription.
7. Example Applications for Notification Filtering REQ I7: Authorization SHOULD occur irrespective of the filtering.
1. A watcher wishes to get to know presentity's availability and 8. Example Applications for Notification Filtering
o A watcher wishes to get to know presentity's availability and
willingness for messaging (e.g. IM and MMS). willingness for messaging (e.g. IM and MMS).
2. A watcher is interested in getting information about the o A watcher is interested in getting information about the
communication means and contact addresses the presentity is communication means and contact addresses the presentity is
currently available for communication. currently available for communication.
3. A watcher requires a notification if the state of a buddy has o A watcher requires a notification if the state of a buddy has
changed to 'open'. changed to 'open'.
4. A watcher only wants to be notified when the presentity's o A watcher only wants to be notified when the presentity's location
location is Dallas or Fort Worth. The notification should include is Dallas or Fort Worth. The notification should include the
the vehicle license, driver name, and city. vehicle license, driver name, and city.
5. A Basic location tracking service requires notification when the o A Basic location tracking service requires notification when the
presentity's cell id changes. The notification should include the presentity's cell id changes. The notification should include the
cell id. cell id.
6. A watcher is interested in being notified when a presentity gains o A watcher is interested in being notified when a presentity gains
a new communication capability such as a new networked a new communication capability such as a new networked
multi-player game. multi-player game.
8. Acknowledgements 9. Acknowledgements
The authors would like to thank Andrew Allen, Sreenivas Addagatla, The authors would like to thank Andrew Allen, Sreenivas Addagatla,
Mikko Lonnfors, Juha Kalliokulju, Aki Niemi, Jose Costa-Requena and Mikko Lonnfors, Juha Kalliokulju, Aki Niemi, Jose Costa-Requena,
Markus Isomaki for their valuable input. Markus Isomaki, Paul Kyzivat, Aki Niemi and Chris Boulton for their
valuable input.
9. Main changes from version 01 10. Changes from previous versions
10.1 Main changes from version 02
o Added filtering model section.
o Rephrased some requirements for clarity.
o Rearranged requirements into more appropriate sections.
10.2 Main changes from version 01
o "Overview of Operation" section removed . o "Overview of Operation" section removed .
o "Common Syntax" section removed. o "Common Syntax" section removed.
o "Discovery of Items" section removed as agreed in IETF 57 o "Discovery of Items" section removed as agreed in IETF 57
o Added requirement about filtering using namespaces. o Added requirement about filtering using namespaces.
o Added requirement about filtering using domain name. o Added requirement about filtering using domain name.
o Clarified and split larger requirements into smaller more concrete o Clarified and split larger requirements into smaller more concrete
requirements. requirements.
o Updated the Authors of this ID o Updated the Authors of this ID
10. Main changes from version 00 10.3 Main changes from version 00
o Overview of functionality chapter added. o Overview of functionality chapter added.
o More specific requirements for supporting filtering with the o More specific requirements for supporting filtering with the
resource lists, and nested lists. resource lists, and nested lists.
o Interaction with other features chapter added. o Interaction with other features chapter added.
o More specific requirements to support getting information about o More specific requirements to support getting information about
the structure of presence document, and changes in it. the structure of presence document, and changes in it.
skipping to change at page 9, line 32 skipping to change at page 10, line 30
updates. updates.
References References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[2] Sugano, H., "CPIM Presence Information Data Format", [2] Sugano, H., "CPIM Presence Information Data Format",
draft-ietf-impp-cpim-pidf-08.txt, May 2003. draft-ietf-impp-cpim-pidf-08.txt, May 2003.
[3] Schulzrinne, H., "RPIDS -- Rich Presence Information Data Format [3] Schulzrinne, H., "RPID -- Rich Presence Information Data
for Presence Based on the Session Initiation Protocol (SIP)", Format", draft-ietf-simple-rpid-00.txt, July 2003.
draft-schulzrinne-simple-rpids-01.txt, February 2003.
[4] Kiss, K., "Requirements for Presence Service based on 3GPP [4] Kiss, K., "Requirements for Presence Service based on 3GPP
specifications and wireless environment characteristics", specifications and wireless environment characteristics",
draft-kiss-simple-presence-wireless-reqs-02, February 2003. draft-kiss-simple-presence-wireless-reqs-02, February 2003.
[5] Rosenberg, J., "Session Initiation Protocol (SIP) Extensions for [5] Rosenberg, J., "Session Initiation Protocol (SIP) Extensions for
Presence", draft-ietf-simple-presence-10.txt, January 2003. Presence", draft-ietf-simple-presence-10.txt, January 2003.
[6] Roach, A., "Session Initiation Protocol (SIP)-Specific Event [6] Roach, A., "Session Initiation Protocol (SIP)-Specific Event
Notification", RFC 3265, June 2002. Notification", RFC 3265, June 2002.
[7] Rosenberg, J., "A Watcher Information Event Template-Package for [7] Rosenberg, J., "A Watcher Information Event Template-Package for
the Session Initiation Protocol (SIP)", the Session Initiation Protocol (SIP)",
draft-ietf-simple-winfo-package-05.txt, January 2003. draft-ietf-simple-winfo-package-05.txt, January 2003.
[8] Rosenberg, J., "A Session Initiation Protocol (SIP) Event [8] Roach, A., "A Session Initiation Protocol (SIP) Event
Notification Extension for Resource Lists", Notification Extension for Resource Lists",
draft-ietf-simple-event-list-03.txt, May 2003. draft-ietf-simple-event-list-03.txt, June 2003.
[9] Lonnfors, M., "Partial Notification of Presence Information", [9] Lonnfors, M., "Partial Notification of Presence Information",
draft-lonnfors-simple-partial-notify-01.txt, May 2003. draft-lonnfors-simple-partial-notify-01.txt, May 2003.
Authors' Addresses Authors' Addresses
Tim Moran
2800 Britt Drive
Argyle, Texas 76226
USA
Phone: +1 972 849 8821
EMail: tl_moran@att.net
Hisham Khartabil Hisham Khartabil
Nokia Nokia
P.O BOX 321 P.O BOX 321
Helsinki Helsinki
Finland Finland
Phone: +358 7180 76161 Phone: +358 7180 76161
EMail: hisham.khartabil@nokia.com EMail: hisham.khartabil@nokia.com
Eva Leppanen Eva Leppanen
Nokia Nokia
P.O BOX 785 P.O BOX 785
Tampere Tampere
Finland Finland
Phone: +358 7180 77066 Phone: +358 7180 77066
EMail: eva-maria.leppanen@nokia.com EMail: eva-maria.leppanen@nokia.com
Tim Moran
2800 Britt Drive
Argyle, Texas 76226
USA
Phone: +1 972 849 8821
EMail: tl_moran@att.net
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 or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of standards-related documentation can be found in BCP-11. Copies of
skipping to change at page 11, line 29 skipping to change at page 12, line 29
be obtained from the IETF Secretariat. be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this 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
skipping to change at page 12, line 7 skipping to change at page 13, line 7
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 assignees. revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

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