Skip to main content

Last Call Review of draft-ietf-rift-applicability-06

Request Review of draft-ietf-rift-applicability-03
Requested revision 03 (document currently at 16)
Type Last Call Review
Team Internet Area Directorate (intdir)
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-07-25
Completed reviews Rtgdir Last Call review of -14 by Sasha Vainshtein (diff)
Secdir Last Call review of -14 by Watson Ladd (diff)
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)
The chairs are starting WGLC for the draft, we appreciate your reviews and comments.
Assignment Reviewer Ralf Weber
State Completed
Request Last Call review on draft-ietf-rift-applicability by Internet Area Directorate Assigned
Posted at
Reviewed revision 06 (document currently at 16)
Result Ready w/issues
Completed 2021-07-25

I am an assigned INT directorate reviewer for draft-ietf-rift-applicability.

These comments were written primarily for the benefit of the Internet Area
Directors. Document editors and shepherd(s) should treat these comments just
like they would treat comments from any other IETF contributors and resolve
them along with any other Last Call comments that have been received. For more
details on the INT Directorate, see

This document does a good job explaining when RIFT can be used and how it
should be used in certain scenarios. The examples, especially the operational
considerations are understandable and describe applicable cases. There is a
steep learinig curve though with a lot of field (Date Center architecture and
routing) specific acronnyms used which while at least name expanded and
somtimed document referenced require a lot of external reading for a non field
aware reader, to fully understand the document. If the addressees of this
document are technical experts in the field as the intro to section 3 suggest,
then this is fine, however if the audience is more general IETF audience some
more introductionary explanation of these architectures and terms instead of
referring to external documents would be benefical.

So long