Re: [rmcat] Request for comment/input for draft-zhu-rmcat-framework-00

Ingemar Johansson S <ingemar.s.johansson@ericsson.com> Thu, 26 January 2017 14:34 UTC

Return-Path: <ingemar.s.johansson@ericsson.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58BD5129622 for <rmcat@ietfa.amsl.com>; Thu, 26 Jan 2017 06:34:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level:
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.onmicrosoft.com
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 setJxWL93HTU for <rmcat@ietfa.amsl.com>; Thu, 26 Jan 2017 06:34:03 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD5B912961A for <rmcat@ietf.org>; Thu, 26 Jan 2017 06:34:02 -0800 (PST)
X-AuditID: c1b4fb30-13a0498000007085-db-588a08d802a2
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.183.90]) by (Symantec Mail Security) with SMTP id DB.FF.28805.8D80A885; Thu, 26 Jan 2017 15:34:00 +0100 (CET)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.90) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 26 Jan 2017 15:33:07 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=dk8aLFjycNEm2PhfJZ8kmkuH6vtqYm2YIlndcudpU6I=; b=KM9hHQZh1iuQcCAhXC5bBrGgKagAA58Lfg95oNMrJj6Dkb3CeCvOZ2DcyDYkJWGhnjAYmG6JR8RhVAgI3tzt2phzRAuMdv3FaKGcQQNanJAnpCPATWcNfXn3B3i+piHPSSINA8wQZBe0hZm8/ISzFWNDvjh71Pok9szOMSK/j5M=
Received: from DB4PR07MB348.eurprd07.prod.outlook.com (10.141.234.148) by DB4PR07MB348.eurprd07.prod.outlook.com (10.141.234.148) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.860.6; Thu, 26 Jan 2017 14:33:06 +0000
Received: from DB4PR07MB348.eurprd07.prod.outlook.com ([10.141.234.148]) by DB4PR07MB348.eurprd07.prod.outlook.com ([10.141.234.148]) with mapi id 15.01.0860.023; Thu, 26 Jan 2017 14:33:05 +0000
From: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
To: "Xiaoqing Zhu (xiaoqzhu)" <xiaoqzhu@cisco.com>, Roni Even <roni.even@huawei.com>, "rmcat@ietf.org" <rmcat@ietf.org>
Thread-Topic: [rmcat] Request for comment/input for draft-zhu-rmcat-framework-00
Thread-Index: AQHSdnyvszFI+GoaFUW+Evn566rid6FIseuwgACz64CAAWyWkA==
Date: Thu, 26 Jan 2017 14:33:05 +0000
Message-ID: <DB4PR07MB3489E1E1197801801E38C4EC2770@DB4PR07MB348.eurprd07.prod.outlook.com>
References: <1483980831999.36398@cisco.com>, <6E58094ECC8D8344914996DAD28F1CCD76E311@DGGEMM506-MBX.china.huawei.com> <1485232670117.71585@cisco.com>, <DB4PR07MB3486DFAEC41800B9851A480C2740@DB4PR07MB348.eurprd07.prod.outlook.com> <1485362287761.65279@cisco.com>
In-Reply-To: <1485362287761.65279@cisco.com>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ingemar.s.johansson@ericsson.com;
x-originating-ip: [192.176.1.92]
x-ms-office365-filtering-correlation-id: 645c9bee-3ab0-4b68-6fa8-08d445f83df6
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:DB4PR07MB348;
x-microsoft-exchange-diagnostics: 1; DB4PR07MB348; 7:sg0RyTeaMJQGDtx9QUzAyo1Pj5FtOu7DrOyu47IZkDR+5RB4tFdU/jggW3a417q2ivw+JZ9i1qEuFLwMwZQ1qkuUeh6SIQXhTybtk2fRhYP4PRYtZoegDRFSE0H++tTQJbVvNRil17pZWs6HHNE4/NzB5RESf1cB2DROGYXV9fgD7El8a1g6eDnWP78vn6VUMiPjpOrzfKIWHrxkC2an34b1fryWRr4J+8csoCthmM9lpmxJMZ4ajCyH5NH1nJ/uYiNtV+o1WJ2CKquuYl8PXzfkUGprNZUxlPd79XOuEKNb26xDwmUnkODnwcwZEa10FX/XUDc3QVMQpLbLJGBH06XfigxExTOaNTGazSqKRCZZZ+BF8vqXg4YsQpFb4ZVN4rG6uQSHrA8TSaJ0G8HEftEIpNxoQM43AxWsZeM2FocW2omzHTZBLf2utWWmXQvDmzHViOcURQWLFN6s+dXHEw==
x-microsoft-antispam-prvs: <DB4PR07MB34853B577F0B43D4DD78AEAC2770@DB4PR07MB348.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(37575265505322)(50582790962513)(95692535739014)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6041248)(20161123555025)(20161123562025)(20161123564025)(20161123560025)(6072148); SRVR:DB4PR07MB348; BCL:0; PCL:0; RULEID:; SRVR:DB4PR07MB348;
x-forefront-prvs: 019919A9E4
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(7916002)(39450400003)(53754006)(377454003)(199003)(189002)(55674003)(4326007)(33656002)(74316002)(38730400001)(7736002)(7906003)(54896002)(9686003)(55016002)(99286003)(101416001)(6506006)(54356999)(76176999)(606005)(25786008)(6436002)(50986999)(2906002)(6306002)(77096006)(122556002)(106356001)(93886004)(106116001)(105586002)(81156014)(81166006)(9326002)(2501003)(53936002)(8936002)(7696004)(3280700002)(229853002)(236005)(5660300001)(6116002)(102836003)(790700001)(97736004)(5001770100001)(3846002)(2950100002)(2900100001)(92566002)(230783001)(189998001)(3660700001)(66066001)(3900700001)(68736007)(86362001); DIR:OUT; SFP:1101; SCL:1; SRVR:DB4PR07MB348; H:DB4PR07MB348.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DB4PR07MB3489E1E1197801801E38C4EC2770DB4PR07MB348eurprd_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Jan 2017 14:33:05.8286 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB4PR07MB348
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA01Sa0hTYRjmO5ed43L0tdS9rYIaBSmVFlaLLLKijIrSbsPAWnqw5dxsxyKj YoiXdsQyKWJmZbguGumyqLW0y7RyZChdoNlFc9GF7KIkUcvK7TPo3/M+z/N+z/u+fDytbGTV vMGUK1hMeqNGJmfsumup057xki6uvHKe9oLvq0zbf6+d0Q4cviXTfiw4Sy1kkiq9h+ikI4FL bFJByyc2yeH4Qa1hUuUJGYLRsEuwxC7YIt/m8j6gcpx2ane1p4mxIms5JaEwHnA89PY8pINY iesQeF8pJCQfwq0IfgbymWDB4FIapConRZSjFBys7mNJcQ9Bb8sXLtgvwwlQ4/mOgjgC58Hj hs+hd2k8CW53t8kkxPOjcTI8L48ilhRof5/PEbwIinua2SBm8GTo8PlCvAKnwrG3Tppk2Si4 3nGVC74ThqdCWZ066EF4PHR9f8WQKBV0vjk1vBoGR2M7TXAkfPD/Zok/Hfp9pSzhJ8CvRz2h 0QCvAsdgNKFXwpeC87JgLOASBr7dPc0QjwFq24dbt8MNa9mw5wAFzfWdHBHGgb+hiSXCcRkc lS4z5L4CnLtYGLrPaKyGl09sqAxFV/w3N8FmaPQPchWh/UeB1/6GqRjKpnE01LtjiWUiHCl5 zRE8BQorT3D/81WIq0WRoiBuzc6cOXO6YDGki6LZNN0k5DagoT9150ogzoU+vEv0IMwjTbgi p+mATsnqd4l52R4EPK2JUCxmJZ1SkaHP2yNYzJstO42C6EFjeUajUsyu6dqoxJn6XCFLEHIE yz+V4sPUVjS+pLglMm0Dv2lB8kmVWXJdWD4XluWPqd1vz35ha21YPGDN2lvmtK6p06zdx3dQ I9d9Dqw/c9NWej8K8W73kj5D344J81fH94efrpkbm7j0a5Y8gW395Xs7W7l/xGXlillF3e45 GoPGFePWtYmfEv9wqmq/sXdt5o3mrqdSSlqRhhG36WfE0BZR/xddNKwsTwMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/lbG5ZRzO5yuwTJxEBY9h6QH462A>
Cc: Varun Singh <varun@callstats.io>
Subject: Re: [rmcat] Request for comment/input for draft-zhu-rmcat-framework-00
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 26 Jan 2017 14:34:05 -0000

Hi

The resource management concept with SCReAM assumes that all the outgoing RTP streams use the same congestion controller (= the same UDP port).
The RTP streams are registered with the SCReAM controller, besides a min and max target bitrate, also a scheduling priority in the range ]0.0 1.0] is given as a parameter.
The shared state in this case is the SCReAM network congestion controller state, i.e. the congestion window.

/Ingemar


From: Xiaoqing Zhu (xiaoqzhu) [mailto:xiaoqzhu@cisco.com]
Sent: den 25 januari 2017 17:38
To: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>; Roni Even <roni.even@huawei.com>; rmcat@ietf.org
Cc: Varun Singh <varun@callstats.io>
Subject: Re: [rmcat] Request for comment/input for draft-zhu-rmcat-framework-00


Hi Ingemar,



Thanks for providing this example.  Will refer to it in the next version of the draft.  Just wondering, if you can help to identify what "shared states" are in the case of SCReAM?  Or does the concept of "shared state" apply at all?



Best,

Xiaoqing



________________________________
From: Ingemar Johansson S <ingemar.s.johansson@ericsson.com<mailto:ingemar.s.johansson@ericsson.com>>
Sent: Wednesday, January 25, 2017 12:00 AM
To: Xiaoqing Zhu (xiaoqzhu); Roni Even; rmcat@ietf.org<mailto:rmcat@ietf.org>
Cc: Varun Singh
Subject: RE: [rmcat] Request for comment/input for draft-zhu-rmcat-framework-00

Hi
Another example of the resource management is the configurable flow prioritization embedded in the packet scheduling in SCReAM. See https://tools.ietf.org/html/draft-ietf-rmcat-scream-cc-07#page-32

Regards
/Ingemar

From: Xiaoqing Zhu (xiaoqzhu) [mailto:xiaoqzhu@cisco.com]
Sent: den 24 januari 2017 05:38
To: Roni Even <roni.even@huawei.com<mailto:roni.even@huawei.com>>; rmcat@ietf.org<mailto:rmcat@ietf.org>
Cc: Varun Singh <varun@callstats.io<mailto:varun@callstats.io>>
Subject: Re: [rmcat] Request for comment/input for draft-zhu-rmcat-framework-00


Hi Roni,



Thanks for reading the draft and providing your input.   You are right that to a resource management algorithm is needed to decide which flow get how much portion of the aggregate BW calculated by the network congestion controller.  Currently, my intention is for the "Rate Controller" to host that algorithm.  Will add some text to clarify on this part.



An example of the shared states would be the set of "flow state information" mentioned in the coupled-cc draft (https://tools.ietf.org/html/draft-ietf-rmcat-coupled-cc-05), such as priority, current flow rate, etc.  I'll add a reference to the coupled-cc draft to help make this concept more concrete.



Best,

Xiaoqing



________________________________
From: Roni Even <roni.even@huawei.com<mailto:roni.even@huawei.com>>
Sent: Thursday, January 19, 2017 3:57 AM
To: Xiaoqing Zhu (xiaoqzhu); rmcat@ietf.org<mailto:rmcat@ietf.org>
Cc: Varun Singh
Subject: RE: Request for comment/input for draft-zhu-rmcat-framework-00

Hi,

I read the document and have a question about the multiple streams case.  Figure 2 adds the shared states module.  The text say
“The Rate Controller divides up the aggregate estimated bandwidth (1) from the Network Congestion Controller amongst sub-streams based on their relative priority levels, Shared States, as well as current occupancy level of the Transmission Queue.”
I am not sure what the shared state is but definitely in order to divide the bandwidth there is a need to know the required bw for each of the video streams (as a number or information about the encoding parameters like codec, resolution,…) this is a resource management algorithm that is needed here.

Roni Even

From: rmcat [mailto:rmcat-bounces@ietf.org] On Behalf Of Xiaoqing Zhu (xiaoqzhu)
Sent: יום ב 09 ינואר 2017 18:54
To: rmcat@ietf.org<mailto:rmcat@ietf.org>
Cc: Varun Singh
Subject: [rmcat] Request for comment/input for draft-zhu-rmcat-framework-00


Hi everyone,



This draft has just expired and Zahed and I do plan to revive it soon. Currently we have on our "edit-to-address" list only some questions raised by Varun from IETF-96 (Berlin) regarding RTP taxonomy.  Varun has graciously agreed to provide some specific comments as follow-up, so we are waiting for those (thanks ahead Varun).



In the meantime, I would like to poll the mailing list to collect further review comments on this draft.  Please let us know what other issues you'd like us to address.



https://tools.ietf.org/html/draft-zhu-rmcat-framework-00​



Thanks,

Xiaoqing