Early Review of draft-ietf-nmop-terminology-07
review-ietf-nmop-terminology-07-opsdir-early-korhonen-2024-11-24-00
| Request | Review of | draft-ietf-nmop-terminology |
|---|---|---|
| Requested revision | No specific revision (document currently at 09) | |
| Type | Early Review | |
| Team | Ops Directorate (opsdir) | |
| Deadline | 2024-11-22 | |
| Requested | 2024-10-17 | |
| Requested by | Mohamed Boucadair | |
| Authors | Nigel Davis , Adrian Farrel , Thomas Graf , Qin Wu , Chaode Yu | |
| I-D last updated | 2024-11-24 | |
| Completed reviews |
Secdir Early review of -07
by Hilarie Orman
(diff)
Genart Early review of -07 by Paul Kyzivat (diff) Opsdir Early review of -07 by Jouni Korhonen (diff) Rtgdir Early review of -07 by Stewart Bryant (diff) Iotdir Early review of -07 by Carsten Bormann (diff) Intdir Early review of -07 by Dirk Von Hugo (diff) |
|
| Comments |
The document establishes foundational terms and concepts for anomaly, incident, and fault management. Coining carefully these terms is thus important for adoption within the IETF at large (but also in discussion with other SDOs). Some of these terms may have more contextualized meaning in areas such as "incident" in security. We do appreciate your review on the scope, clarity, articulation of various concepts in the document. Of course, the WG and the authors welcome other comments. Thank you. |
|
| Assignment | Reviewer | Jouni Korhonen |
| State | Completed | |
| Request | Early review on draft-ietf-nmop-terminology by Ops Directorate Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/ops-dir/5eeo5T-Kxot7xCjb8Fbk_EHT_Zs | |
| Reviewed revision | 07 (document currently at 09) | |
| Result | Ready | |
| Completed | 2024-11-24 |
review-ietf-nmop-terminology-07-opsdir-early-korhonen-2024-11-24-00
I have done the OPSDIR review for this document. Although not being too familiar with NMOP work I found the document easy to read and understand. While most of the content is rather obvious and well established in the industry the NMOP must have a reason to collect them into one place. I think the document is good to progress as it is now. Or maybe the authors could address the concern below: - After reading the document I was left with one small question. The term "Relevant Value" used in Figure 6 and referred only a couple of times in the text. Now that you have a "Relevant Value" then what?