Re: [AVTCORE] Comments on draft-ietf-avtcore-feedback-supression-rtp-06.txt

Roni Even <Even.roni@huawei.com> Tue, 13 September 2011 14:23 UTC

Return-Path: <Even.roni@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 88ACC21F8AE6 for <avt@ietfa.amsl.com>; Tue, 13 Sep 2011 07:23:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 WYmzW9Qwjeio for <avt@ietfa.amsl.com>; Tue, 13 Sep 2011 07:23:22 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 07DB521F8AB0 for <avt@ietf.org>; Tue, 13 Sep 2011 07:23:22 -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 <0LRG00FQDTDKNC@szxga05-in.huawei.com> for avt@ietf.org; Tue, 13 Sep 2011 22:24:56 +0800 (CST)
Received: from 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 <0LRG00K6HTDJ6G@szxga05-in.huawei.com> for avt@ietf.org; Tue, 13 Sep 2011 22:24:56 +0800 (CST)
Received: from windows8d787f9 ([222.94.199.235]) by szxml12-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LRG00FRCTDI0D@szxml12-in.huawei.com>; Tue, 13 Sep 2011 22:24:55 +0800 (CST)
Date: Tue, 13 Sep 2011 17:23:40 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <EC3FD58E75D43A4F8807FDE0749175461918135D@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
To: "'Van Caenegem, Tom (Tom)'" <tom.van_caenegem@alcatel-lucent.com>, 'Magnus Westerlund' <magnus.westerlund@ericsson.com>, 'Qin Wu' <bill.wu@huawei.com>
Message-id: <007501cc7220$bbf7c940$33e75bc0$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset="us-ascii"
Content-language: en-us
Content-transfer-encoding: 7bit
Thread-index: AcxxWn71b8os3w8jSUWbt27xmcX+nAAw0IowAACYzNA=
References: <20110831070359.24630.22446.idtracker@ietfa.amsl.com> <4E5F9C23.8050702@ericsson.com> <4E69F7AE.3040601@ericsson.com> <8CD73AC40EDC452A80EE42BBF82E7DE8@china.huawei.com> <4E6E1A90.7050805@ericsson.com> <EC3FD58E75D43A4F8807FDE0749175461918135D@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
Cc: avt@ietf.org, draft-ietf-avtcore-feedback-supression-rtp@tools.ietf.org
Subject: Re: [AVTCORE] Comments on draft-ietf-avtcore-feedback-supression-rtp-06.txt
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, 13 Sep 2011 14:23:26 -0000

Hi Tom,
I reviewed this section in the 6.2 and mostly agree with your suggestion.
I also suggested to Qin to look also at the difference when there is
retransmission or not and also if the retransmission is in unicast or
multicast. 

Regards
Roni 

> -----Original Message-----
> From: Van Caenegem, Tom (Tom) [mailto:tom.van_caenegem@alcatel-
> lucent.com]
> Sent: Tuesday, September 13, 2011 5:11 PM
> To: Magnus Westerlund; Qin Wu
> Cc: avt@ietf.org; draft-ietf-avtcore-feedback-supression-
> rtp@tools.ietf.org
> Subject: RE: [AVTCORE] Comments on draft-ietf-avtcore-feedback-
> supression-rtp-06.txt
> 
> Magnus,
> 
> If you want a view of the RAMS' authors, please check:
> http://tools.ietf.org/html/draft-vancaenegem-avtcore-retransmission-
> for-ssm-00
> 
> I did ask Qin to refer to this draft which provides a detailed
> description on how feedback suppression can work for RAMS topology.
> 
> In summary:
> 
> The BRS sends a NACK or TPLR message to the DS, where the SSRC in this
> NACK or TPLR message is the one of the BRS. The DS forwards/reflects
> this message down on the primary SSM. This procedure will allow
> isolated feedback suppression, when RTP receivers only trigger FB
> suppression when recognising the SSRC as belonging to the BRS to which
> they report.
> 
> Tom
> 
> > 4. Section 6.2: "If the BRS impacted by packet loss has been told the
> > actual packet loss, the BRS MAY choose to create new Third Party Loss
> > Report message and send it to the receivers in the downstream link.
> > "
> >
> > I don't understand how the BRS can inject any message into the SSM
> > tree, as the source anchor of the SSM tree is up at the multicast
> > source. Thus a BRS needs to tell the distribution source to send
> > something down stream on its behalf.
> >
> >
> >
> >
> > [Qin]: It is possbile for BRS to tell the distrbution source to send
> > TPLR down on its BRS. My question is Is the BRS similar to
> > Distribution source as an intermediary between multicast source and
> >
> > downstream receivers? Why BRS can not inject in between while
> > Distribution Source can?
> 
> My understanding what that the BRS is in fact not owner of their own
> SSM session, only help nodes that are receiver of the SSM session but
> not DS in it. And having the BRS send something to the DS which is only
> valid for its little part of a large SSM session is strange.
> 
> But RAMS authors view would be appreciated.