1. Event Filtering Hisham Khartabil SIMPLE WG Interim Meeting, Boston 24 th May, 2004 hisham.khartabil@nokia.com

2. Functional Description Issue (1) A SUBSCRIBE request is allowed to carry multiple filters. Need to add text that disallows more than 1 filter per resource to be specified (eg: If the subscribe is for a list) SUBSCRIBE sip:myfirends@domain.com SIP/2.0 … <filter-set xmlns="urn:ietf:params:xml:ns:simple-filter" xmlns:pidf="urn:ietf:params:xml:ns:pidf"> //pidf:tuple/pidf:status/pidf:basic urn:ietf:params:xml:ns:pidf //pidf:tuple/pidf:note

3. Functional Description Issue (2) Current text: “If the URI indicated by the filter is for one resource who's URI is NOT one of the URIs that result from a lookup, by the RLS, on the Request-URI, the filter is propagated to all the fanned out subscriptions.” List1 (list1@example1.com) on RLS1 has:list1@example1.com bob@example1.com list2@example2.com List2 on RLS2 has: alice@example2.com

4. Functional Description Issue (2) RLS1 receives the following SUBSCRIBE request SUBSCRIBE sip:List1@example1.com SIP/2.0 … <filter-set xmlns="urn:ietf:params:xml:ns:simple-filter" xmlns:pidf="urn:ietf:params:xml:ns:pidf"> urn:ietf:params:xml:ns:pidf //pidf:tuple/pidf:note //pidf:tuple/pidf:status/pidf:basic List1 (list1@example1.com) on RLS1 has:list1@example1.com bob@example1.com list2@example2.com List2 on RLS2 has: alice@example2.com

5. Functional Description Issue (2) Currently, this is propagated to RLS2 SUBSCRIBE sip:List2@example2.com SIP/2.0 … <filter-set xmlns="urn:ietf:params:xml:ns:simple-filter" xmlns:pidf="urn:ietf:params:xml:ns:pidf"> urn:ietf:params:xml:ns:pidf //pidf:tuple/pidf:note //pidf:tuple/pidf:status/pidf:basic

6. Functional Description Issue (2) Suggestion: if a filter is destined to a resource that is part of list that is outside the administrative domain of an RLS, then that filter is propagated. The rest are consumed. SUBSCRIBE sip:List2@example2.com SIP/2.0 … <filter-set xmlns="urn:ietf:params:xml:ns:simple-filter" xmlns:pidf="urn:ietf:params:xml:ns:pidf"> //pidf:tuple/pidf:status/pidf:basic

7. Functional Description Issue (2) What if the list last was: List1 (list1@example1.com) on RLS1 has:list1@example1.com bob@example1.com list2@example2.com List2 on RLS2 has: alice@example2.com sarah@example1.com Proposal 1: Only propagate filters that are for resources not under an RLS’s administrative domain. The rest are consumed Proposal 2: Propagate all filters for resources that the RLS did not find an entry for in a list, including resources under its own administrative domain List1 (list1@example1.com) on RLS1 has:list1@example1.com bob@example1.com list2@example2.com List2 on RLS2 has: alice@example2.com

8. Functional Description Issue (3) Need to clarify that a filter for an individual resource overrides a domain filter. <filter-set xmlns="urn:ietf:params:xml:ns:simple-filter" xmlns:pidf="urn:ietf:params:xml:ns:pidf"> //pidf:tuple/pidf:status/pidf:basic urn:ietf:params:xml:ns:pidf //pidf:tuple/pidf:note

9. Filter Format Issues (1) <filter-set xmlns="urn:ietf:params:xml:ns:simple-filter" xmlns:pidf="urn:ietf:params:xml:ns:pidf"> //pidf:tuple/pidf:note When removing a filter, a subscriber must explicitly do so by specifying the filter ID along with the “remove” attribute set to True.

10. Filter Format Issues (1) Problem: How does a subscriber replace a filter? <filter-set xmlns="urn:ietf:params:xml:ns:simple-filter" xmlns:pidf="urn:ietf:params:xml:ns:pidf"> //pidf:tuple/pidf:status/pidf:basic

11. Filter Format Issues (1) Proposal 1: disallow inclusion of ‘uri’ attribute when removing a filter <filter-set xmlns="urn:ietf:params:xml:ns:simple-filter" xmlns:pidf="urn:ietf:params:xml:ns:pidf"> //pidf:tuple/pidf:status/pidf:basic Proposal 2: Allow a filter to be replaced using the same filter id <filter-set xmlns="urn:ietf:params:xml:ns:simple-filter" xmlns:pidf="urn:ietf:params:xml:ns:pidf"> //pidf:tuple/pidf:status/pidf:basic