Last Call Review of draft-ietf-rtgwg-yang-vrrp-07

Request Review of draft-ietf-rtgwg-yang-vrrp
Requested rev. no specific revision (document currently at 11)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2017-12-12
Requested 2017-11-28
Other Reviews Rtgdir Early review of -02 by Henning Rogge (diff)
Yangdoctors Early review of -01 by Radek Krejčí (diff)
Secdir Last Call review of -07 by Rich Salz (diff)
Opsdir Last Call review of -08 by Zitao Wang (diff)
Genart Telechat review of -08 by Linda Dunbar (diff)
Review State Completed
Reviewer Linda Dunbar
Review review-ietf-rtgwg-yang-vrrp-07-genart-lc-dunbar-2017-12-04
Posted at
Reviewed rev. 07 (document currently at 11)
Review result Ready
Draft last updated 2017-12-04
Review completed: 2017-12-04


I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at


Document: draft-ietf-rtgwg-yang-vrrp-07
Reviewer: Linda Dunbar
Review Date: 2017-12-04
IETF LC End Date: 2017-12-12
IESG Telechat date: 2018-01-11


Major issues: None

Minor issues: None

Nits/editorial comments: It would be helpful to add description on why you need both Tracking Interface and Tracking network. Both of them have the same description "to detect interface connectivity failures".  What kind of "connectivity failures" will be reported over the "Tracking Interface"? what connectivity failures will be reported to "Tracking Network"? 

Thanks, Linda Dunbar