Last Call Review of draft-ietf-lpwan-schc-compound-ack-13
review-ietf-lpwan-schc-compound-ack-13-secdir-lc-weis-2023-03-04-00
Request | Review of | draft-ietf-lpwan-schc-compound-ack |
---|---|---|
Requested revision | No specific revision (document currently at 17) | |
Type | IETF Last Call Review | |
Team | Security Area Directorate (secdir) | |
Deadline | 2023-03-09 | |
Requested | 2023-02-23 | |
Authors | Juan-Carlos Zúñiga , Carles Gomez , Sergio Aguilar , Laurent Toutain , Sandra Cespedes , Diego S. Wistuba La Torre | |
I-D last updated | 2023-07-26 (Latest revision 2023-04-04) | |
Completed reviews |
Yangdoctors Early review of -14
by Ebben Aries
(diff)
Secdir IETF Last Call review of -13 by Brian Weis (diff) Opsdir IETF Last Call review of -12 by Tianran Zhou (diff) Tsvart IETF Last Call review of -14 by Wesley Eddy (diff) |
|
Assignment | Reviewer | Brian Weis |
State | Completed | |
Request | IETF Last Call review on draft-ietf-lpwan-schc-compound-ack by Security Area Directorate Assigned | |
Posted at | https://mailarchive.ietf.org/arch/msg/secdir/fXbkA3CMLTTRMEiUZn1g7_iTkWE | |
Reviewed revision | 13 (document currently at 17) | |
Result | Ready | |
Completed | 2023-03-04 |
review-ietf-lpwan-schc-compound-ack-13-secdir-lc-weis-2023-03-04-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 summary of the review is Ready. This document builds on existing data flows defined in RFC 8724 (Static Context Header Compression and Fragmentation) used in Low-Power Wide Area Networks (LPWANs). It decribes a new method for a sender to return bitmaps of lost SCHC fragments to the sender. In this method the receiver can return more than one bitmap in an "SCHC Compound ACK". The Security Considerations section states that Security Considerations of RFC 8724 apply, and I agree. No new issues appear to be introduced.