Re: [alto] Review on draft-ietf-alto-performance-metrics-01 by Geng

Qin Wu <bill.wu@huawei.com> Thu, 29 June 2017 10:29 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7134612EBFA; Thu, 29 Jun 2017 03:29:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 fR6H6HPFcjay; Thu, 29 Jun 2017 03:29:01 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7035B127876; Thu, 29 Jun 2017 03:29:00 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml702-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DQA82248; Thu, 29 Jun 2017 10:28:58 +0000 (GMT)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 29 Jun 2017 11:28:56 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.25]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0235.001; Thu, 29 Jun 2017 18:28:52 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "Li, Geng" <geng.li@yale.edu>, "alto@ietf.org" <alto@ietf.org>, "draft-ietf-alto-performance-metrics@ietf.org" <draft-ietf-alto-performance-metrics@ietf.org>
Thread-Topic: Review on draft-ietf-alto-performance-metrics-01 by Geng
Thread-Index: AQHS8HfYt8rCC6ciPE6maaEoxvOQy6I7ohGA
Date: Thu, 29 Jun 2017 10:28:51 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9A98C8B3@nkgeml513-mbx.china.huawei.com>
References: <CY4PR08MB3526919211B51665A5855A5091D20@CY4PR08MB3526.namprd08.prod.outlook.com>
In-Reply-To: <CY4PR08MB3526919211B51665A5855A5091D20@CY4PR08MB3526.namprd08.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.78.218]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA9A98C8B3nkgeml513mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090201.5954D66A.0066, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.25, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 8a77e176b53efc78ede77fda33ffe0f5
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/b_mHb4S7YTi9kY6t_OCFNnGaRtE>
Subject: Re: [alto] Review on draft-ietf-alto-performance-metrics-01 by Geng
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jun 2017 10:29:04 -0000

Thanks Geng for your interesting comments, please see my reply inline below.

-Qin
发件人: Li, Geng [mailto:geng.li@yale.edu]
发送时间: 2017年6月29日 9:34
收件人: alto@ietf.org; draft-ietf-alto-performance-metrics@ietf.org
主题: Review on draft-ietf-alto-performance-metrics-01 by Geng


Dear authors,



Your work is quite excellent, and here are some suggestions I have.



1.     The ALTO server should have the capability to track and record the most frequently used or requested cost metrics of each ALTO client. I’m not sure if it is true, that each client may only run one or two certain applications at most of the time. Then, the benefit is that the ALTO server can prepare the cost metrics in advanced and respond the clients fast after receiving the request.

[Qin]: This draft allows ALTO server collect and record a bunch of data on time period covering past and present, but I am not sure how you can prepare cost metrics in advance, unless you can predict the change pattern of some performance metric or predict the possible value of cost metric in the future.



2.     Another benefit of recording the type of cost metrics of each client is that the ALTO server can detect abnormal behavior of client or application, such as database resource leaks, illegal occupation, or other security issues.

[Qin]: The performance metric we exposed to the client is used to help the client to select the right access point or select appropriate site in the data center based on network performance criteria. I am not sure we can used these performance metric to detect abnormal behavior of client or prevent any resource leak unless you provide me  a clear use cases for that.

3. A variety of performance cost metrics also raise an interesting scheduling problem. For example, client “A” requests two metrics, client “B” just requests one, and client “C” requests three metrics, then how the ALTO server schedules to respond them in the constraint of given resources for workload processing and network transmitting. And for each client, what is the order of the cost metric types to be returned?

[Qin]: I am not sure we need a sophisticated scheduling feature here. The ALTO server will process request from each client by order, who request first, whose request will be processed first.



Hope these are helpful.



Best, Geng

Computer Science, Yale