Re: [netmod] WGLC on node-tags-09

Andy Bierman <andy@yumaworks.com> Wed, 19 April 2023 18:39 UTC

Return-Path: <andy@yumaworks.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34C21C14CE22 for <netmod@ietfa.amsl.com>; Wed, 19 Apr 2023 11:39:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks.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 TKqBZZWex1Fz for <netmod@ietfa.amsl.com>; Wed, 19 Apr 2023 11:39:04 -0700 (PDT)
Received: from mail-pj1-x102b.google.com (mail-pj1-x102b.google.com [IPv6:2607:f8b0:4864:20::102b]) (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 93618C14F736 for <netmod@ietf.org>; Wed, 19 Apr 2023 11:39:04 -0700 (PDT)
Received: by mail-pj1-x102b.google.com with SMTP id 98e67ed59e1d1-24782fdb652so37586a91.3 for <netmod@ietf.org>; Wed, 19 Apr 2023 11:39:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks.com; s=google; t=1681929543; x=1684521543; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=JpdzxJdtMXR6TzfVa4GCfWU21ChGNlduvH7BOge22xI=; b=NhF/4il/zEL/zNoY9LxF1HDceTMNoKANxaY3v+PcpHJ1qb8g5Xwc5HL2E6VHILFGtT PKSEihvjI12L2xG1+MfIC7fsw/hN2zGof47ZqAP7iYNt5coDq5K/e+N0ChMntA5ECjdo Y6ZCr6BScCTmBRd3yg6+pURW3/oB7wOJyqy495/c5kBrjsQYNX69ntEFjJ2cPPjehQZ7 OdsEf7G9rVzvkoWkmdChoMmSiP5Ho9VAqRxUdVnOs3PlMbPfUVzR1SX4xQWEYHnEshrQ Nx/LsODpyrmYeCVNzoOk23tnYLuOg4dIYO79V7igrMoTUNLiMEQDcwyICB02XUhxsw/d sFJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681929543; x=1684521543; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=JpdzxJdtMXR6TzfVa4GCfWU21ChGNlduvH7BOge22xI=; b=h1JUovDwaJu9U87sBzc0dhoVk7axUdGV4j4fSPr8QoQrz3xByJGE6mIt9D/5mTxP4p npr53x0bKJRks5joW5S0oZ3oAuAin2ItmNR3LD3wSQlj44Umb8hmzyGxU44OUHjvP8M3 rR6GV7B/H9ro6XGM7CrSaGnDsrBSDYFp2Tl0v7N7jA7OHtcmee3fpHWh40rbkqhfyvph a41m0KxCIoGOjVDChPUl9fzfqzTjJV6fCoUQp5jvB48qdJApWHXEc2T3rZwN2Ja7hvsK 5cZkLCLmpSgqYTJiJg9X656BPD3KwhhsoHWs5B05nWAaLKOa931cHURomeUbAzXa2nGx 4ozg==
X-Gm-Message-State: AAQBX9eBxgngqVIXuUxo8+Se3TmFJGIbvWGMN7r+v99PO3cwpAxloI1Z M6JWvywBLURItiXSgVqLgF4skL26J1S0QphH6pBCX02bvrYYe6U+
X-Google-Smtp-Source: AKy350YyI5F3pmAOhtKEqaUl7pZjp5kBZu1VHmTGZ7yq+CqAEODMPnb8xoSxE/weGQX1s6a+NcbatoI6OLRup2A/F6M=
X-Received: by 2002:a17:90a:6fe1:b0:23d:29c7:916f with SMTP id e88-20020a17090a6fe100b0023d29c7916fmr3567818pjk.32.1681929542337; Wed, 19 Apr 2023 11:39:02 -0700 (PDT)
MIME-Version: 1.0
References: <01000187973d01c1-3045965f-faf7-4f2d-a7fa-48283d42eeec-000000@email.amazonses.com>
In-Reply-To: <01000187973d01c1-3045965f-faf7-4f2d-a7fa-48283d42eeec-000000@email.amazonses.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Wed, 19 Apr 2023 11:38:49 -0700
Message-ID: <CABCOCHRyNb4ZbFxpr4awKj_m=An188OB0dO86nXLNSfPEfDTJg@mail.gmail.com>
To: Kent Watsen <kent+ietf@watsen.net>
Cc: "netmod@ietf.org" <netmod@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e8a31705f9b4bc08"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/4PFtQXwOuNP4KSP46ymIaY_FCuQ>
Subject: Re: [netmod] WGLC on node-tags-09
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2023 18:39:08 -0000

On Tue, Apr 18, 2023 at 6:59 PM Kent Watsen <kent+ietf@watsen.net> wrote:

> This email begins a two-week WGLC on:
>
>
> https://datatracker.ietf.org/doc/html/draft-ietf-netmod-node-tags-09
>
> Please take time to review this draft and post comments by May 2nd.
> Favorable comments are especially welcomed.
>
>
I have read the latest draft and IMO it needs more work.

1) metrics

The identities to represent system tags are quite vague.
There are no specific guidelines for selecting the correct tag.
There are no references to other RFCs for the metric definitions.
I would expect IPPM WG to define the classification system, not NETMOD WG.

2) System tag procedures

There are no procedures defined for YANG model developers.
Are they supposed to add a node-tag extension to almost every leaf in the
module?
The administration and maintenance of node-tags will be a huge burden.
That was one reason they were not added to the module-tags module in the
first place.

The YANG extension itself is under-specified since it offers no guidance on
which YANG statements are allowed to have this extension as a sub-statement.

IMO all the metrics (tag type identities) should be removed from this
document and moved to separate work
that is properly defined using IPPM metrics.

3) YANG module issues

- what module entry is used if the node is from a module that augments
another one?
   I would assume the augmented module not the base module.  Specify which
one

-  nacm:node-instance-identifier as a list key is complex to implement
   - not sure a canonical representation is possible or required
   - syntax allows notification and action nodes to be tagged. Are these
allowed in thislist?

-  it is possible for multiple 'tags' entries to represent the same data
node instances.
   Figuring out precedence and enforcing masked-tag rules seems complicated.
   NACM has ordered by-user semantics.  This module has "all entries at
once" semantics.
   Not that easy to implement or deploy.

- What if a tag value appears in the masked-tag leaf-list that has the same
value as the 'tag' key leaf?

- the indentation in the YANG module is wrong for masked-tag

- the list and key naming (tags/tag) is not consistent with other IETF
modules .
  Maybe should be list tag and key leaf id.



Andy



> This draft went through a WGLC a year ago.  The authors addressed the
> comments received and have been were waiting for feedback.   In essence,
> this draft is presumed to reflect WG consensus and thusly, if no objection
> is received, the draft will move to the next step in the publication
> process.
>
> Ref:
> https://mailarchive.ietf.org/arch/msg/netmod/n2P9yohA-X-xSIt6FlMr4wOqmuI/
>
> Kent  // co-chair
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
>