Paging through the document, I found the following:
- The main module uses YANG 1.1, others modules use YANG 1.0. I think
it makes sense to generally use YANG 1.1. (The packet header module
may not need YANG 1.1 but then the main module is YANG 1.1 anyway.)
- Since YANG 1.1 is used, the references to RFC6020 should be replaced
with references to RFC 7950.
- The security consideration needs to be updated to follow the newer
template (which also covers RESTCONF).
- There is an open issue in the document (section 8) - are we going
to resolve that during WG last call or is this a leftover?
- There are references to RFCs in the YANG modules (in reference
statement) that must also be listed in the text and added to the
references section. This is why you usually find text of the form
This YANG module imports types from [RFC...] and references
[RFC...], [RFC...], and [RFC...].
/js
On Wed, Jan 17, 2018 at 09:55:04PM +0000, Kent Watsen wrote:
> All,
>
> This starts a two-week working group last call on
> draft-ietf-netmod-acl-model-15.
>
> This working group last call ends on January 31st.
> Please send your comments to the NETMOD mailing list.
>
> Positive comments, e.g., "I've reviewed this document
> and believe it is ready for publication", are welcome!
> This is useful and important, even from authors.
>
> Also, could the authors, explicitly CC-ed on this email,
> please confirm at this time that they are unaware of
> any IPR related to this draft.
>
> Thank you,
> NETMOD Chairs
>
> _______________________________________________
> netmod mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/netmod
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <https://www.jacobs-university.de/>
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
