Re: [AVTCORE] Commentson draft-vancaenegem-avtcore-fb-supp-and-retransm-00

Roni Even <Even.roni@huawei.com> Sun, 19 June 2011 20:38 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 91B8911E80E0 for <avt@ietfa.amsl.com>; Sun, 19 Jun 2011 13:38:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level:
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[AWL=2.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 n0GOLOIC1ntj for <avt@ietfa.amsl.com>; Sun, 19 Jun 2011 13:38:38 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 6C34811E8077 for <avt@ietf.org>; Sun, 19 Jun 2011 13:38:38 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LN200MWA1CDG6@szxga04-in.huawei.com> for avt@ietf.org; Mon, 20 Jun 2011 04:38:37 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LN200ARW1CD3K@szxga04-in.huawei.com> for avt@ietf.org; Mon, 20 Jun 2011 04:38:37 +0800 (CST)
Received: from windows8d787f9 (bzq-79-181-47-132.red.bezeqint.net [79.181.47.132]) by szxml12-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LN200E2H1C7I6@szxml12-in.huawei.com>; Mon, 20 Jun 2011 04:38:37 +0800 (CST)
Date: Sun, 19 Jun 2011 23:36:38 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <04CAD96D4C5A3D48B1919248A8FE0D540F4408AF@xmb-sjc-215.amer.cisco.com>
To: "'Ali C. Begen (abegen)'" <abegen@cisco.com>, 'IETF AVTCore WG' <avt@ietf.org>, 'VAN CAENEGEM Tom' <Tom.Van_Caenegem@alcatel-lucent.com>
Message-id: <004801cc2ec0$9ac3e630$d04bb290$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset="iso-8859-1"
Content-language: en-us
Content-transfer-encoding: quoted-printable
Thread-index: AcvroApIveZeR4mXT1CxBcCiD4iXBxC5bN+gAAl5A5AABTWEAA==
References: <4D8DBEDB.4090406@ericsson.com> <004401cc2e87$523c06b0$f6b41410$%roni@huawei.com> <04CAD96D4C5A3D48B1919248A8FE0D540F4408AF@xmb-sjc-215.amer.cisco.com>
Cc: 'Magnus Westerlund' <magnus.westerlund@ericsson.com>
Subject: Re: [AVTCORE] Commentson draft-vancaenegem-avtcore-fb-supp-and-retransm-00
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: Sun, 19 Jun 2011 20:38:39 -0000

Hi Ali,
Sorry about my email,
I read the retransmission-for-ssm and my comments are on that draft.
Roni

> -----Original Message-----
> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> Sent: Sunday, June 19, 2011 9:07 PM
> To: Roni Even; IETF AVTCore WG; VAN CAENEGEM Tom
> Cc: Magnus Westerlund
> Subject: RE: [AVTCORE] Commentson draft-vancaenegem-avtcore-fb-supp-
> and-retransm-00
> 
> Did you check
> https://datatracker.ietf.org/doc/draft-vancaenegem-avtcore-
> retransmission-for-ssm/
> ? It addresses at least some of the points you made below.
> 
> -acbegen
> 
> > -----Original Message-----
> > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> Roni Even
> > Sent: Sunday, June 19, 2011 6:47 AM
> > To: 'IETF AVTCore WG'; 'VAN CAENEGEM Tom'
> > Cc: 'Magnus Westerlund'
> > Subject: Re: [AVTCORE] Commentson draft-vancaenegem-avtcore-fb-supp-
> and-retransm-00
> >
> > Hi,
> > I have finally found the time to read the document. I agree with
> Magnus that
> > the issue of retransmission in the RAMS architecture where the RS and
> FT are
> > collocated is not specified and it should also be reflected in the
> feedback
> > suppression draft.
> > I think the draft has good text on the analysis of the feedback
> suppression
> > and this should be added to the WG document. Maybe Tom and Qin can
> work on
> > the WG document on this topic.
> > As for the retransmission, I am not sure if this should be as part of
> the
> > suppression draft. If the issue is only for the case where we have
> the FT/RS
> > collocated with unicast feedback as in the RAMS case maybe it can be
> in the
> > RAMS scenario draft. If we are looking at a broader retransmission
> case
> > (that is not well specified in current draft) that includes also the
> > multicast retransmission from the RS or from the DS it may be good to
> > discuss it as part of the WG document.
> >
> > Regards
> > Roni
> >
> >
> >
> > > -----Original Message-----
> > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf
> Of
> > > Magnus Westerlund
> > > Sent: Saturday, March 26, 2011 12:24 PM
> > > To: IETF AVTCore WG; VAN CAENEGEM Tom
> > > Subject: [AVTCORE] Comments on draft-vancaenegem-avtcore-fb-supp-
> and-
> > > retransm-00
> > >
> > > Tom, AVTCORE,
> > >
> > > I have reviewed this draft and have the following comment.
> > >
> > > To me it appears that one big reason for the issues is actually
> that we
> > > haven't specified how RTP retransmission in SSM with unicast
> delivery
> > > is
> > > supposed to work. Because if that was well defined we would likely
> have
> > > concluded that one should not forward NACK request to the DS from a
> FT
> > > for any request it service locally.
> > >
> > > Thus as I raised before in relation to the RAMS work that there
> > > appeared
> > > to be a need for defining this properly, including this aspect. Do
> we
> > > have anyone that is interested in defining this?
> > >
> > > Secondly I think there clearly are some improvements needed of the
> WG
> > > document based on what you comment. One thing is clearly to clarify
> the
> > > WG document on its usages, and then map those usages of suppression
> to
> > > different topologies.
> > >
> > > My personal opinion on how to handle your comments are to include
> your
> > > concerns in the WG document.
> > >
> > > Cheers
> > >
> > > Magnus Westerlund
> > >
> > > -------------------------------------------------------------------
> ---
> > > Multimedia Technologies, Ericsson Research EAB/TVM
> > > -------------------------------------------------------------------
> ---
> > > Ericsson AB                | Phone  +46 10 7148287
> > > Färögatan 6                | Mobile +46 73 0949079
> > > SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> > > -------------------------------------------------------------------
> ---
> > > _______________________________________________
> > > Audio/Video Transport Core Maintenance
> > > avt@ietf.org
> > > https://www.ietf.org/mailman/listinfo/avt
> >
> > _______________________________________________
> > Audio/Video Transport Core Maintenance
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt