Re: [ippm] Paul Wouters' No Objection on draft-ietf-ippm-stamp-on-lag-05: (with COMMENT)

Tianran Zhou <zhoutianran@huawei.com> Tue, 05 December 2023 08:18 UTC

Return-Path: <zhoutianran@huawei.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7456C14CF1F; Tue, 5 Dec 2023 00:18:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.904
X-Spam-Level:
X-Spam-Status: No, score=-6.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5cGEM_UcSh2p; Tue, 5 Dec 2023 00:17:57 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1DA6C14CE51; Tue, 5 Dec 2023 00:17:56 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Sktf2021fz6K9KL; Tue, 5 Dec 2023 16:16:10 +0800 (CST)
Received: from lhrpeml500001.china.huawei.com (unknown [7.191.163.213]) by mail.maildlp.com (Postfix) with ESMTPS id AE8B11400D2; Tue, 5 Dec 2023 16:17:53 +0800 (CST)
Received: from kwepemd500004.china.huawei.com (7.221.188.173) by lhrpeml500001.china.huawei.com (7.191.163.213) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.35; Tue, 5 Dec 2023 08:17:53 +0000
Received: from kwepemd100004.china.huawei.com (7.221.188.31) by kwepemd500004.china.huawei.com (7.221.188.173) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.28; Tue, 5 Dec 2023 16:17:51 +0800
Received: from kwepemd100004.china.huawei.com ([7.221.188.31]) by kwepemd100004.china.huawei.com ([7.221.188.31]) with mapi id 15.02.1258.028; Tue, 5 Dec 2023 16:17:51 +0800
From: Tianran Zhou <zhoutianran@huawei.com>
To: Paul Wouters <paul.wouters@aiven.io>, The IESG <iesg@ietf.org>
CC: "draft-ietf-ippm-stamp-on-lag@ietf.org" <draft-ietf-ippm-stamp-on-lag@ietf.org>, "ippm-chairs@ietf.org" <ippm-chairs@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>, "marcus.ihlar@ericsson.com" <marcus.ihlar@ericsson.com>
Thread-Topic: Paul Wouters' No Objection on draft-ietf-ippm-stamp-on-lag-05: (with COMMENT)
Thread-Index: AQHaIzfqlvgAiKNBFEW0qtRooSDT1bCaXmwQ
Date: Tue, 05 Dec 2023 08:17:51 +0000
Message-ID: <b28f66fce99648b8aa1296b706ed58ea@huawei.com>
References: <170131258346.475.3868874477726524732@ietfa.amsl.com>
In-Reply-To: <170131258346.475.3868874477726524732@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.112.40.118]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/nHqjI2AtPrlg9Aj8y9Co1zW9rOI>
Subject: Re: [ippm] Paul Wouters' No Objection on draft-ietf-ippm-stamp-on-lag-05: (with COMMENT)
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Dec 2023 08:18:00 -0000

Hi Paul,

Thanks very much for your comments.
Please see inline.

Cheers,
Tianran

-----Original Message-----
From: Paul Wouters via Datatracker [mailto:noreply@ietf.org] 
Sent: Thursday, November 30, 2023 10:50 AM
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-ippm-stamp-on-lag@ietf.org; ippm-chairs@ietf.org; ippm@ietf.org; marcus.ihlar@ericsson.com; marcus.ihlar@ericsson.com
Subject: Paul Wouters' No Objection on draft-ietf-ippm-stamp-on-lag-05: (with COMMENT)

Paul Wouters has entered the following ballot position for
draft-ietf-ippm-stamp-on-lag-05: No Objection

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/about/groups/iesg/statements/handling-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-ippm-stamp-on-lag/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


        This document intends to address

"Do, there is no try" :)  eg you "This documents addresses ....".

ZTR> Yes, will revise in the next version.

        Test packets MAY carry the member link information for validation
        check, which is RECOMMENDED.

MAY RECOMMENDED is novel invention :) I recommend to use "test packets are
RECOMMENDED to carry ..."

ZTR> There is another comment on this discussed in the mailing list. We will revise and change to MUST based on the discussion. 

Section 3.1: Should it state the two octet fields are in network order?

Operational Considerations: The text does not mention if the testing may occur
on a production link (with non-test data), or whether the link is seperated
from the production link to obtain more accurate measurements? That is, should
there be an Operational Considerations section that talks about how/when to run
these tests?

ZTR> I understand production network with work load will impact the accuracy of the active measurement. However, we always use TWAMP/STAMP in production network. I do not think there is any operational issue.