Early Review of draft-ietf-manet-dlep-traffic-classification-12
review-ietf-manet-dlep-traffic-classification-12-opsdir-early-tsou-2024-07-30-00
| Request | Review of | draft-ietf-manet-dlep-traffic-classification |
|---|---|---|
| Requested revision | No specific revision (document currently at 13) | |
| Type | Early Review | |
| Team | Ops Directorate (opsdir) | |
| Deadline | 2024-08-13 | |
| Requested | 2024-07-23 | |
| Requested by | Jim Guichard | |
| Authors | Bow-Nan Cheng , David Wiggins , Lou Berger , Don Fedyk | |
| I-D last updated | 2024-07-30 | |
| Completed reviews |
Tsvart Early review of -06
by David L. Black
(diff)
Opsdir Early review of -12 by Tina Tsou (Ting ZOU) (diff) Rtgdir Early review of -12 by Darren Dukes (diff) Secdir Early review of -12 by Shawn M Emery (diff) Genart Last Call review of -12 by Stewart Bryant (diff) Secdir Telechat review of -13 by Shawn M Emery |
|
| Assignment | Reviewer | Tina Tsou (Ting ZOU) |
| State | Completed | |
| Request | Early review on draft-ietf-manet-dlep-traffic-classification by Ops Directorate Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/ops-dir/B8GO78lq73cmU7zPcCgLbULMaGk | |
| Reviewed revision | 12 (document currently at 13) | |
| Result | Has issues | |
| Completed | 2024-07-30 |
review-ietf-manet-dlep-traffic-classification-12-opsdir-early-tsou-2024-07-30-00
1. Introduction: The purpose and scope are well-defined. Consider providing additional real-world examples to illustrate the need for traffic classification. 2. Traffic Classification Types: The classification types are comprehensive. Ensure that the definitions are aligned with industry standards. 3. Traffic Classification Attributes: The attributes are detailed and well-explained. Verify that the attribute values cover all potential use cases. 4. Traffic Classification Procedures: The procedures are clear and logically structured. Consider adding flowcharts or diagrams to visualize the message exchanges. 5. IANA Considerations: The section is thorough. Double-check the parameter values and ensure all necessary registrations are included. 6. Security Considerations: The security section addresses key risks. Consider expanding on specific attack scenarios and their mitigations. By addressing these feedback areas, the document can be improved for clarity, completeness, and technical accuracy.