1) It would be useful to expand section 4.3 a bit more to add another example
of the tree with some specifics that cater to most of the protocols work being
done in other WGs. Something along the line of the following:
Config (intended)
State (derived with or without applied)
Notification
RPC
..
Authors of numerous YANG models could refer to the above guideline and use it
as a starting point.
2) It would be helpful if the guideline suggested a preference (yes,
recommendation would be better) for keeping applied state and derived state
together (in the same container, per each field) or separate (containers);
--
Cheers,
Rajiv Asati
Distinguished Engineer, Cisco
https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
