Re: [rmcat] Generic RTCP feedback message AGAIN

"Xiaoqing Zhu (xiaoqzhu)" <xiaoqzhu@cisco.com> Tue, 24 November 2015 03:31 UTC

Return-Path: <xiaoqzhu@cisco.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 380F21B3B43 for <rmcat@ietfa.amsl.com>; Mon, 23 Nov 2015 19:31:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.085
X-Spam-Level:
X-Spam-Status: No, score=-15.085 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 ah7Wm3p2rO1K for <rmcat@ietfa.amsl.com>; Mon, 23 Nov 2015 19:30:59 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 052371B3B44 for <rmcat@ietf.org>; Mon, 23 Nov 2015 19:30:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16982; q=dns/txt; s=iport; t=1448335858; x=1449545458; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=jaVBHc76yI6VOJusc4yQ6f0wwfsFHTY91Gv0PU5NSXw=; b=lz/S+669AD/jphiEajkcRq7jwG5cC/aY/CNNUsa6jYjoGK616xuRt5/p 1pCGQvDUvD3GZDQwk7bbK11tkljp4ElWndAJYrlSEbeqZX9ztbfwPxeeV ZGGfI6lI2Daf3CDiog1U4BHNNXF/+6eSCv7H8wtSFhyBh07t7PMQi5UiR 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D9AQDX2FNW/4ENJK1egm5NgUIGvQaCGgENgWWGDwKBPjgUAQEBAQEBAYEKhDQBAQEEeQwEAgEIEQMBAQEoBzIUCQgBAQQBDQWILr8BAQEBAQEBAQEBAQEBAQEBAQEBAQEBGIZUhH6EKhEBPxaEKAWNV4UUg2UBiBWFG4FbhECSPoNxAR8BAUKEBHIBg2AJFwQfgQcBAQE
X-IronPort-AV: E=Sophos; i="5.20,338,1444694400"; d="scan'208,217"; a="52449975"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 24 Nov 2015 03:30:57 +0000
Received: from XCH-ALN-017.cisco.com (xch-aln-017.cisco.com [173.36.7.27]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id tAO3UvEZ014387 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 24 Nov 2015 03:30:57 GMT
Received: from xch-rcd-016.cisco.com (173.37.102.26) by XCH-ALN-017.cisco.com (173.36.7.27) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 23 Nov 2015 21:30:56 -0600
Received: from xch-rcd-016.cisco.com ([173.37.102.26]) by XCH-RCD-016.cisco.com ([173.37.102.26]) with mapi id 15.00.1104.000; Mon, 23 Nov 2015 21:30:56 -0600
From: "Xiaoqing Zhu (xiaoqzhu)" <xiaoqzhu@cisco.com>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, Stefan Holmer <stefan@webrtc.org>, "rmcat@ietf.org" <rmcat@ietf.org>
Thread-Topic: [rmcat] Generic RTCP feedback message AGAIN
Thread-Index: AdEgQQ56skfo130IRESj4fMkgjcn4gDrUFoAAIIQDQAAHH1fgA==
Date: Tue, 24 Nov 2015 03:30:56 +0000
Message-ID: <D27933DC.2BE34%xiaoqzhu@cisco.com>
References: <09b97044300b550586ac59b692ebbe50@mail.gmail.com> <CAEdus3LyX1oz9o0CHjw5DFVh1M+S62w1-L_-LWdXcaesGeYF4g@mail.gmail.com> <46ba1363508e82072dd0504d60a330d6@mail.gmail.com>
In-Reply-To: <46ba1363508e82072dd0504d60a330d6@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.5.8.151023
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.89.2.130]
Content-Type: multipart/alternative; boundary="_000_D27933DC2BE34xiaoqzhuciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rmcat/5wyHhXxin_RvBrh66Gcp24fEiqc>
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: Tue, 24 Nov 2015 03:31:03 -0000

Hi Karen,

I'd like to be part of this effort too.  However, instead of jumping directly to the effort of trying with a common feedback message design, some preliminary work is needed.

For me the first two steps needed are exactly as you described: a) to clearly describe feedback mechanism used in the current CC implementation; and b) to perform some analysis on the required feedback interval and message content (what, when, how often).

With a good understanding of the above, we can then decide whether it's feasible to shift some of the receiver-based processing to the sender side - and, if so, how.

Best,
Xiaoqing


From: rmcat <rmcat-bounces@ietf.org<mailto:rmcat-bounces@ietf.org>> on behalf of Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com<mailto:karen.nielsen@tieto.com>>
Date: Monday, November 23, 2015 at 1:55 AM
To: Stefan Holmer <stefan@webrtc.org<mailto:stefan@webrtc.org>>, "rmcat@ietf.org<mailto:rmcat@ietf.org>" <rmcat@ietf.org<mailto:rmcat@ietf.org>>
Cc: Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch<mailto:mirja.kuehlewind@tik.ee.ethz.ch>>
Subject: Re: [rmcat] Generic RTCP feedback message AGAIN

Thanks a lot Stefan !!

Others who want to share opinions on this and/or wants to be part of this work.
Please repond ! :)

BR, Karen

From: Stefan Holmer [mailto:stefan@webrtc.org<mailto:stefan@webrtc.org>]
Sent: 20. november 2015 18:51
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com<mailto:karen.nielsen@tieto.com>>; rmcat@ietf.org<mailto:rmcat@ietf.org>
Cc: Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch<mailto: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<mailto: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<mailto:karen.nielsen@tieto.com>]
> Sent: 3. november 2015 01:29
> To: 'rmcat@ietf.org<mailto:rmcat@ietf.org>' <rmcat@ietf.org<mailto: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
>
>
>
>
>
>