IETF Logo Mail Archive

Re: [YANG] new pyang errors

Phil Shafer <phil@juniper.net> Fri, 25 January 2008 06:14 UTC

Return-path: <yang-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JIHpd-0004xK-Hp; Fri, 25 Jan 2008 01:14:29 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JIHpb-0004x9-Mx for yang-confirm+ok@megatron.ietf.org; Fri, 25 Jan 2008 01:14:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JIHpb-0004wz-AB for yang@ietf.org; Fri, 25 Jan 2008 01:14:27 -0500
Received: from exprod7og107.obsmtp.com ([64.18.2.167]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JIHpa-0004ow-E8 for yang@ietf.org; Fri, 25 Jan 2008 01:14:26 -0500
Received: from source ([66.129.224.36]) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP; Thu, 24 Jan 2008 22:14:15 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Thu, 24 Jan 2008 22:14:23 -0800
Received: from idle.juniper.net (idleski.juniper.net [172.25.4.26]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m0P6ENq43297; Thu, 24 Jan 2008 22:14:23 -0800 (PST) (envelope-from phil@idle.juniper.net)
Received: from idle.juniper.net (localhost [127.0.0.1]) by idle.juniper.net (8.13.8/8.13.8) with ESMTP id m0P6EJwJ036835; Fri, 25 Jan 2008 06:14:19 GMT (envelope-from phil@idle.juniper.net)
Message-Id: <200801250614.m0P6EJwJ036835@idle.juniper.net>
To: "Randy Presuhn" <randy_presuhn@mindspring.com>
Subject: Re: [YANG] new pyang errors
In-reply-to: <000601c85f09$2fbe3c80$6801a8c0@oemcomputer>
Date: Fri, 25 Jan 2008 01:14:19 -0500
From: Phil Shafer <phil@juniper.net>
X-OriginalArrivalTime: 25 Jan 2008 06:14:23.0863 (UTC) FILETIME=[87E23870:01C85F19]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: yang@ietf.org
X-BeenThere: yang@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: YANG modeling Language for NETCONF <yang.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/yang>
List-Post: <mailto:yang@ietf.org>
List-Help: <mailto:yang-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=subscribe>
Errors-To: yang-bounces@ietf.org

"Randy Presuhn" writes:
>In the SNMP/SMI worlds, the "optionality" Ladislav refers to is
>handled by conformance statements, rather than the model per se.

Ah so maybe the confusion is "mandatory to implement" versus
"mandatory to configure".  YANG's mandatory statement is the latter.

YANG has no conformance mechanism.  Whether it appears in YANG-2.0,
I can't predict, but I'm hoping we can make base models that devices
can implement, with augmentations for additional config.

Thanks,
 Phil


_______________________________________________
YANG mailing list
YANG@ietf.org
https://www1.ietf.org/mailman/listinfo/yang

v2.8.7 | Report a Bug | By Email