IETF Logo Mail Archive

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

Andy Bierman <andy@yumaworks.com> Wed, 17 May 2023 17:27 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 27959C1516E9 for <netconf@ietfa.amsl.com>; Wed, 17 May 2023 10:27:13 -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 2z_S8AhJmLFf for <netconf@ietfa.amsl.com>; Wed, 17 May 2023 10:27:09 -0700 (PDT)
Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) (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 15F66C151099 for <netconf@ietf.org>; Wed, 17 May 2023 10:27:09 -0700 (PDT)
Received: by mail-lf1-x133.google.com with SMTP id 2adb3069b0e04-4f004cc54f4so1329575e87.3 for <netconf@ietf.org>; Wed, 17 May 2023 10:27:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks.com; s=google; t=1684344427; x=1686936427; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=B9yBZXgn9HPhSR9lVeG+RmxptWRuLM384Vyo+7EzeUQ=; b=azAd/xqM9Fe7Gt8Sqzz+oM0fMdW1DWjeoFVP0R11rkxaMcpruhsNUc+M2V4Wfu/xLP o190O0Kbr0+dzif2N0S+TxL6M22Dmwabo1DaLsqyDOJI5oQZynNtbPcjTy9ezY4nM5uj Q8QGk5/stgeJmPqTPGyHNWrfRS9oG6xhOA+Q0EReCmswcxtmszNNNEMQugPTONshuAbQ WQW/W9p6Ks2+KHB+X+PkHZ46owQ2O9nkM1y+WvJc5JkChDJ49AD2HNnVyhmpgU9J9WSS cw+5zp2yJl+b1e4hEtqurv9LVfyKZI4cQC9RrJUorBKHFszhDf+2lubpZNXGukUZmqy7 nXmw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684344427; x=1686936427; 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=B9yBZXgn9HPhSR9lVeG+RmxptWRuLM384Vyo+7EzeUQ=; b=dJkNlv5/k8dENr8TX5GFI2wdSAnIbXzH65p2AKU/UpF2lC39FsnY6ZkvXkJZKz1nQg 3DksNQuWkJlMHvB2rdvlwRq9gD0nhrTGiZ4VE3wlPFVk2YYtnT15ou1skyTkU1MHEkyI 0LpbygTezEObVEtgNgiwpc5Hba1ctuHrJxdPFdXYmlocxGS2BwXYAaj65rCDe+gLoXWl 7FQTkzRbj4MAMrUyw9r5ej/Ks51nHgOuop/zZTs8ZFXqNSG+HP78XRaOpS0L3rjP7Npq 58kzL5scXHALLzWNEdG9l5Lm9B5PSJcS9MlIHgM20qRNBTCtbl5sLcQhqBcAeGFMX0mh MLeQ==
X-Gm-Message-State: AC+VfDw1OhLonv7u5VUVHu4/xyI75n+Co5hUJ4/3ksnTvJwL1/ZZOgnz NmIF0sNWwN/gZ/MY+l0qCcZ9D/HKECgvEbO38crE/Q==
X-Google-Smtp-Source: ACHHUZ6EA8Bz+KKRy3OFtCOfpksHl2nxj8Yo1WdCVtRo4toMIHPdUmvARUcmBAxIP7st4d2ITUNaWSfNr2+0ylX2erk=
X-Received: by 2002:a19:7011:0:b0:4ed:d250:1604 with SMTP id h17-20020a197011000000b004edd2501604mr418277lfc.57.1684344426827; Wed, 17 May 2023 10:27:06 -0700 (PDT)
MIME-Version: 1.0
References: <E78B3C0B-B415-4E8C-9080-ADFB69D4464E@gmail.com> <AM8PR06MB776465A8890FA1FF944F7249957E9@AM8PR06MB7764.eurprd06.prod.outlook.com> <fxqbpxqt4uddzynsqu7nrphks4ffdbcet2s4mzgq5kjybc7h5r@34fjvmua6eva> <AM8PR06MB77647944C3C804FB22E38B50957E9@AM8PR06MB7764.eurprd06.prod.outlook.com> <ibonfs57tsr2ymul4wsns5jhpoiofkciz7zw27udzixtt7olrx@zh5p3tjohxoo>
In-Reply-To: <ibonfs57tsr2ymul4wsns5jhpoiofkciz7zw27udzixtt7olrx@zh5p3tjohxoo>
From: Andy Bierman <andy@yumaworks.com>
Date: Wed, 17 May 2023 10:26:55 -0700
Message-ID: <CABCOCHRmnOw_Tex1ixcyA=bjdHptHVyQ1nN1UKOfyC9nPqdxpQ@mail.gmail.com>
To: Jürgen Schönwälder <jschoenwaelder@constructor.university>, IGNACIO DOMINGUEZ MARTINEZ-CASANUEVA <ignacio.dominguezmartinez@telefonica.com>, Mahesh Jethanandani <mjethanandani@gmail.com>, netconf <netconf@ietf.org>, netconf-chairs <netconf-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003daafe05fbe6ff4b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/GZkzURB_kefbyOjzu8RjpIJM9i4>
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: Wed, 17 May 2023 17:27:13 -0000

On Wed, May 17, 2023 at 1:42 AM Jürgen Schönwälder
<jschoenwaelder@constructor.university> wrote:

> All of this has been pointed out before and does not come as a
> surprise. So we should have a general answer how to handle the
> "damage" created by an NBC update of YANG that according to some does
> not even require a YANG version number change.
>

It is more than just a conformance issue.
It is hard to overstate the importance of RFC 7950 as the 1 well-written
document needed to learn YANG.  It may be OK to distribute the
YANG data model in lots of ad-hoc specifications, but not the
data modeling language definition.

People (way outside the IETF) will be expected to learn and use the "new"
YANG correctly,
and that will be much more difficult without even a name, let alone a
version number.
What is the new YANG called? "NBC YANG"?


Andy



> ..
> /js
>
> ...

v2.23.0 | Report a Bug | By Email