Re: [xrblock] ops-dir review of draft-ietf-xrblock-rtcp-xr-loss-conceal-10

Qin Wu <bill.wu@huawei.com> Wed, 26 March 2014 02:44 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 B47661A008D for <xrblock@ietfa.amsl.com>; Tue, 25 Mar 2014 19:44:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 MR580O1C8twM for <xrblock@ietfa.amsl.com>; Tue, 25 Mar 2014 19:44:54 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id F38D71A006C for <xrblock@ietf.org>; Tue, 25 Mar 2014 19:44:52 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BEY24282; Wed, 26 Mar 2014 02:44:50 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 26 Mar 2014 02:44:25 +0000
Received: from nkgeml409-hub.china.huawei.com (10.98.56.40) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 26 Mar 2014 02:44:48 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.85]) by nkgeml409-hub.china.huawei.com ([10.98.56.40]) with mapi id 14.03.0158.001; Wed, 26 Mar 2014 10:44:41 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: ops-dir review of draft-ietf-xrblock-rtcp-xr-loss-conceal-10
Thread-Index: Ac9EP1GAEfXLX+wdRQexAZEQCXhwhgCxe69QABY6fYAAG1/mkAAVgbcgAB3axBA=
Date: Wed, 26 Mar 2014 02:44:40 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA8450C35A@nkgeml501-mbs.china.huawei.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.115]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/xrblock/vOM9EtKfYN__lEVGMils0MteZrc
Cc: "csp@csperkins.org" <csp@csperkins.org>
Subject: Re: [xrblock] ops-dir review of draft-ietf-xrblock-rtcp-xr-loss-conceal-10
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 Mar 2014 02:44:56 -0000

Hi,
In the OPS-DIR review, our reviewer asked to provide the hex value of the default threshold setting and one rounding issue was brought up.
The related paragraph in the draft is:
"
> >    SCS Threshold: 8 bits
> >
> >       The SCS Threshold is defined as the percentage of packets
> >       corresponding to lost or discarded frames that must occur within a
> >       one second period in order for the second to be classified as a
> >       Severely Concealed Second.  This is expressed in numeric format
> >       0:8 and hence can represent a range of 0.1 to 25.5 percent loss or
> >       discard.
> >
> >       A default threshold of 5% effective frame loss (50ms effective
> >       frame loss ) per second is suggested.
"
The SCS threshold is represented in percentage. When we use numeric format 0:8
to represent the default value of SCS threshold, we only can represent 0.05078125
rather than 0.05 or 5% (which is set as the default value of threshold in the draft).

If we change the default threshold value into 0.05078125 and the hex value of 0.05078125 is 0x0D,
This rounding issue can be resolved. 

Alternatively, we can change unit of SCS threshold back into millisecond, we can precisely represent 5% 
frame loss per second or the default threshold value 0.05. The range of 0.1 to 25.5 percentage can be
represented into the range from 1ms effective frame loss to 255ms effective frame loss.

Regards!
-Qin