Skip to main content

Early Review of draft-ietf-anima-rfc8366bis-29
review-ietf-anima-rfc8366bis-29-iotdir-early-fossati-2026-04-17-00

Request Review of draft-ietf-anima-rfc8366bis
Requested revision No specific revision (document currently at 31)
Type Early Review
Team Internet of Things Directorate (iotdir)
Deadline 2026-04-21
Requested 2026-04-07
Requested by Mahesh Jethanandani
Authors Kent Watsen , Michael Richardson , Esko Dijk , Toerless Eckert , Qiufang Ma
I-D last updated 2026-06-04 (Latest revision 2026-05-14)
Completed reviews Opsdir Early review of -29 by Tim Wicinski (diff)
Yangdoctors Early review of -29 by Michal Vaško (diff)
Iotdir Early review of -29 by Thomas Fossati (diff)
Genart IETF Last Call review of -30 by Behcet Sarikaya (diff)
Dnsdir IETF Last Call review of -31 by Geoff Huston
Assignment Reviewer Thomas Fossati
State Completed
Request Early review on draft-ietf-anima-rfc8366bis by Internet of Things Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/iot-directorate/_B1h1ylNW3pE5an8TrFrL2iICrQ
Reviewed revision 29 (document currently at 31)
Result Ready
Completed 2026-04-17
review-ietf-anima-rfc8366bis-29-iotdir-early-fossati-2026-04-17-00
The document is well-written, clear and complete.
Kudos to the authors and the ANIMA WG for all their hard and careful
work.
Sections 5 and 6, which describe the differences from RFC8366 and
RFC8995, were particularly useful to me.

IoT-wise, it like like cBRSKI performs most of the heavy lifting, with
PRM providing additional support.  Therefore, there is not much more to
say about this document, except that by integrating these two
technologies, it produces an impressive step forward compared to RFC8366
in terms of supporting devices with a radically smaller footprint and
unreliable network connections, as well as improving interoperability
across a potentially huge number of new devices.

The usual considerations around clokcs, low-bandwidth and lossy network,
memory and CPU constraints, plus basement/dark installations, are the
responsibility of cBRSKI and PRM.
From a quick skim of the relevant documents, these seem to be well
addressed.

I am completely ignorant of YANG matters, so I cannot provide any
assistance in this area, apologies.

From an IoT prepstecive, I reckon that the document is ready.