Hi,
I have submitted a new draft for provides several augmentations to the
ietf if:interfaces to define configuration YANG for basic interface
parameters that are commonly supported on network devices. E.g. it is
includes leaves such as bandwidth, carrier delay, dampening, loopback,
mtu, & sub-interface parent ref, and configurable interface MAC
addresses. I am hoping that this draft could be adopted and
standardized by the netmod WG.
https://datatracker.ietf.org/doc/draft-wilton-netmod-intf-ext-yang/
Any comments or feedback is appreciated.
Potential points of interest/discussion may be:
- Is it acceptable to define standard YANG for features that are not
backed by any formal standard if they are commonly implemented?
- We've tried to restrict the leaves to just the interface types
(using when if:type = ...) that the configuration applies to rather than
adding them to all interfaces. Feedback would be welcome on whether
this approach is a good idea/maintainable.
- For MTU, I've defined two different MTU leaves because devices
program interface MTU in different ways based on whether the configured
MTU value includes the L2 header overhead or not. Is this a reasonable
approach?
Thanks,
Rob
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
