IETF Logo Mail Archive

Re: [xrblock] Mail regarding draft-jayaprabhu-xrblock-rtcp-xr-viewership

"Huangyihong (Rachel)" <rachel.huang@huawei.com> Thu, 16 January 2014 02:57 UTC

Return-Path: <rachel.huang@huawei.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 DE3771AE4A7 for <xrblock@ietfa.amsl.com>; Wed, 15 Jan 2014 18:57:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.738
X-Spam-Level:
X-Spam-Status: No, score=-4.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-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 nEPv3PL7Zt9K for <xrblock@ietfa.amsl.com>; Wed, 15 Jan 2014 18:57:06 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 684AB1AE4A6 for <xrblock@ietf.org>; Wed, 15 Jan 2014 18:57:05 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BCN56382; Thu, 16 Jan 2014 02:56:52 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 16 Jan 2014 02:55:56 +0000
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 16 Jan 2014 02:56:50 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.56]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.03.0158.001; Thu, 16 Jan 2014 10:56:46 +0800
From: "Huangyihong (Rachel)" <rachel.huang@huawei.com>
To: "Jayaprabhu Nadarajan -X (janadara - HCL TECHNOLOGIES LIMITED at Cisco)" <janadara@cisco.com>, "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: [xrblock] Mail regarding draft-jayaprabhu-xrblock-rtcp-xr-viewership
Thread-Index: Ac770GiHx4KX33anRZuHLk7X6T77gQWGpmfgAB3vcPA=
Date: Thu, 16 Jan 2014 02:56:44 +0000
Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBB4591B6A4@nkgeml501-mbs.china.huawei.com>
References: <B97EEE46B1D7E04C961B2F0A94201D920ACC424C@xmb-aln-x14.cisco.com>
In-Reply-To: <B97EEE46B1D7E04C961B2F0A94201D920ACC424C@xmb-aln-x14.cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.116]
Content-Type: multipart/alternative; boundary="_000_51E6A56BD6A85142B9D172C87FC3ABBB4591B6A4nkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [xrblock] Mail regarding draft-jayaprabhu-xrblock-rtcp-xr-viewership
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: <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: Thu, 16 Jan 2014 02:57:08 -0000

Hi Jp,

Like RTCP SR/RR, RTCP XR is designed to covey the detailed QoS/QoE information for RTP, which could reflect the problems in RTP transmission. So the metrics defined in RTCP XR are usually closely related to RTP stream, and are standard and universal metrics. In this draft, the viewship metrics seem not so closely related to RTP streams, rather, they are produced by actions of users. IMHO, this kind of information could be conveyed by other ways, such as signaling. So why RTCP XR?

Best regards,
Rachel

From: xrblock [mailto:xrblock-bounces@ietf.org] On Behalf Of Jayaprabhu Nadarajan -X (janadara - HCL TECHNOLOGIES LIMITED at Cisco)
Sent: Wednesday, January 15, 2014 8:18 PM
To: xrblock@ietf.org
Subject: Re: [xrblock] Mail regarding draft-jayaprabhu-xrblock-rtcp-xr-viewership

Dear All,

I have submitted an internet draft, draft-jayaprabhu-xrblock-rtcp-xr-viewership-00.txt

URL:             http://www.ietf.org/internet-drafts/draft-jayaprabhu-xrblock-rtcp-xr-viewership-00.txt


Is there any comments on the contents of the draft  or any queries related to the scope ?

Regards,
Jp

From: Jayaprabhu Nadarajan -X (janadara - HCL TECHNOLOGIES LIMITED at Cisco)
Sent: Wednesday, December 18, 2013 2:36 PM
To: 'xrblock@ietf.org'
Subject: Mail regarding draft-jayaprabhu-xrblock-rtcp-xr-viewership

Dear All,

I have submitted an internet draft, draft-jayaprabhu-xrblock-rtcp-xr-viewership-00.txt

URL:             http://www.ietf.org/internet-drafts/draft-jayaprabhu-xrblock-rtcp-xr-viewership-00.txt

Could you please provide your comments/opinions regarding this I-D. Following is the brief introduction about this block

This document defines a new report block type within the framework of RTP Control Protocol (RTCP) Extended Reports (XRs) that allows the reporting of the usage pattern of a receiver in a RTP session.  As the number of IPTV deployments continue to increase, it becomes necessary for the operator to collect various information on the streams that are being delivered to the user. This document defines a new report block type for the Extended Report (XR) packet type of the  RTP Control Protocol (RTCP) which allows IPTV clients to report to a server on the usage pattern of the stream that is being delivered to them.

Thanks

Regards,
Jayaprabhu

v2.23.0 | Report a Bug | By Email