Re: [ippm] WGLC for STAMP Extensions

Greg Mirsky <gregimirsky@gmail.com> Thu, 11 June 2020 21:41 UTC

Return-Path: <gregimirsky@gmail.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 3D7623A0A5E for <ippm@ietfa.amsl.com>; Thu, 11 Jun 2020 14:41:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.934
X-Spam-Level: **
X-Spam-Status: No, score=2.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_COMMENT_SAVED_URL=1.391, HTML_MESSAGE=0.001, MANY_SPAN_IN_TEXT=3.63, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_HTML_ATTACH=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 g-AgGcqhPdZx for <ippm@ietfa.amsl.com>; Thu, 11 Jun 2020 14:41:49 -0700 (PDT)
Received: from mail-lj1-x22a.google.com (mail-lj1-x22a.google.com [IPv6:2a00:1450:4864:20::22a]) (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 ACA8A3A0A53 for <ippm@ietf.org>; Thu, 11 Jun 2020 14:41:48 -0700 (PDT)
Received: by mail-lj1-x22a.google.com with SMTP id s1so8758594ljo.0 for <ippm@ietf.org>; Thu, 11 Jun 2020 14:41:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MLkJhHKAbhLMrj5IRDLTBqFEVgA62zxvRlJ24memRQY=; b=FzQ2Z2NYxagGz8yTUC6c77/YbbIRJq4eUF4ykyNEtxIHoZYAGh4tEI/G3e6NC2Z8RH pehYOE3D0y30jA+wtPESS55EIfdOlibkNEla4zubyhZVCfcgN93g5aEs97k2lXcJ/fgN xtaGH6XspJGq/K/6a/Z0rpfDSIdB5cBym2k7lCoHyXJuQwznvng+ziJfMhSLMIzdBSHl bX4gN0yeMifHajlVd3JxdmC/ENWTBNwP7bp5dFsJ3SSDBjKhdGuOMk2ycXEp0HrdskyM XZyWrjes3CrrmuLVQUUs8IHcWeeDt8KEq++3ap5eQmZjYTxKt48t1ETiNCRHyLNcBJVp 0XSQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MLkJhHKAbhLMrj5IRDLTBqFEVgA62zxvRlJ24memRQY=; b=bcdS2Av6W5E7q8o1DdvfoX4EDlRXc8pU2ep/4QF9sSMszx5GrN7OyyiZtgYqdfzjVp 1/FNAxEWCqj5PvuReRgh766eMH/vXeqMYROh9kccBCLEU7qigISFk3C4uwY9tlg6egQo 22S1XBGs/x5+yMS/VF4aC1CteRl1CcgwwBjjLfhgqZPejq4LNrImBNUIudQLEfRksAM8 jAzdvSsDbxNl79WfYhkfhi15PY4IV5Fq8zt3Cw9TGLIRW71+WqP12YqmXP6WF+Obi09G tOGZ2WxRrbho1mQw2drTN/OA+LWycDF8uoPsw/i2Cgsz6EvXCMvf3vNwWYYXpZNu9BKZ ipgQ==
X-Gm-Message-State: AOAM530jJ+UcRir+2Sr8s67Nx82zkv1QUBJEBMHrTy4FYakU4PY2IJHd jCj7u6Qc2WbBzQJEO8wIKm7eN0CSyw9W3EMAEPY=
X-Google-Smtp-Source: ABdhPJyeem+X62Z/KSp3m5ah/dvr4TXX4Q0PkIgQ3SYvlP0NOC8r2P/tpvey3M5IKO8KsQE3cUsv9S93m68890uli5c=
X-Received: by 2002:a2e:b88c:: with SMTP id r12mr5256363ljp.266.1591911706638; Thu, 11 Jun 2020 14:41:46 -0700 (PDT)
MIME-Version: 1.0
References: <CAKcm_gMVc88xpkOMmV7L-ybVCBzw+LhNS6Jw3=iB2gutR0ZhxA@mail.gmail.com> <1520992FC97B944A9979C2FC1D7DB0F404E7D60D@dggeml524-mbx.china.huawei.com>
In-Reply-To: <1520992FC97B944A9979C2FC1D7DB0F404E7D60D@dggeml524-mbx.china.huawei.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Thu, 11 Jun 2020 14:41:34 -0700
Message-ID: <CA+RyBmXDuf45wFfoKV6hqkXQUTGjtyVLafrrAB6kJdHRshx7Nw@mail.gmail.com>
To: wangyali <wangyali11@huawei.com>
Cc: "ippm@ietf.org" <ippm@ietf.org>, "xiao.min2@zte.com.cn" <xiao.min2@zte.com.cn>
Content-Type: multipart/mixed; boundary="000000000000c9f12f05a7d5d3e9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/_uZ2YryJQm0dosXmdJ9zgyqBrWM>
X-Mailman-Approved-At: Thu, 11 Jun 2020 14:51:34 -0700
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: Thu, 11 Jun 2020 21:41:59 -0000

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> 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.

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] *On Behalf Of *Ian Swett
> *Sent:* Saturday, May 23, 2020 5:26 AM
> *To:* IETF IPPM WG (ippm@ietf.org) <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 with your reviews and comments.
>
> Thanks,
> Ian & Tommy
>