Re: [netconf] Adoption-suitability for draft-tao-netconf-notif-node-tag-capabilities

Andy Bierman <andy@yumaworks.com> Mon, 10 August 2020 19:39 UTC

Return-Path: <andy@yumaworks.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBD6C3A0C86 for <netconf@ietfa.amsl.com>; Mon, 10 Aug 2020 12:39:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Level:
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-com.20150623.gappssmtp.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 qntXpVmTb6qm for <netconf@ietfa.amsl.com>; Mon, 10 Aug 2020 12:39:32 -0700 (PDT)
Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450: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 0704E3A0C99 for <netconf@ietf.org>; Mon, 10 Aug 2020 12:39:31 -0700 (PDT)
Received: by mail-lf1-x133.google.com with SMTP id b11so5354301lfe.10 for <netconf@ietf.org>; Mon, 10 Aug 2020 12:39:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dKWaU6PQG19x7RQ4BtJ5KVDemUyZFGlT497+i/br5Og=; b=VP5J/TW92AvjcIXeEyDNScx12TipeUieewZzrRKJmDTwBOhFPedEjncyaSmEXZisbb ErKcNp9Gl/zZx+nXsh05aWH3REoJ0+zOn/KURz2zwL2GzByp1NfvF3lVb7vd++/swpyP bX9qS0YzqPVUnNz0BAMaIa6Nn0Y88wkV2LOwfdvmn/bDnosRVCIEWUENwrDAipq48fQL pTB9cP893+1FDIwlKmusywNqSYP4gdKtFHMEKohNvgOdjbx0u5qSVRaEorOjuGwmcjUW uaQ5yp/tHgf8rbsYtOM0q0xTiZSnNJPujIdxv/yBTV0gE3lPsYfWD9CiKYB9+MGAmySj dWOA==
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=dKWaU6PQG19x7RQ4BtJ5KVDemUyZFGlT497+i/br5Og=; b=mMED4+9LOkefDu44/BKw23EiUb+eNK1zs566AUNQriKyF2NKfb40nE87REZGaLZ0M6 X50O0/VB8SgTJ/DexHpq8/QmUGD0O490MliXhNsuvt6rUap9njOIzOT8v2kXtbsG606D eau7BS09a6HDMvZ8+LkZ/GuVmmkDAOHZitc9pcao6oPIHJXUrF4MBQlUCo6zM+H+B3VF gRgoeFdgsynCsLBl+FahjXE5HCDoG5ckJeGLmLfygcAHwQrt5SUJULH0tlC0n2lQa6Za 4FNEVKHXTM/VcNuqZE/YImDHMDP5hMKAZ2fXN0wCSoiYnhIkTm50EmEgHCNLWqW4yP9Z /4gg==
X-Gm-Message-State: AOAM5302kBmflu6qDw57+rHCoyjOafq+bvZfXY0dM3xpO+BHkuUkmupE qod+ObrqA/aCQxgugqjOc8fXC7RtoTPfzTSfZvu37qVnTEg=
X-Google-Smtp-Source: ABdhPJw/oGYPLRXlPiLhmV6s1ad007FztCCNEx/2YgJYW8yjty7s6mR5e6J9AEL3g0IS6dosS5DWYCkbKscEaF//9VU=
X-Received: by 2002:a05:6512:330c:: with SMTP id k12mr1305236lfe.151.1597088369955; Mon, 10 Aug 2020 12:39:29 -0700 (PDT)
MIME-Version: 1.0
References: <01000173c0b39fd1-1bd0309b-e56f-4378-b33a-08e9b56a068c-000000@us-east-1.amazonses.com>
In-Reply-To: <01000173c0b39fd1-1bd0309b-e56f-4378-b33a-08e9b56a068c-000000@us-east-1.amazonses.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Mon, 10 Aug 2020 12:39:19 -0700
Message-ID: <CABCOCHSdHEosNT13v3O3vNGQKhfbF5aasf-RPgo7KxCxNcBDHA@mail.gmail.com>
To: Kent Watsen <kent+ietf@watsen.net>
Cc: "netconf@ietf.org" <netconf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f7714205ac8b1cf9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/IBzqg0ojESgzfjGxF-BzjLYkKDQ>
Subject: Re: [netconf] Adoption-suitability for draft-tao-netconf-notif-node-tag-capabilities
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Aug 2020 19:39:39 -0000

Hi,

I am trying to understand the problem statement in this draft.
It seems to be a way to assign various tags to data node objects.
It uses the tags type from ietf-module-tags, which implies that modules and
nodes
share the same set of tags.

There is also an assumption that the error/hints mechanism in RFC 8639 and
8641
do not work and this significant amount of proposed metadata could be used
to avoid
receiving an <rpc-error> for an <establish-subscription> or <edit-config>
request.

IMO the current approach is sufficient and new mechanisms are not needed.

Andy


On Wed, Aug 5, 2020 at 3:18 PM Kent Watsen <kent+ietf@watsen.net> wrote:

>
> NETCONF WG,
>
> Per the previous email sent moments ago, the chairs would like to solicit
> input on the following draft:
>
>    Title: Self-explanation data Node tag capability
>    Link: https://tools.ietf.org/html/
> draft-tao-netconf-notif-node-tag-capabilities
>    Abstract:
>
>       Before a client application subscribes to updates from a datastore,
>       server capabilities related to "Subscription to YANG Datastores" can
>       be advertised using YANG Instance Data format.  These server
>       capabilities can be documented at implement time or reported at run-
>       time.
>
>       This document proposes a YANG module for self-explanation data Node
>       tag capability which augments system capabilities model and provide
>       additional self-explanation data node attributes associated with node
>       selectors within per-node capabilities.
>
>
> In particular, please discuss adoption-suitability as it regards to the
> following questions:
>
>     1) is the problem important for the NETCONF WG to solve?
>     2) is the draft a suitable basis for the work?
>
>
> PS: this message is itself not an adoption poll, but rather an attempt to
> gauge interest/support for a potential future adoption poll.
>
> NETCONF Chairs
> _______________________________________________
> netconf mailing list
> netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
>