[netmod] YANG next

Ladislav Lhotka <lhotka@nic.cz> Tue, 23 July 2019 16:03 UTC

Return-Path: <lhotka@nic.cz>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id D6BA91203A5 for <netmod@ietfa.amsl.com>; Tue, 23 Jul 2019 09:03:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.998
X-Spam-Status: No, score=-6.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, 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=nic.cz
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Tnk47CoVajdx for <netmod@ietfa.amsl.com>; Tue, 23 Jul 2019 09:03:22 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA04812039B for <netmod@ietf.org>; Tue, 23 Jul 2019 09:03:22 -0700 (PDT)
Received: from birdie (unknown [IPv6:2001:67c:370:128:c2e5:fc72:9ee5:1635]) by mail.nic.cz (Postfix) with ESMTPSA id DC50F140943 for <netmod@ietf.org>; Tue, 23 Jul 2019 18:03:19 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1563897800; bh=Wn3Y63aHVijh3YbkVKNVYCJz8bw484KsQbM6SD1r4Jo=; h=From:To:Date; b=qRE2+JRYpwGtaxqC3XjmaSTQc7AfYAAqLhdVNXZd8m8EyIzI/EFYMGGNEp5MSrnJf gEALF7IC/WYkC5JPXH5RSopnDLPhV8m//jAOZcU7jXzAvhic4N2dg7uXWcnDeA3Wir K5m8UqB/nN/6CbX67i5db/RXApK+cZHMxk3BEcuo=
Message-ID: <ff5d90b51872df190abb226cb10d51a635e88521.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: NETMOD WG <netmod@ietf.org>
Date: Tue, 23 Jul 2019 12:03:17 -0400
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.32.4
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.100.3 at mail.nic.cz
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/rzKrtoOrMU9snpOJ70l6EHgmEqo>
Subject: [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: Tue, 23 Jul 2019 16:03:34 -0000


this morning I attended the side meeting "Next Step of IETF YANG". I was
somewhat misled into thinking that it would be about future evolution of YANG
the language, which was not the case at all. However, my personal conclusion
from the meeting is that it would be a total disaster to throw in a new version
of YANG within the next few years or so.

The operators and equipment vendors are busy putting together YANG modules and
tools, filling the gaps, coping with NMDA, schema mount, IETF versus OpenConfig
etc. A new YANG version (and modules written in it) would IMO be extremely
counter-productive at this rather turbulent stage.

So, if we want to continue the yang-next discussion, I think we first have to
figure out how to evolve YANG without making waves in the current YANG pond and
let the operators and vendors do their work, without which YANG can never


Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67