<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> Hi, It would certainly be beneficial to Implement the mandatory stats required but it wouldn't quite be a hard rejection if they aren't implemented. It would require a reasonable explanation as to why they aren't implemented for new structures though. Cheers -Matt <div class="moz-cite-prefix">On 23/10/20 8:00 am, Lin, Sherrill wrote: </div> <blockquote type="cite" cite="mid:C531EFE3-8F9E-4351-B7B2-8FA1AC2CFF2B@amazon.com"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style><!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:DengXian; panose-1:2 1 6 0 3 1 1 1 1 1;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:"\@DengXian"; panose-1:2 1 6 0 3 1 1 1 1 1;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; font-size:12.0pt; font-family:"Calibri",sans-serif;} a:link, span.MsoHyperlink {mso-style-priority:99; color:#0563C1; text-decoration:underline;} span.EmailStyle17 {mso-style-type:personal-compose; font-family:"Calibri",sans-serif; color:windowtext;} .MsoChpDefault {mso-style-type:export-only; font-size:12.0pt;}size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt;} div.WordSection1 {page:WordSection1;}</style> <div class="WordSection1"> Hi there,<o:p></o:p> <o:p> </o:p> Our team in Alexa Communications wants to add selected ice candidates information to WebRTC stats. We find that in gstwebrtcstats.c (<a href="https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/blob/master/ext/webrtc/gstwebrtcstats.c" moz-do-not-send="true">https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/blob/master/ext/webrtc/gstwebrtcstats.c</a>), RTCIceCandidateStats, RTCIceCandidatePairStats and RTCTransportStats are not constructed yet. We think these three stats are the structures needed for hosting selected ice candidate data, and we are interested in implementing them following the w3.org spec (<a href="https://www.w3.org/TR/webrtc-stats/" moz-do-not-send="true">https://www.w3.org/TR/webrtc-stats/</a>).<o:p></o:p> <o:p> </o:p> However, we notice there’s a list of mandatory fields for implementing each stats structure: <a href="https://w3c.github.io/webrtc-pc/#mandatory-to-implement-stats" moz-do-not-send="true">https://w3c.github.io/webrtc-pc/#mandatory-to-implement-stats</a>. Does it mean, for Gstreamer community to accept the code changes, we will have to implement all the mandatory fields for all three stats structures as defined in that doc?<o:p></o:p> <o:p> </o:p> Thanks,<o:p></o:p> Sherrill<o:p></o:p> </div> <fieldset class="mimeAttachmentHeader"></fieldset> <pre class="moz-quote-pre" wrap="">_______________________________________________ gstreamer-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:gstreamer-devel@lists.freedesktop.org">gstreamer-devel@lists.freedesktop.org</a> <a class="moz-txt-link-freetext" href="https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel">https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a> </pre> </blockquote> </body> </html>