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

Shida Schubert <shida@ntt-at.com> Thu, 21 January 2016 03:57 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 312F11B2E1C for <xrblock@ietfa.amsl.com>; Wed, 20 Jan 2016 19:57:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OD2barNIvj75 for <xrblock@ietfa.amsl.com>; Wed, 20 Jan 2016 19:57:15 -0800 (PST)
Received: from gateway32.websitewelcome.com (gateway32.websitewelcome.com [192.185.145.102]) (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 A01011B2E1B for <xrblock@ietf.org>; Wed, 20 Jan 2016 19:57:15 -0800 (PST)
Received: from cm1.websitewelcome.com (cm.websitewelcome.com [192.185.0.102]) by gateway32.websitewelcome.com (Postfix) with ESMTP id D9360DB4685E9 for <xrblock@ietf.org>; Wed, 20 Jan 2016 21:57:14 -0600 (CST)
Received: from gator4135.hostgator.com ([192.185.4.147]) by cm1.websitewelcome.com with id 8TxD1s00v3AKFgo01TxEp4; Wed, 20 Jan 2016 21:57:14 -0600
Received: from [71.202.231.23] (port=45780 helo=[10.0.96.16]) by gator4135.hostgator.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.85) (envelope-from <shida@ntt-at.com>) id 1aM6Mz-000OHZ-JI; Wed, 20 Jan 2016 21:57:13 -0600
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Shida Schubert <shida@ntt-at.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA6BEF0A1D@AZ-FFEXMB04.global.avaya.com>
Date: Wed, 20 Jan 2016 19:57:12 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <3A96CDF3-E8E2-4381-AC9E-A19F5A92B29A@ntt-at.com>
References: <08A91250-8AB4-4B33-8C9A-D8D589653811@ntt-at.com> <9904FB1B0159DA42B0B887B7FA8119CA6BEF0A1D@AZ-FFEXMB04.global.avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
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-Source-IP: 71.202.231.23
X-Exim-ID: 1aM6Mz-000OHZ-JI
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: ([10.0.96.16]) [71.202.231.23]:45780
X-Source-Auth: shida@agnada.com
X-Email-Count: 3
X-Source-Cap: c3NoaWRhO3NzaGlkYTtnYXRvcjQxMzUuaG9zdGdhdG9yLmNvbQ==
Archived-At: <http://mailarchive.ietf.org/arch/msg/xrblock/pSLrg79NMo-7mAC2WjCEaOt1pco>
Cc: xrblock <xrblock@ietf.org>
Subject: Re: [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: Thu, 21 Jan 2016 03:57:18 -0000

Hi Dan, dear co-chair :) 

Much appreciate the comments. 

I will revise it based on your feedback!

Thanks!
Shida

> On Jan 20, 2016, at 7:54 AM, Romascanu, Dan (Dan) <dromasca@avaya.com> wrote:
> 
> Hi Shida,
> 
> Here are a few comments: 
> 
> - to avoid extra processing and dispatching time we should send the liaison statement to the WebRTC WG rather than the whole W3C
> - use https://datatracker.ietf.org/doc/draft-ietf-xrblock-rtcweb-rtcp-xr-metrics/ as a better reference to the I-D 
> - point to the WG mail list for comments (so that they do not feel obliged to respond with a formal liaison) e.g. s/ Any comments are welcome/Comments from the W3C WebRTC WG participants are welcome, they can be provided directly to the WG xrblock@ietf.org mail list/
> 
> Regards,
> 
> Dan
> 
> 
>> -----Original Message-----
>> From: xrblock [mailto:xrblock-bounces@ietf.org] On Behalf Of Shida
>> Schubert
>> Sent: Wednesday, January 20, 2016 6:33 AM
>> To: xrblock
>> Subject: [xrblock] Liaison Statement to W3C for rtcweb-rtcp-xr-metrics
>> 
>> 
>> All;
>> 
>> Below is a draft for liaison statement to W3C for draft-ietf-xrblock-rtcweb-
>> rtcp-xr-metrics.
>> 
>> Welcoming comments…
>> 
>> *****
>> 
>> W3C,
>> 
>> 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.
>> 
>> http://tools.ietf.org/wg/xrblock/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 are welcome.
>> 
>> S. Schubert
>> Co-chair, XRBLOCK Workgroup
>> 
>