IETF Logo Mail Archive

Re: [xrblock] TS Decodability Metric Reporting as WG item?

"Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl> Mon, 25 June 2012 09:46 UTC

Return-Path: <ray.vanbrandenburg@tno.nl>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 166CB21F84E6 for <xrblock@ietfa.amsl.com>; Mon, 25 Jun 2012 02:46:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.775
X-Spam-Level: *
X-Spam-Status: No, score=1.775 tagged_above=-999 required=5 tests=[AWL=2.279, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ik7G45uyinmH for <xrblock@ietfa.amsl.com>; Mon, 25 Jun 2012 02:46:12 -0700 (PDT)
Received: from fromintouta.tno.nl (fromintouta.tno.nl [134.221.1.26]) by ietfa.amsl.com (Postfix) with ESMTP id 66DB321F8475 for <xrblock@ietf.org>; Mon, 25 Jun 2012 02:46:12 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.77,471,1336341600"; d="scan'208";a="71133352"
Received: from unknown (HELO mail.tno.nl) ([134.221.225.220]) by mailhost1a.tno.nl with ESMTP; 25 Jun 2012 11:46:08 +0200
Received: from EXC-MBX03.tsn.tno.nl ([169.254.3.152]) by EXC-CASHUB01.tsn.tno.nl ([134.221.225.220]) with mapi id 14.02.0298.004; Mon, 25 Jun 2012 11:46:08 +0200
From: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Thread-Topic: [xrblock] TS Decodability Metric Reporting as WG item?
Thread-Index: Ac1HxhQcvNDuu4uJSeWU/UooNFrHzABna1YAAlTbTSA=
Date: Mon, 25 Jun 2012 09:46:07 +0000
Message-ID: <FCC100FC8D6B034CB88CD8173B2DA1581C61CA88@EXC-MBX03.tsn.tno.nl>
References: <EDC652A26FB23C4EB6384A4584434A0407B53738@307622ANEX5.global.avaya.com> <17E076CF-DFFC-4160-8EED-2A01D806C5C7@csperkins.org>
In-Reply-To: <17E076CF-DFFC-4160-8EED-2A01D806C5C7@csperkins.org>
Accept-Language: en-US, nl-NL
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [134.221.225.191]
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Cc: xrblock <xrblock@ietf.org>
Subject: Re: [xrblock] TS Decodability Metric Reporting as WG item?
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, 25 Jun 2012 09:46:17 -0000

I support this work. Up until now I wasn't aware of this document, but now that I am, I am able to provide reviews.

Ray

-----Original Message-----
From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On Behalf Of Colin Perkins
Sent: woensdag 13 juni 2012 16:55
To: Romascanu, Dan (Dan)
Cc: xrblock
Subject: Re: [xrblock] TS Decodability Metric Reporting as WG item?

Dan,

On 11 Jun 2012, at 13:33, Romascanu, Dan (Dan) wrote:
> Shida and me are reviewing items that may meet the consensus threshold 
> to be included in the next round of chartered deliverables for the 
> XRBLOCK WG  (pending on AD and IESG approval).
> 
> We would like to solicit expressions of interest for including the 
> RTCP XR Report Block for Transport Stream (TS) Decodability Metric 
> reporting on the list of variable. We have an Internet-Draft 
> http://www.ietf.org/id/draft-huang-xrblock-rtcp-xr-decodability-03.txt
> with four co-authors. Who else is interested in working on this item?
> Implementing? Reviewing? 


I've read this draft, and will review future versions. I'm not an MPEG expert, and so can't comment on the MPEG aspects, but it appears to use RTCP XR in a reasonable way. I'd support it being adopted as a working group draft, provided there's nothing wrong with the metrics from the MPEG viewpoint.

--
Colin Perkins
http://csperkins.org/



_______________________________________________
xrblock mailing list
xrblock@ietf.org
https://www.ietf.org/mailman/listinfo/xrblock
This e-mail and its contents are subject to the DISCLAIMER at http://www.tno.nl/emaildisclaimer

v2.36.0 | Report a Bug | By Email | System Status