Re: [YANG] new pyang errors

"Randy Presuhn" <randy_presuhn@mindspring.com> Wed, 23 January 2008 05:40 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 1JHYLt-0004gf-5s; Wed, 23 Jan 2008 00:40:45 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JHYLs-0004gX-74 for yang-confirm+ok@megatron.ietf.org; Wed, 23 Jan 2008 00:40:44 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHYLr-0004gP-T0 for yang@ietf.org; Wed, 23 Jan 2008 00:40:43 -0500
Received: from elasmtp-masked.atl.sa.earthlink.net ([209.86.89.68]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHYLr-0008Km-JO for yang@ietf.org; Wed, 23 Jan 2008 00:40:43 -0500
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=gnaQfrfRkUZQiF0Y7x99D1rnULP5xaZ/QXITQcLZEpC6sXMHkqi+IJS9TJWiTHeI; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [69.3.145.174] (helo=oemcomputer) by elasmtp-masked.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1JHYLq-0008Re-Rk for yang@ietf.org; Wed, 23 Jan 2008 00:40:43 -0500
Message-ID: <000401c85d82$c082fa40$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <yang@ietf.org>
References: <200801230532.m0N5W7Tt019859@idle.juniper.net>
Subject: Re: [YANG] new pyang errors
Date: Tue, 22 Jan 2008 21:42:32 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8885d2a9c731cc8911704f1fca974f0955c33c3634babadca13350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 69.3.145.174
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
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

Hi -

> From: "Phil Shafer" <phil@juniper.net>
> To: "Ladislav Lhotka" <lhotka@cesnet.cz>
> Cc: <yang@ietf.org>
> Sent: Tuesday, January 22, 2008 9:32 PM
> Subject: Re: [YANG] new pyang errors 
...
> My view of configuration is that if you set it, it should be there.
> If you didn't set it, it shouldn't be there.  If you want extra
> information, ask for it.  But the normal view of configuration
> should be restricted to only what the user or application expressed
> configured.

Strongly disagree.  Operationally, one needs to be able to
determine what the configuration actually *is*, regardless of
whether it was ever expressed by a user or application.

> This leads directly to my interpretation of "mandatory".  A mandatory
> config statement is one that some user or application must expressly
> configure.  If the configuration is valid without the statement,
> then it's not mandatory.
...

This is sufficient to configure a device, but it's not
configuration management.

Randy



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