SIP Event Lists

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
Example Message

• NOTIFY sippres.example.com SIP/2.0
• Via SIP/2.0/TCP pres.example.combranchz9hG4b
  KmGL1nyZfQI
• Max-Forwards 70
• From ltsipadam-friends_at_example.orggttagJenZ40
  P3
• To ltsippres.example.comgttaga12eztNf
• Call-ID kBq5XhtZLN_at_pres.example.com
• CSeq 294444656 NOTIFY
• Contact ltsipexample.orggt
• Event presence
• Subscription-State pending
• Require eventlist
• Content-Type multipart/relatedtype"applicatio
  n/rlmixml"
• start"ltCvjpeo_at_example.orggt"boundary"tuLL
  l3lDyPZX0GMr2YOo"
• Content-Length 2038
• --tuLLl3lDyPZX0GMr2YOo
• Content-Transfer-Encoding 8bit
• Content-ID ltCvjpeo_at_example.orggt
• Content-Type application/rlmixmlcharset"UTF
  -8"

• --tuLLl3lDyPZX0GMr2YOo
• Content-Transfer-Encoding 8bit
• Content-ID ltmrEakg_at_example.orggt
• Content-Type application/cpim-pidfxmlcharset
  "UTF-8"
• lt?xml version"1.0" encoding"UTF-8"?gt
• ltpresence xmlns"urnietfparamsxmlnscpim-pi
  df"
• entity"sipjoe_at_example.org"gt
• lttuple id"7823a4"gt
• ltstatusgt
• ltbasicgtopenlt/basicgt
• lt/statusgt
• ltcontact priority"1.0"gtsipjoe_at_example.org
  lt/contactgt
• lt/tuplegt
• lt/presencegt
• --tuLLl3lDyPZX0GMr2YOo
• Content-Transfer-Encoding 8bit
• Content-ID ltKKMDmv_at_example.orggt

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

• ltlist uri"sipadam-friends_at_lists.example.com"
  version"7" name"Buddy List" fullState"true"gt
• ltresource uri"sipbob_at_example.com" name"Bob
  Smith"gt
• ltinstance id"juwigmtboe" state"active"
  cid"12345.aaa_at_example.com"/gt
• lt/resourcegt
• ltresource uri"sipdave_at_example.com" name"Dave
  Jones"gt
• ltinstance id"hqzsuxtfyq" state"active"
  cid"12345.aab_at_example.com"/gt
• lt/resourcegt
• lt/listgt

7
Example 2 Downstream Forking

• ltlist uri"sipadam-friends_at_lists.example.com"
  version"7" name"Buddy List" fullState"true"gt
• ltresource uri"sipbob_at_example.com" name"Bob
  Smith"gt
• ltinstance id"juwigmtboe" state"active"
  cid"12345.aaa_at_example.com"/gt
• lt/resourcegt
• ltresource uri"sipdave_at_example.com" name"Dave
  Jones"gt
• ltinstance id"hqzsuxtfyq" state"active"
  cid"12345.aab_at_example.com"/gt
• ltinstance idmbjqslikeo" state"active"
  cid"12345.aac_at_example.com"/gt
• lt/resourcegt
• lt/listgt

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. (Shouldnt take
  long only 16 pages of spec, 12 pages of
  example).
• Other than that, should be ready for last call.