[xrblock] Liaison Statement to W3C for rtcweb-rtcp-xr-metrics

Shida Schubert <shida@ntt-at.com> Wed, 20 January 2016 04:32 UTC

Return-Path: <shida@ntt-at.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id E8C051A1B7B for <xrblock@ietfa.amsl.com>; Tue, 19 Jan 2016 20:32:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id p7XS_9E9v-8p for <xrblock@ietfa.amsl.com>; Tue, 19 Jan 2016 20:32:55 -0800 (PST)
Received: from gateway22.websitewelcome.com (gateway22.websitewelcome.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E97C1A1B73 for <xrblock@ietf.org>; Tue, 19 Jan 2016 20:32:55 -0800 (PST)
Received: from cm1.websitewelcome.com (cm.websitewelcome.com []) by gateway22.websitewelcome.com (Postfix) with ESMTP id E4D74D9644419 for <xrblock@ietf.org>; Tue, 19 Jan 2016 22:32:54 -0600 (CST)
Received: from gator4135.hostgator.com ([]) by cm1.websitewelcome.com with id 84Yt1s0113AKFgo014YuA6; Tue, 19 Jan 2016 22:32:54 -0600
Received: from [] (port=34954 helo=[]) by gator4135.hostgator.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.85) (envelope-from <shida@ntt-at.com>) id 1aLkRx-000Q5q-OO for xrblock@ietf.org; Tue, 19 Jan 2016 22:32:53 -0600
From: Shida Schubert <shida@ntt-at.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <08A91250-8AB4-4B33-8C9A-D8D589653811@ntt-at.com>
Date: Tue, 19 Jan 2016 20:32:53 -0800
To: xrblock <xrblock@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
X-Mailer: Apple Mail (2.2104)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator4135.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ntt-at.com
X-BWhitelist: no
X-Exim-ID: 1aLkRx-000Q5q-OO
X-Source-Sender: ([]) []:34954
X-Source-Auth: shida@agnada.com
X-Email-Count: 2
X-Source-Cap: c3NoaWRhO3NzaGlkYTtnYXRvcjQxMzUuaG9zdGdhdG9yLmNvbQ==
Archived-At: <http://mailarchive.ietf.org/arch/msg/xrblock/1jvxUX0sbe29NwOhWbucESXrl-k>
Subject: [xrblock] Liaison Statement to W3C for rtcweb-rtcp-xr-metrics
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xrblock/>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jan 2016 04:32:57 -0000


Below is a draft for liaison statement to W3C for draft-ietf-xrblock-rtcweb-rtcp-xr-metrics. 

Welcoming comments…



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.


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 are welcome. 

S. Schubert
Co-chair, XRBLOCK Workgroup