Re: [alto] Review of draft-ietf-alto-performance-metrics-02

Qin Wu <bill.wu@huawei.com> Mon, 04 December 2017 01:07 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 DDCAA127201 for <alto@ietfa.amsl.com>; Sun, 3 Dec 2017 17:07:57 -0800 (PST)
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, SPF_PASS=-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 nWYAGhqz17kd for <alto@ietfa.amsl.com>; Sun, 3 Dec 2017 17:07:56 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 CAE4D126B7E for <alto@ietf.org>; Sun, 3 Dec 2017 17:07:55 -0800 (PST)
Received: from LHREML714-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 8FF857FB669CE for <alto@ietf.org>; Mon, 4 Dec 2017 01:07:51 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by LHREML714-CAH.china.huawei.com (10.201.108.37) with Microsoft SMTP Server (TLS) id 14.3.361.1; Mon, 4 Dec 2017 01:07:53 +0000
Received: from NKGEML513-MBS.china.huawei.com ([169.254.2.231]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0361.001; Mon, 4 Dec 2017 09:07:48 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "haizhou.du@cs.yale.edu" <haizhou.du@cs.yale.edu>, IETF ALTO <alto@ietf.org>
Thread-Topic: [alto] Review of draft-ietf-alto-performance-metrics-02
Thread-Index: AQHTarFiPV8oQjqXB06z8GMKIwUfYqMyYtig
Date: Mon, 4 Dec 2017 01:07:47 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9ACF929C@nkgeml513-mbs.china.huawei.com>
References: <CADdws+y30doQ6OErX+vy3kn21x28OeWRTMcvjAVDrV5s5=8QcA@mail.gmail.com>
In-Reply-To: <CADdws+y30doQ6OErX+vy3kn21x28OeWRTMcvjAVDrV5s5=8QcA@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.79.67]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA9ACF929Cnkgeml513mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/fR1HEKfjI_5f7RCBihCYmskVl0Q>
Subject: Re: [alto] Review of draft-ietf-alto-performance-metrics-02
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: Mon, 04 Dec 2017 01:07:58 -0000

Thank Haizhou for valuable review. Thank for your proposal to section 3.
I agree with all your proposed changes.

-Qin
发件人: Haizhou Du [mailto:duhaizhou@gmail.com]
发送时间: 2017年12月1日 22:34
收件人: Qin Wu; IETF ALTO
主题: [alto] Review of draft-ietf-alto-performance-metrics-02

Dear Qin and whole ALTO Working Group,
I just reviewed the draft-ietf-performance-metrics-02, and see the Kai and Qin mails.Below are some of my opinions. Your feedback and comments are highly appreciated.
========================================================

1. p5,  The very purpose of ALTO is to guide application traffic with provider network centric information that may be exposed to ALTO Clients in the form of network performance metric values.

-> The very important purpose of ALTO is to guide application traffic with provider network-centric
information that may be exposed to ALTO Clients in the form of network performance metric values.

2. p6,  The metric specifications may also expose the utilised aggregation laws.

-> The metric specifications may also expose the utilized aggregation laws.

3.  I also agree with Kai option of section 2.  Section 2 describes three challenges. Why not split 3 subsections as follows?
2.1 Data Sources Challenges
2.2 Configuration Parameters Challenges
2.3 Availability of Path values  Challenges

I think it's more clear and direct to the readers.


--
Thanks a lot!
Sincerely!
*************************************************************
Haizhou Du,
*************************************************************