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

Kevin Gross <kevin.gross@avanw.com> Wed, 26 February 2014 02:39 UTC

Return-Path: <kevin.gross@avanw.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 0C26F1A0304 for <xrblock@ietfa.amsl.com>; Tue, 25 Feb 2014 18:39:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.202
X-Spam-Level: **
X-Spam-Status: No, score=2.202 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_NEUTRAL=0.779] autolearn=no
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 Z_A2bJC6S8Zy for <xrblock@ietfa.amsl.com>; Tue, 25 Feb 2014 18:39:31 -0800 (PST)
Received: from qmta06.emeryville.ca.mail.comcast.net (qmta06.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:56]) by ietfa.amsl.com (Postfix) with ESMTP id 1A3C21A0341 for <xrblock@ietf.org>; Tue, 25 Feb 2014 18:39:30 -0800 (PST)
Received: from omta02.emeryville.ca.mail.comcast.net ([76.96.30.19]) by qmta06.emeryville.ca.mail.comcast.net with comcast id WpFl1n0090QkzPwA6qfW1s; Wed, 26 Feb 2014 02:39:30 +0000
Received: from mail-yh0-f46.google.com ([209.85.213.46]) by omta02.emeryville.ca.mail.comcast.net with comcast id WqdV1n00L10dfBD8NqdWfv; Wed, 26 Feb 2014 02:37:30 +0000
Received: by mail-yh0-f46.google.com with SMTP id v1so316612yhn.33 for <xrblock@ietf.org>; Tue, 25 Feb 2014 18:37:29 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=N9ux+APgihWtUKa1SplLMUFCOheMzl0ujNP+zGMmgi8=; b=P0df3dG9wWj4z5rEG/3Jh0srUSGu3F31cv7OfP66WQQiAymyHiHOll1ADqRWfHxJgn cJZe1hSpcjpetsPl/nxoo0VkyNlsRHvkMIdDsVoadxzDgVLblQCfsglU0ryclxUMjl5H Y4Asg/m7JqnnESEeZHVkmUkU7yvlo8JStyUgaxz1o6q5dAEGiUe7pM0NGwEvs4hjeJqu DGjmmnQi7K1UuYvxALz0+lFwqwHcO08qcsUvjAdMoYVs4ZCPi8wb+gu7J1nXbgsQ2lKs W3P1hr7MZw1PH1w8R/TnCnt9gFFPsQT4kbPloIOWpM/7c6m7HdSp5JLz4yxXoOUZP0W3 L1LA==
MIME-Version: 1.0
X-Received: by 10.236.151.198 with SMTP id b46mr4146620yhk.3.1393382249749; Tue, 25 Feb 2014 18:37:29 -0800 (PST)
Received: by 10.170.216.197 with HTTP; Tue, 25 Feb 2014 18:37:29 -0800 (PST)
In-Reply-To: <51E6A56BD6A85142B9D172C87FC3ABBB4591B6A4@nkgeml501-mbs.china.huawei.com>
References: <B97EEE46B1D7E04C961B2F0A94201D920ACC424C@xmb-aln-x14.cisco.com> <51E6A56BD6A85142B9D172C87FC3ABBB4591B6A4@nkgeml501-mbs.china.huawei.com>
Date: Tue, 25 Feb 2014 19:37:29 -0700
Message-ID: <CALw1_Q003+OHbWUmiMzB=gChaBuaLfNkkDBC1KSRCfcWcSy=bg@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: "Huangyihong (Rachel)" <rachel.huang@huawei.com>
Content-Type: multipart/alternative; boundary="20cf301cc5aa0862bf04f34616ad"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1393382370; bh=N9ux+APgihWtUKa1SplLMUFCOheMzl0ujNP+zGMmgi8=; h=Received:Received:Received:MIME-Version:Received:Date:Message-ID: Subject:From:To:Content-Type; b=CkjoCjTQf1Tw9TU/7SuiodX9gZQ8icpGQruLXUg5WA0sGRmMnkcTrG5mxywnOCz0B Q5qztmiFcZKKJKDljr4KhERngZxkhhXI/cfPMBnmuLRX02u0IXFwaCaJlNBT79Nf9S m5R/PaKJM3Y1rskkFbsZ2mW6UisrwpVk4aPV8L0bdUZJHDoGFU/7taOmlpw5XFCiBT 3qD4KC2KYvEQTbCbw1Kbyjcz4GqzOyQxHa139vvCXIjrnWGFfDrBMo2W+2F67Y96nr jXmzHbCf1F1iHEJLPo5SQRunJaZoLu78TjtGdsY4TUAF/nxHn2dbJHbPJPr/iO/HC5 SNwVhl4yAXxGQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/xrblock/m7Ub9NpWOeSVKGkX-_HVhEA6beg
Cc: "Jayaprabhu Nadarajan -X (janadara - HCL TECHNOLOGIES LIMITED at Cisco)" <janadara@cisco.com>, "xrblock@ietf.org" <xrblock@ietf.org>
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, 26 Feb 2014 02:39:33 -0000

I can see the potential utility of this but I'd like to see it explained in
the introduction. All we have now is "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."

Please add definitions of what it means to be recording and what it means
to be watching. The former is pretty obvious but the latter less so.

A couple technical comments:

Are you sure we need to worry about rollover of these counters? 2^31
seconds is 68 years.

Consider moving the V and R flags into the "rsvd" field so that the "time
watched" and "time recorded" fields can be interpreted as 32-bit numbers
without fuss.


Kevin Gross - AVA Networks


On Wed, Jan 15, 2014 at 7:56 PM, Huangyihong (Rachel) <
rachel.huang@huawei.com> wrote:

>  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
> <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
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock
>
>