IETF Logo Mail Archive

Re: [YANG] mandatory & default

"Randy Presuhn" <randy_presuhn@mindspring.com> Mon, 28 January 2008 04:55 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 1JJM1N-0005qa-18; Sun, 27 Jan 2008 23:55:01 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JJM1M-0005qM-5G for yang-confirm+ok@megatron.ietf.org; Sun, 27 Jan 2008 23:55:00 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJM1L-0005pR-Qy for yang@ietf.org; Sun, 27 Jan 2008 23:54:59 -0500
Received: from elasmtp-kukur.atl.sa.earthlink.net ([209.86.89.65]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JJM1L-0007uI-FP for yang@ietf.org; Sun, 27 Jan 2008 23:54:59 -0500
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=AIrYq/Xp0VAKo8rytxht78oY+1b0of5B3z2pj831iU1AsgPoVLFX6HeKLs4fuxbf; 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 [68.166.38.34] (helo=oemcomputer) by elasmtp-kukur.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1JJM1I-0007vQ-Ik for yang@ietf.org; Sun, 27 Jan 2008 23:54:56 -0500
Message-ID: <000a01c86169$eb717200$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <yang@ietf.org>
References: <200801280322.m0S3Mqhi051945@idle.juniper.net>
Subject: Re: [YANG] mandatory & default
Date: Sun, 27 Jan 2008 20:54:51 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8885d2a9c731cc89117625e425a6198b370564ba4729c3ba521350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 68.166.38.34
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
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: "Andy Bierman" <ietf@andybierman.com>
> Cc: <yang@ietf.org>
> Sent: Sunday, January 27, 2008 7:22 PM
> Subject: Re: [YANG] mandatory & default 
...
> If I'm using NETCONF to archive configurations, I don't
> want them littered with defaults.
...

If I'm archiving a configuration, I want to know *exactly*
what it is.  One of the reasons for archiving configurations
is so that if a box fails, a replacement can be quickly made
to function in its place.   If there is even a remote chance
that a default value might change between releases or on
different versions of a hardware platform, that value needs
to be included in an archive of the configuration.

Randy



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

v2.8.7 | Report a Bug | By Email