Hello Chunshan Xiong, Thanks a lot for bringing these 5G use cases to the ALTO WG, and for the comprehensive description of related experiments. Indeed apps such as Low Delay Live Show are getting highly important in the current context of confinement, where classes are all getting virtual and interactive. The challenges faced by networks are an additional motivation to further optimize traffic for such applications.
I would like to initiate discussions on section 5 "Standardization Considerations of MoWIE as an Extension to ALTO", where some key considerations are provided. 1 - Regarding item "Network information selection and binding consideration": indeed, a flexible mechanism deciding which metrics an ALTO client should query will allow to support a variety of applications and contexts, that may each require a particular set of metrics. Such a mechanism, that prepares input to ALTO Client requests, will use the IRD information, starting with the list of available cost metrics. - Did you identify particular IRD features that need to be added or upgraded to support flexibility for ALTO Client requests? - What type of flexibility is otherwise missing in ALTO information resources? 2 - In item "Compact network information encoding consideration": the processing overhead due to frequent updates especially for cellular networks raises a key point regarding future ALTO extensions. Definitely, ALTO is currently not meant to provide information at such a frequency. - A first aspect to investigate in the ALTO WG may be requirements for reliable cellular network information. In particular: at which frequency does an application need to update network information? In which extent can cellular network information be aggregated over time and still be reliable for an application? All this considering several applications and several metrics. - Another consideration on this item: very frequent network information updates, if predicable may be conveyed in Calendars with SSE updates for unexpected changes, but this is still near real time. One way around is to investigate extensions that may combine ALTO information with "conditional" real-time information, obtained with other means. A first attempt in this direction is proposed in “ALTO Contextual Cost Values” [1] where ALTO Calendar values are further interpreted with real-time parameter values acquired by other means. This is preliminary work and does not directly provide real-time cellular values but we may look at what can be extended in the design, to support cases for very frequent network information updates. I look forward to hearing your presentation at the interim meeting. Best regards, Sabine [1] https://tools.ietf.org/id/draft-randriamasy-alto-cost-context-03.txt From: alto <[email protected]> On Behalf Of chunshxiong(???) Sent: Tuesday, March 10, 2020 2:35 AM To: [email protected] Subject: [alto] Welcome your comments on new draft-huang-alto-mowie-for-network-aware-app Hello all, A new alto draft https://datatracker.ietf.org/doc/draft-huang-alto-mowie-for-network-aware-app/ is submitted. In this paper, we uses the network information of Mobile and Wireless Information Exposure (MoWIE) to adapt key control knobs such as media codec scheme, encapsulation and application logical function to improve the QoE. We provide some detailed testing and evaluations. And we discuss how MoWIE can be a systematic extension of the ALTO protocol, to expose more lower-layer and finer grain network dynamics. We spend a lot of time and testing to produce this paper, welcome your comments and we will update the testing and improve the paper based on your comments. BRs, Chunshan Xiong Tencent
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
