Re: [rmcat] Generic RTCP feedback message AGAIN

Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com> Mon, 23 November 2015 07:55 UTC

Return-Path: <karen.nielsen@tieto.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 426881B36F5 for <rmcat@ietfa.amsl.com>; Sun, 22 Nov 2015 23:55:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level:
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WekH56sXx2-R for <rmcat@ietfa.amsl.com>; Sun, 22 Nov 2015 23:55:10 -0800 (PST)
Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E1681B36F6 for <rmcat@ietf.org>; Sun, 22 Nov 2015 23:55:10 -0800 (PST)
Received: by igcto18 with SMTP id to18so50832128igc.0 for <rmcat@ietf.org>; Sun, 22 Nov 2015 23:55:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type; bh=CRBm6gf9lCK2fd0Wxo2X4ppmapepm9TTxmxONjyT+kM=; b=syHQWyaQ8bbIRrqENlIhOhZTX4H6kETIfdJ0bBDYs0iVsgu0+YIzQ6Scbg6SuWyYZV YU7DKi1Km+gzJeGPUthMBFfrdwnCKwLZXFRs2VGS/yYqcO91pJfCPg+3AgqYEn9YM47g L3Fxb8SD0cc34z3poXaqAjcaJcaVuT9kMozmE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=CRBm6gf9lCK2fd0Wxo2X4ppmapepm9TTxmxONjyT+kM=; b=R12FIUVo/3Tf1HVvgCGq9p6v3oOzaBb9yUJnFvdjMl0HNyw6/Wuq+aKLhC9Ep6gVZZ RvtGM4Q30g++T4akjXgH9LE/OiguKJYTrO2RQz2larWl1W33XW8E+FvEX2W+75WunanN PGqxGSo9UE11TKlvbr5CfTajUUcCC538qyd3hMr6dFOHkh9EdHA/g7irxh5FXv3foAwI t+iCqBuLFMhu9N5OvV+eYSk5eTmOmhcIEY6npGZM9J/MjFh5x4VboUV1yuLLXojjY6gt 6N5EfZAZ87CTmwgjZORE1F+GllgMlWvYKDGIR+3VDedwoFARI5lS9xIoRhf23nreR/ZY rjsg==
X-Gm-Message-State: ALoCoQnhdqx3eQoz+euq4KH9d5ft/a8hjjfU0wxftp9zNLnj6DXVWB3FmNndFqrM1TvHNbZXAqzbHWEE+3FlC9X8StkLZNVaKedKsr1Dup/W0pO7iB1eZa4=
X-Received: by 10.50.142.40 with SMTP id rt8mr4661920igb.24.1448265309690; Sun, 22 Nov 2015 23:55:09 -0800 (PST)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <09b97044300b550586ac59b692ebbe50@mail.gmail.com> <CAEdus3LyX1oz9o0CHjw5DFVh1M+S62w1-L_-LWdXcaesGeYF4g@mail.gmail.com>
In-Reply-To: <CAEdus3LyX1oz9o0CHjw5DFVh1M+S62w1-L_-LWdXcaesGeYF4g@mail.gmail.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQGegXSHWkVYiE47f5qHra2zPSD0EAI7ySPenvym7kA=
Date: Mon, 23 Nov 2015 08:55:08 +0100
Message-ID: <46ba1363508e82072dd0504d60a330d6@mail.gmail.com>
To: Stefan Holmer <stefan@webrtc.org>, rmcat@ietf.org
Content-Type: multipart/alternative; boundary="001a11c30c6c533ab70525308b28"
X-DomainID: tieto.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/-K_XWhmewfVZDYBQdwX0_rT8F5g>
Cc: Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch>
Subject: Re: [rmcat] Generic RTCP feedback message AGAIN
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Nov 2015 07:55:13 -0000

Thanks a lot Stefan !!



Others who want to share opinions on this and/or wants to be part of this
work.

Please repond ! J



BR, Karen



*From:* Stefan Holmer [mailto:stefan@webrtc.org]
*Sent:* 20. november 2015 18:51
*To:* Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>;
rmcat@ietf.org
*Cc:* Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch>
*Subject:* Re: [rmcat] Generic RTCP feedback message AGAIN





On Mon, Nov 16, 2015 at 4:51 AM Karen Elisabeth Egede Nielsen <
karen.nielsen@tieto.com> wrote:

HI,

At the 2nd RMCAT session we proposed the following:

* Give usage of a common feedback message for sender side only RMCAT CC's
_a try_.

With the following proposed way forward

*1* Requirements to be considered in each CC algs draft
*2* Analyse required feedback rates and timing as well as content
   and point to existing remedies and/or what new needed

At the RMCAT session agreement on this not established.
Only *1* was agreed upon.  Whereas *2* was left for future potentially.

NOW given the recent discussion on the list it looks (to me) as
if we in the wg have a more mature view on this task.
Note the wg already has a milestone to which this work
can be associated. I.e., "Submit RTCP extension requirements
for use with congestion control algorithms to AVTCORE (if needed)".
Please respond to this email and give your view:

Shall we NOW give the usage of a common feedback message
for a sender side only CC a try ?
[Yes I want to be part of this - OR -  No I don't want to be part of this]



Yes - I want to be part of this. :)




Assuming Yes. How shall we collect the requirements ?
Possible options (I can think of):

* have new updates of the CCs alg candidates (incl. SBD, coupled CC as
applicable)
   come soon with a good specification of the requested
* have the same information instead go into a (potentially temporary?)
    Appendix of draft-perkins-rmcat-rtp-cc-feedback-01.txt or new draft ?
* others - email ?



I vote for either updating the current CC algorithm candidate drafts with
this information, or doing it over e-mail as a first step while we wait for
the updated drafts.




Assuming Yes. Where shall the outcome of the work be specified ?
draft-perkins-rmcat-rtp-cc-feedback-01.txt or new draft



No strong opinion about this.





BR,
Karen, on behalf of the chairs

> -----Original Message-----
> From: Karen Elisabeth Egede Nielsen [mailto:karen.nielsen@tieto.com]
> Sent: 3. november 2015 01:29
> To: 'rmcat@ietf.org' <rmcat@ietf.org>
> Subject: Generic RTCP feedback message
>
> Hi,
>
> Following Stefan’s presentation in the RMCAT session yesterday there was
> agreement at the mike that we in the RMCAT wg should try to give the
usage
> of a generic common feedback message a try.
>
> It seems a prerequisite for this that the receiver (sender of the
feedback
> message) is (in principle) unaware of the particular CC algorithm that
the
> sender is using, but will generate a *to be defined* set of  feedback
> information in a *to be defined* form that will fulfil the requirements
of all
> RMCAT CC algorithms.
>
> In order to start on this task we hereby solicit for the people working
with CC
> algorithms to respond to this email with information on the requirements
> that they have to such a generic feedback mechanism.
>
> In addition _or alternatively_   please (all) provide feedback on
> * how you think we should proceed with this task, e.g., start a new
draft to
> collect this information (eventually to proceed in an ART wg)
> * concerns with this approach
>
> We will try to collect the information provided and have a short follow
up in
> Fridays RMCAT meeting.
>
> BR, Mirja/Karen
>
>
>
>
>
>