Last Call Review of draft-ietf-trill-address-flush-05
review-ietf-trill-address-flush-05-secdir-lc-harkins-2018-02-08-00

Request Review of draft-ietf-trill-address-flush
Requested revision No specific revision (document currently at 06)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2018-02-05
Requested 2018-01-22
Authors Hao Weiguo , Donald E. Eastlake 3rd , Yizhou Li , Mohammed Umair
I-D last updated 2018-02-08
Completed reviews Rtgdir Early review of -00 by Henning Rogge (diff)
Opsdir Last Call review of -05 by Shwetha Bhandari (diff)
Genart Last Call review of -05 by Robert Sparks (diff)
Secdir Last Call review of -05 by Dan Harkins (diff)
Assignment Reviewer Dan Harkins
State Completed
Request Last Call review on draft-ietf-trill-address-flush by Security Area Directorate Assigned
Reviewed revision 05 (document currently at 06)
Result Has nits
Completed 2018-02-08
review-ietf-trill-address-flush-05-secdir-lc-harkins-2018-02-08-00
   Hello,

   I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written primarily for the benefit of the
security area directors.  Document editors and WG chairs should treat
these comments just like any other last call comments.

   This draft defines a new message to tell TRILL implementations to
flush certain reachability information it has learned. It seems quite
extensible and complete. The security considerations are adequate and
discuss what would happen if these messages are not secured.

   The draft is "Ready" for publication.

   One editorial nit (to show I really did read it!): in section 2.2,
"...where using a set of contiguous blocks if cumbersome." should be
"is cumbersome" I think.

   regards,

   Dan.