[alto] several views on "ALTO Performance Cost Metrics draft-ietf-alto-performance-metrics-01”

Lili Liu <lili.liu@yale.edu> Thu, 29 June 2017 22:31 UTC

Return-Path: <lili.liu@yale.edu>
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 8945112773A for <alto@ietfa.amsl.com>; Thu, 29 Jun 2017 15:31:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yale.edu
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 kik-ASbr73YY for <alto@ietfa.amsl.com>; Thu, 29 Jun 2017 15:31:29 -0700 (PDT)
Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::22f]) (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 D68B6126C7A for <alto@ietf.org>; Thu, 29 Jun 2017 15:31:28 -0700 (PDT)
Received: by mail-qk0-x22f.google.com with SMTP id p21so88382347qke.3 for <alto@ietf.org>; Thu, 29 Jun 2017 15:31:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yale.edu; s=googleprd; h=from:content-transfer-encoding:subject:message-id:date:to :mime-version; bh=H4Lv8rPP5GhdGz0Hdcqw68wdCC/p9a/DbQzWZrYkHC4=; b=M3PWq2lcSQV7/SdT1x31m11n7HPlpd3cYsDRCW9QRuZYr/sqFk/r+fWGPLG0Eci5Bw cKbJp9DSA4llM9NBcp1dO6Ms81/OT3eIPID5wf9KC21aq0tN8+5dXPtI7bp7ZdBCdipC eQNiD+yXgKwInvSFxvbhuGHZlmsLsEh3JxEtA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=H4Lv8rPP5GhdGz0Hdcqw68wdCC/p9a/DbQzWZrYkHC4=; b=FfFtMecVZ7fIlqnQ+lL/jvc6tHEm+KIfYtzDJCCclIiXnq2tBJfMLmJojCV0+I695s i+gCx6rMjMaA2GZ6MpQKkuVolWYmR9HBcfntElgPHQ49hBXuwhyUrwQjS5GjM/YXAY2y Z67+gLpssyL/Gga9jDgRw01oqKJJrG6vsBMxLnlGDypzSAqLX/1bY4pfomovwmIB7h0P lKtFbBSYNXXQQ/LCmnLqh1kMF6OlEWS+kom03ns5Wbki74OHQoH8np72hBWkmxemuFJx rcXygPWxmZfu/LCbVLWYwKKikiitOZgcgwqHKF64jGu9yyx26ZYnHJbH/om6WWUfmTPt UDaA==
X-Gm-Message-State: AKS2vOw5OHbWvXlSY9N+HxPOrlOxYjGo0daa3uiHx1G4XlkFgSLZjwmG sD31tzX0c80rdJD7B+rN3w==
X-Received: by 10.55.164.88 with SMTP id n85mr21465052qke.159.1498775487912; Thu, 29 Jun 2017 15:31:27 -0700 (PDT)
Received: from [192.168.0.19] (cpe-66-108-205-11.nyc.res.rr.com. [66.108.205.11]) by smtp.gmail.com with ESMTPSA id h17sm5355905qte.20.2017.06.29.15.31.27 for <alto@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 29 Jun 2017 15:31:27 -0700 (PDT)
From: Lili Liu <lili.liu@yale.edu>
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5802735-CF8D-4711-9E74-6DBFAB69A703@yale.edu>
Date: Thu, 29 Jun 2017 18:31:26 -0400
To: alto@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/ipctUw0bQlYP8msEGtizNV9zTUM>
Subject: [alto] several views on "ALTO Performance Cost Metrics draft-ietf-alto-performance-metrics-01”
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 22:31:30 -0000

Hi everyone,

I’ve been reading  "ALTO Performance Cost Metrics draft-ietf-alto-performance-metrics-01” these days and have some comments as follows:
This draft is written in good organization. The authors present a set of Cost Metrics which work for ALTO system, give them a detailed description and give some examples for them. 
But there’re still some grammar errors in the draft as follows:

page1:
para2 line 3: offers->offer
para3 line 3: end to end-> end-to-end

page4:
para 3 line 2: policy->policies
para 3 line 3: end to end->end-to-end
para 3 line 4: ALTO may convey such information, not available via 3rd party measurement tools.->seems strange
para 4 line 2: if they feel-> how could applications feel something?

page5:
para 1 to para 2: unnatural transition
para 2 line 5: them->the
para 4 line 4: on time periods covering the past and present-> based on both previous and current time

page6:
para 1 line 2: bandwidth related->bandwidth-related

page16:
para 2 line 2: neighbor->neighbors

page24:
pare1 line 1:Indeed, TE performance is a highly sensitive ISP information and sharing TE metric values in numerical mode requires full mutual confidence between the entities managing the ALTO Server and Client.-> Indeed, TE performance is a kind of highly sensitive ISP information. Therefore, sharing TE metric values in numerical mode requires full mutual confidence between the entities managing the ALTO Server and Client.

Best,
Lili