Hi all,
The 'type' leaf in the interfaces model is a funny beast:
https://datatracker.ietf.org/doc/html/rfc8343
It is marked as mandatory and the description says this:
When an interface entry is created, a server MAY
initialize the type leaf with a valid value, e.g., if it
is possible to derive the type from the name of the
interface.
That's always been a behavior that seemed 'iffy' to me (the client would then
read back something different from what they sent, i.e. the client isn't the
master/owner of the config in that case).
In any case, in the latest system-config draft
(https://datatracker.ietf.org/doc/html/draft-ietf-netmod-system-config-18),
section B.2 doesn't have that leaf in the running or the intended. It makes
running invalid if it isn't in there. We've talked about validity of running in
the context of template expansion before, but for something basic like
'mandatory' don't we expect that to be enforced in running?
If not - then it should at least be showing up in intended? (but strange to
have it show up there IMO and not running)
Jason (he/him)
_______________________________________________
netmod mailing list -- [email protected]
To unsubscribe send an email to [email protected]
