1 / 15

SIPREC Recording Metadata (draft-ietf-siprec-metadata-07)

SIPREC Recording Metadata (draft-ietf-siprec-metadata-07). August 2nd 2012 IETF 84 meeting. Authors: Ram Mohan R, R Parthasarathi, Paul Kyzivat . Agenda. Changes in draft-ietf-siprec-metadata-07 from last version. Discuss Open & closed items in Metadata Next Steps.

cliff
Download Presentation

SIPREC Recording Metadata (draft-ietf-siprec-metadata-07)

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 (draft-ietf-siprec-metadata-07) August 2nd 2012 IETF 84 meeting Authors: Ram Mohan R, R Parthasarathi, Paul Kyzivat

  2. Agenda • Changes in draft-ietf-siprec-metadata-07 from last version. • Discuss Open & closed items in Metadata • Next Steps

  3. Changes from Previous version • The new version of draft has following changes: • Incorporated start/stop times for CS • Edits to CSRSassociation and ParticipantCSAssociation • Minor NITS received as comments in previous version • Changed “id” attribute into XML element specific id like session “id” attribute as session_id. • Modified the examples to reflect the change in schema

  4. Metadata Model Recording Session(RS) 1..* 0..* Communication Session(CS) Group 1..* 0..* 0..1 1..* Communication Session(CS) 1.. * 0..* 1.. * 0..* receives 0.. * 0.. * Participant Media Stream 1.. * 0..* sends ParticipantCS Association ParticipantStream Association

  5. Metadata Model: Media Stream Participant OpenItem: BT usecase • Media stream shall associate with multiple CS and it shall be mixed stream. But participant who is contributing at the specific time has to be identified by RTP/RTCP mechanism. 0..* 1..* Media Stream • Media Stream Reference • Content-type CS 0.. * 1.. * receives sends 0..* 0..*

  6. Metadata Model: Media Streamwhat we really have Issues • Implicit and unnamed element for the stream itself, with no attributes. Participant 0..* 1..* ??? CS Media Stream • Media StreamReference (label) • Content-type • Associate-time • Dissociate-time 0.. * 1.. * receives sends 0..* 0..*

  7. Metadata : Multiple CS into single stream_id usage • <stream stream_id="Axzg12XHdhjelfjhdldjf;34jn78==“ session_id="zzlafnvvjlCHllaHF6mn8kkSS=="> • <label>99</label> • </stream> • <stream stream_id="Axzg12XHdhjelfjhdldjf;34jn78==" • session_id=" zSfPoSvdSDCmU3A3TRDxAw=="> • <label>99</label> • </stream> • This is current proposal for representing multiple CSs for same stream: • <stream> has two keys, so it is effectively an association class. • Multiple instances with same stream_id • <send> and <recv> reference only the stream_id. There is no element with that single key.

  8. Metadata Model: Media StreamAlternative Representation • Stream is identified by an unique id within the XML document • The association to the CS can be represented by an attribute (non-key) in the XML element. • But this then requires a different way to represent the BT Use case – multiple CS media streams recorded as a single mix. Participant 0..* 1..* Media Stream • Media Stream Reference • Content-type • Associate-time • Dissociate-time CS 0.. * 1.. * receives sends 0..* 0..*

  9. Metadata : Multiple CS into single stream_id usage - Alternative • <stream stream_id="Axzg12XHdhjelfjhdldjf;34jn78==“ session_id="zzlafnvvjlCHllaHF6mn8kkSS=="> • <label>99</label> • </stream> • <stream stream_id=”Byzh12XHdhjelfjhdldjf;34jn99==" • session_id=" zSfPoSvdSDCmU3A3TRDxAw=="> • <label>99</label> • </stream> • Two distinct instances of <stream>, with unique ids. • The mix is indicated by both of these instances referencing the same label, and hence the same SDP m-line. • This allows two ways of accomplishing the mix: • A single RTPstream, one SSRC • Separate RTP stream for each CS media session.

  10. Metadata: Duplicate stream Participant Open Items: • Duplicate stream shall be represented in SDP itself as shown in draft-begen-avtcore-rtp-duplication-01 ? 0..* 1..* Media Stream • Media Stream Reference • Content-type CS 0.. * 1.. * receives sends 0..* 0..*

  11. Metadata Format: Participant •  <participant participant_id="srfBElmCRp2QB23b7Mpk0w==" session_id="hVpd7YQgRW2nD22h7q60JQ=="> <name ID=sip:bob@biloxi.com> <name xml:lang="it">Bob R</name> </nameID> • </participant> Closed Items: • Removing session_id attribute from Participant XML element to align the XML schema with model. Any objection?

  12. Metadata Model: CSRS association Closed Items: • Adding CSRS association in the model figure. Recording Session(RS) CSRS Association 1..* 0..* Communication Session(CS)

  13. Metadata Format: Stream •   <xs:element name="csrc" type='xs:string' minOccurs='0' maxOccurs='1'/> Open Items: • Removing of CSRC attribute from stream XML element to align the XML schema with model.

  14. Metadata Format: URN UUID • i1Pz3to5hGk8fuXl+PbwCw== Open Items: • Removing the fixed padding “==“ in base64 form of URN UUID?

  15. Next steps • Update draft based on the current closure • Add more metadata examples • Publish next version (08) and ask for WGLC

More Related