[xrblock] FW: [rtcweb] RTP Usage: RTCP XR metrics

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Mon, 18 February 2013 14:10 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id DC30421F8971; Mon, 18 Feb 2013 06:10:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.415
X-Spam-Status: No, score=-103.415 tagged_above=-999 required=5 tests=[AWL=0.184, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 1PMKaWAVKoDv; Mon, 18 Feb 2013 06:10:28 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com []) by ietfa.amsl.com (Postfix) with ESMTP id 3033D21F8958; Mon, 18 Feb 2013 06:10:17 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="4.84,541,1355115600"; d="scan'208";a="344094165"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([]) by de307622-de-outbound.net.avaya.com with ESMTP; 18 Feb 2013 09:12:33 -0500
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([]) by co300216-co-erhwest-out.avaya.com with ESMTP; 18 Feb 2013 09:08:26 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([]) with mapi id 14.02.0328.009; Mon, 18 Feb 2013 09:10:38 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "xrblock@ietf.org" <xrblock@ietf.org>, "pm-dir@ietf.org" <pm-dir@ietf.org>
Thread-Topic: [rtcweb] RTP Usage: RTCP XR metrics
Thread-Index: AQHODeFroiEq9I65BEqhdI/HyMgtSJh/p0dQ
Date: Mon, 18 Feb 2013 14:10:38 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA08CFD5@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [xrblock] FW: [rtcweb] RTP Usage: RTCP XR metrics
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 18 Feb 2013 14:10:30 -0000

The XRBLOCK WG and the PM-Directorate should be aware about this discussion taking place in the RTCWEB WG. 



-----Original Message-----
From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of Magnus Westerlund
Sent: Monday, February 18, 2013 4:08 PM
To: rtcweb@ietf.org
Cc: Colin Perkins
Subject: [rtcweb] RTP Usage: RTCP XR metrics


In Section 8 of
https://datatracker.ietf.org/doc/draft-ietf-rtcweb-rtp-usage/ there is an open issue regarding RTCP XR.

The question is if any RTCP XR metrics should be mandated or recommended to be implemented in WebRTC end-points?

So far there has been some lukewarm interest in metrics, but no clear proposals on what to include.

As an author I like to either get some discussion going or be able to remove this open issue. So people, either make a proposal for what to include or we will remove the TBD and consider the question dealt with.
Please note that there do exist signalling support for negotiating RTCP XR metrics to use in a particular session.

Submit any proposal no later than the 17th of March.


Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVM
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com

rtcweb mailing list