Skip to main content

IETF Last Call Review of draft-ietf-iotops-7228bis-06
review-ietf-iotops-7228bis-06-artart-lc-smyslov-2026-04-23-00

Request Review of draft-ietf-iotops-7228bis
Requested revision No specific revision (document currently at 08)
Type IETF Last Call Review
Team ART Area Review Team (artart)
Deadline 2026-05-06
Requested 2026-04-22
Authors Carsten Bormann , Mehmet Ersue , Ari Keränen , Carles Gomez
I-D last updated 2026-06-04 (Latest revision 2026-05-15)
Completed reviews Artart IETF Last Call review of -06 by Valery Smyslov (diff)
Secdir IETF Last Call review of -07 by Shawn M Emery (diff)
Iotdir IETF Last Call review of -07 by Jouni Korhonen (diff)
Tsvart IETF Last Call review of -07 by Marcus Ihlar (diff)
Assignment Reviewer Valery Smyslov
State Completed
Request IETF Last Call review on draft-ietf-iotops-7228bis by ART Area Review Team Assigned
Posted at https://mailarchive.ietf.org/arch/msg/art/NspCidGH89cWREu3CNpOS2iTLB0
Reviewed revision 06 (document currently at 08)
Result Ready w/nits
Completed 2026-04-23
review-ietf-iotops-7228bis-06-artart-lc-smyslov-2026-04-23-00
I am the assigned ART directorate reviewer for this document. These
comments were written primarily for the benefit of the ART area directors.
Document editors and WG chairs should treat these comments just like any
other last call comments.

The document describes  basic terms used in research and standardization work
concerned with constrained-node networks. The text is clear and easy to read.

Since the document does not define any protocol, I see no issues in this
document related to ART.

Nits:
1. The purpose of the note below Table 10 (the text in parentheses: "'Sx'
stands for 'Size x'") is not clear to me. If it is concerned with the Name
column in this table, then it must be placed in some other place (preferrably
before the table with some explanatory words). And honestly in this case I see
no reason for this text, since the constration of name for all other tables is
not explained. If it is concerned with something else, then I wonder what it is
(I failed to find other "S*" words in the draft).

2. Section 5.3
I do not think that reference to MSL in the context of B0 networks is relevant.
MSL is only defined for TCP and I doubt if nodes connected to B0 network will
use TCP. In any case, MSL in TCP is only concerned with the chance for SN
repeat after host reboots. Referring to COAP's MAX_LATENCY value (discussed in
I-D.gomez-tiptop-coap) is more appropriate in this context, but its default
value is 100 (and not 120 as MSL).

3. Section 5.3
I also think that 62.5 bytes calculated here must be rounded to the full number
of bytes (I assume that all protocols operate on byte boundary and cannot send
say 62.3 bytes to remain "responsive" in B1 networks).