Re: [xrblock] Proposed change to summary discard draft to address discard type issue
Qin Wu <bill.wu@huawei.com> Fri, 21 September 2012 07:38 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 ADED921F8692 for <xrblock@ietfa.amsl.com>; Fri, 21 Sep 2012 00:38:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.133
X-Spam-Level:
X-Spam-Status: No, score=-4.133 tagged_above=-999 required=5 tests=[AWL=-1.587, BAYES_00=-2.599, MANGLED_TOOL=2.3, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pP1Z2URieIpf for <xrblock@ietfa.amsl.com>; Fri, 21 Sep 2012 00:38:12 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5F93D21F8686 for <xrblock@ietf.org>; Fri, 21 Sep 2012 00:38:11 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AJW57196; Fri, 21 Sep 2012 07:38:07 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 21 Sep 2012 08:37:20 +0100
Received: from SZXEML418-HUB.china.huawei.com (10.82.67.157) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 21 Sep 2012 08:37:47 +0100
Received: from w53375 (10.138.41.149) by szxeml418-hub.china.huawei.com (10.82.67.157) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 21 Sep 2012 15:36:36 +0800
Message-ID: <7F72B132A3234A76827932D2E3361A1B@china.huawei.com>
From: Qin Wu <bill.wu@huawei.com>
To: "Huangyihong (Rachel)" <rachel.huang@huawei.com>, Glen Zorn <glenzorn@gmail.com>
References: <51E6A56BD6A85142B9D172C87FC3ABBB4438C7ED@szxeml539-mbx.china.huawei.com><505BE0A2.4040109@gmail.com><51E6A56BD6A85142B9D172C87FC3ABBB4438C8CA@szxeml539-mbx.china.huawei.com><505C0895.3050902@gmail.com> <51E6A56BD6A85142B9D172C87FC3ABBB4438C8EF@szxeml539-mbx.china.huawei.com>
Date: Fri, 21 Sep 2012 15:36:34 +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
Cc: xrblock <xrblock@ietf.org>
Subject: Re: [xrblock] Proposed change to summary discard draft to address discard type issue
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: Fri, 21 Sep 2012 07:38:12 -0000
Hi, ----- Original Message ----- From: "Huangyihong (Rachel)" <rachel.huang@huawei.com> To: "Glen Zorn" <glenzorn@gmail.com> Cc: "xrblock" <xrblock@ietf.org> Sent: Friday, September 21, 2012 2:48 PM Subject: Re: [xrblock] Proposed change to summary discard draft to address discard type issue > > > Best Regards! > Rachel > > > -----Original Message----- > From: Glen Zorn [mailto:glenzorn@gmail.com] > Sent: Friday, September 21, 2012 2:26 PM > To: Huangyihong (Rachel) > Cc: Glen Zorn; xrblock > Subject: Re: [xrblock] Proposed change to summary discard draft to address discard type issue > > On 09/21/2012 12:55 PM, Huangyihong (Rachel) wrote: > > ... > >> > > > > In section 3.2.2, the description of Gap Discard Rate field, the > > third paragraph. > > > > OLD TEXT: > > > > " > > > > where "number of packets discarded" is obtained from the RTCP XR > > > > Discard Block [DISCARD] and Packets Expected is calculated as the > > > > difference between "extended last sequence number" and "extended > > > > first sequence number" (Interval or Cumulative) provided in the > > > > Measurement Information block [MEASIDENT]. > > > > " > > > > NEW TEXT: > > > > " > > > > where "number of packets discarded" is filled with number of packets > > due to both > > > > early and late to be played outwhich is obtained from the RTCP XR > > > > Discard Block [DISCARD], and Packets Expected is calculated > > > > as the difference between "extended last sequence number" and > > "extended > > > > first sequence number" (Interval or Cumulative) provided in the > > > > Measurement Information block [MEASIDENT]. > > > > " > > > > > > I would rewrite this as > > > > "where "number of packets discarded" is filled with the number of > > packets discarded due to both early and late arrivalwhich is obtained > > from the RTCP XRDiscard Block [DISCARD], and Packets Expected is > > calculatedas the difference between "extended last sequence number" > > and "extendedfirst sequence number" (Interval or Cumulative) provided > > in The Measurement Information block [MEASIDENT]." > > > > But even so, it would imply that two instances of the RTCP XR Discard > > Block are required, since a single Discard block can only report > > discards due to either early or late arrival, not both. Is that your > > intent? If so, then I would suggest making it explicit; if not, the > > maybe just leave the text as it is. > > > > [Rachel]: I am okay with your proposed change. Also one instance is > > sufficient since Discard draft supports reporting discards due to > > both. > > Yes but the statement that the '"number of packets discarded" is filled > with the number of > packets discarded due to both early and late arrival which is obtained > from the RTCP XR Discard Block" is only true if a) the "Discard Type" > field in the Discard block is set to 11 or b) two instances of the > Discard block are present, one with the DT field set to 10 & the other > with the DT field set to 01. Do you think that that should be mentioned? > > [Rachel]: I got your point. How about changing the text to : > " > where "number of packets discarded" is filled with the number of packets discarded > due to both early and late arrival (e.g. the discard type field in the Discard block is > set to 11) [Qin]: say "e.g." is not correct, it is better to rephrase as (i.e.,Discard Type (DT) field set to 11 in the Discard block) >which is obtained from the RTCP XR Discard Block [DISCARD], and Packets > Expected is calculated as the difference between "extended last sequence number" > and "extended first sequence number" (Interval or Cumulative) provided in The > Measurement Information block [MEASIDENT]. > > " > ... > > _______________________________________________ > xrblock mailing list > xrblock@ietf.org > https://www.ietf.org/mailman/listinfo/xrblock >
- [xrblock] Proposed change to summary discard draf… Huangyihong (Rachel)
- Re: [xrblock] Proposed change to summary discard … Qin Wu
- Re: [xrblock] Proposed change to summary discard … Glen Zorn
- Re: [xrblock] Proposed change to summary discard … Huangyihong (Rachel)
- Re: [xrblock] Proposed change to summary discard … Glen Zorn
- Re: [xrblock] Proposed change to summary discard … Huangyihong (Rachel)
- Re: [xrblock] Proposed change to summary discard … Qin Wu
- Re: [xrblock] Proposed change to summary discard … Glen Zorn
- Re: [xrblock] Proposed change to summary discard … Qin Wu