Last Call Review of draft-ietf-manet-dlep-ether-credit-extension-05
review-ietf-manet-dlep-ether-credit-extension-05-secdir-lc-smyslov-2024-07-10-00
Request | Review of | draft-ietf-manet-dlep-ether-credit-extension |
---|---|---|
Requested revision | No specific revision (document currently at 08) | |
Type | Last Call Review | |
Team | Security Area Directorate (secdir) | |
Deadline | 2024-08-08 | |
Requested | 2024-06-25 | |
Requested by | Jim Guichard | |
Authors | David Wiggins , Lou Berger , Donald E. Eastlake 3rd | |
I-D last updated | 2024-07-10 | |
Completed reviews |
Tsvart Early review of -02
by David L. Black
(diff)
Genart Last Call review of -05 by Behcet Sarikaya (diff) Rtgdir Last Call review of -06 by He Jia (diff) Secdir Last Call review of -05 by Valery Smyslov (diff) Opsdir Last Call review of -06 by Susan Hares (diff) |
|
Assignment | Reviewer | Valery Smyslov |
State | Completed | |
Request | Last Call review on draft-ietf-manet-dlep-ether-credit-extension by Security Area Directorate Assigned | |
Posted at | https://mailarchive.ietf.org/arch/msg/secdir/KLEyyDF5Ol4Q98blfhZD6MOP0qQ | |
Reviewed revision | 05 (document currently at 08) | |
Result | Ready | |
Completed | 2024-07-10 |
review-ietf-manet-dlep-ether-credit-extension-05-secdir-lc-smyslov-2024-07-10-00
I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the security area directors. Document editors and WG chairs should treat these comments just like any other last call comments. The short draft defines an extension to the Dynamic Link Exchange Protocol (DLEP) that enables an Ethernet-based flow control mechanism for traffic sent from a router to a modem. The Security Considerations section of the draft resembles similar sections in other documents defining DLEP extensions, mostly stating that adversary able to inject DLEP messages can mount a DoS attack. I wish more details are given on what type of DoS attacks are possible (e.g. advertising too large or too small window, or associating it with wrong type of traffic, etc.), but this is only my personal preference. The draft mentions the possibility to use security mechanisms defined in RFC8175 (base DLEP specification), but with no BCP14 wording like "RECOMMENDED" or "SHOULD" (other DLEP extension documents that I looked into do not have BCP14 language on using these security mechanisms either).