Chris, >> Security Considerations does not use template (which other grouping modules >> such as Kent's do) > > I've pinged Kent for a pointer.
The template Tom is referring to is from https://tools.ietf.org/html/rfc8407#section-3.7.1. That said, I have always felt that this template is a starting point that needs to be customized per YANG module (ideally, a separate template instance for each module in the draft). For instance, if a module defines no "notification” or “rpc" statements, it is better for it to just say that instead of strictly following the template and producing an empty list. For instance: <note: a separate template instance per YANG module in draft> https://tools.ietf.org/html/rfc8572#section-9.15. (only defines an rc:yang-data structure) https://tools.ietf.org/html/rfc8572#section-9.16 (only defines a couple “rpc” statements) <the following are unpublished, so may not be perfect> https://tools.ietf.org/html/draft-ietf-netconf-tcp-client-server-04.html#section-6 (only defines “grouping”) https://tools.ietf.org/html/draft-ietf-netconf-tls-client-server-04.html#section-5 (only defines “grouping”) Kent // contributor
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
