Re: [YANG] default values

Jon Saperia <saperia@jdscons.com> Wed, 16 January 2008 15:21 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 1JFA4l-0001Ov-99; Wed, 16 Jan 2008 10:21:11 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JFA4k-0001Om-LV for yang-confirm+ok@megatron.ietf.org; Wed, 16 Jan 2008 10:21:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JFA4k-0001Oe-Bs for yang@ietf.org; Wed, 16 Jan 2008 10:21:10 -0500
Received: from rs40.luxsci.com ([65.61.166.82]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JFA4j-0000Oy-Rh for yang@ietf.org; Wed, 16 Jan 2008 10:21:10 -0500
Received: from [192.168.50.14] ([209.19.56.4]) (authenticated bits=0) by rs40.luxsci.com (8.13.1/8.13.7) with ESMTP id m0GFKmV1030779 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 16 Jan 2008 09:20:49 -0600
In-Reply-To: <478E1EF4.4050002@andybierman.com>
References: <1200478981.7029.27.camel@missotis> <20080116.123549.140000433.mbj@tail-f.com> <1200487153.7029.71.camel@missotis> <478E0FCD.6080908@andybierman.com> <1200493871.7029.137.camel@missotis> <478E1EF4.4050002@andybierman.com>
Mime-Version: 1.0 (Apple Message framework v753)
Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed
Message-Id: <DCABA351-3933-4AED-A6E6-80C5F85E3F9C@jdscons.com>
Content-Transfer-Encoding: quoted-printable
From: Jon Saperia <saperia@jdscons.com>
Subject: Re: [YANG] default values
Date: Wed, 16 Jan 2008 10:20:47 -0500
To: Andy Bierman <ietf@andybierman.com>
X-Mailer: Apple Mail (2.753)
X-Spam-Score: -1.0 (-)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: yang@ietf.org, Ladislav Lhotka <lhotka@cesnet.cz>
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

On Jan 16, 2008, at 10:12 AM, Andy Bierman wrote:

> Ladislav Lhotka wrote:
>> Andy Bierman píše v St 16. 01. 2008 v 06:08 -0800:
>>> YANG has the "DEFVAL with teeth" that SMIv2 never had.
>>> In YANG the default MUST be supported by the agent.
>>> It is not just a suggestion.  This means the manager can
>>> actually pay attention to the default defined in the data model,
>>> and change it only if needed.
>> I understand this but, as a matter of fact, most defaults in protocol
>> standards are of the SHOULD class at most. In a vendor-neutral
>> environment, it would be much safer if each device fills all the  
>> blanks.
>>> On large NE devices, it is common practice to keep the CLI config  
>>> file
>>> as small as possible by only including non-default values.  NETCONF
>>> needs to support this feature as well, and YANG leaf/typedef  
>>> default does that.
>> Yes, but this is only possible because the CLIs are vendor- 
>> specific. It
>> is quite common that different vendors use different defaults. If you
>> try to enforce a single default in the data model, the vendor that
>> thinks otherwise will come up with an entirely new data model  
>> (namespace
>> URI) which is IMO much worse for interoperability.
>
> You are entering a new topic zone -- why the IETF has never been
> successful in standardizing the configuration of any of its protocols.
> After 20 years and a pathetic handful of standard writable knobs,
> one has to ask if maybe there is some part of the problem space
> that has been overlooked.
>
> We will never have standard writable knobs until vendors understand
> the concept of a standard, and make an effort to define some
> standard knobs, which actually provide enough functionality
> to configure the device.

And they believe it is in their best interest (beyond lip service and  
Marketing) to have the standard.  There are plenty of smart people at  
vendors, they have the money to do it.  If they really wanted it and  
the customers really wanted to push it we would have them.  It has  
nothing to do with technology.
/jon
>
> It takes a lot of work to define the standard knob settings,
> and protocol WGs usually decide not to bother with any configuration
> at all.  But we make all our hammers and all our nails by hand,
> so it is easy to get away with it.
>
> (Lewis and Clark burned down some forts along the way, to
> recover and reuse their precious handmade nails.  We need to
> learn how to get machines to make the nails... ;-)
>
>> Lada
>
> Andy
>
>
> _______________________________________________
> YANG mailing list
> YANG@ietf.org
> https://www1.ietf.org/mailman/listinfo/yang
>



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