- From: Dominique Hazael-Massieux <dom@w3.org>
- Date: Thu, 3 Mar 2016 08:39:52 +0100
- To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Hello, We have received the following liaison statement from the IETF XRBLOCK Workgroup: https://datatracker.ietf.org/liaison/1459/ > Dear WebRTC WG, > > The XRBLOCK WG in IETF has been working on a draft recommending the type of > RTCP XR blocks that would be beneficial for webrtc endpoint, in order to > identify any issues regarding media stream(s) and act on to provide better > overall user-experience to the end-user. The draft defines a IANA registry > with a list of identifiers for the WebRTC's statistics API with a set of RTCP > SR, RR, and XR metrics related to the transport of multimedia flows. > > https://datatracker.ietf.org/doc/draft-ietf-xrblock-rtcweb-rtcp-xr-metrics/ > <https://datatracker.ietf.org/doc/draft-ietf-xrblock-rtcweb-rtcp-xr-metrics/> > > Gist from the introduction of the draft: > "The WebRTC Stats API currently lists metrics reported in the RTCP Sender and > Receiver Report (SR/RR) [RFC3550] to fulfill this requirement. However, the > basic metrics from RTCP SR/RR are not sufficient for precise quality > monitoring, or diagnosing potential issues. > > In this document, we provide some guidelines on choosing additional RTP > metrics for the WebRTC [W3C.WD-webrtc-20150210]. Furthermore, we create a > registry containing metrics reported in RTCP XR." > > Any comments from the W3C WebRTC WG participants are welcome, they can be > provided directly to the WG by sending your comments to xrblock@ietf.org > <mailto:xrblock@ietf.org>. > > S. Schubert > Co-chair, XRBLOCK Workgroup Regards, Dom
Received on Thursday, 3 March 2016 07:39:58 UTC