[Int-dir] Re: draft-ietf-opsawg-rfc5706bis-04 early Intdir review

["Joe Clarke (jclarke)" <[e-mail]>]

Thanks for the review, Tim.  We have finally got around to working on -05, which we just published which should address all of your issues.

https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-rfc5706bis-05


This document should suggest that protocol designs consider all aspects IPv6
when using IP as part of the operation and management solution.  For example,
reducing the need for fragmentation and leverage appropriate MTU sizes when
making operational considerations.   Another area that you may want to consider
tunnel behavior if the operation and management solution will need to deal with
tunnels as part of the solution.

[JMC] We added text to Section 4.4 on MTU and fragmentation, as well as a mention of this in our appendix checklist.


Nits:
 - RFC3139 has an error in the reference.
 - Section 2 - Probable Root Cause: See [I-D.ietf-nmop-network-incident-yang]
 needs a "." - {{RFC6291}} has an error with the reference. - Section 1.2
 "explicit in a operational considerations discussion" -> "explicit in an
 operational considerations discussion”

[JMC] We believe all nits are fixed in -05.

Joe (on behalf of the authors)