Re: Blog: YANG Really Takes Off in the Industry

Ted Lemon <Ted.Lemon@nominum.com> Tue, 02 December 2014 02:59 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A1DA1A007C for <ietf@ietfa.amsl.com>; Mon, 1 Dec 2014 18:59:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 nrMAqwKAyPFS for <ietf@ietfa.amsl.com>; Mon, 1 Dec 2014 18:59:49 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 901B61A006E for <ietf@ietf.org>; Mon, 1 Dec 2014 18:59:49 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 6BBC0DA011A for <ietf@ietf.org>; Tue, 2 Dec 2014 02:59:20 +0000 (UTC)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 42DC653E072; Mon, 1 Dec 2014 18:59:19 -0800 (PST)
Received: from [192.168.0.10] (72.182.60.179) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.195.1; Mon, 1 Dec 2014 18:59:18 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Blog: YANG Really Takes Off in the Industry
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <0BFD0B22-EC45-473F-8E7A-7FB608B60E6F@juniper.net>
Date: Mon, 01 Dec 2014 20:59:08 -0600
Content-Transfer-Encoding: quoted-printable
Message-ID: <139D837E-F131-4791-A026-234699A7E617@nominum.com>
References: <54770BA5.5060603@cisco.com> <809EFD2B-A845-46B7-A394-A9C9E5393CD5@piuha.net> <547874D6.1090001@cisco.com> <7890AE32-F7A9-4C32-9C3D-8251E70B1F29@lucidvision.com> <m2sigyhpxc.wl%randy@psg.com> <8BBBDF7F-00A0-44BD-AA64-DA7044D35012@lucidvision.com> <C51AC247-C16D-4452-874E-0D97BDB009EB@juniper.net> <547D0AEA.4020309@gmail.com> <0BFD0B22-EC45-473F-8E7A-7FB608B60E6F@juniper.net>
To: Dean Bogdanovic <deanb@juniper.net>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [72.182.60.179]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Y7LYNzaAHivRC-mCZK-f7ukej1U
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 02:59:54 -0000

On Dec 1, 2014, at 8:54 PM, Dean Bogdanovic <deanb@juniper.net> wrote:
> this is one part I don't understand. Why adding another language would make them less agile?

If the yang model isn't a good representation of what is being modeled, it can cause more harm than good.   Same problem exists with MIBs.   When different implementations of the same thing use different base assumptions, it can be difficult to come up with a management model that is congruent with all of the different base assumptions and is still useful.   I wouldn't say it's impossible, but it's a good bet that a poorly thought out model or a model that is based on experience with a single implementation will fail in this regard.