1. SIP Event Lists Adam Roach 3/17/2003

2. Major Changes No longer a template; now simply an extension (using Supported/Require). Arbitrary nesting of lists is allowed. Lists may contain individual resources and lists at the same level. Meta-information moved into own XML body part. 12-page example added.

3. Meta-Information Example Message SIP Headers Resource 1 Resource 2 NOTIFY sip:pres.example.com SIP/2.0 Via: SIP/2.0/TCP pres.example.com;branch=z9hG4bKmGL1nyZfQI Max-Forwards: 70 From: ;tag=JenZ40P3 To: ;tag=a12eztNf Call-ID: kBq5XhtZLN@pres.example.com CSeq: 294444656 NOTIFY Contact: Event: presence Subscription-State: pending Require: eventlist Content-Type: multipart/related;type="application/rlmi+xml"; start=" ";boundary="tuLLl3lDyPZX0GMr2YOo" Content-Length: 2038 --tuLLl3lDyPZX0GMr2YOo Content-Transfer-Encoding: 8bit Content-ID: Content-Type: application/rlmi+xml;charset="UTF-8" <list uri="sip:adam-friends@example.org" version="1" name="Buddy List at ORG" fullState="true"> --tuLLl3lDyPZX0GMr2YOo Content-Transfer-Encoding: 8bit Content-ID: Content-Type: application/cpim-pidf+xml;charset="UTF-8" <presence xmlns="urn:ietf:params:xml:ns:cpim-pidf" entity="sip:joe@example.org"> open sip:joe@example.org --tuLLl3lDyPZX0GMr2YOo Content-Transfer-Encoding: 8bit Content-ID: Content-Type: application/cpim-pidf+xml;charset="UTF-8" <presence xmlns="urn:ietf:params:xml:ns:cpim-pidf" entity="sip:mark@example.org"> closed --tuLLl3lDyPZX0GMr2YOo--

4. Open Issue: Filters RFC 3265 allows bodies for applying filters to the subscription. The interaction with lists is tricky. Does the body apply to the top-level list, the nodes, or both? Note that filter syntax may vary depending on the answer. Could make filters a provisioned part of the list, but doing so is not a complete solution. Similar issue arises with Event header parameters.

5. Help: I Am Not An XML Guy Read through as much of the W3C spec as I could take in one sitting, but not certain my usage is 100% correct. Need an XML expert to look over usage of XML in draft, and to provide feedback.

6. Example 1: Metainformation

7. Example 2: Downstream Forking

8. TBD Some editorial cleanup to separate specific example of “pass through” of subscriptions from normative sections.

9. What Now? Need discussion on the list about handling of filters. Generally, needs more eyeballs. (Shouldn’t take long: only 16 pages of spec, 12 pages of example). Other than that, should be ready for last call.