Re: [YANG] new pyang errors

On Fri, Jan 25, 2008 at 11:02:05AM +0100, Ladislav Lhotka wrote:

> I guess I differ from Andy here: in my view the agent will fill here a
> value that satisfies the DM, even though it is not a default specified
> in the DM (i.e, it is vendor's internal default). For example, if IP
> address is mandatory on an interface but no default is defined in the
> DM, the device could set it to 0.0.0.0. From the viewpoint of validating
> the configuration (my item 2), it is valid - the mandatory element
> exists and its value (presumably) conforms to inet:ip-address. True, the
> interface is not fully operational, but this has nothing to do with
> validity of the configuration wrt the DM.

I guess part of the problem we have in this discussion is that we do
not properly distinguish between configuration data and operational
state data. While a device may choose to assign automatically an
operational state of 0.0.0.0 for an unconfigured IPv4 address, this
particular address may still not be configuration state.

/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