siprec recording metadata format (draft-ram-siprec-metadata-format-01)
DESCRIPTION
SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-01). IETF-80 SIPREC MEETING R Parthasarathi On behalf of the team. Team: Paul Kyzivat, Ram Mohan R, R Parthasarathi. Agenda. Update in Metadata format (draft-ram-siprec-metadata-format-01) Recording-Metadata XML Example - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-01)](https://reader036.vdocument.in/reader036/viewer/2022062301/56814044550346895dabb49b/html5/thumbnails/1.jpg)
1
SIPRECRecording Metadata format
(draft-ram-siprec-metadata-format-01)
IETF-80 SIPREC MEETING
R ParthasarathiOn behalf of the team
Team: Paul Kyzivat, Ram Mohan R, R Parthasarathi
![Page 2: SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-01)](https://reader036.vdocument.in/reader036/viewer/2022062301/56814044550346895dabb49b/html5/thumbnails/2.jpg)
Agenda
• Update in Metadata format (draft-ram-siprec-metadata-format-01)
• Recording-Metadata XML Example• URN UUID details• Partial XML mechanism explanation• Discuss Open items in Metadata format• Glance at Closed items in Metadata format• Next Steps
![Page 3: SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-01)](https://reader036.vdocument.in/reader036/viewer/2022062301/56814044550346895dabb49b/html5/thumbnails/3.jpg)
Update in (-01) Metadata format• Include recording-metadata element as a
container element instead of recording element. This helps in avoiding duplicate data of recording elements during the partial XML update
• Removed container element like sessions, participants, streams from XML document as parent reference exists in each element
![Page 4: SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-01)](https://reader036.vdocument.in/reader036/viewer/2022062301/56814044550346895dabb49b/html5/thumbnails/4.jpg)
Recording-Metadata Example<recording-metadata xmlns='...:siprec'> <recording id=""> </recording> <group id="" recording=""></group> <session id=""group=""></session>
<participant id=""session=""></participant> <stream id=""session=""></stream> <extensiondata id="" parent=""> </extensiondata></recording-metadata>
![Page 5: SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-01)](https://reader036.vdocument.in/reader036/viewer/2022062301/56814044550346895dabb49b/html5/thumbnails/5.jpg)
sendsreceives0.. *
1
1
11
0..*
Metadata Format element view by SRS
5
Recording
group
Stream
ExtensionData
Session 1
Participant
0.. *1..*
11..*
1
1..*0..*
0..*
1.. *
0..*
![Page 6: SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-01)](https://reader036.vdocument.in/reader036/viewer/2022062301/56814044550346895dabb49b/html5/thumbnails/6.jpg)
Update in (-01) Metadata format• URN UUID (RFC 4122) mechanism is used as
the unique id mechanism for relevant XML elements like recording, group, session, stream, participant, extensiondata
• Partial XML passing in RS is supported by having unique URN UUID for group, session, stream, participant, recording, extension data which are directly under recording-metadata (“root”) container/namespace.
![Page 7: SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-01)](https://reader036.vdocument.in/reader036/viewer/2022062301/56814044550346895dabb49b/html5/thumbnails/7.jpg)
URN UUID usage in each element
7
• URN UUID (RFC 4122) mechanism is used as the unique id mechanism for relevant XML elements like recording, group, session, stream, participant, extensiondata
• All UUID will be used in partial update of XML• UUID is unique in case multiple SRC to single
SRS. No feedback from SRS required• Group UUID is also used to abstract the exact
grouping mechanism
![Page 8: SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-01)](https://reader036.vdocument.in/reader036/viewer/2022062301/56814044550346895dabb49b/html5/thumbnails/8.jpg)
Participant URN UUID XML example
8
<participant id="urn:uuid:b2b7c112-5982-469d-9007-6ddbecca64d3" session="urn:uuid:855a5ded-8420-456d-a70f-6da1eeaeb425">
<aor>sip:[email protected]</aor> <name xml:lang="it">Partha</name> <send> <id>urn:uuid:8b53f3de-da39-4846-93c7-
ee5e5f8f6f0b</id> </send> <recv> <id>urn:uuid:50000c9b-9191-40a4-8231-
5bcbca5e2b17</id></recv></participant>
![Page 9: SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-01)](https://reader036.vdocument.in/reader036/viewer/2022062301/56814044550346895dabb49b/html5/thumbnails/9.jpg)
URN UUID extension
9
• The usage of URN UUID can be extended later to other kinds of URNs if that becomes necessary
![Page 10: SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-01)](https://reader036.vdocument.in/reader036/viewer/2022062301/56814044550346895dabb49b/html5/thumbnails/10.jpg)
Partial XML Update mechanism
10
• Partial XML passing in RS is supported by having unique URN UUID for group, session, stream, participant, recording, extension data which are directly under recording-metadata (“root”) container/namespace. All UUID will be used in partial update of XML
• Each metadata block will be able to passed partially within the same RS
![Page 11: SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-01)](https://reader036.vdocument.in/reader036/viewer/2022062301/56814044550346895dabb49b/html5/thumbnails/11.jpg)
Partial XML Alternative approaches analyzed
11
• Partial XML data using RFC 5261 - An Extensible Markup Language (XML) Patch Operations - Too complex for Recording
• Rest based architecture for passing XML. – Best for Non-realtime protocol like HTTP but in case of SIP, duplicate information required both in SIP and XML
![Page 12: SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-01)](https://reader036.vdocument.in/reader036/viewer/2022062301/56814044550346895dabb49b/html5/thumbnails/12.jpg)
Partial XML Update
12
<recording-metadata xmlns='urn:ietf:params:xml:ns:siprec'> <dataMode>partial</dataMode>
<stream id="urn:uuid:50000c9b-9191-40a4-8231-5bcbca5e2b17">
<stop-time>2010-12-16T23:41:07Z</stop-time> <label>96</label> </stream> </recording-metadata>
![Page 13: SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-01)](https://reader036.vdocument.in/reader036/viewer/2022062301/56814044550346895dabb49b/html5/thumbnails/13.jpg)
Update in (-01) Metadata format• Updated elements in XML document as per
draft-ram-siprec-metadata-04 elements & associations
• Changed appdata element name as extensiondata
• Added Partial Update example & SIP usage XML+SDP example for readability
• Portion of security considerations section is added.
![Page 14: SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-01)](https://reader036.vdocument.in/reader036/viewer/2022062301/56814044550346895dabb49b/html5/thumbnails/14.jpg)
Recording Element Example
14
<?xml version="1.0" encoding="UTF-8"?> <recording-metadata xmlns='urn:ietf:params:xml:ns:siprec'>
<recording id="urn:uuid:7979087f-959c-4b84-bb22-07da66733b47">
<requestor>SRC</requestor> <type>selective</type> </recording></recording-metadata>
![Page 15: SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-01)](https://reader036.vdocument.in/reader036/viewer/2022062301/56814044550346895dabb49b/html5/thumbnails/15.jpg)
Group & Session Element Example
15
<group id="urn:uuid:efe3930b-2a31-4e6a-a6ab-203fd7078302“ recording="urn:uuid:7979087f-959c-4b84-bb22-07da66733b47">
<initiator>sip:[email protected]</initiator> </group><session id="urn:uuid:855a5ded-8420-456d-a70f-
6da1eeaeb425" group="urn:uuid:efe3930b-2a31-4e6a-a6ab-203fd7078302" />
</session>
![Page 16: SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-01)](https://reader036.vdocument.in/reader036/viewer/2022062301/56814044550346895dabb49b/html5/thumbnails/16.jpg)
Extension Data Element Example
16
<extensiondata xmlns='http://example.com/sessionapp' id="urn:uuid:a54d6aa5-d40d-43f9-88c5-b4633d873bdd"
parent="urn:uuid:855a5ded-8420-456d-a70f-6da1eeaeb425">
<structure>FOO!</structure> <whatever>bar</whatever>
</extensiondata> Parent UUID belongs any one of metadata block
element recording, group, session, participant, stream
![Page 17: SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-01)](https://reader036.vdocument.in/reader036/viewer/2022062301/56814044550346895dabb49b/html5/thumbnails/17.jpg)
Open Issue – Id generation scope
17
• The current approach of partial data is based on metadata block like stream, participant which helps is reducing the number of URN UUID maintained in SRC and SRS
• Another approach for Partial Update is to have URN UUID for individual elements like aor, name. This can bloat up the XML structure with a lot of URN UUIDs.
• Which approach is the best way for SIPREC?
![Page 18: SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-01)](https://reader036.vdocument.in/reader036/viewer/2022062301/56814044550346895dabb49b/html5/thumbnails/18.jpg)
Open Issue – Codec Parameters in Stream element
18
• Whether Codec parameters in RS SDP has to be duplicated in Stream XML or Stream XML linkage with RS SDP using label attribute will be suffice? Till now, Identified attributes are–Media Type (audio/video/…)–Direction attribute–Content type (RFC 4796)–RTP MUX (RFC 5576)
![Page 19: SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-01)](https://reader036.vdocument.in/reader036/viewer/2022062301/56814044550346895dabb49b/html5/thumbnails/19.jpg)
Open Issue – Multiplexing different participants' streams on the same
port
19
– In case RTP MUX, Multiple participants will have single stream on the same port. How these stream has to be represented in the format?• Multiple Participant element refers single
stream• RFC 5576 – ssrc attribute with cname param• Some other?
![Page 20: SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-01)](https://reader036.vdocument.in/reader036/viewer/2022062301/56814044550346895dabb49b/html5/thumbnails/20.jpg)
Closed Issue – SIP usage table & example
20
• SIP usage table & Example are provided in Sec 7 & 8 for the readability. These section will be removed when the draft is getting accepted as WG item (John e-mail on 3/10 with title “Comments on draft-portman-siprec-protocol-03”)
![Page 21: SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-01)](https://reader036.vdocument.in/reader036/viewer/2022062301/56814044550346895dabb49b/html5/thumbnails/21.jpg)
Closed Issue – Initiator attribute removal in group element
21
• Remove Initiator attribute in group element – (Partha e-mail on 3/12 with title “Review Request for draft-ram-siprec-metadata-format-01”)
• AI: -02 draft has to remove Initiator attribute
![Page 22: SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-01)](https://reader036.vdocument.in/reader036/viewer/2022062301/56814044550346895dabb49b/html5/thumbnails/22.jpg)
Closed Issue – Minor text changes
22
• ExtensionData element XML schema shows “session” instead of “parent”
• Sec 4.2.2 has to add “participant” and the text has to look like: "recording-metadata element has recording, group, session, participant, stream elements”(John e-mail on 3/13 with title “Comments on draft-portman-siprec-protocol-03”)
• AI: -02 draft has to update the text
![Page 23: SIPREC Recording Metadata format (draft-ram-siprec-metadata-format-01)](https://reader036.vdocument.in/reader036/viewer/2022062301/56814044550346895dabb49b/html5/thumbnails/23.jpg)
Next steps
• Add Milestone in SIPREC or merge with SIPREC solution?
• In case of adding milestone, Request to Adopt as WG item
• Close all the open items• Update next revision based on the comments• Request for further review in the mailer