1 / 11

Event Filtering

This document discusses various functional description issues related to filtering in the SIMPLE (Session Initiation Protocol (SIP) for Instant Messaging and Presence Leveraging Extensions) Working Group. Key issues include the allowance of multiple filters in SUBSCRIBE requests, propagation of filters based on administrative domains, and the hierarchy of individual resource filters over domain filters. Proposals for enhancing filter propagation rules are also presented, ensuring clarity in managing subscriptions effectively across different resource lists.

louis
Télécharger la présentation

Event Filtering

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Event Filtering Hisham Khartabil SIMPLE WG Interim Meeting, Boston 24th 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 … <?xml version="1.0" encoding="UTF-8"?> <filter-set xmlns="urn:ietf:params:xml:ns:simple-filter" xmlns:pidf="urn:ietf:params:xml:ns:pidf"> <filter id="8439" uri="sip:sarah@domain.com"> <what> <include>//pidf:tuple/pidf:status/pidf:basic</include> </what> </filter> <filter id="999" uri="sip:sarah@domain.com"> <what> <include type="namespace">urn:ietf:params:xml:ns:pidf</include> <exclude>//pidf:tuple/pidf:note</exclude> </what> </filter> </filter-set>

  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: bob@example1.com list2@example2.com • List2 on RLS2 has: alice@example2.com

  4. Functional Description Issue (2) • List1 (list1@example1.com) on RLS1 has: • bob@example1.com • list2@example2.com • List2 on RLS2 has: • alice@example2.com • RLS1 receives the following SUBSCRIBE request SUBSCRIBE sip:List1@example1.com SIP/2.0 … <?xml version="1.0" encoding="UTF-8"?> <filter-set xmlns="urn:ietf:params:xml:ns:simple-filter" xmlns:pidf="urn:ietf:params:xml:ns:pidf"> <filter id="999" uri="sip:sarah@example1.com"> <what> <include type="namespace">urn:ietf:params:xml:ns:pidf</include> <exclude>//pidf:tuple/pidf:note</exclude> </what> </filter> <filter id="8439" uri="sip:alice@example2.com"> <what> <include>//pidf:tuple/pidf:status/pidf:basic</include> </what> </filter> </filter-set>

  5. Functional Description Issue (2) • Currently, this is propagated to RLS2 SUBSCRIBE sip:List2@example2.com SIP/2.0 … <?xml version="1.0" encoding="UTF-8"?> <filter-set xmlns="urn:ietf:params:xml:ns:simple-filter" xmlns:pidf="urn:ietf:params:xml:ns:pidf"> <filter id="999" uri="sip:sarah@example1.com"> <what> <include type="namespace">urn:ietf:params:xml:ns:pidf</include> <exclude>//pidf:tuple/pidf:note</exclude> </what> </filter> <filter id="8439" uri="sip:alice@example2.com"> <what> <include>//pidf:tuple/pidf:status/pidf:basic</include> </what> </filter> </filter-set>

  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 … <?xml version="1.0" encoding="UTF-8"?> <filter-set xmlns="urn:ietf:params:xml:ns:simple-filter" xmlns:pidf="urn:ietf:params:xml:ns:pidf"> <filter id="8439" uri="sip:alice@example2.com"> <what> <include>//pidf:tuple/pidf:status/pidf:basic</include> </what> </filter> </filter-set>

  7. Functional Description Issue (2) • List1 (list1@example1.com) on RLS1 has: • bob@example1.com • list2@example2.com • List2 on RLS2 has: • alice@example2.com • What if the list last was: • List1 (list1@example1.com) on RLS1 has: 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

  8. Functional Description Issue (3) • Need to clarify that a filter for an individual resource overrides a domain filter. <?xml version="1.0" encoding="UTF-8"?> <filter-set xmlns="urn:ietf:params:xml:ns:simple-filter" xmlns:pidf="urn:ietf:params:xml:ns:pidf"> <filter id="8439" uri="sip:example1.com"> <what> <include>//pidf:tuple/pidf:status/pidf:basic</include> </what> </filter> <filter id="999" uri="sip:bob@example1.com"> <what> <include type="namespace">urn:ietf:params:xml:ns:pidf</include> <exclude>//pidf:tuple/pidf:note</exclude> </what> </filter> </filter-set>

  9. Filter Format Issues (1) <?xml version="1.0" encoding="UTF-8"?> <filter-set xmlns="urn:ietf:params:xml:ns:simple-filter" xmlns:pidf="urn:ietf:params:xml:ns:pidf"> <filter id=“8439" uri="sip:alice@example1.com“> <what> <include>//pidf:tuple/pidf:note</include> </what> </filter> </filter-set> • When removing a filter, a subscriber must explicitly do so by specifying the filter ID along with the “remove” attribute set to True. <?xml version="1.0" encoding="UTF-8"?> <filter-set xmlns="urn:ietf:params:xml:ns:simple-filter“> <filter id="8439" remove=“True”/> </filter-set>

  10. Filter Format Issues (1) • Problem: How does a subscriber replace a filter? <?xml version="1.0" encoding="UTF-8"?> <filter-set xmlns="urn:ietf:params:xml:ns:simple-filter" xmlns:pidf="urn:ietf:params:xml:ns:pidf"> <filter id="8439" uri="sip:alice@example1.com“ remove=“True”/> <filter id="8440" uri="sip:alice@example1.com“> <what> <include>//pidf:tuple/pidf:status/pidf:basic</include> </what> </filter> </filter-set>

  11. Filter Format Issues (1) • Proposal 1: disallow inclusion of ‘uri’ attribute when removing a filter <?xml version="1.0" encoding="UTF-8"?> <filter-set xmlns="urn:ietf:params:xml:ns:simple-filter" xmlns:pidf="urn:ietf:params:xml:ns:pidf"> <filter id="8439" remove=“True”/> <filter id="8440" uri="sip:alice@example1.com“> <what> <include>//pidf:tuple/pidf:status/pidf:basic</include> </what> </filter> </filter-set> • Proposal 2: Allow a filter to be replaced using the same filter id <?xml version="1.0" encoding="UTF-8"?> <filter-set xmlns="urn:ietf:params:xml:ns:simple-filter" xmlns:pidf="urn:ietf:params:xml:ns:pidf"> <filter id=“8439" uri="sip:alice@example1.com“> <what> <include>//pidf:tuple/pidf:status/pidf:basic</include> </what> </filter> </filter-set>

More Related