Re: [ippm] Fwd: New Version Notification for draft-mirsky-ippm-asymmetrical-pkts-00.txt
Tianran Zhou <zhoutianran@huawei.com> Tue, 27 June 2023 06:09 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 670F5C152567 for <ippm@ietfa.amsl.com>; Mon, 26 Jun 2023 23:09:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.193
X-Spam-Level:
X-Spam-Status: No, score=-4.193 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 eWsPx1NQpdmE for <ippm@ietfa.amsl.com>; Mon, 26 Jun 2023 23:09:29 -0700 (PDT)
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 9FBFCC15108B for <ippm@ietf.org>; Mon, 26 Jun 2023 23:09:28 -0700 (PDT)
Received: from lhrpeml500003.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4QqvQW3Mfhz6J7kP for <ippm@ietf.org>; Tue, 27 Jun 2023 14:08:03 +0800 (CST)
Received: from kwepemi100010.china.huawei.com (7.221.188.54) by lhrpeml500003.china.huawei.com (7.191.162.67) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.27; Tue, 27 Jun 2023 07:09:25 +0100
Received: from kwepemi500009.china.huawei.com (7.221.188.199) by kwepemi100010.china.huawei.com (7.221.188.54) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.27; Tue, 27 Jun 2023 14:09:23 +0800
Received: from kwepemi500009.china.huawei.com ([7.221.188.199]) by kwepemi500009.china.huawei.com ([7.221.188.199]) with mapi id 15.01.2507.027; Tue, 27 Jun 2023 14:09:23 +0800
From: Tianran Zhou <zhoutianran@huawei.com>
To: Greg Mirsky <gregimirsky@gmail.com>
CC: IETF IPPM WG <ippm@ietf.org>
Thread-Topic: [ippm] Fwd: New Version Notification for draft-mirsky-ippm-asymmetrical-pkts-00.txt
Thread-Index: AQHZqGy26hZST+0Vv0aNk6GJ2AN/UK+d01Cg//+N1QCAAKOSkA==
Date: Tue, 27 Jun 2023 06:09:23 +0000
Message-ID: <d3e31abf75cc4bc491034d325413c6cf@huawei.com>
References: <168781045941.57145.13085166230362026738@ietfa.amsl.com> <CA+RyBmXbT=kWFRVWV278ndjdaLuz8WcezM3ed_HjumaKxML79A@mail.gmail.com> <8a0c78fff96843af93cdac5c2c42e5d4@huawei.com> <CA+RyBmUdxaJ2TFjzm_KJmp8kaut3jcWD7jfjwScLaPZRERVB4A@mail.gmail.com>
In-Reply-To: <CA+RyBmUdxaJ2TFjzm_KJmp8kaut3jcWD7jfjwScLaPZRERVB4A@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.112.41.58]
Content-Type: multipart/alternative; boundary="_000_d3e31abf75cc4bc491034d325413c6cfhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/61QHryg01az2ray1loc0n-LyWIo>
Subject: Re: [ippm] Fwd: New Version Notification for draft-mirsky-ippm-asymmetrical-pkts-00.txt
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, 27 Jun 2023 06:09:33 -0000
Hi Greg, Please see inline. Tianran From: Greg Mirsky [mailto:gregimirsky@gmail.com] Sent: Tuesday, June 27, 2023 10:07 AM To: Tianran Zhou <zhoutianran@huawei.com> Cc: IETF IPPM WG <ippm@ietf.org> Subject: Re: [ippm] Fwd: New Version Notification for draft-mirsky-ippm-asymmetrical-pkts-00.txt Hi Tianran, thank you for your questions. Please find my notes below tagged by GIM>>. Regards, Greg On Mon, Jun 26, 2023 at 5:57 PM Tianran Zhou <zhoutianran@huawei.com<mailto:zhoutianran@huawei.com>> wrote: Hi Greg, STAMP is to standardize TWAMP light. GIM>> I cannot find that being stated in RFC 8762<https://datatracker.ietf.org/doc/rfc8762/>. STAMP was designed to interwork with systems that support TWAMP Light in unauthenticated mode. That, in the view of the authors, should ease the deployment of STAMP as there are already many operators that use TWAMP Light in the unauthenticated mode in their networks. But STAMP, in my opinion, has many other benefits that go beyond that interworking capability. And that is its extensibility that has been demonstrated in RFC 8972<https://datatracker.ietf.org/doc/rfc8972/>, draft-ietf-ippm-stamp-srpm<https://datatracker.ietf.org/doc/draft-ietf-ippm-stamp-srpm/>, and draft-ietf-ippm-stamp-on-lag<https://datatracker.ietf.org/doc/draft-ietf-ippm-stamp-on-lag/> (that you and I have worked together) ZTR> It’s not much relevant STAMP is TWAMP light or not. What I mean is that STAMP is like TWAMP light, should eliminate control plane, IMHO. If you want to extend the control msg, why not to use TWAMP? GIM>> I've worked on several TWAMP extensions and learned that that is not an easy task. I've used the lesson learned when working with other authors on defining the extension mechanism for STAMP. Also, if I remember correctly, the IPPM WG discussed future extensions of active measurement protocols and, as I recall it, has reached the conclusion to encourage new proposals based on STAMP. ZTR> I think for STAMP, the right way is to augment the STAMP YANG model for this feature. I do not think STAMP defines the control plane. Best, Tianran From: ippm [mailto:ippm-bounces@ietf.org<mailto:ippm-bounces@ietf.org>] On Behalf Of Greg Mirsky Sent: Tuesday, June 27, 2023 4:26 AM To: IETF IPPM WG <ippm@ietf.org<mailto:ippm@ietf.org>> Subject: [ippm] Fwd: New Version Notification for draft-mirsky-ippm-asymmetrical-pkts-00.txt Dear All, a new draft describes an extension of STAMP, Reflected Test Packet Control TLV, that adds some interesting behaviors, including the ability for a Session-Sender to control test packet reflection by the Session-Reflector. Among the controllable parameters are the length of the reflected packet, the number of reflected packets transmitted in response to the received STAMP test packet, and the time interval between those reflected packets. One of the behaviors that can be achieved by using Reflected Test Packet Control TLV is selective suppression of Session-Reflector transmitting a reflected packet. I greatly appreciate your comments, questions, and suggestions, and I welcome cooperation. Regards, Greg ---------- Forwarded message --------- From: <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>> Date: Mon, Jun 26, 2023 at 1:14 PM Subject: New Version Notification for draft-mirsky-ippm-asymmetrical-pkts-00.txt To: Greg Mirsky <gregimirsky@gmail.com<mailto:gregimirsky@gmail.com>> A new version of I-D, draft-mirsky-ippm-asymmetrical-pkts-00.txt has been successfully submitted by Greg Mirsky and posted to the IETF repository. Name: draft-mirsky-ippm-asymmetrical-pkts Revision: 00 Title: Performance Measurement with Asymmetrical Packets in STAMP Document date: 2023-06-26 Group: Individual Submission Pages: 6 URL: https://www.ietf.org/archive/id/draft-mirsky-ippm-asymmetrical-pkts-00.txt Status: https://datatracker.ietf.org/doc/draft-mirsky-ippm-asymmetrical-pkts/ Html: https://www.ietf.org/archive/id/draft-mirsky-ippm-asymmetrical-pkts-00.html Htmlized: https://datatracker.ietf.org/doc/html/draft-mirsky-ippm-asymmetrical-pkts Abstract: This document describes an optional extension to a Simple Two-way Active Measurement Protocol (STAMP) that enables the use of STAMP test and reflected packets of variable length during a single STAMP test session. In some use cases, the use of asymmetrical test packets allow for the creation of more realistic flows of test packets and, thus, a closer approximation between active performance measurements and conditions experienced by the monitored application. The IETF Secretariat
- [ippm] Fwd: New Version Notification for draft-mi… Greg Mirsky
- Re: [ippm] Fwd: New Version Notification for draf… Tianran Zhou
- Re: [ippm] Fwd: New Version Notification for draf… Greg Mirsky
- Re: [ippm] Fwd: New Version Notification for draf… Tianran Zhou
- Re: [ippm] Fwd: New Version Notification for draf… Ernesto Ruffini
- Re: [ippm] Fwd: New Version Notification for draf… Greg Mirsky
- Re: [ippm] Fwd: New Version Notification for draf… Greg Mirsky
- Re: [ippm] Fwd: New Version Notification for draf… Ernesto Ruffini
- Re: [ippm] Fwd: New Version Notification for draf… Henrik Nydell
- Re: [ippm] Fwd: New Version Notification for draf… Greg Mirsky
- Re: [ippm] Fwd: New Version Notification for draf… Henrik Nydell
- Re: [ippm] Fwd: New Version Notification for draf… Tianran Zhou
- Re: [ippm] Fwd: New Version Notification for draf… Henrik Nydell
- Re: [ippm] Fwd: New Version Notification for draf… Tianran Zhou
- Re: [ippm] Fwd: New Version Notification for draf… Tianran Zhou