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

"Xiaoqing Zhu (xiaoqzhu)" <xiaoqzhu@cisco.com> Thu, 26 January 2017 16:00 UTC

Return-Path: <xiaoqzhu@cisco.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 1F469129525 for <rmcat@ietfa.amsl.com>; Thu, 26 Jan 2017 08:00:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.719
X-Spam-Level:
X-Spam-Status: No, score=-17.719 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 E4l1aGT0jwF1 for <rmcat@ietfa.amsl.com>; Thu, 26 Jan 2017 08:00:55 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15F76129717 for <rmcat@ietf.org>; Thu, 26 Jan 2017 08:00:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=34773; q=dns/txt; s=iport; t=1485446452; x=1486656052; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=/c+NlsUiRF9iSJCKlzU6R6FHpXV/gjuhcRwkH1XoFZ4=; b=W5o/dJjT5ekc6xbHx/18SwRy30ZFKiv0/bTRSap/WDLP7lACEn6pkzXz pbAdNBxIC8tEx4FWMy5We66rPw//O+UuWYwtbYKRkkaaihnP+3AvUdhmh VyIcKD+bciX96tCZWjLuOqWDe89OVhWBl6Rxi/vXvdy8DXitPel3c+meb k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AWAQBgHIpY/5FdJa1TChkBAQEBAQEBAQEBAQcBAQEBAYJvOQ0BAQEBAR9hgQkHg06CTIc9kgGDegEDkTCCDSqFeAIaghA/GAECAQEBAQEBAWIohGkBAQEEI0sLEAIBBgIRBAEBChcHAwICAg0jFAkIAgQBDQWJYQ6QN51OgiWKbwEBAQEBAQEBAQEBAQEBAQEBAQEBARgFhkuEb4Ekgn0wDxAPglCCXwWIeoQng1SKWwGGZIMah3eBd4USg02GG3CSCgEfODqBERU7hjl1AYdrgQ0BAQE
X-IronPort-AV: E=Sophos;i="5.33,290,1477958400"; d="scan'208,217";a="375745896"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Jan 2017 16:00:51 +0000
Received: from XCH-RCD-018.cisco.com (xch-rcd-018.cisco.com [173.37.102.28]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id v0QG0oqr003041 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 26 Jan 2017 16:00:51 GMT
Received: from xch-rcd-016.cisco.com (173.37.102.26) by XCH-RCD-018.cisco.com (173.37.102.28) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 26 Jan 2017 10:00:50 -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.1210.000; Thu, 26 Jan 2017 10:00:50 -0600
From: "Xiaoqing Zhu (xiaoqzhu)" <xiaoqzhu@cisco.com>
To: Ingemar Johansson S <ingemar.s.johansson@ericsson.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: AQHSdtBtKicDmlu94ESq56+dfZUYi6FJZH25gAHUrYD//7PbWw==
Date: Thu, 26 Jan 2017 16:00:50 +0000
Message-ID: <1485446451961.43618@cisco.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>, <DB4PR07MB3489E1E1197801801E38C4EC2770@DB4PR07MB348.eurprd07.prod.outlook.com>
In-Reply-To: <DB4PR07MB3489E1E1197801801E38C4EC2770@DB4PR07MB348.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.152.245.76]
Content-Type: multipart/alternative; boundary="_000_148544645196143618ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/YOMdDn2WbVmbjBRWdOImDredZtg>
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 16:00:57 -0000

​Thanks, Ingemar.   This is helpful.


Best,

Xiaoqing


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

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