IETF Logo Mail Archive

Re: Blog: YANG Really Takes Off in the Industry

Ted Lemon <Ted.Lemon@nominum.com> Tue, 09 December 2014 17:08 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 9080F1A89B3 for <ietf@ietfa.amsl.com>; Tue, 9 Dec 2014 09:08:38 -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 srrJUGtNE071 for <ietf@ietfa.amsl.com>; Tue, 9 Dec 2014 09:08:37 -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 556591A89B1 for <ietf@ietf.org>; Tue, 9 Dec 2014 09:08:37 -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 4A355DA00D1 for <ietf@ietf.org>; Tue, 9 Dec 2014 17:08:53 +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 D957853E076; Tue, 9 Dec 2014 09:08:06 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 9 Dec 2014 09:08:06 -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: <54872ABD.6010509@gmail.com>
Date: Tue, 09 Dec 2014 12:07:46 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <2C597CA7-BBF8-40B9-AA4E-ED7A067863B7@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> <139D837E-F131-4791-A026-234699A7E617@nominum.com> <01f901d00ee4$3c077b40$4001a8c0@gateway.2wire.net> <FF42158A-AC42-4EBF-9FCB-1A3EF4162027@nominum.com> <00f601d013bd$a1d23900$4001a8c0@gateway.2wire.net> <822FFCEB-7848-484E-9231-9BFDA4B97672@nominum.com> <54872ABD.6010509@gmail.com>
To: Tim Wicinski <tjw.ietf@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/tPcJYNGfrsetj-zW3MtV95XNomU
Cc: 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, 09 Dec 2014 17:08:38 -0000

On Dec 9, 2014, at 12:00 PM, Tim Wicinski <tjw.ietf@gmail.com> wrote:
> I would concur that is something that the everyday yang user should never have to do on a regular basis.  If we do, then we need to fix this.  I believe this is why libraries were invented.

If by "everyday yang user" you mean an ops person in a data center, then I agree, but that's not what I was talking about.   What I mean is that if yang is hard enough to understand well that only someone who hacks yang models full-time can do it, then that's a bit of a problem since we need people who are experts in the protocols and systems being _managed_ to be writing yang data models.   And those people are not going to be doing yang full-time.

v2.23.0 | Report a Bug | By Email