Re: [netconf] Adoption poll for draft-tgraf-netconf-yang-notifications-versioning

Andy Bierman <andy@yumaworks.com> Tue, 16 May 2023 12:12 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 A987CC05E050 for <netconf@ietfa.amsl.com>; Tue, 16 May 2023 05:12:21 -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_DNSWL_NONE=-0.0001, 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=unavailable 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 KZNDwcOplQMD for <netconf@ietfa.amsl.com>; Tue, 16 May 2023 05:12:15 -0700 (PDT)
Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (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 DE708C15106C for <netconf@ietf.org>; Tue, 16 May 2023 05:12:15 -0700 (PDT)
Received: by mail-lj1-x22c.google.com with SMTP id 38308e7fff4ca-2ac770a99e2so149753471fa.3 for <netconf@ietf.org>; Tue, 16 May 2023 05:12:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks.com; s=google; t=1684239134; x=1686831134; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=6ANCpZDvwU4BWL4BP9lIvEHh3vbvZBQEly52r6kJ+ao=; b=Flm/8RbYpj9mNB4J+gYFEf/cP2wJSA1hoCMyCmtjuuVW8PlYJb74heG8+k0JLIQ25O 0ZMZ/k6/s9yWL/j0wKke9xfjC19LN2cdKUQm6k0iBzedqaGi7LmPwjOkWKlChJhk7fF2 HZ4cEOk1BjVfNc2loIAvxoj4SRGSuGdWXFxKF2iWRAz1POr1Sq8bQ5A48Y0JiD5YZax8 UjtGpjb56IRTWW0ePJoSUZmSdcV7TzPo6C+NnGkcwLE3i6UhmeSsRUm2Nu2JDEd4XMB+ WaIR7o1S/Wj25s85VpRf3zXvbvtwCn0vfRI+zSsfQr4f8rl6WR5RRWzphgIgj5kJL3JD 8nsw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684239134; x=1686831134; h=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=6ANCpZDvwU4BWL4BP9lIvEHh3vbvZBQEly52r6kJ+ao=; b=BJcVb/TF4FdBxsTsjhbx5lQMNUmc1x2bMhG5Fv2NFR0wAr2PqjiKax668FTTLp/nIw Wd33iRvbYMS54BwvrYqJ+ZKWg26DmCwGZW1XvMrBM69dHbRy170YeuTHOio9DgbVZz0D LP0dTB8jeXzLUrncMjqhUdxN1fcSPMcQ1hpyglgZQIZB6DEdRm/Jv82+Cp8kpSOP4Clb LwlgyK20Mk6Egg0se+8drBrEXdHY7f8WxJjR8jhI4mNEilZDne+FIP7W1QvlBpCI1DZt SMChs/Xcpp9KmlJyF/5RdG/DeU9W9/+hjfe+GNg3GsdprutUeHGsmnuNnGYUQaf8yi6L wJ7g==
X-Gm-Message-State: AC+VfDzsBJtPwDC0c1rXOTFI4Xh3kZC9HtOhF0eORu/6Ju/NmAgJS2BM 5sV9aLoufjHlYI/g3nQ514B9g9i2ox+XPMY2ecFxlJOVbnDrcnvG
X-Google-Smtp-Source: ACHHUZ7rklx00CtaJDOJofOlsgHN0x+n2AbWdToO0BUVWgJ5obXoksNJ6l06snCY0wRPkwWmJ6akL1n9ARoS/yFJGvs=
X-Received: by 2002:a2e:b2d4:0:b0:2ad:94cd:3cb7 with SMTP id 20-20020a2eb2d4000000b002ad94cd3cb7mr8067996ljz.51.1684239133591; Tue, 16 May 2023 05:12:13 -0700 (PDT)
MIME-Version: 1.0
References: <E78B3C0B-B415-4E8C-9080-ADFB69D4464E@gmail.com> <h5euo22hv6poh6hdomcdbdbgomrwrkbqwauwvlf3yhnriuqvaa@v4xmvx5ikonx>
In-Reply-To: <h5euo22hv6poh6hdomcdbdbgomrwrkbqwauwvlf3yhnriuqvaa@v4xmvx5ikonx>
From: Andy Bierman <andy@yumaworks.com>
Date: Tue, 16 May 2023 05:12:02 -0700
Message-ID: <CABCOCHRjkS4UCCyqAJfgr+Z9Yv=COOVg8K5nwcM680mTpzt3Eg@mail.gmail.com>
To: Jürgen Schönwälder <jschoenwaelder@constructor.university>, Mahesh Jethanandani <mjethanandani@gmail.com>, netconf <netconf@ietf.org>, netconf-chairs <netconf-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004661bd05fbce7b59"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/uuaEP7KpLM-66JoTK_JN2vM2bi8>
Subject: Re: [netconf] Adoption poll for draft-tgraf-netconf-yang-notifications-versioning
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 16 May 2023 12:12:21 -0000

On Mon, May 15, 2023 at 11:17 PM Jürgen Schönwälder
<jschoenwaelder@constructor.university> wrote:

> So here we go. The change from (module, path) names to (module, path,
> version) names will trigger a series of followup works, like this one.
> Adding version numbers to how we name things is a fundamental change
> of YANG and its protocols (and people still pretend this change can be
> done without even changing the YANG version number).
>
>
I need to re-read the details in this draft, but it did not appear to work
with current YANG library restrictions.

Some obvious questions arise:

1) The YANG library allows ONE implementation of ONE revision of each
module.
How can the server have multiple implemented revisions of each module to
choose from?

2) The server decides (via operator configuration) which revisions of which
modules to use.
How can the client override this configuration by selecting filters?

3) If a client can request different revisions of a subtree for Push,
what revision do they receive if a <get> or <get-data> operation is done to
retrieve
that subtree?


I doubt that fixing things piecewise is the right strategy but I fear
> this is where the IETF is heading. The result will likely look like
> some patchwork glued together by some implementation specific bits and
> pieces.
>

I would prefer a coherent evolution of YANG (e.g. YANG 1.2) but that does
not appear likely.



>
> /js
>

Andy


>
> On Mon, May 15, 2023 at 01:42:14PM -0700, Mahesh Jethanandani wrote:
> > All,
> >
> > This is start of a two week poll on making
> draft-tgraf-netconf-yang-notifications-versioning-03 a working group
> > document. Please send email to the list indicating "yes/support” or
> "no/do not support".  If indicating no, please state your reservations
> > with the document.  If yes, please also feel free to provide comments
> you'd like to see addressed once the document is a WG document.
> >
> > The poll ends May 31.
> >
> > Mahesh and Kent (as co-chairs)
> >
> >
> >
> >
> >
>
> > _______________________________________________
> > netconf mailing list
> > netconf@ietf.org
> > https://www.ietf.org/mailman/listinfo/netconf
>
>
> --
> Jürgen Schönwälder              Constructor University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   +49 421 200 3103         <https://constructor.university/>
>
> _______________________________________________
> netconf mailing list
> netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
>