IETF Logo Mail Archive

Re: [netmod] YANG next

Kent Watsen <kent@watsen.net> Wed, 24 July 2019 17:28 UTC

Return-Path: <0100016c25074dba-bffd4eea-f851-4913-83da-df3da8774f76-000000@amazonses.watsen.net>
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 CEBC01202E3 for <netmod@ietfa.amsl.com>; Wed, 24 Jul 2019 10:28:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 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_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.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 0I_zJx-YynUa for <netmod@ietfa.amsl.com>; Wed, 24 Jul 2019 10:28:52 -0700 (PDT)
Received: from a8-33.smtp-out.amazonses.com (a8-33.smtp-out.amazonses.com [54.240.8.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5D4312028E for <netmod@ietf.org>; Wed, 24 Jul 2019 10:28:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1563989331; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=YPgvTPPKB6A+XYEg4BxBNTm3XAmWDtEcRIRUcg8rkoI=; b=kitbNIV9LkjTyxMt+mOhrugj/Ua9G5LThxfnK1SuPHQyMtEGdrjBgJwlq6uDnStG IIa7MOc/bN8WzuFR/EO9E0ANYW6Iuv2OPQ7g/pV5X8i2Ug3e2fiXdoQz0tjslWMBQJ2 TEBns+/70JvNWJGwvMEVgEqyVuDI0pqXlTQI3yZQ=
From: Kent Watsen <kent@watsen.net>
Message-ID: <0100016c25074dba-bffd4eea-f851-4913-83da-df3da8774f76-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9BA93241-4BDB-4A39-A9A8-ECACB11205E3"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Wed, 24 Jul 2019 17:28:51 +0000
In-Reply-To: <856cce29-f524-be31-b5e5-bcb679721e9a@hq.sk>
Cc: Ladislav Lhotka <lhotka@nic.cz>, Andy Bierman <andy@yumaworks.com>, "netmod@ietf.org" <netmod@ietf.org>
To: Robert Varga <nite@hq.sk>
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>
X-Mailer: Apple Mail (2.3445.104.11)
X-SES-Outgoing: 2019.07.24-54.240.8.33
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/KZf3PyeMz4f9x9w3h7F_9YjuYfk>
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: Wed, 24 Jul 2019 17:28:55 -0000

>>> 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).

[1] https://github.com/netmod-wg/yang-next/projects/2 <https://github.com/netmod-wg/yang-next/projects/2>
 
Kent

v2.26.15 | Report a Bug | By Email | System Status