SIPREC Recording Metadata Model for SRS draftietfsiprecmetadata01 June

SIPREC Recording Metadata Model for SRS (draft-ietf-siprec-metadata-01) June 23, 2011 Virtual Interim meeting Ram Mohan R On behalf of the team Team: Paul Kyzivat, Ram Mohan R, R Parthasarathi 1

Agenda • Changes in draft-ietf-siprec-metadata from the previous version • Discuss Open items in Metadata Model • Next Steps

Changes from Previous version • The new version of draft has following changes (Most of which were agreed in last interim meeting and rest over mailer) : – Associate CS block directly with RS since CS-Group is optional – RS shall be retained in model but no XML representation is needed[ RS dialog will serve the purpose]. Hence attributes of RS shall be removed – Comments from Charles/Henry/Muthu (on instance diagrams and minor nits)

Metadata Model 1 Recording Session(RS) 1. . * 0. . * Communication Session(CS) Group 0. . 1 1. . * Communication Session(CS) 1. . * 2. . * Participant receives 0. . * 1. . * 0. . * sends 1 1 1. . * 0. . * Media Stream 1 0. . * Extension Data 1 4

Metadata Model: Communication Session Group Recording Session (RS) Open Items: 1. . * 0. . * Ø Any objection for the addition of Optional Stop/Start time attribute Communication Session Group (CS Group) CS Group unique ID 1 0. . * Extension Data 0. . 1 1. . * Communication Session 5

Metadata Model: Media Stream Participant 0. . * receives 0. . * Closed Items: 1. . * 0. . * Ø Codec params (CS SDP) removed sends Open Items: Media Stream CS 1. . * 0. . * • Start Time • End Time • Media Stream Reference 1 0. . * Ø Does MS has a life outside CS? [ e. g. MMOH cases and Extension transfer by 3 PCC with Data multiple CS and single MS] – There is a general inclination to keep MS local to CS. However it may have some issues described in http: //www. ietf. org/mailarchive/web/siprec/curren t/msg 02091. html – How do we want to go forward on this ? 6

Metadata Model: Media Stream Ø What does an MS object represent? – There was a general agreement on option 2 of http: //www. ietf. org/mailarchive/web/siprec/current/msg 02044. html. Towards this we agreed there is a need to have an attribute(like “content”) in MS block to tie together the two MS ( of same content type) that represent the two sides of a single conversation – What should content attribute have as value ? And how SRC shall derive the same ? – Is RFC 4796 sufficient (as Charles says)? or do we need content element in recording metadata xml schema ?

Metadata Model: Participant Communication Session Open Items: 1. . * 2. . * Participant • Ao. R list • Name 0. . * 1 Extension Data 1. . * receives 0. . * Ø Participant lifetime is within the scope of CS or CSG/RS. Ø Is Optional Stop/Start time attribute needed? 0. . * sends Media Stream 8

General Open items in model draft • Use of RFC 2119 language in the metadata model – Do we want to leave the current language ( use of RFC 2119) as it is for now and re-visit later when we merge format in to model ? OR – Do we want to remove all the normative statements right now (in the next revision) and have them (around the format portions) when we merge format and model ?

Next steps • Close the remaining open items [we have only few minor ones] • Is it the right time to merge format doc with model document ?