Early Review of draft-ietf-opsawg-rfc5706bis-04
review-ietf-opsawg-rfc5706bis-04-intdir-early-winters-2026-03-18-00
| Request | Review of | draft-ietf-opsawg-rfc5706bis |
|---|---|---|
| Requested revision | No specific revision (document currently at 04) | |
| Type | Early Review | |
| Team | Internet Area Directorate (intdir) | |
| Deadline | 2026-03-20 | |
| Requested | 2026-01-07 | |
| Requested by | Alvaro Retana | |
| Authors | Benoît Claise , Joe Clarke , Adrian Farrel , Samier Barguil , Carlos Pignataro , Ran Chen | |
| I-D last updated | 2026-04-08 (Latest revision 2026-03-15) | |
| Completed reviews |
Iotdir Early review of -01
by Dave Thaler
(diff)
Dnsdir Early review of -01 by Johan Stenstam (diff) Yangdoctors Early review of -01 by Martin Björklund (diff) Artart Early review of -01 by Harald T. Alvestrand (diff) Genart Early review of -01 by Joel M. Halpern (diff) Tsvart Early review of -01 by Lars Eggert (diff) Secdir Early review of -03 by Jacqueline McCall (diff) Perfmetrdir Early review of -01 by Greg Mirsky (diff) Rtgdir Early review of -01 by Dhruv Dhody (diff) Opsdir Early review of -01 by Tina Tsou (Ting ZOU) (diff) Intdir Early review of -04 by Timothy Winters |
|
| Comments |
Hi! I'm requesting an early review of this document from all directorates, given the requirement that all future RFCs include an Operational Considerations section (see Section 3 for details). Focus on how the contents of the draft (including the concise checklist of key questions in Appendix A) apply to your specific area of expertise. Thanks! |
|
| Assignment | Reviewer | Timothy Winters |
| State | Completed | |
| Request | Early review on draft-ietf-opsawg-rfc5706bis by Internet Area Directorate Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/int-dir/GyENbqKhC5IADFFT4TyUAIRwJTs | |
| Reviewed revision | 04 | |
| Result | On the right track | |
| Completed | 2026-03-18 |
review-ietf-opsawg-rfc5706bis-04-intdir-early-winters-2026-03-18-00
I am the assigned int-dir reviewer for this draft. For background on int-dir, please see the [FAQ](https://wiki.ietf.org/en/group/intdir). Please resolve these comments along with any other comments you may receive. Summary: I found this document clear and concise with the purpose of this document. Appendix A has an excellent set of questions for protocol designers. I have some suggestions for improving how operation considerations over the internet. INTAREA: 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. In both cases, it would be helpful to suggest to authors to consider these factors when documenting the management and operation solution for new or extended protocols. I looked thru the document for references to Internet protocols (DHCP/IP). The references to IP based protocols such as the reference to Router Alert were accurate. 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"