Re: [ippm] Call for adoption: draft-zhou-ippm-ioam-yang

Dhruv Dhody <dhruv.ietf@gmail.com> Thu, 12 November 2020 13:51 UTC

Return-Path: <dhruv.ietf@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 A55A63A0ED2; Thu, 12 Nov 2020 05:51:44 -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 bC9KQw51TxBI; Thu, 12 Nov 2020 05:51:42 -0800 (PST)
Received: from mail-il1-x133.google.com (mail-il1-x133.google.com [IPv6:2607:f8b0:4864:20::133]) (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 CEFF63A0ECB; Thu, 12 Nov 2020 05:51:42 -0800 (PST)
Received: by mail-il1-x133.google.com with SMTP id y9so5320207ilb.0; Thu, 12 Nov 2020 05:51:42 -0800 (PST)
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=mBd3zCmlpwErhpUYFF/oLMRp/Lg0z/CUiTjuQhC50ic=; b=KdAN43bXNyH7PCUHUfhynzxifbgsgnlYNQrLd39yg1YhbjrTqSHu/giFF1yhIGV4k1 MI99G0aGzwibVcqNFmU9te5Q3D05TKzIch5G3smlDmemlOyC3mEmgw9t8k1of05cq3fS ctZM19zERwfkos1I31Aj4R+9wbfu5LdnTEedoPtM5xVadTBZ2DfAfP2XipS5XNVlypzA TJHCtYBOHMKCyEUFTbH4kLS8p/hEt0cQfxNKSCb69I5xeMISIDk2fuEeaJHDdvsOhrTo U8gbMMH+BqzMdjLwSyJ5uHoYKooOnutJwOwV++XoNX0SyKFkPNh1wRTLEtkVYqkPviIP Ymgw==
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=mBd3zCmlpwErhpUYFF/oLMRp/Lg0z/CUiTjuQhC50ic=; b=RTXF6azXYcPhWCD0VGsQcNOBhAqjLsIdUrJ+0oGXk4huhTtqWUIdJ/vMUO7GCsw83k 0UiSEocueTvWyNNTqRW2nIOoe+/o03x77OHckbIR1M16t5Wu1bzIoL2hAcG99a4i69Sz nEIwLABkz1IR9nlQu45po2FErV50wv9P4ZVR+cE8FYlVxYvF9wZLRH+QT+kmcZh7GUTm CtPvviiHWWGQNCl+ConpZRtijKih1XSr/tnV9lgtBu0RdBXOYLehnSkEfoiJE3Prxvgs 12PIHBOI4daZTbCdaUr9lFsxWGBP1lrLUnADbNV71HyzobrYsAMREZ/OlcPp8zxD7VYz thmw==
X-Gm-Message-State: AOAM5321xt55nS9R3MKdp9UQCVKhrVaqGTG0m92810aeBCrJeM8heyBn Mmx5oNHv7dckvXPy900jhIAqA6zgilh56Q2WdL4=
X-Google-Smtp-Source: ABdhPJzbz6TKRyw6Nvr4WNLTZ6ykWDuomJGAD0NbUBUDC5SibxcbwoEFyJmTW7RNak0lbdX/icvEofzc55j77qCGw5w=
X-Received: by 2002:a92:cc52:: with SMTP id t18mr13320271ilq.124.1605189101815; Thu, 12 Nov 2020 05:51:41 -0800 (PST)
MIME-Version: 1.0
References: <43DADFB5-FE8A-49A1-BF39-1ECC10594211@apple.com>
In-Reply-To: <43DADFB5-FE8A-49A1-BF39-1ECC10594211@apple.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Thu, 12 Nov 2020 19:21:05 +0530
Message-ID: <CAB75xn4NP8T_P-icT1qz+Nvxra6f2of8zZew1Ymvgzr2Hjb1Kg@mail.gmail.com>
To: Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>
Cc: "IETF IPPM WG (ippm@ietf.org)" <ippm@ietf.org>, IPPM Chairs <ippm-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000360c8105b3e93686"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/VCBA9NgzBboINteMZZKkVljLVbw>
Subject: Re: [ippm] Call for adoption: draft-zhou-ippm-ioam-yang
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, 12 Nov 2020 13:51:45 -0000

Hi WG,

I support adoption of this YANG draft. A few high-level comments -

- Currently all 5 profiles can be configured at the same time in a single
ioam-profile (as each of them have a separate container of their own). Is
that intentional?

- Can I configure an ioam-profile that is applicable to both IPv6 and NSH?
The current yang model would force me to create two separate ioam-profile
and give them different names!

- Currently ACL is the only way to identify the flow for which the IOAM
profile needs to be applied. Think about how this could be used
alongside SR policy YANG for instance. Maybe a generic grouping that can be
used to augment SR Policy? Not sure how to make it work with the current
filter-type.

Hope these comments help to improve the YANG module!

Thanks!
Dhruv

On Sat, Oct 31, 2020 at 12:11 AM Tommy Pauly <tpauly=
40apple.com@dmarc.ietf.org> wrote:

> Hello IPPM,
>
> This email starts a Working Group call for adoption
> for draft-zhou-ippm-ioam-yang. Now that our IOAM documents are mature and
> progressing, the chairs believe it is time to consider the YANG work
> officially.
>
> The document can be found here:
>
> https://tools.ietf.org/html/draft-zhou-ippm-ioam-yang-08
>
> Please provide your feedback on these document, and state whether or not
> you believe the IPPM WG should adopt this work by replying to this email.
> Please provide your feedback by the start of the IETF 109 meeting week, on *Monday,
> November 16*.
>
> Best,
> Tommy & Ian
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://www.ietf.org/mailman/listinfo/ippm
>