[Netconf] My review of draft-ietf-netconf-netconf-event-notifications

[Mahesh Jethanandani <[e-mail]>]

I have read -07 version of the above draft, and I believe the document needs work.

Abstract:

One does not put normative references in the abstract section. You have to spell them out (without any cross references), and put a RFC editor note some where to indicate that the references need to be updated to the RFC number, whenever that is assigned.

Since you repeat what is included in the abstract in the introduction section also, you can shorten the abstract to say that it provides NETCONF bindings for subscribed notifications and yang-push - period.

Section 3:

Can you please follow the template in RFC 6241, Appendix D for defining a new capability. Also see examples in the same document for what all things need to be captured as part of defining a new capability, e.g. Positive Response, Negative Response, Example, SHOULD, MUST, and MAY conditions.

Section 5.1 and 5.2 and the entire Section 7 will then move under the Overview section of the template from Appendix D of RFC 6241.

Section 8 Security Considerations

Should this follow the template in rfc6087bis, at least for the part about NETCONF protocol and the security it provides. 

Please update reference to rfc6536bis instead of RFC6536.

Missing IANA considerations section.

Needs to capture the new capability in the NETCONF capability registry of IANA.

Appendix

Most of the examples in the appendix are for subscribed-notifications or yang-push. Why are these examples not in those documents? 

Which brings up the question. If the examples are moved to their own documents, you would be left with the new :interleave capability. Do you really need a separate draft just for that?

Thanks.

Mahesh Jethanandani
[e-mail]