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

"Van Caenegem, Tom (Tom)" <tom.van_caenegem@alcatel-lucent.com> Tue, 13 September 2011 14:10 UTC

Return-Path: <tom.van_caenegem@alcatel-lucent.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 B728221F8B08 for <avt@ietfa.amsl.com>; Tue, 13 Sep 2011 07:10:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.175
X-Spam-Level:
X-Spam-Status: No, score=-6.175 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 YXTtM8ZY2kjB for <avt@ietfa.amsl.com>; Tue, 13 Sep 2011 07:10:10 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by ietfa.amsl.com (Postfix) with ESMTP id E59B721F8B0C for <avt@ietf.org>; Tue, 13 Sep 2011 07:10:09 -0700 (PDT)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail5.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p8DEB7ZG027195 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 13 Sep 2011 16:11:12 +0200
Received: from FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com ([135.120.45.41]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Tue, 13 Sep 2011 16:11:07 +0200
From: "Van Caenegem, Tom (Tom)" <tom.van_caenegem@alcatel-lucent.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, Qin Wu <bill.wu@huawei.com>
Date: Tue, 13 Sep 2011 16:11:06 +0200
Thread-Topic: [AVTCORE] Comments on draft-ietf-avtcore-feedback-supression-rtp-06.txt
Thread-Index: AcxxWn71b8os3w8jSUWbt27xmcX+nAAw0Iow
Message-ID: <EC3FD58E75D43A4F8807FDE0749175461918135D@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
References: <20110831070359.24630.22446.idtracker@ietfa.amsl.com> <4E5F9C23.8050702@ericsson.com> <4E69F7AE.3040601@ericsson.com> <8CD73AC40EDC452A80EE42BBF82E7DE8@china.huawei.com> <4E6E1A90.7050805@ericsson.com>
In-Reply-To: <4E6E1A90.7050805@ericsson.com>
Accept-Language: nl-NL, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: nl-NL, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.13
Cc: "avt@ietf.org" <avt@ietf.org>, "draft-ietf-avtcore-feedback-supression-rtp@tools.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:10:10 -0000

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.