IETF Logo Mail Archive

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

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 18 December 2013 09:21 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 8ABAC1AE339 for <xrblock@ietfa.amsl.com>; Wed, 18 Dec 2013 01:21:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level:
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538] 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 69AFeAIb98s8 for <xrblock@ietfa.amsl.com>; Wed, 18 Dec 2013 01:21:53 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 3D21D1ADFCD for <xrblock@ietf.org>; Wed, 18 Dec 2013 01:21:53 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhsMAJVosVKHCzI1/2dsb2JhbABZgkYjIThVo1uVB4EUFnSCJQEBAQEDEhtcAgEIDQQEAQELHQcyFAkIAQEEARIIARmHYgEMpiijOxeOOgcBAR43AYIudYETBJ8CiyiDK4FoCRci
X-IronPort-AV: E=Sophos; i="4.95,506,1384318800"; d="scan'208,217"; a="41780642"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 18 Dec 2013 04:21:51 -0500
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 18 Dec 2013 04:10:56 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.03.0158.001; Wed, 18 Dec 2013 10:21:49 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Jayaprabhu Nadarajan -X (janadara - HCL TECHNOLOGIES LIMITED at Cisco)" <janadara@cisco.com>, "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: Mail regarding draft-jayaprabhu-xrblock-rtcp-xr-viewership
Thread-Index: Ac770GiHx4KX33anRZuHLk7X6T77gQAAXZwg
Date: Wed, 18 Dec 2013 09:21:48 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA129F2C74@AZ-FFEXMB04.global.avaya.com>
References: <B97EEE46B1D7E04C961B2F0A94201D920ACC10F1@xmb-aln-x14.cisco.com>
In-Reply-To: <B97EEE46B1D7E04C961B2F0A94201D920ACC10F1@xmb-aln-x14.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.46]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA129F2C74AZFFEXMB04globa_"
MIME-Version: 1.0
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: Wed, 18 Dec 2013 09:21:55 -0000

Hi,

Specifically the WG participants are asked to provide answers to the following questions:


1.       Does the current I-D contain enough information to understand the scope?

2.       Is this work within the charter of the XRBLOCK WG?

3.       Is this work useful?

4.       Are there any major technical flaws or other kind of problems (like IPR issues, similar work in other SDOs, etc.) that would prevent adoption?

5.       Do you support adoption of this work as WG item?

6.       Are you interested in editing/reviewing/implementing this document?

Thanks and Regards,

Dan


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