Hi Authors, I read this draft and I think this work is valuable. There are several comments for your consideration. 1. We have YANG as the modeling language for configuration DM. For this draft, do you have any formal language for the IM? While I think the tree diagram is also clear, I am afraid the expression is not very strict. 2. The title indicates the content is about discard. And in fact section 4.1 only described the discard class. However, the IM you proposed includes "traffic" as a large part. So, I am thinking if you would consider to remove the "traffic" part, or your document is actually a more generic traffic IM. 3. In section 5, all your Signal-Cause-Mitigation mapping examples are actually "discard". Is there any use case for "good traffic"? I.e., maybe there is no need for the "good traffic" report, hence no need to include the "traffic" in your draft for your scenario. 4. In section 5, the Signal-Cause-Mitigation table is confusing. It's not clear what's the signal, cause, mitigation respectively. So it's better to indicate this information explicitly in the table.
Best, Tianran -----Original Message----- From: OPSAWG [mailto:[email protected]] On Behalf Of Henk Birkholz Sent: Wednesday, January 17, 2024 8:52 PM To: OPSAWG <[email protected]> Subject: [OPSAWG] 🔔 WG Adoption Call for draft-opsawg-evans-discardmodel-02 Dear OPSAWG members, this email starts a call for Working Group Adoption of > https://www.ietf.org/archive/id/draft-opsawg-evans-discardmodel-02.htm > l ending on Wednesday, January 31st. As a reminder, this I-D describes an information model in support of automated network mitigation on what and how to report about unintentional packet discards/losses that can have an impact on service level objectives. Implementation of the informational model, which could manifest, e.g., via NETCONF/YANG, SNMP or IPFIX, is out-of-scope. The chairs acknowledge feedback to and interest for the topic during the IETF118 meeting and on the list after afterwards. We would like to gather feedback from the WG if there is interest to further contribute and review. Please reply with your support and especially any substantive comments you may have. For the OPSAWG co-chairs, Henk _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
