1 / 11

SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-02)

SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-02). 23rd June 2011 Interim SIPREC MEETING R Parthasarathi On behalf of the team. Team: Paul Kyzivat, Ram Mohan R, R Parthasarathi. 1. Agenda. Update on Metadata format (draft-ram-siprec-metadata-format-02)

edmunda
Télécharger la présentation

SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-02)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SIPRECRecording Metadata format(draft-ram-siprec-metadata-format-02) 23rd June 2011 Interim SIPREC MEETING R Parthasarathi On behalf of the team Team: Paul Kyzivat, Ram Mohan R, R Parthasarathi 1

  2. Agenda Update on Metadata format (draft-ram-siprec-metadata-format-02) Discuss Open items in Metadata format Next Steps

  3. Update in (-02) Metadata format Changed recording element as a container element instead of recording-metadata element. Also, removed existing recording element as RS SIP dialog will carry those info. Updated XML example, XML schema as per review comments Made “group” element as an optional one

  4. Recording-Metadata Example <recording xmlns='...:siprec'> <group id="" recording=""></group> <session id=""group=""></session> <participant id="“ session = “”> </participant> <stream id=""session=""></stream> <extension data id="" parent=""> </extension data> </recording>

  5. Metadata Format element view by SRS group 1 Extension Data 0..1 0..* 0..* Session 1 1.. * 2..* 1..* 1..* Participant 1 0.. * 1.. * receives sends 0..* 0..* 1 1 Stream 5

  6. Open Issue 1 – Stream Unique Id generation mechanism • Usecases where Stream (MS) needs to be globally unique • Mapping between CS media stream and RS media stream is 1:1 or 1:N or N:1. As all possible relationship possible, there is a need for URN UUID (global id). • Multicast scenario wherein MS is span across CS. There is a need for global id. • Multiple SRC records same CS and MS to single SRS • Open issue: Whether unique id has to be URN UUID (global) or xml:id (local) 6

  7. Open Issue 2 – Participant Unique Id generation mechanism • Participant needs to be unique id within CS or it may extend to multiple CS within single RS. Whether unique id has to be URN UUID or xml:id • participant scope is within single CS with multiple RS or single RS within CS or depends ? 7

  8. Open Issue 3 – Extensiondata in XML • Whether extension data has to be passed as a separate metadata element or not? • Passing the extension data as a individual metadata block allows partial-update of extension-data alone or partial-update of metadata main element without resending extension-data in each transaction 8

  9. Open Issue 4 – Unique id for Extensiondata • If Extension data is required to be passed separately, Global unique id (URN UUID) or xml:id has to be used. 9

  10. Open Issue 5 – Codec Parameters in Stream element • Whether Codec parameters in RS SDP has to be duplicated in Stream XML or Stream XML “label” attribute linkage with RS SDP will be suffice? Till now, Identified attributes are • Media Type (audio/video/…) • Direction attribute • Content type (RFC 4796) • RTP MUX (RFC 5576) 10

  11. Next steps • Ready to merge with SIPREC metadata draft? • Close all the open items • Update next revision based on the accepted comments • Request for further review in the mailer

More Related