IETF Logo Mail Archive

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

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 20 January 2016 15:55 UTC

Return-Path: <dromasca@avaya.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 D072A1A8F42 for <xrblock@ietfa.amsl.com>; Wed, 20 Jan 2016 07:55:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] 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 Yvc8lNG33gth for <xrblock@ietfa.amsl.com>; Wed, 20 Jan 2016 07:54:59 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD8C11A8ABA for <xrblock@ietf.org>; Wed, 20 Jan 2016 07:54:58 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2AHBQBmrZ9W/yYyC4dUChkBAQEBDwEBAQGCXytSbQaIUbJ5gWMkhWsCHIEpOhIBAQEBAQEBgQqENAEBAQEDEhERUQQCAQgNBAQBAQMCBh0DAgICMBQBCAgCBAESCBqHeQENpXGKSY9AAQEBAQEBAQMBAQEBAQEBAQEBARV7hUGEcoQnCwEBHYMBLIERBZcUAYVHgnSHS4cZhUCOVikLMIN6boVpNQF7AQEB
X-IPAS-Result: A2AHBQBmrZ9W/yYyC4dUChkBAQEBDwEBAQGCXytSbQaIUbJ5gWMkhWsCHIEpOhIBAQEBAQEBgQqENAEBAQEDEhERUQQCAQgNBAQBAQMCBh0DAgICMBQBCAgCBAESCBqHeQENpXGKSY9AAQEBAQEBAQMBAQEBAQEBAQEBARV7hUGEcoQnCwEBHYMBLIERBZcUAYVHgnSHS4cZhUCOVikLMIN6boVpNQF7AQEB
X-IronPort-AV: E=Sophos;i="5.22,321,1449550800"; d="scan'208";a="139341817"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by de307622-de-outbound.net.avaya.com with ESMTP; 20 Jan 2016 10:54:55 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC02.global.avaya.com) ([135.64.58.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES256-SHA; 20 Jan 2016 10:54:55 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([135.64.58.12]) with mapi id 14.03.0174.001; Wed, 20 Jan 2016 16:54:53 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Shida Schubert <shida@ntt-at.com>, xrblock <xrblock@ietf.org>
Thread-Topic: [xrblock] Liaison Statement to W3C for rtcweb-rtcp-xr-metrics
Thread-Index: AQHRUzuwK/N99jhBc0itW0uIZl5y+J8EhxOA
Date: Wed, 20 Jan 2016 15:54:53 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA6BEF0A1D@AZ-FFEXMB04.global.avaya.com>
References: <08A91250-8AB4-4B33-8C9A-D8D589653811@ntt-at.com>
In-Reply-To: <08A91250-8AB4-4B33-8C9A-D8D589653811@ntt-at.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.48]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/xrblock/LEso-nWtRulOPrwpuUmHEtTH7Go>
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: Wed, 20 Jan 2016 15:55:01 -0000

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
>

v2.23.0 | Report a Bug | By Email