Subject: [xrblock] New Liaison Statement, "IETF XRBLOCK Workgroup to W3C WebRTC WG"

From: Liaison Statement Management Tool <[email-masked]>
Date: Wed, 02 Mar 2016 10:45:47 -0800

Title: IETF XRBLOCK Workgroup to W3C WebRTC WG
Submission Date: 2016-03-02
URL of the IETF Web page: https://datatracker.ietf.org/liaison/1459/

From: "Shida Schubert" <[email-masked]>
To: Wendy Seltzer <[email-masked]>,Philippe Le Hégaret <[email-masked]>
Cc: Barry Leiba <[email-masked]>,Dan Romascanu <[email-masked]>,Ben Campbell <[email-masked]>,Alissa Cooper <[email-masked]>,mnot <[email-masked]>,Metric Blocks for use with RTCP's Extended Report Framework Discussion List <[email-masked]>,Shida Schubert <[email-masked]>,
Response Contacts: Dan Romascanu <[email-masked]>, Shida Schubert <[email-masked]>
Technical Contacts: 
Purpose: For information

Body: 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 [email-masked] <mailto:[email-masked]>. 

S. Schubert
Co-chair, XRBLOCK Workgroup
Attachments:

No document has been attached