Re: [ippm] WGLC for STAMP Extensions

wangyali <wangyali11@huawei.com> Fri, 12 June 2020 06:26 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 9D9D33A0A8E for <ippm@ietfa.amsl.com>; Thu, 11 Jun 2020 23:26:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 wJSMBo0JjKR0 for <ippm@ietfa.amsl.com>; Thu, 11 Jun 2020 23:26:43 -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 839153A0A8C for <ippm@ietf.org>; Thu, 11 Jun 2020 23:26:43 -0700 (PDT)
Received: from lhreml721-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 8478EAF20EA84CF96023; Fri, 12 Jun 2020 07:26:40 +0100 (IST)
Received: from lhreml721-chm.china.huawei.com (10.201.108.72) by lhreml721-chm.china.huawei.com (10.201.108.72) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Fri, 12 Jun 2020 07:26:40 +0100
Received: from DGGEML405-HUB.china.huawei.com (10.3.17.49) by lhreml721-chm.china.huawei.com (10.201.108.72) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1913.5 via Frontend Transport; Fri, 12 Jun 2020 07:26:40 +0100
Received: from DGGEML524-MBX.china.huawei.com ([169.254.1.10]) by dggeml405-hub.china.huawei.com ([10.3.17.49]) with mapi id 14.03.0487.000; Fri, 12 Jun 2020 14:26:32 +0800
From: wangyali <wangyali11@huawei.com>
To: Greg Mirsky <gregimirsky@gmail.com>
CC: "ippm@ietf.org" <ippm@ietf.org>, "xiao.min2@zte.com.cn" <xiao.min2@zte.com.cn>
Thread-Topic: [ippm] WGLC for STAMP Extensions
Thread-Index: AQHWQDkTOsKZ9XEYAE6EISSxOhlQYqjUfkXg
Date: Fri, 12 Jun 2020 06:26:32 +0000
Message-ID: <1520992FC97B944A9979C2FC1D7DB0F404E9B938@dggeml524-mbx.china.huawei.com>
References: <CAKcm_gMVc88xpkOMmV7L-ybVCBzw+LhNS6Jw3=iB2gutR0ZhxA@mail.gmail.com> <1520992FC97B944A9979C2FC1D7DB0F404E7D60D@dggeml524-mbx.china.huawei.com> <CA+RyBmXDuf45wFfoKV6hqkXQUTGjtyVLafrrAB6kJdHRshx7Nw@mail.gmail.com>
In-Reply-To: <CA+RyBmXDuf45wFfoKV6hqkXQUTGjtyVLafrrAB6kJdHRshx7Nw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.203.65]
Content-Type: multipart/alternative; boundary="_000_1520992FC97B944A9979C2FC1D7DB0F404E9B938dggeml524mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/VKwSiUFqp0iVCzJkr4QLQwOLX3I>
Subject: Re: [ippm] WGLC for STAMP Extensions
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: Fri, 12 Jun 2020 06:26:46 -0000

Hi Greg,

Glad to receive your reply. Just a minor question. Please see inline <Yali>.

From: Greg Mirsky [mailto:gregimirsky@gmail.com]
Sent: Friday, June 12, 2020 5:42 AM
To: wangyali <wangyali11@huawei.com>
Cc: ippm@ietf.org; xiao.min2@zte.com.cn
Subject: Re: [ippm] WGLC for STAMP Extensions

Hi Yali,
my apologies for the delayed response. Please find my answers below tagged GIM>>. Attached, please find the updated working version and the diff. I hope that the proposed updates address your concerns.

Regards,
Greg

On Mon, Jun 1, 2020 at 1:40 AM wangyali <wangyali11@huawei.com<mailto:wangyali11@huawei.com>> wrote:
Hi authors and IPPM,

I support its publication. But after reading, I have two questions and comments as follows:


1.       In the draft, I confused a sentence that said 'The Session-Sender MUST NOT stop the session if it receives a zeroed  SSID field.' If a STAMP Session-Reflector that does not support this specification and return the zeroed SSID field in the reflected STAMP test packet, the STAMP Session-Sender MUST stop the session. I assume there's a edit error.
GIM>> Great catch, thank you!





2.       Does the TLV field shown in figure 1 indicate that the STAMP Session-Sender test packet with TLV in unauthenticated mode can contains one or more TLVs defined in this draft? I suggest to give an illustration about the TLV field in the test packet and revise TLV field in figure 1 that is not very clear.
GIM>> You are absolutely correct, multiple TLVs can be used in the same test packet either sequentially or enclosed. I've added a new text in the first paragraph of Section 4:
OLD TEXT:
   Type-Length-Value (TLV) encoding scheme provides flexible extension
   mechanism for optional informational elements.  TLV is an optional
   field in the STAMP test packet.
NEW TEXT:
   Type-Length-Value (TLV) encoding scheme provides a flexible extension
   mechanism for optional informational elements.  TLV is an optional
   field in the STAMP test packet.  Multiple TLVs MAY be placed in the
   STAMP test packet.  A TLV MAY be enclosed in a TLV.

<Yali> what do you mean 'A TLV MAY be enclosed in a TLV'?

Also, I've updated captions for Figure 1 and Figure 2 to indicate that they present an example of an extended STAMP test packet.

Best regards,
Yali



From: ippm [mailto:ippm-bounces@ietf.org<mailto:ippm-bounces@ietf.org>] On Behalf Of Ian Swett
Sent: Saturday, May 23, 2020 5:26 AM
To: IETF IPPM WG (ippm@ietf.org<mailto:ippm@ietf.org>) <ippm@ietf.org<mailto:ippm@ietf.org>>
Subject: [ippm] WGLC for STAMP Extensions

Hi IPPM,

At our virtual interim meeting, we decided draft-ietf-ippm-stamp-option-tlv was ready for last call. This email starts a two-week WGLC for this draft.

The latest version can be found here: https://tools.ietf.org/html/draft-ietf-ippm-stamp-option-tlv-04

This last call will end on Monday, June 8th. Please reply to ippm@ietf.org<mailto:ippm@ietf.org> with your reviews and comments.

Thanks,
Ian & Tommy