1. Event List Template: Open Issues Adam Roach Ben Campbell Jonathan Rosenberg

2. 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.

3. 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?

4. Meta-data: presence list

5. Option 1: presence list list

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

7. 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?

8. Uniform Depth, cont. presence list presence list presence list Illegal!

9. Uniform Depth, cont. presence list presence list presence list presence list

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