Skip to main content

Last Call Review of draft-ietf-rift-applicability-03
review-ietf-rift-applicability-03-iotdir-lc-chakrabarti-2021-01-19-00

Request Review of draft-ietf-rift-applicability-03
Requested revision 03 (document currently at 14)
Type Last Call Review
Team Internet of Things Directorate (iotdir)
Deadline 2021-01-10
Requested 2020-12-09
Requested by Jeff Tantsura
Authors Yuehua Wei , Zheng Zhang , Dmitry Afanasiev , Pascal Thubert , Tony Przygienda
I-D last updated 2021-01-19
Completed reviews Secdir Last Call review of -14 by Watson Ladd
Secdir Last Call review of -03 by Watson Ladd (diff)
Genart Last Call review of -03 by Linda Dunbar (diff)
Intdir Last Call review of -06 by Ralf Weber (diff)
Iotdir Last Call review of -03 by Samita Chakrabarti (diff)
Rtgdir Last Call review of -03 by Mike McBride (diff)
Tsvart Last Call review of -03 by Tommy Pauly (diff)
Comments
The chairs are starting WGLC for the draft, we appreciate your reviews and comments.
Assignment Reviewer Samita Chakrabarti
State Completed
Request Last Call review on draft-ietf-rift-applicability by Internet of Things Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/iot-directorate/c0Sq7kWNwtumj-a6u8_XRHyzTSA
Reviewed revision 03 (document currently at 14)
Result Ready w/nits
Completed 2021-01-19
review-ietf-rift-applicability-03-iotdir-lc-chakrabarti-2021-01-19-00
I have reviewed  draft-ietf-rift-applicability from IoT point of view.

The document describes routing in the Fat Tree ( mostly CLOS architecture)
applicability. I do not find any impact of this work on the IETF IoT networks.
The document methods and RIFT/Fat trees generally are not used in IETF IoT
protocols.  However RPL uses  directed graphs with a different protocol.  I did
not see any direct IoT applicability of this document to IoT networks. However,
 for larger IoT devices and switches one might extract some ideas out of this
document in the future.  Though I don't see direct IoT applicability, I still
wish to ask a question to the authors: will they view a root gateway/switch of
a IoT  network  to act as a leaf in the fat tree architecture ( example: DC
scenario) ?  If so, please consider adding a paragraph on IoT applicability in
RIFT.

In general, the document is full of acronyms that might be too familiar with
the routing area group ( PoD, TOF, ...), but it will help if the document has a
definition of terms section or a pointer to such document in the beginning ;
alternately, it can  add the acronyms in the relevant diagrams to understand
their usage.