Re: [ippm] [spring] Active OAM in SRv6

Greg Mirsky <gregimirsky@gmail.com> Wed, 26 January 2022 23:01 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 73F513A2650; Wed, 26 Jan 2022 15:01:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 1swDdEhT6WHT; Wed, 26 Jan 2022 15:01:34 -0800 (PST)
Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) (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 06CD93A2652; Wed, 26 Jan 2022 15:01:33 -0800 (PST)
Received: by mail-ej1-x636.google.com with SMTP id me13so1668898ejb.12; Wed, 26 Jan 2022 15:01:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pj3dNI1qMy2keLgxu00MDWPnSRn2sjJniUSCLUA2ito=; b=L/zWoHB/WhSSOhBdiEIq5lCljoCr2mgVYtUT/Y8HPGST9/y8epNCszfgFgqsrjJHpE 1j7XWLWkkATAg9KIszzzZKLMT/WFTCkhO6pcnJXQYja//bI7Mn0iE2ZuNP/IJhMzrwGx H5gVsc9i3dOxvQxVlHy3K4Qp5zE4ZuXyBphaZisF6BlNuMASNAVWqOSxMWPtlpunc0JI cZCw05/i99uXW9N6WNxZGZ+6VhJiD8tCvMJ6lmcgPXqu4SuQ5m4PcJPMbmQNzFE2RQCz w1vUpdyIIkG3k6azVSBISj8/FrVyuo60yR/DBWPV/2jHQEjRjJiJp2ze/xXZ6LUstKAZ Y7yg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pj3dNI1qMy2keLgxu00MDWPnSRn2sjJniUSCLUA2ito=; b=FKPl0h9CkSKUCp8CEq6eFOBdg16olT+F2pxB95fMOd1AUmac4N8B+fc7/z/Ld3xmx6 T1za7HBc/xUD9r8uWYraEIesL0Cw1VM7OvcrPsIS2dHI9/z4Yrs9mQ77aov16QTUY5NF ooqHYibplVBTSMbrqN2rLVLaRaw23ueN6TQW7yldDiU9ANMVoL/vJvtN+PoN1iUub/AP vJ4laaevK8hJzFOC9FFowmSvEgoxEJ2Bb0k4n9RiGbmxjGBuLbKcYp+MQG4CPgG9edtS fMz0GvkKJFKzaIeZVJElGHyUbg02+/p8nO8qtHtj7XRGipVQ8zAErnYT2bKn/J46QEKZ 5gGQ==
X-Gm-Message-State: AOAM533qxOBAG8Pf3U8KzeVkHnWCHJgjFdrMFWwGmPgZbSwgiJ2OBjIf mQyapc3rPz/dW+VlWM3xeo7onbSBYTDy9DFj/1px6ZdVR9M=
X-Google-Smtp-Source: ABdhPJxFeylXyTRO1ckOwpLAov+gr+NkJoW17qp8CP1jZnDDXdnb9ph9vla0MZtLr1rtyUk6NRGMPY5mojAAAXhDSJk=
X-Received: by 2002:a17:907:1614:: with SMTP id hb20mr725670ejc.255.1643238091099; Wed, 26 Jan 2022 15:01:31 -0800 (PST)
MIME-Version: 1.0
References: <BY3PR13MB4787D2E50FA60705DF306FD19A209@BY3PR13MB4787.namprd13.prod.outlook.com>
In-Reply-To: <BY3PR13MB4787D2E50FA60705DF306FD19A209@BY3PR13MB4787.namprd13.prod.outlook.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Wed, 26 Jan 2022 15:01:19 -0800
Message-ID: <CA+RyBmWDiBQfMrHHdqyVf_oi7dMW-sLrv2DF0RQLfXO47j=Bvg@mail.gmail.com>
To: Haoyu Song <haoyu.song@futurewei.com>
Cc: "spring@ietf.org" <spring@ietf.org>, IETF IPPM WG <ippm@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b3b81505d6842e52"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/-0DBN5Q8c3yz4Qu0wZx6-DhEEUY>
Subject: Re: [ippm] [spring] Active OAM in SRv6
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, 26 Jan 2022 23:01:39 -0000

Hi Haoyu,
thank you for bringing the topic of Active OAM to the discussion. As the
concept of Active IOAM is introduced in the IPPM WG draft
<https://datatracker.ietf.org/doc/html/draft-ietf-ippm-ioam-flags> it seems
to me like adding the IPPM WG community to the discussion is the right
thing to do.
Please find my notes in-lined below under the GIM>> tag.

Regards,
Greg

On Wed, Jan 26, 2022 at 2:37 PM Haoyu Song <haoyu.song@futurewei.com> wrote:

> Hi SPRING WG,
>
>
>
> Real time monitor on every node and every link on a network is necessary
> to detect  gray failures, which are the key culprit for poor QoS but hard
> to catch. SR provides an ideal mechanism, when working with some efficient
> planning algorithm, to achieve that with low cost.   Our proposal SRv6
> In-situ Active Measurement (SIAM) suggests a simple  active measurement
> approach which can support different
>
GIM>> I wonder what gaps you find in the existing active measurement
protocols, e.g., STAMP and RFC 6734 (would be more convenient to use an
acronym). It appears to me that, for example, STAMP and its extensions,
including the SRPM draft
<https://datatracker.ietf.org/doc/html/draft-ietf-ippm-stamp-srpm>,
comprehensively address the PM OAM requirements for SRv6.

> options of IOAM and other OAM methods in SRv6, without needing to worry
> about the extension header issue.
>
GIM>> draft-ietf-ippm-ioam-data classifies IOAM as follows:
   In terms of the classification given
   in [RFC7799] IOAM could be portrayed as Hybrid Type 1.
Does your proposal change that?

>
>
> Your comments, questions, and suggestions are very welcome. I’d like to
> know your opinion if you think this work is in scope and should be adopted
> by the working group.  If you are interested in contributing to this work,
> please also let me know.
> https://datatracker.ietf.org/doc/draft-song-spring-siam/
>
>
>
> Thank you very much!
>
>
>
> Best regards,
>
> Haoyu
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>