Re: [YANG] mandatory & default

On Mon, Jan 28, 2008 at 11:10:12AM +0100, Ladislav Lhotka wrote:
> 
> Juergen Schoenwaelder p????e v Po 28. 01. 2008 v 10:47 +0100:
> 
> > 
> > My point is you need to be able to (a) get all configuration settings
> > of a box and (b) the subset that was explicitely configured. It is
> > then the operator's choice what to use where and when. Trying to rule
> > out (a) over (b) or (b) over (a) is wasting time and bandwidth.
> 
> I don't intend to rule anything out, I just don't wan't to have (b) as a
> mandatory function in all devices. It should be an optional capability.
> On the other hand, (a) is by all means essential.

Our problem is that others believe (b) is by all means essential and
(a) should be an optional capability. This is our dilemma.

Why is it not OK to have (a) and (b)? Why do you not want to have (b)
as a mandatory function in all devices? Do you think it is too costly
to maintain this additional bit per explicitely configured knob or are
there other reasons?

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

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