IETF Logo Mail Archive

Re: [xrblock] Transport of I.D-xrblock-rtcp-xr-qoe style quality datain IPFIX

Qin Wu <bill.wu@huawei.com> Tue, 17 July 2012 03:32 UTC

Return-Path: <bill.wu@huawei.com>
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 7496211E8073 for <xrblock@ietfa.amsl.com>; Mon, 16 Jul 2012 20:32:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.543
X-Spam-Level:
X-Spam-Status: No, score=-4.543 tagged_above=-999 required=5 tests=[AWL=0.303, BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4]
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 G40LkiTVPpZA for <xrblock@ietfa.amsl.com>; Mon, 16 Jul 2012 20:32:35 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 13B9C11E80AA for <xrblock@ietf.org>; Mon, 16 Jul 2012 20:32:32 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AHU89292; Mon, 16 Jul 2012 23:33:18 -0400 (EDT)
Received: from DFWEML407-HUB.china.huawei.com (10.193.5.132) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 16 Jul 2012 20:30:51 -0700
Received: from SZXEML416-HUB.china.huawei.com (10.82.67.155) by dfweml407-hub.china.huawei.com (10.193.5.132) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 16 Jul 2012 20:30:53 -0700
Received: from w53375 (10.138.41.149) by szxeml416-hub.china.huawei.com (10.82.67.155) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 17 Jul 2012 11:30:44 +0800
Message-ID: <21EDE4323D7E465383A56DE5E1D6C853@china.huawei.com>
From: Qin Wu <bill.wu@huawei.com>
To: Hendrik Scholz <hs@123.org>, xrblock@ietf.org
References: <50040877.8040400@123.org>
Date: Tue, 17 Jul 2012 11:30:44 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Originating-IP: [10.138.41.149]
X-CFilter-Loop: Reflected
Subject: Re: [xrblock] Transport of I.D-xrblock-rtcp-xr-qoe style quality datain IPFIX
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: Tue, 17 Jul 2012 03:32:36 -0000

Hi, Hendrik:
That is an interesting draft you published. Thank for sharing.
I am wondering what the goal of this draft is? Is this draft an part of 
draft-akhter-opsawg-perfmon-ipfix or will be incorporated into draft-akhter-opsawg-perfmon-ipfix?
Would you like to clarify the status of this draft?

Just have a quick look at this draft, I think the 1st reference has been outdated
and should be replaced with I.D-xrblock-rtcp-xr-qoe.

Also it seems you give a range for each RTPMOSClass as follows:

rtpMOSClass 1: MoS value < 3.10
rtpMOSClass 2:  3.10<=MoS value<3.60
rtpMOSClass 3:  3.60<=MoS value<4.03
rtpMOSClass 4:  4.03<=MoS value< 4.34
rtpMOSCalss 5: 4.34<= MoS value<=5

I am wondering what the rationale is for such range allocation. which reference are you based on?

Lastly why should the rtpMoSClass choose 'number of seconds' as unit?

Regards!
-Qin
----- Original Message ----- 
From: "Hendrik Scholz" <hs@123.org>
To: <xrblock@ietf.org>
Sent: Monday, July 16, 2012 8:26 PM
Subject: [xrblock] Transport of I.D-xrblock-rtcp-xr-qoe style quality datain IPFIX


> Hi!
> 
> I've published draft-scholz-ipfix-rtp-audio-quality-00
> which contains Information Elements for IPFIX to transport audio
> quality information.
> The scope is audio only and the multiple channel issue
> which was discussed in Paris is also present in this.
> My intention is to keep the format in sync with the xrblock format
> so that it is easy to transport the existing data in IPFIX or
> even take it from RTCP reports.
> The metric block part is taken care of in
> draft-akhter-opsawg-perfmon-ipfix which will be renamed/updated
> before Vancouver.
> 
> So far this is just informational and I'll dedicate some more
> time to synchronize the content and check for potential pitfalls.
> 
> Just FYI,
>  Hendrik
> 
> -- 
> Hendrik Scholz <hs@123.org>
> 
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock

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