Re: [ippm] Call for adoption of PM on LAG

Greg Mirsky <gregimirsky@gmail.com> Fri, 09 September 2022 06:50 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 218F2C14CE29 for <ippm@ietfa.amsl.com>; Thu, 8 Sep 2022 23:50:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.094
X-Spam-Level:
X-Spam-Status: No, score=-7.094 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_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 877kKbPK0PLI for <ippm@ietfa.amsl.com>; Thu, 8 Sep 2022 23:50:29 -0700 (PDT)
Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BF70C14CE28 for <ippm@ietf.org>; Thu, 8 Sep 2022 23:50:29 -0700 (PDT)
Received: by mail-lf1-x12b.google.com with SMTP id f14so144574lfg.5 for <ippm@ietf.org>; Thu, 08 Sep 2022 23:50:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=th3fiNSPoVKiUcrKCe/Kj+gqWzEe1CtIPox+sb6pMEg=; b=DiGzVg1e3DRia4M0Gn140x8M7WyD0+7o2EBpiEVsg1YaW65ZCfSsKolnCQLIyNi/xl aSGsaLTrAAe6QK2HnzhvTnGUHybQ3PVin1X0DyI+H8hN20MizWBU7dwOXXA1qeOcRKBI 9H+KJW9jIo6kmim3phk2WxfA7GS2+Gzn5KGr0e0iknmiYh0p6Mz6hPINtgpiJlaqCj+A hNenzTwix+pBUxOg1L5+dnUDdJfezWFHX0Co+WvglavBG4CShDd4GpRkhybCybhrjdOK yZneKKGAwWvd0JVs8d3Wur5d+H371TmZclgyCKL/ScJoQXahMGP/01EeTv+6h377O1if xkog==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=th3fiNSPoVKiUcrKCe/Kj+gqWzEe1CtIPox+sb6pMEg=; b=cbKtxiF3WieX4Pt7IjxtyLRc818QeRUW24/JItmqYZtPKceEbKkoFnGdwzhzhBLICw fh53rdLSx0c1WxPcd9yvOkQSlcIF9+gdIh8HnPT3WA9BGQ5HFdWiaJjq+Q40IwQ+R3LL X2rSBED3IP2InrkRHAAqgoZIRDTfeHMkS+Ek63bI94aFL0ONioBC8yzhOe7l0Gxb709V fkSz+iHF7AquMY+z/19GuVYutF5Eq+AA0Wjomj0yx4VjTbn5iQRmKrClxQeuk7J5rD9H CKp7d7BmS+llYPLhbbX9//MpM3JfzvDQOoyWqkzzn3KK8D6WF53LiB0WVJzF8BPt4LxF 2SYg==
X-Gm-Message-State: ACgBeo3IM63Iugq5wkP1z+7/25HxRbE2ZoZMDx3zUbVzEXuJX8hsY3Ki 8qtn24g34KJuFyAB4ikV5j7YP2dqr89WTwOLHIKWA+23rQc=
X-Google-Smtp-Source: AA6agR7hgWBd8FnJcOov14nXGi29/v12Trrw509Gg5SQC2Q2IpUTbR5LGfhCremPH04MULTmNiiXSEbttwNKl99g2F0=
X-Received: by 2002:a05:6512:33c9:b0:494:79c1:8ea1 with SMTP id d9-20020a05651233c900b0049479c18ea1mr3719292lfg.26.1662706227296; Thu, 08 Sep 2022 23:50:27 -0700 (PDT)
MIME-Version: 1.0
References: <AM0PR07MB4131BFFD304468FA4CCD0484E27B9@AM0PR07MB4131.eurprd07.prod.outlook.com> <2022090717491209387539@unitechs.com>
In-Reply-To: <2022090717491209387539@unitechs.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Fri, 09 Sep 2022 08:50:15 +0200
Message-ID: <CA+RyBmVc5skSwJK2Y=xqFkEgmHj5iQ+DgEur7EUBpPNmOYQwCA@mail.gmail.com>
To: Lu Yunyang <luyy@unitechs.com>
Cc: Marcus Ihlar <marcus.ihlar=40ericsson.com@dmarc.ietf.org>, IETF IPPM WG <ippm@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000b3f4e05e838f66a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/32egC9ns1BSfEynd1U9BSsa9B30>
Subject: Re: [ippm] Call for adoption of PM on LAG
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: Fri, 09 Sep 2022 06:50:33 -0000

Hi Yungyang Lu,
thank you for supporting our work and your thoughtful questions. The
scenario you've presented is realistic and we believe that our proposal can
address it. We'll describe handling of this interoperability scenario in
the future version of the draft.  Please find my notes in-lined below under
the GIM>> tag.

Regards,
Greg

On Wed, Sep 7, 2022 at 11:49 AM Lu Yunyang <luyy@unitechs.com> wrote:

> Hi WG,
>
>
>
> I support the adoption of these drafts. PM on LAG could solve some
> essential problem for provider and enterprise level network operation.
>
>
> Besides, I think it's necessary to add some clarification for
> interoperability betweet STAMP and TWAMP-Light, as those stated in RFC8762.
> Several issues should be considered:
>
> 1)  whether STAMP sender / TWAMP-Light reflector and TWAMP-Light sender /
> STAMP reflector combinations can be used for PM on LAG.
>
GIM>> I think that both scenarios can be supported, although that would
expect more from STAMP implementation as well as more configuration by an
operator to use STAMP-TWAMP Light interoperability principles described in
Section 4.6 of RFC 8762 <https://datatracker.ietf.org/doc/rfc8762/>. As a
result, each of LAG member links will be configured as a separate test
session.

> 2)  any protocol modifaction or restriction for such measurements.
>
GIM>> It seems like this scenario would require more operational effort but
without specific protocol extensions. What do you think?

> 3)  other considerations that may involve, like security and compatibility
> with other TWAMP / STAMP extensions.
>
GIM>> Thank you for this suggestion! We'll certainly work on adding text
addressing security and interworking with other STAMP extensions.

>
>
> Best regards,
>
> Yunyang Lu
>
>
> *发件人:* ippm <ippm-bounces@ietf.org> *代表 *Marcus Ihlar
> *发送时间:* 2022年9月2日 00:44
> *收件人:* IETF IPPM WG (ippm@ietf.org) <ippm@ietf.org>
> *主题:* [ippm] Call for adoption of PM on LAG
>
>
>
> Hello IPPM,
>
> This email starts an adoption call in the IPPM working group for the
>  draft-li-ippm-stamp-on-lag and draft-li-ippm-otwamp-on-lag documents.
> These documents extend STAMP, OWAMP and TWAMP to support performance
> measurements on member links of a Link Aggregation Group.
>
>
>
> The first draft specifies an extension to STAMP and can be found here:
>
> https://datatracker.ietf.org/doc/draft-li-ippm-stamp-on-lag/
>
> https://datatracker.ietf.org/doc/html/draft-li-ippm-stamp-on-lag/
>
>
>
> The second draft specifies extensions to OWAMP and TWAMP and can be found
> here:
>
> https://datatracker.ietf.org/doc/draft-li-ippm-otwamp-on-lag/
>
> https://datatracker.ietf.org/doc/html/draft-li-ippm-otwamp-on-lag/
>
>
>
> Please reply to this email by *Thursday September 15*, to indicate
> whether you support adoption of these documents.
>
>
>
> BR
>
> Marcus & Tommy
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://www.ietf.org/mailman/listinfo/ippm
>