Last Call Review of draft-ietf-manet-dlep-traffic-classification-12
review-ietf-manet-dlep-traffic-classification-12-genart-lc-bryant-2024-08-12-00
| Request | Review of | draft-ietf-manet-dlep-traffic-classification |
|---|---|---|
| Requested revision | No specific revision (document currently at 13) | |
| Type | Last Call Review | |
| Team | General Area Review Team (Gen-ART) (genart) | |
| Deadline | 2024-08-06 | |
| Requested | 2024-07-23 | |
| Authors | Bow-Nan Cheng , David Wiggins , Lou Berger , Don Fedyk | |
| I-D last updated | 2024-08-12 | |
| 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) |
|
| Assignment | Reviewer | Stewart Bryant |
| State | Completed | |
| Request | Last Call review on draft-ietf-manet-dlep-traffic-classification by General Area Review Team (Gen-ART) Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/gen-art/capioDhlDxDX8EdfTpgYEhTdQhk | |
| Reviewed revision | 12 (document currently at 13) | |
| Result | Ready | |
| Completed | 2024-08-12 |
review-ietf-manet-dlep-traffic-classification-12-genart-lc-bryant-2024-08-12-00
I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair. Please treat these comments just like any other last call comments. For more information, please see the FAQ at <https://wiki.ietf.org/en/group/gen/GenArtFAQ>. Document: draft-ietf-manet-dlep-traffic-classification-12 Reviewer: Stewart Bryant Review Date: 2024-08-12 IETF LC End Date: 2024-08-06 IESG Telechat date: Not scheduled for a telechat Summary: A well written document that from a GenArt perspective is OK to publish. I do have a bit of a worry that finer granularity flow identification does not raise privacy and security concerns but these are not called out in the early security review so I assume that this is considered safe. Major issues:None Minor issues: None Nits/editorial comments:None