Event List Template: Open Issues

Adam RoachBen CampbellJonathan Rosenberg

mixed vs. parallel Current draft specifies

“multipart/mixed”, which is defined by MIME as containing ordered entries. Is “multipart/parallel” more appropriate?

Concerns with parallel have been raised: it might obligate the RLS to prune duplicates.

Meta-data Current draft uses MIME multitype

“preamble” area and in body-part headers. Neither practice is really endorsed by MIME.

Would a separate, structured body part containing, e.g., XML be more appropriate?

Do we bother aggregating meta-data?

Meta-data: presence list<list uri=“sip:friends@home.com” version =“7” state=“partial”> <resource uri=“sip:bob@example.com” state=“active” name=“Bob Smith” cid=“1”/> <resource uri=“sip:dave@example.com” state=“active” name=“Dave Jones” cid=“2”/></list>

Option 1: presence list list<list uri=“sip:mylists@example.com” version=“11” state=“partial”> <list uri=“sip:friends@home.com” version=“7” state=“partial”> <resource uri=“sip:bob@example.com” state=“active” name=“Bob Smith” cid=“1”/> <resource uri=“sip:dave@example.com” state=“active” name=“Dave Jones” cid=“2”/> </list> <list uri=“sip:eng@work.com” version =“4” state=“partial”> <resource uri=“sip:jdrosen@dynamicsoft.com” state=“active” name=“Jonathan Rosenberg” cid=“3”/> <resource uri=“sip:bcampbell@dynamicsoft.com” state=“active” name=“Ben Campbell” cid=“4”/> </list></list>

Option 2: presence list listContent-Type: multipart/mixed…Content-Type: application/elist+xml

<list uri=“sip:mylists@example.com” version=“11” state=“partial”> <resource uri=“sip:friends@home.com” state=“active” cid=“1” /> <resource uri=“sip:eng@work.com” state=“active” cid=“2” /></list>…Content-Type: application/elist+xml

<list uri=“sip:friends@home.com” version=“7” state=“partial”> <resource uri=“sip:bob@example.com” state=“active” name=“Bob Smith” cid=“1”/> <resource uri=“sip:dave@example.com” state=“active” name=“Dave Jones” cid=“2”/></list>

Uniform Depth As defined, you can subscribe to

trees that are only of the same depth.

I believe this to be mandatory behavior if we use templates.

Is this a large enough issue to warrant revisiting the template issue?

Uniform Depth, cont.

presence

presence presence presence presence presence presence

presencelist

presencelist

presencelistlist

Illegal!

Uniform Depth, cont.

presence presence presence presence presence presence presence

presencelist

presencelist

presencelist

presencelistlist

Note

Next version will be draft-ietf-simple-list-template-00.txt