Re: [AVTCORE] Comments ondraft-ietf-avtcore-feedback-supression-rtp-07
Qin Wu <bill.wu@huawei.com> Tue, 11 October 2011 07:21 UTC
Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 683B321F8C8A for <avt@ietfa.amsl.com>; Tue, 11 Oct 2011 00:21:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.551
X-Spam-Level:
X-Spam-Status: No, score=-4.551 tagged_above=-999 required=5 tests=[AWL=1.163, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 ehQcsC48lOEg for <avt@ietfa.amsl.com>; Tue, 11 Oct 2011 00:21:28 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 1504421F8C83 for <avt@ietf.org>; Tue, 11 Oct 2011 00:21:28 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSW0082T4EBB2@szxga05-in.huawei.com> for avt@ietf.org; Tue, 11 Oct 2011 15:20:36 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSW00K0O4EA65@szxga05-in.huawei.com> for avt@ietf.org; Tue, 11 Oct 2011 15:20:35 +0800 (CST)
Received: from szxeml206-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AEJ05364; Tue, 11 Oct 2011 15:19:54 +0800
Received: from SZXEML403-HUB.china.huawei.com (10.82.67.35) by szxeml206-edg.china.huawei.com (172.24.2.58) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 11 Oct 2011 15:19:51 +0800
Received: from w53375q (10.138.41.130) by szxeml403-hub.china.huawei.com (10.82.67.35) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 11 Oct 2011 15:19:48 +0800
Date: Tue, 11 Oct 2011 15:19:48 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, IETF AVTCore WG <avt@ietf.org>, draft-ietf-avtcore-feedback-supression-rtp@tools.ietf.org
Message-id: <46B94027CF7149FD9238297DB6FA4320@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: multipart/alternative; boundary="Boundary_(ID_b191HPidGGJFkjL00E6sNw)"
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <4E8D76C1.5080508@ericsson.com> <BAC40485A1FA456CA771192D4F750C77@china.huawei.com>
Subject: Re: [AVTCORE] Comments ondraft-ietf-avtcore-feedback-supression-rtp-07
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Oct 2011 07:21:29 -0000
Hi,Magnus: As regarding if there is better solution, I have some corrections and additional thoughts. I think If the media source is the repair server, the receiver should set timer to T1=max(the RTT from media source to middlebox sending TPLR, 1/2 of RTT from middlebox to receiver) when the receiver receives first TPLR. When the receiver receive addtional TPLR within T1, the receiver should reset the timer to the RTT from media source to middlebox sending TPLR. If the middlebox is the repair server, the receiver should set the timer to T2=1/2 of RTT from middlebox to receiver when the receiver receives first TPLR. When the receiver receive addtional TPLR within T2, the receiver should reset the timer to the T2. Regards! -Qin ----- Original Message ----- From: Qin Wu To: Magnus Westerlund ; IETF AVTCore WG ; draft-ietf-avtcore-feedback-supression-rtp@tools.ietf.org Sent: Tuesday, October 11, 2011 9:40 AM Subject: Re: [AVTCORE] Comments ondraft-ietf-avtcore-feedback-supression-rtp-07 Hi, Magnus, Thank for your valuable review, please see my replies belows. Regards! -Qin ----- Original Message ----- From: "Magnus Westerlund" <magnus.westerlund@ericsson.com> To: "IETF AVTCore WG" <avt@ietf.org>; <draft-ietf-avtcore-feedback-supression-rtp@tools.ietf.org> Sent: Thursday, October 06, 2011 5:37 PM Subject: [AVTCORE] Comments on draft-ietf-avtcore-feedback-supression-rtp-07 Thanks for updating the draft, I have reviewed the updated draft and have the following comments on the updated version. Some issues are follow up on previous version or on the actual changes. 2. Section 3. "The timer value shall be based on the observed round-trip time. A receiver should compute an estimate of the round-trip time (RTT) to the sender of TPLR from RTCP report round-trip time if available, or its reception time of the reflected RTCP FB message (e.g.,NACK), or any other means." We hade the discussion before but now that you clarified which RTT to be used, I think it is worth having a discussion if that RTT is the right one. So you suggest that the RTT between the sender of the TPLR and the receiver of the message is the most appropriate to use when suppressing the message. I am not certain that is the case. Lets consider the use cases. In the case of an intermediary in a distribution tree sending the TPLR and at the same time sending a NACK upstream. Then the time until the retransmission reaches the suppressed receiver is the time from the sending of the NACK up to the retransmitting entity and all the way down past the TPLR sender to the suppressed receiver. The receiver may not have a true RTT to the original media sender as that source appears to live at the TPLR sender, not further upstream. Yes, the sender of the TPLR and the receiver might at least have mutual knowledge of each other, thus the TPLR sender is able to determine the lowest RTT in the set of receviers thus determining how often to repeat it to cover additional time requried for the upstream part of the request. But I do note that these times aren't matching what appear to be the delays in the systems. Can we find a better solution?
- [AVTCORE] Comments on draft-ietf-avtcore-feedback… Magnus Westerlund
- Re: [AVTCORE] Comments on draft-ietf-avtcore-feed… Qin Wu
- Re: [AVTCORE] Comments ondraft-ietf-avtcore-feedb… Qin Wu
- Re: [AVTCORE] Comments on draft-ietf-avtcore-feed… Magnus Westerlund
- Re: [AVTCORE] Comments on draft-ietf-avtcore-feed… Qin Wu
- Re: [AVTCORE] Comments on draft-ietf-avtcore-feed… Roni Even
- Re: [AVTCORE] Comments on draft-ietf-avtcore-feed… Magnus Westerlund
- Re: [AVTCORE] Comments on draft-ietf-avtcore-feed… Magnus Westerlund
- Re: [AVTCORE] Comments on draft-ietf-avtcore-feed… Qin Wu
- Re: [AVTCORE] Comments on draft-ietf-avtcore-feed… Roni even
- Re: [AVTCORE] Comments on draft-ietf-avtcore-feed… Magnus Westerlund