Re: [xrblock] Calculation of delay metrics defined in the Delay Block

zhaojing@sttri.com.cn Fri, 28 October 2011 08:25 UTC

Return-Path: <zhaojing@sttri.com.cn>
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 481B721F8AF0 for <xrblock@ietfa.amsl.com>; Fri, 28 Oct 2011 01:25:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.05
X-Spam-Level: ****
X-Spam-Status: No, score=4.05 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_50=0.001, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_NJABL_PROXY=1.643]
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 J9btsokqxHH1 for <xrblock@ietfa.amsl.com>; Fri, 28 Oct 2011 01:25:25 -0700 (PDT)
Received: from corp.21cn.com (corp.forptr.21cn.com [121.14.129.37]) by ietfa.amsl.com (Postfix) with ESMTP id 756E921F8AEE for <xrblock@ietf.org>; Fri, 28 Oct 2011 01:25:25 -0700 (PDT)
Received: from ip?218.2.129.2? (entas8.inner-hermes.com [10.27.101.8]) by corp.21cn.com (HERMES) with ESMTP id 939E6AC0A0 for <xrblock@ietf.org>; Fri, 28 Oct 2011 16:25:23 +0800 (CST)
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_IP: wmail.10.27.101.8.974824256
HMM_SOURCE_TYPE: WEBMAIL
Received: from ip<218.2.129.2> ([218.2.129.2]) by 21CN-ent8(Yuwen filter gate 10.27.101.8) with ESMTP id 1319790323.30708 for xrblock@ietf.org ; Fri Oct 28 16:25:24 2011
0/X-Total-Score: 8:
X-FILTER-SCORE: to=<xrblock@ietf.org>, score=<1319790324BMMVMnMMnnMnljy5FDBVMMBBZBCBBCCBChopS78YZBBY>
Date: Fri, 28 Oct 2011 16:25:23 +0800
From: zhaojing@sttri.com.cn
To: xrblock <xrblock@ietf.org>
Message-ID: <29087808.18541319790323615.JavaMail.root@ent8>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_Part_1932_17650376.1319790323377"
HMM_WEBCLN_IP: 218.2.129.2
X-HERMES-SENDMODE: normal
Subject: Re: [xrblock] Calculation of delay metrics defined in the Delay Block
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, 28 Oct 2011 08:25:26 -0000

Hi, Qin:

Would you like to explain to me how End System Delay is calculated?

Is it based on DLSR or something else? It looks like a internal calculation.

Regards!

-JingZhao

 


Hi,jing:
Please refere to RFC3550.
The round trip time computation method is defined as a example in the figure 2 of RFC3550.
 
Regards!
-Qin
----- Original Message -----
To: mailto:xrblock%20at%20ietf.org" rel="nofollow">xrblock
Sent: Thursday, October 20, 2011 10:07 AM
Subject: [xrblock] Calculation of delay metrics defined in the Delay Block

Hi,
I have read Delay draft avaiable at:
It is not clear to me how each metric is calculated, For example,
it is said Mean Network Round Trip Delay metric is ypically determined
using RTCP SR/RR?
I am not sure I understand the rationale? Who would like to explain a little to me?
Regards!
jing Zhao  
ShangHai Research Institute of China Telecom Corporation Limited.