Re: [netmod] YANG next

Andy Bierman <andy@yumaworks.com> Thu, 25 July 2019 14:41 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 B669C12006D for <netmod@ietfa.amsl.com>; Thu, 25 Jul 2019 07:41:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 ePh0spnqszd5 for <netmod@ietfa.amsl.com>; Thu, 25 Jul 2019 07:41:56 -0700 (PDT)
Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (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 D7311120024 for <netmod@ietf.org>; Thu, 25 Jul 2019 07:41:55 -0700 (PDT)
Received: by mail-lj1-x22f.google.com with SMTP id v24so48349588ljg.13 for <netmod@ietf.org>; Thu, 25 Jul 2019 07:41:55 -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=aoNO533Xn3dsBWSqhBe1yxPOuq2Nsk5kKaDorThp0e0=; b=IKXJtWTtXuwbHO1sTnsWMyhaf5J2A+TD/k5KBOUERuZ6ChgzisOqgxXoioNLw1B2up xENOE24D37iJ3DUehSq5VCbJ4DtrUa3IrmQpsBAyLlU6KFRPwE31fgq78KEof6Xs97Ry 0TpXo8VtteliYZdulMfZeOQUALdFSHJZ32UT0/5uupk8AZ0720IP08dSHZ8vMsJ5n9Hj 5w/k/JooSwfpLxv9aSWnqIriehPgS3by4vnTsC5g71ptozj7iD3jOYAA4NUf6Ij5ZQL4 lcsGufxwSS4jmpxbqY1sc6tS/F2tbVKs2DRtpL/JCsnk8+l/xbd8lJaa0W3dMSOYMm4d 5Ogw==
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=aoNO533Xn3dsBWSqhBe1yxPOuq2Nsk5kKaDorThp0e0=; b=R7j8K8NKYGxCkQpg0RnQAgChGeAwBHb3VTEU7R/1D+xL4rfQLluKFi9+bMWVkFSrpO 6drQG9oaPaRRDNcQklh8FwYHwqlWG/+3zgbudyBqgKZssNabiXHwML9EbC/GkI4ToFGa uD9NZ5+xQiRne/N0cTz35m8GC7zQas13WnLO3pzDIbRRWvgVcINnZF55T1N/Y4ygJAlp 6oP1v38j9c6IOQinGk1lFMrGAN3reMFZpzqQvnUQ9G2RYsJVEQRf+HkwCIS4qb5120Vo Xx+lcOfKPtJ+BFHOaDwnedKMXY5yJC/2bgwWG4xT2Wuhm4Rw/tl9+gxPsGcYDavvVc5p PCZw==
X-Gm-Message-State: APjAAAUmowdH+g702G9q6tY/eS3bgFpPPs7Z3WKSRied3nS9sx/Cmfi1 icemg6ZvgDHjKI4PudxSRA8KbVpVL9AJ7agPw/nbsw==
X-Google-Smtp-Source: APXvYqyMbgSjAxGVrWQ/ueAjB8A5oYONRenyjslwI+ifUgg1abxgvNqwLGoZdolJPx1e26uZXdzdM+SGgE4uk/aggm0=
X-Received: by 2002:a2e:b0ea:: with SMTP id h10mr1802537ljl.50.1564065713743; Thu, 25 Jul 2019 07:41:53 -0700 (PDT)
MIME-Version: 1.0
References: <ff5d90b51872df190abb226cb10d51a635e88521.camel@nic.cz> <CABCOCHRxfKWh1OS3bUJAabk3XAqTCiOswiE65JtMC8eyxMUxMA@mail.gmail.com> <02c4110737b4ff23f966e6153fad764f04436089.camel@nic.cz> <CABCOCHQoKAiugVsDhuHSvhfnCbP2D2caLU88cF-AkkH0aCSOUA@mail.gmail.com> <c35ae918e65411575b7e18dfd24547cbbf9d216d.camel@nic.cz> <856cce29-f524-be31-b5e5-bcb679721e9a@hq.sk> <0100016c25074dba-bffd4eea-f851-4913-83da-df3da8774f76-000000@email.amazonses.com> <CABCOCHR5MJLuRVtZBa_VbBXX4nrRJMUQBpU13P8a1oRE1_6C2g@mail.gmail.com> <BYAPR11MB26313098C4AABAF268329BDCB5C10@BYAPR11MB2631.namprd11.prod.outlook.com>
In-Reply-To: <BYAPR11MB26313098C4AABAF268329BDCB5C10@BYAPR11MB2631.namprd11.prod.outlook.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Thu, 25 Jul 2019 07:41:42 -0700
Message-ID: <CABCOCHToOuB=bomA6JEnS8VTgUGyTo1tRcHfiMWeHy6o4Pr90g@mail.gmail.com>
To: "Rob Wilton (rwilton)" <rwilton@cisco.com>
Cc: Kent Watsen <kent@watsen.net>, "netmod@ietf.org" <netmod@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000045ff5d058e826d77"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/lvdBJNe4RZl1ipX8mIW9jxNFRzs>
Subject: Re: [netmod] YANG next
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 25 Jul 2019 14:41:59 -0000

Hi,

Was this a big topic at the side meeting?
The issues blocking NMDA, schema-mount, and other deployment problems
are related to YANG document organization?  I doubt it.

So how would this work?
There will be 2 versions of YANG 1.1?
If old YANG 1.1 is equivalent to new YANG 1.1, can a developer safely
ignore the new RFCs?
If not, then something changed that was not supposed to change.

The old YANG 1.1 RFC will be obsolete and the 2 (or more) new YANG 1.1 RFCs
will replace it?
Then of course all the RFCs that reference RFC 7950 might have to be
updated so the subject matter
is cited from the correct new YANG 1.1 RFC.

IMO this will only serve to confuse the end-users and offer them no real
benefit at all.
As for finishing quickly because the NETMOD WG is so fast and has nothing
better to work on anyway...  sure.


Andy



On Thu, Jul 25, 2019 at 5:56 AM Rob Wilton (rwilton) <rwilton@cisco.com>
wrote:

> I also think that there is significant value to splitting the NETCONF and
> XML specification out of RFC 7950 (but keeping XML examples).  I think that
> this may be beneficial to YANG’s longevity, and I’m sure that it would make
> it easier to maintain and extend the NETCONF/RESTCONF/YANG document set in
> future.
>
>
>
> Thanks,
>
> Rob
>
>
>
>
>
> *From:* netmod <netmod-bounces@ietf.org> *On Behalf Of *Andy Bierman
> *Sent:* 24 July 2019 14:32
> *To:* Kent Watsen <kent@watsen.net>
> *Cc:* netmod@ietf.org
> *Subject:* Re: [netmod] YANG next
>
>
>
>
>
>
>
> On Wed, Jul 24, 2019 at 10:28 AM Kent Watsen <kent@watsen.net> wrote:
>
>
>
> So you want to work on YANG 1.2, but just the parts you want to change? ;-)
>
> I am actually fine with not doing any changes to YANG 1.1 at all, except
> perhaps
> bug fixes. This doesn't necessarily mean closing the NETMOD WG, it would
> IMO be
> immensely useful to rewrite the language specification and remove NETCONF-
> and
> XML-specific part.
>
>
> +1. There are plenty of ambiguities and NETCONF/XML pollution in the
> spec. Having the specifications in a DAG would be immensely useful :)
>
>
>
> Agreed and I should've mentioned before that Martin said in Prague that
> he'd already started this effort, seeing it as a necessary pre-step before
> making other changes.  I'm unsure if the intention is to release this by
> itself as an RFC 7950 bis but, if looking for a minimal change, that might
> be it.  The next rung up would be to just add clarifications.  The next
> rung up from there would be to add only backwards-compatible changes
> (currently targeted by [1]).  The last rung being to also target NBC
> changes (there's no consensus to do this).
>
>
>
>
>
> This WG sure likes to spend time refactoring documents.
>
> Moving lots of text will create bugs and strong coupling, and only help
> the standards purists.
>
> It will be a lot of work for the WG and IESG to review such a massive
> document split,
>
> and in the end we have no improvement in YANG, just more RFCs to read.
>
>
>
> Andy
>
>
>
> [1] https://github.com/netmod-wg/yang-next/projects/2
> <https://github..com/netmod-wg/yang-next/projects/2>
>
>
>
> Kent
>
>
>
>
>
>