IETF Logo Mail Archive

[xrblock] Fw: Comments on draft-ietf-xrblock-rtcp-xr-synchronization-00

Qin Wu <bill.wu@huawei.com> Tue, 23 October 2012 02:29 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 A66BC21F847F for <xrblock@ietfa.amsl.com>; Mon, 22 Oct 2012 19:29:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.318
X-Spam-Level:
X-Spam-Status: No, score=-4.318 tagged_above=-999 required=5 tests=[AWL=-0.357, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, 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 efYSOPVYOEFs for <xrblock@ietfa.amsl.com>; Mon, 22 Oct 2012 19:29:53 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 63D9D21F8168 for <xrblock@ietf.org>; Mon, 22 Oct 2012 19:29:52 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ALX39405; Tue, 23 Oct 2012 02:29:51 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 23 Oct 2012 03:29:44 +0100
Received: from SZXEML442-HUB.china.huawei.com (10.82.67.180) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 23 Oct 2012 03:29:50 +0100
Received: from w53375 (10.138.41.149) by szxeml442-hub.china.huawei.com (10.82.67.180) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 23 Oct 2012 10:29:24 +0800
Message-ID: <EF49424A2FD8483C9A2FAA7E6A7FE0C7@china.huawei.com>
From: Qin Wu <bill.wu@huawei.com>
To: xrblock@ietf.org
Date: Tue, 23 Oct 2012 10:29:24 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_053E_01CDB109.458B9510"
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: [xrblock] Fw: Comments on draft-ietf-xrblock-rtcp-xr-synchronization-00
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, 23 Oct 2012 02:29:53 -0000

Hi,Rachel:
Please see comments inline.

Regards!
-Qin
----- Original Message ----- 
From: Huangyihong (Rachel) 
To: xrblock@ietf.org 
Sent: Thursday, October 18, 2012 11:30 AM
Subject: [xrblock] Comments on draft-ietf-xrblock-rtcp-xr-synchronization-00


Hi folks,

 

I have 2 comments for draft-ietf-xrblock-rtcp-xr-synchronization:

 

1.       In RTP flows synchronization offset metric block, only one SSRC set to the SSRC of the reference RTP stream has been specified. IMO,  the SSRC of the reporting stream should be also required. 



[Qin]: Are you saying the synchronization offset is applied to two streams and used to measure the time difference between two stream, so for reporting stream, how to choose the reference stream?



2.       Synchronization offset is a 64-bit unsigned fixed-point number. No indication shows which stream, the reporting stream or the reference stream,  is lag behind. So I propose to split one bit from "Reserved" field to indicate the offset direction.



[Qin]: What do you mean offset direction? Are you saying the value of offset can be either less than zero or greater than zero? However in the current text, the synchronization offset is unsigned value or positive value.

       I am thinking if we can choose one slow stream as reference stream, in that case, the offset value is always a positive value.

 

Best Regards!

Rachel

 



--------------------------------------------------------------------------------


_______________________________________________
xrblock mailing list
xrblock@ietf.org
https://www.ietf.org/mailman/listinfo/xrblock

v2.23.0 | Report a Bug | By Email