Skip to main content

Last Call Review of draft-ietf-lpwan-schc-compound-ack-12

Request Review of draft-ietf-lpwan-schc-compound-ack
Requested revision No specific revision (document currently at 17)
Type Last Call Review
Team Ops Directorate (opsdir)
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-03-02
Completed reviews Yangdoctors Early review of -14 by Ebben Aries (diff)
Secdir Last Call review of -13 by Brian Weis (diff)
Opsdir Last Call review of -12 by Tianran Zhou (diff)
Tsvart Last Call review of -14 by Wesley Eddy (diff)
Assignment Reviewer Tianran Zhou
State Completed
Request Last Call review on draft-ietf-lpwan-schc-compound-ack by Ops Directorate Assigned
Posted at
Reviewed revision 12 (document currently at 17)
Result Has issues
Completed 2023-03-02
I have reviewed this document as part of the Operational directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written with the intent of improving the operational aspects of
the IETF drafts. Comments that are not addressed in last call may be included
in AD reviews during the IESG review.  Document editors and WG chairs should
treat these comments just like any other last call comments.

This draft introduces an SCHC Compound ACK message, which is intended to reduce
the number of SCHC ACKs in the ACK-on-Error mode.

From the operation point of view, there are several concerns.
1. What's the interaction with legacy devices? I.e., what if the sender does
not support the Compound ACK message? 2. Combining several ACKs to one Compound
ACK will introduce more response delay(no?). What's the impact to the sender?
For example, more buffer/cache for re-sending messages. For example, the
setting of timer expiration, etc.

I do not think these are big issues, but I hope there are texts to clarify in
the document.