Re: [alto] Zaheduzzaman Sarker's Discuss on draft-ietf-alto-performance-metrics-20: (with DISCUSS and COMMENT)
"Y. Richard Yang" <yry@cs.yale.edu> Mon, 28 February 2022 21:14 UTC
Return-Path: <yang.r.yang@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 AB7B93A1521; Mon, 28 Feb 2022 13:14:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.412
X-Spam-Level:
X-Spam-Status: No, score=-1.412 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 klYAd0pvW52e; Mon, 28 Feb 2022 13:14:30 -0800 (PST)
Received: from mail-yb1-f174.google.com (mail-yb1-f174.google.com [209.85.219.174]) (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 4F5683A14F9; Mon, 28 Feb 2022 13:14:30 -0800 (PST)
Received: by mail-yb1-f174.google.com with SMTP id y189so23207819ybe.4; Mon, 28 Feb 2022 13:14:30 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=W7ShvBLaGAL67WwujoqLppc0FL5REFL/wmKRQEOMGLg=; b=FLbppEcuMCPlgRDdsLyhnzLxYTMx9P/zC5Yisrn8qNxhHIDP/SEN6EdOU0wrbkv2B0 pi4DuNIJmU3xUrbyW1iZ4VhlE2egW8aR8jKIZyqMlYqdg8eUcN+z/6gRoc53YYrhVv3W m62yMlUlDQxUxg+xfpX9M3dVEaYABrKKIaGvSbWiFio5iFv6wXl/N0cnHnhvnxZnaNmw qCMQuFDRvk0AdTqGTtW8YoejlP5u4MYU3oc0ZtJbkgR0pZbxqR9+kCoGHRU8U4n+GR2H 0RzJ6okXHT38j7vQTYjZkFRqp4K8k4WKBVvW4PrS9J0/veUfETiTpRGcqMbZ1C2aapKQ Nj0g==
X-Gm-Message-State: AOAM532ul2mUQ+kcxtNyuzFpXfjVlii5Jws+QFQtiUkTpwd6qnK5B7f2 aIfPzLkJjEXgLp+9GS/coQDvX0snHe1rAL8Y3A8=
X-Google-Smtp-Source: ABdhPJzQddv3vOQGZjWyJ1c+rxaiMhyYiJGZ4ZHcvGVs+YJfT5NJwy8r0mp1sLU9EHfkmgldq/BhHGlOXUXNArU+S1A=
X-Received: by 2002:a25:3d2:0:b0:61a:18e5:c5e0 with SMTP id 201-20020a2503d2000000b0061a18e5c5e0mr20904567ybd.589.1646082869451; Mon, 28 Feb 2022 13:14:29 -0800 (PST)
MIME-Version: 1.0
References: <d2c14e67364f480b902e532894930daa@huawei.com>
In-Reply-To: <d2c14e67364f480b902e532894930daa@huawei.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
Date: Mon, 28 Feb 2022 16:14:18 -0500
Message-ID: <CANUuoLq=7Cr+WpNfVTMFTL=z8FhypTYQaakwbCW4mwjSXZNfGQ@mail.gmail.com>
To: Qin Wu <bill.wu=40huawei.com@dmarc.ietf.org>
Cc: Zaheduzzaman Sarker <Zaheduzzaman.Sarker@ericsson.com>, The IESG <iesg@ietf.org>, "alto-chairs@ietf.org" <alto-chairs@ietf.org>, "draft-ietf-alto-performance-metrics@ietf.org" <draft-ietf-alto-performance-metrics@ietf.org>, "alto@ietf.org" <alto@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b45e5605d91a889c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/ayQERLYI880WlIVaQKG1GCxKQAY>
Subject: Re: [alto] Zaheduzzaman Sarker's Discuss on draft-ietf-alto-performance-metrics-20: (with DISCUSS and COMMENT)
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.29
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, 28 Feb 2022 21:14:35 -0000
Hi Zaheduzzaman, We have posted the latest version of the document: https://datatracker.ietf.org/doc/html/draft-ietf-alto-performance-metrics-24 Could you please take a look to see if all of your comments are addressed? In particular, - We checked and made sure that the normative references are correct. - We updated the abstract to clarify the wording and added sentences in Sec. 1 on the uses. - We revised the final wording of 2.2 on the number format - We checked all json examples and fixed the issues. Please take a look and let us know if there are remaining issues to be addressed. Thank you so much! Richard On Thu, Dec 2, 2021 at 8:32 AM Qin Wu <bill.wu=40huawei.com@dmarc.ietf.org> wrote: > Hi, Zaheduzzaman: > -----邮件原件----- > 发件人: Zaheduzzaman Sarker via Datatracker [mailto:noreply@ietf.org] > 发送时间: 2021年12月2日 19:35 > 收件人: The IESG <iesg@ietf.org> > 抄送: draft-ietf-alto-performance-metrics@ietf.org; alto-chairs@ietf.org; > alto@ietf.org; ietf@j-f-s.de; ietf@j-f-s.de > 主题: Zaheduzzaman Sarker's Discuss on > draft-ietf-alto-performance-metrics-20: (with DISCUSS and COMMENT) > > Zaheduzzaman Sarker has entered the following ballot position for > draft-ietf-alto-performance-metrics-20: Discuss > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > > Please refer to https://www.ietf.org/blog/handling-iesg-ballot-positions/ > for more information about how to handle DISCUSS and COMMENT positions. > > > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/draft-ietf-alto-performance-metrics/ > > > > ---------------------------------------------------------------------- > DISCUSS: > ---------------------------------------------------------------------- > > I perhaps understand the intention of extending the ALTO protocol so that > the ALTO client and server have defined way of exchanging values for > already defined metrics. However, I need to agree with my fellow AD > colleagues that this document need to describe why those metrics are needed > and describe the relationship with other RFCs those defines those metrics > mostly for other contexts. To that end all the RFCs in the Table 1 in > section 1 need to be normative references. > > [Qin Wu] I think the key use case is defined in RFC7752 section 2.2, i.e., > export BGP-LS collected topology data to ALTO server and the ALTO server > expose data to the client. RFC8571 provides additional performance metric > related data which is part of topology data. Most of performance cost > metrics derived from metrics defined in RFC8571. > Another two relevant use cases are documented in section 3 of > draft-xie-alto-lmap-00, one is targeted to network operators who need to > understand the performance of their networks, the performance of the > suppliers (downstream and upstream networks), the performance of Internet > access services, and the impact that such performance has on the experience > of their customers. > The other is targeted to regulators who want to evaluate the performance > of the network services offered by operators. > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > Thanks for the work on this document and thanks to Brian Trammell for his > TSVART early review. > > I have following comments which I believe will improve the document > quality - > > 1. In the abstract I read about "a better delay performance" and was > hoping it will be clear to me what is "a better delay performance". > Unfortunately, I was unable to get that. This comes to the point that this > document needs to describe why purpose of using the defined metrics well. > [Qin Wu] See clarification above. > > 2. Section 2.2 says > > The number MUST be a non-negative JSON integer in the range [0, 100] > (i.e., > greater than or equal to 0 and less than or equal to 100), followed by > an > optional decimal part, if a higher precision is needed. > > This should be a JSON number type not integer type. > [Qin Wu] See clarification to Ben's comments. The format of percentile is > integer number followed by optional decimal part starting with the '.' > separator. > 3. There are number of broken JSON examples. for example, in section 4.2.3 > "ipv4:192.0.2.2" { > "ipv4:192.0.2.89" : 0, > "ipv4:198.51.100.34": 2000 > } > missing ":" after ipv4:192.0.2.2 > [Qin Wu] Agree to fix this. > 4. Content-Length: TBA in the examples, I actually don't know how to > interpret it. > > [Qin Wu] Agree to fix this. > > _______________________________________________ > alto mailing list > alto@ietf.org > https://www.ietf.org/mailman/listinfo/alto >
- [alto] Zaheduzzaman Sarker's Discuss on draft-iet… Zaheduzzaman Sarker via Datatracker
- Re: [alto] Zaheduzzaman Sarker's Discuss on draft… Qin Wu
- Re: [alto] Zaheduzzaman Sarker's Discuss on draft… Y. Richard Yang
- Re: [alto] Zaheduzzaman Sarker's Discuss on draft… Zaheduzzaman Sarker
- Re: [alto] Zaheduzzaman Sarker's Discuss on draft… Qin Wu
- Re: [alto] Zaheduzzaman Sarker's Discuss on draft… Y. Richard Yang