Early Review of draft-ietf-nmop-terminology-07
review-ietf-nmop-terminology-07-rtgdir-early-bryant-2024-11-12-00
Request | Review of | draft-ietf-nmop-terminology |
---|---|---|
Requested revision | No specific revision (document currently at 09) | |
Type | Early Review | |
Team | Routing Area Directorate (rtgdir) | |
Deadline | 2024-11-22 | |
Requested | 2024-10-18 | |
Requested by | Mohamed Boucadair | |
Authors | Nigel Davis , Adrian Farrel , Thomas Graf , Qin Wu , Chaode Yu | |
I-D last updated | 2024-11-12 | |
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 specific to your area. |
|
Assignment | Reviewer | Stewart Bryant |
State | Completed | |
Request | Early review on draft-ietf-nmop-terminology by Routing Area Directorate Assigned | |
Posted at | https://mailarchive.ietf.org/arch/msg/rtg-dir/et5XmYKVQ-87fstTO0SZ6mVZAHs | |
Reviewed revision | 07 (document currently at 09) | |
Result | Ready | |
Completed | 2024-11-12 |
review-ietf-nmop-terminology-07-rtgdir-early-bryant-2024-11-12-00
Summary: A well written, concise and useful document that is ready for publication. Figure 6 was an interesting way of explaining the linkage between events, state and time. There were no issues either minor or major. There was one nit: 195 used to support the delivery of some function. Such function can 196 be local (e.g., within a node) or distributed (e.g., at the level 197 of a network). Should be such a function or such functions --------