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

Haizhou Du <duhaizhou@gmail.com> Fri, 01 December 2017 14:33 UTC

Return-Path: <duhaizhou@gmail.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 6AA201292F4 for <alto@ietfa.amsl.com>; Fri, 1 Dec 2017 06:33:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 iyhaAdDlphL0 for <alto@ietfa.amsl.com>; Fri, 1 Dec 2017 06:33:36 -0800 (PST)
Received: from mail-wr0-x234.google.com (mail-wr0-x234.google.com [IPv6:2a00:1450:400c:c0c::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED33F127078 for <alto@ietf.org>; Fri, 1 Dec 2017 06:33:35 -0800 (PST)
Received: by mail-wr0-x234.google.com with SMTP id s66so10303642wrc.9 for <alto@ietf.org>; Fri, 01 Dec 2017 06:33:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:from:date:message-id:subject:to; bh=cvFjMmkO4sfL0ebbf+8p64KeyqFgpDCMFUzye7fhYys=; b=tkOWCTuZajoEi5YjiJB7Sht4ORBSf04qQsoFyQ0E4GYR+sj6/QcVKrJoynz/sWmWM4 C815qdUGJ5PPnFzNz+A2cqpO7eovbb2PEbiItmrieRttZPogqF5ux/lzQI6Firn7e7D4 Tgn/NPSmQsgmr4KVmYkLYk5qUi0+YykeGHCnyogrZGgXB6t0UUz21hoRsnAws2i5tHWd VCWi29Mvx+963uuzZbJL8BtHXknHUuCcJNZivjGf6hBbw6dQYHCG9s0D8mtaA+CYNqsp IkoaTg6D1w2LSG2JpAo010XAH79+W8EMo5weIFcMeLneF9kire/GlB2D7N+4z6qdizN5 aJsg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:from:date:message-id :subject:to; bh=cvFjMmkO4sfL0ebbf+8p64KeyqFgpDCMFUzye7fhYys=; b=rS9NVQ5GpV2aedLWxo1LiKU/IhM97nT154e33LxnnTSCUeh0NQ0/aCYIZ2k5yQygiW 4T6TUz6T7bXMhTBC7dnS1XjIN/rrZhyuDM3CcVJtsFgHldfTW4ldVaGppw8v+gYDTTFW /UETd1+rgtFOavzNJORle2iF+sx9puNSoiG65Jhv6Q1GwJSC+epBnZlN8FW+w6vGQMLN qqlei9aZ2xr5Qp3hkaMq7c9VS+D/p1VtEjXbRnDWGQfrTHp+oK94XDz3m1SFoU6TwijQ HUK0EL+HgS7Lm1AAxs9hcMe306HEKfvjzjrbCl2XxVcIxsXRsM/omGxVZQxrUXtAoWut IVUQ==
X-Gm-Message-State: AJaThX49E/PN2L5hF8d6CRmYjLVkSMzoRbHyTAEs8iAKX7ruBtYrdQ57 4MkNoDFvrmoD026JSlN6/tXsDKIZeg8mt6ss8Ezq+w==
X-Google-Smtp-Source: AGs4zMaV5XgNRNSEnBn277tyvzYQLmemDopggfP2+/UgyLPUw//UCbNan5o4HtPHvcHyP4zz5DLvm0RaRdyhAUXQf9A=
X-Received: by 10.223.168.35 with SMTP id l32mr5489802wrc.261.1512138814234; Fri, 01 Dec 2017 06:33:34 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.142.103 with HTTP; Fri, 1 Dec 2017 06:33:33 -0800 (PST)
Reply-To: haizhou.du@cs.yale.edu
From: Haizhou Du <duhaizhou@gmail.com>
Date: Fri, 1 Dec 2017 22:33:33 +0800
Message-ID: <CADdws+y30doQ6OErX+vy3kn21x28OeWRTMcvjAVDrV5s5=8QcA@mail.gmail.com>
To: bill.wu@huawei.com, IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="f403045d58c0dfa49e055f4840b0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/kFD5vZnRgWA5hlOh1c51SRnmsgE>
Subject: [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: Fri, 01 Dec 2017 14:33:37 -0000

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,
*************************************************************