[xrblock] 答复: ops-dir review of draft-ietf-xrblock-rtcp-xr-loss-conceal-10
Qin Wu <bill.wu@huawei.com> Thu, 27 March 2014 02:07 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 1B1801A0047 for <xrblock@ietfa.amsl.com>; Wed, 26 Mar 2014 19:07:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.74
X-Spam-Level: *
X-Spam-Status: No, score=1.74 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, 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 vMngRwOaXl2d for <xrblock@ietfa.amsl.com>; Wed, 26 Mar 2014 19:07:55 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 653FB1A0040 for <xrblock@ietf.org>; Wed, 26 Mar 2014 19:07:54 -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 BEZ24394; Thu, 27 Mar 2014 02:07:51 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 27 Mar 2014 02:07:24 +0000
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 27 Mar 2014 02:07:50 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.85]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.03.0158.001; Thu, 27 Mar 2014 10:07:43 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Kevin Gross <kevin.gross@avanw.com>
Thread-Topic: [xrblock] ops-dir review of draft-ietf-xrblock-rtcp-xr-loss-conceal-10
Thread-Index: Ac9EP1GAEfXLX+wdRQexAZEQCXhwhgCxe69QABY6fYAAG1/mkAAVgbcgAB3axBAABpr/gAAqXIPw
Date: Thu, 27 Mar 2014 02:07:42 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA8450CA25@nkgeml501-mbs.china.huawei.com>
References: <B8F9A780D330094D99AF023C5877DABA8450C35A@nkgeml501-mbs.china.huawei.com> <CALw1_Q14VH_Zw3yjUxEU6VdpLEDz9mHSpiT4Q60x+MHWRCUTfQ@mail.gmail.com>
In-Reply-To: <CALw1_Q14VH_Zw3yjUxEU6VdpLEDz9mHSpiT4Q60x+MHWRCUTfQ@mail.gmail.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: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA8450CA25nkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/xrblock/cFe-uScXZTPDCRgLEnd8mnxf2yk
Cc: "csp@csperkins.org" <csp@csperkins.org>, "xrblock@ietf.org" <xrblock@ietf.org>
Subject: [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: Thu, 27 Mar 2014 02:07:58 -0000
Hi, Kevin: If we use 50ms frame loss per second as default SCS threshold value, that means we are using millisecond as the unit of SCS Threshold. If we use numeric format 0:8, that means we are using percentage of packets as the unit of SCS Threshold, Numeric format 0:8 can represent an unsigned number in the range 0.0 to 0.99609375 with a granularity of 0.0039. Therefore using numeric format can represent larger range that using milliseconds as unit. It looks to me rounding 0.05078125 into 0.05 or 5% is not a issue, since numeric format allows rounding. 5% can be easily transformed into 50ms frame loss per second. Regards! -Qin 发件人: Kevin Gross [mailto:kevin.gross@avanw.com] 发送时间: 2014年3月26日 21:24 收件人: Qin Wu 抄送: xrblock@ietf.org; csp@csperkins.org 主题: Re: [xrblock] ops-dir review of draft-ietf-xrblock-rtcp-xr-loss-conceal-10 Seems like 0:8 as it appears to be used here can support a range 0.0 to 25.5%. 5% would be exactly represented as 50 or 0x32. Kevin Gross - AVA Networks On Tue, Mar 25, 2014 at 8:44 PM, Qin Wu <bill.wu@huawei.com<mailto:bill.wu@huawei.com>> wrote: 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 _______________________________________________ xrblock mailing list xrblock@ietf.org<mailto:xrblock@ietf.org> https://www.ietf.org/mailman/listinfo/xrblock