Hi,
The module has this object:
leaf includes-defaults {
type enumeration {
enum report-all {
value 1;
description
"All data nodes SHOULD be included independent of
any default values.";
}
enum trim {
value 2;
description
"Data nodes that have a default defined and where
the actual value is the default value SHOULD
NOT be included.";
}
enum explicit {
value 3;
description
"Data nodes that have a default defined and where
the actual value is the default value SHOULD NOT be
included. However, if the actual value was set by
a NETCONF client or other management application
by the way of an explicit management operation the
data node SHOULD be included.";
}
}
default trim;
The draft is extremely server-centric, like most IETF standards, but this
leaf is too server-centric to ignore.
Consider the possibility that the source of the file is NOT a NETCONF
server.
This data may not be known so the default of "trim" may not be correct.
IMO this leaf is noise because any tool that knows the schema will also
know the YANG defaults. The solution is incomplete anyway because
the presence of a leaf that has a YANG default is not enough.
The "report-all-tagged" mode must be used to identify defaults.
IMO this leaf should be removed, but at least add an enum called "unknown".
Andy
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
