IETF Logo Mail Archive

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

Qin Wu <bill.wu@huawei.com> Mon, 23 December 2013 09:41 UTC

Return-Path: <bill.wu@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 251C41AC82A for <xrblock@ietfa.amsl.com>; Mon, 23 Dec 2013 01:41:29 -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 Oc2iORVQpLnd for <xrblock@ietfa.amsl.com>; Mon, 23 Dec 2013 01:41:27 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id CB2161AC7EE for <xrblock@ietf.org>; Mon, 23 Dec 2013 01:41:26 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AZH18609; Mon, 23 Dec 2013 09:41:22 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 23 Dec 2013 09:40:24 +0000
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 23 Dec 2013 09:41:05 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.56]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.03.0158.001; Mon, 23 Dec 2013 17:41:00 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: Mail regarding draft-jayaprabhu-xrblock-rtcp-xr-viewership
Thread-Index: Ac770GiHx4KX33anRZuHLk7X6T77gQD8kryQ
Date: Mon, 23 Dec 2013 09:41:00 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA43C6E4F7@nkgeml501-mbs.china.huawei.com>
References: <B97EEE46B1D7E04C961B2F0A94201D920ACC10F1@xmb-aln-x14.cisco.com>
In-Reply-To: <B97EEE46B1D7E04C961B2F0A94201D920ACC10F1@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.149]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA43C6E4F7nkgeml501mbschi_"
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: Mon, 23 Dec 2013 09:41:29 -0000

Hi,
I am wondering how this draft is related to SIPREC scenarios? Why need to distinguish watched time and recorded time?
Is the metrics defined in this draft terminal related metrics or transport metrics?
Is the metrics defined in this draft measured at the terminal or at the middlebox In the network?
It is not clear to me how to use the metrics defined in this draft in the IPTV deployment?

Regards!
-Qin

From: xrblock [mailto:xrblock-bounces@ietf.org] On Behalf Of Jayaprabhu Nadarajan -X (janadara - HCL TECHNOLOGIES LIMITED at Cisco)
Sent: Wednesday, December 18, 2013 5:07 PM
To: xrblock@ietf.org
Subject: [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

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