IETF Logo Mail Archive

[ippm] Comments for draft-li-ippm-pm-on-lag

wangyali <wangyali11@huawei.com> Wed, 14 October 2020 07:11 UTC

Return-Path: <wangyali11@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 D789D3A0EB5; Wed, 14 Oct 2020 00:11:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, 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 a-zOhfbAJXhw; Wed, 14 Oct 2020 00:11:00 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 429D03A0EB4; Wed, 14 Oct 2020 00:11:00 -0700 (PDT)
Received: from lhreml704-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 515077F208AA82F0CC47; Wed, 14 Oct 2020 08:10:55 +0100 (IST)
Received: from lhreml704-chm.china.huawei.com (10.201.108.53) by lhreml704-chm.china.huawei.com (10.201.108.53) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Wed, 14 Oct 2020 08:10:54 +0100
Received: from DGGEML423-HUB.china.huawei.com (10.1.199.40) by lhreml704-chm.china.huawei.com (10.201.108.53) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1913.5 via Frontend Transport; Wed, 14 Oct 2020 08:10:54 +0100
Received: from DGGEML524-MBX.china.huawei.com ([169.254.1.7]) by dggeml423-hub.china.huawei.com ([10.1.199.40]) with mapi id 14.03.0487.000; Wed, 14 Oct 2020 15:09:41 +0800
From: wangyali <wangyali11@huawei.com>
To: "draft-li-ippm-pm-on-lag@ietf.org" <draft-li-ippm-pm-on-lag@ietf.org>
CC: IETF IPPM WG <ippm@ietf.org>
Thread-Topic: Comments for draft-li-ippm-pm-on-lag
Thread-Index: Adah+Gmyf++Ze/DTQGG9a+/qcIAK3A==
Date: Wed, 14 Oct 2020 07:09:40 +0000
Message-ID: <1520992FC97B944A9979C2FC1D7DB0F40500377D@dggeml524-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.243.136]
Content-Type: multipart/alternative; boundary="_000_1520992FC97B944A9979C2FC1D7DB0F40500377Ddggeml524mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/yO-S4dxCSZQBO2A4Ji85Rg2r_hw>
Subject: [ippm] Comments for draft-li-ippm-pm-on-lag
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 14 Oct 2020 07:11:03 -0000

Hi authors,

This is a valuable draft discussing about PM on LAG through OWAMP/TWAMP/STAMP extension.

The basic STAMP defined in RFC8762 has been extended to implement PM on member link of a LAG in your draft.  Do you consider the extended STAMP proposed in [draft-ietf-ippm-stamp-option-tlv] to be used for PM on LAG?


Nits:

OLD: When receives a Test packet, the micro STAMP Session-Reflector MUST

   use the member link from which the Test packet is received to

   correlate to a micro STAMP session and use the Sender/Reflector

   member link identifiers to validate whether the Test packet is is

   correctly transmitted over the expected member link.



NEW: When receives a Test packet, the micro STAMP Session-Reflector MUST

   use the member link from which the Test packet is received to

   correlate to a micro STAMP session and use the Sender/Reflector

   member link identifiers to validate whether the Test packet is

   correctly transmitted over the expected member link.

Best regards,
Yali

v2.23.0 | Report a Bug | By Email