Re: [AVT] Fwd: Retransmission and fast channel change with usage ofRTP/RTCP
"Jose Rey" <Jose.Rey@eu.panasonic.com> Tue, 25 March 2008 15:58 UTC
Return-Path: <avt-bounces@ietf.org>
X-Original-To: ietfarch-avt-archive@core3.amsl.com
Delivered-To: ietfarch-avt-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D63623A6F20; Tue, 25 Mar 2008 08:58:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.662
X-Spam-Level:
X-Spam-Status: No, score=-99.662 tagged_above=-999 required=5 tests=[AWL=0.775, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wJaz1HfvS+Fh; Tue, 25 Mar 2008 08:58:35 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B3A43A6D5E; Tue, 25 Mar 2008 08:58:35 -0700 (PDT)
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E8763A6E52 for <avt@core3.amsl.com>; Tue, 25 Mar 2008 08:58:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F88rlwdcwIW0 for <avt@core3.amsl.com>; Tue, 25 Mar 2008 08:58:34 -0700 (PDT)
Received: from cluster-e.mailcontrol.com (cluster-e.mailcontrol.com [217.79.216.190]) by core3.amsl.com (Postfix) with ESMTP id C9BEF3A6D5E for <avt@ietf.org>; Tue, 25 Mar 2008 08:58:33 -0700 (PDT)
Received: from rly26e.srv.mailcontrol.com (localhost.localdomain [127.0.0.1]) by rly26e.srv.mailcontrol.com (MailControl) with ESMTP id m2PFtpDk000312 for <avt@ietf.org>; Tue, 25 Mar 2008 15:55:58 GMT
Received: from submission.mailcontrol.com (submission.mailcontrol.com [86.111.216.190]) by rly26e.srv.mailcontrol.com (MailControl) id m2PFsurJ030017 for avt@ietf.org; Tue, 25 Mar 2008 15:54:56 GMT
Received: from eundsmtpout02.pan.eu ([168.87.60.204]) by rly26e-eth0.srv.mailcontrol.com (envelope-sender Jose.Rey@eu.panasonic.com) (MIMEDefang) with ESMTP id m2PFsClc028617; Tue, 25 Mar 2008 15:54:53 +0000 (GMT)
Received: from eundadmi02.pan.eu ([10.109.33.23]) by eundsmtpout02.pan.eu (Lotus Domino Release 7.0.2) with ESMTP id 2008032516540566-302416 ; Tue, 25 Mar 2008 16:54:05 +0100
Received: from VPN-MRelay-02.PRDCG.Panasonic.de ([10.100.176.57]) by eundadmi02.pan.eu (Lotus Domino Release 7.0.3) with ESMTP id 2008032516540372-1113998 ; Tue, 25 Mar 2008 16:54:03 +0100
Received: from localhost ([127.0.0.1]) by VPN-MRelay-02.PRDCG.Panasonic.de; Tue, 25 Mar 2008 16:56:42 +0100
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
In-Reply-To: <50365D40-4B93-4B00-A68D-10BF08468D6D@csperkins.org>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [AVT] Fwd: Retransmission and fast channel change with usage ofRTP/RTCP
Thread-Index: AciNzwDTE/PLQzmlTUaVtQe6eUFrZAAigGMA
References: <70765B7ABD04E845863F69CAC91A5ADB01B0DAA4@Xms1.etsihq.org> <12919642-CFC2-492C-9FC0-E1381B30CBFA@csperkins.org> <1FEB9B9F2EC38343955D02B2AE86AACB7656DF@lan-ex-02.panasonic.de> <50365D40-4B93-4B00-A68D-10BF08468D6D@csperkins.org>
To: Colin Perkins <csp@csperkins.org>
Message-ID: <1FEB9B9F2EC38343955D02B2AE86AACB7FD805@lan-ex-02.panasonic.de>
Date: Tue, 25 Mar 2008 16:53:46 +0100
From: Jose Rey <Jose.Rey@eu.panasonic.com>
X-MIMETrack: Itemize by SMTP Server on EUNDADMI02/EUR/Matsushita(Release 7.0.3|September 26, 2007) at 25.03.2008 16:54:04, Serialize by Router on EUNDADMI02/EUR/Matsushita(Release 7.0.3|September 26, 2007) at 25.03.2008 16:54:06, Serialize complete at 25.03.2008 16:54:06, Itemize by SMTP Server on EUNDSMTPOUT02/EUR/PANEXTOUT(Release 7.0.2|September 26, 2006) at 03/25/2008 04:54:05 PM, Serialize by Router on EUNDSMTPOUT02/EUR/PANEXTOUT(Release 7.0.2|September 26, 2006) at 03/25/2008 04:54:47 PM, Serialize complete at 03/25/2008 04:54:47 PM
Content-class: urn:content-classes:message
X-Scanned-By: MailControl A-08-00-04 (www.mailcontrol.com) on 10.69.1.136
Cc: VAN CAENEGEM Tom <Tom.Van_Caenegem@alcatel-lucent.be>, IETF AVT WG <avt@ietf.org>, Jeff Goldberg <jgoldber@cisco.com>
Subject: Re: [AVT] Fwd: Retransmission and fast channel change with usage ofRTP/RTCP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
Colin, thanks for your feedback. Inline... [...] > > > Now, since the RTP client at the retransmission proxy > cannot send its > > NACK in the media SSM group, it is proposed to send these in the > > *repair* SSM through its Distribution Source, i.e. the > retransmission > > server, either as RFC-4585-NACKs or in summarized RSI form. > However, > > by doing this, we are mixing the SSRC spaces of two different (but > > associated) sessions. Also the retransmission client > doesn't know what > > to do with this feedback as it would just think the NACK is from > > another *repair* client. > > You probably want to exchange RTCP information, so that all > the devices see the full SSRC space, making this one RTP session. We definitely want to avoid forwarding RTCP information from every single user either in either 'reflection' or 'summarized' mode into the repair session. That is, in part, the reasoning behind the out-of-band definition of who is who in the 'session', as below. It can be a lot of information, which is not really necessary for running IPTV. Is this exchange a prerequisite for forming a valid 'session'? I mean, RTCP receiver bandwidth and session group size can be communicated via SRB messages and RTCP for repair clients is probably going to be 'off', anyway. > > > A proposed solution for indicating the repair client what > to do with > > this forwarded NACK would be to use an additional SDP attribute > > listing the SSRC of the RTP client (we would indicate the > SSRCs of the > > retransmission proxy and feedback target as well). The > repair clients > > would then know, by looking at the SSRCs that it is a > forwarded NACK > > from the media SSM and that they must forward it to the > media client > > for NACK damping. The appropriate semantics would probably > have to be > > writen down in an I-D. > > Explicit SDP signalling of the different roles, addresses, > and SSRC values used would seem to be a good thing. It might > also be possible to include role hints in-band in RTCP > packets, although we'd need to think through the implications of that. I think the first option is the preferred one. What would be the advantages of the second? > > > Now, that's one scenario. Another one, though less common, is where > > losses happen dowstream of the retransmission proxy, where > it cannot > > detect them. We are still thinking about a solution for that. > > You mean correlated loss downstream of the retransmission proxy? Yes. For that, we are planning on distributing a polling mask, much like in PGM: a group of selected users has the 'privilege' to report in advance during a period when noone else is allowed to do it. The proxy then infers whether it is affecting a lot or just a few users (mcast or unicast retransmission). Cheers, José Panasonic R&D Center Germany GmbH 63225 Langen, Hessen, Germany Reg: AG Offenbach (Hessen) HRB 33974 Managing Director: Thomas Micke _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www.ietf.org/mailman/listinfo/avt
- [AVT] Fwd: Retransmission and fast channel change… Colin Perkins
- Re: [AVT] Fwd: Retransmission and fast channel ch… Randell Jesup
- Re: [AVT] Fwd: Retransmission and fast channel ch… Jose Rey
- Re: [AVT] Fwd: Retransmission and fast channel ch… Colin Perkins
- Re: [AVT] Fwd: Retransmission and fast channel ch… Jose Rey
- Re: [AVT] Fwd: Retransmission and fast channel ch… Colin Perkins
- [AVT] Some comments to subsection 8.1.1 in draft-… Ye-Kui.Wang
- Re: [AVT] Some comments to subsection 8.1.1 in dr… Colin Perkins
- Re: [AVT] Some comments to subsection 8.1.1 in dr… Ye-Kui.Wang
- Re: [AVT] Some comments to subsection 8.1.1 indra… Even, Roni
- Re: [AVT] Some comments to subsection 8.1.1 indra… Ye-Kui.Wang
- Re: [AVT] Some comments to subsection 8.1.1 indra… Colin Perkins
- Re: [AVT] Some comments to subsection 8.1.1 indra… Ye-Kui.Wang
- Re: [AVT] Some comments to subsection 8.1.1 indra… Randell Jesup
- Re: [AVT] Some comments to subsection 8.1.1 in dr… Ye-Kui.Wang