Last Call Review of draft-ietf-ospf-link-overload-11

Request Review of draft-ietf-ospf-link-overload
Requested rev. no specific revision (document currently at 16)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2018-01-16
Requested 2018-01-02
Authors Shraddha Hegde, Pushpasis Sarkar, Hannes Gredler, Mohan Nanduri, Luay Jalil
Draft last updated 2018-01-04
Completed reviews Rtgdir Last Call review of -09 by Martin Vigoureux (diff)
Genart Telechat review of -10 by Joel Halpern (diff)
Secdir Telechat review of -11 by Sean Turner (diff)
Opsdir Telechat review of -13 by Tim Chown (diff)
Genart Last Call review of -11 by Joel Halpern (diff)
Genart Telechat review of -12 by Joel Halpern (diff)
Assignment Reviewer Joel Halpern 
State Completed
Review review-ietf-ospf-link-overload-11-genart-lc-halpern-2018-01-04
Reviewed rev. 11 (document currently at 16)
Review result Ready
Review completed: 2018-01-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-ospf-link-overload-11
Reviewer: Joel Halpern
Review Date: 2018-01-04
IETF LC End Date: 2018-01-16
IESG Telechat date: 2018-01-25

Summary: This document is ready for publication as a Proposed Standard

Major issues:
    N/A; my concerns from earlier versions have been addressed.

Minor issues:
    I understand the WG likes using the term "overload" for a link being taken out of service.  I think people will learn what we mean.  I do wish we had not chosen to misuse the words in this fashion.  This is much more a graceful-link-close indication (or clsoe-pending indication) than it is an overload indication.

Nits/editorial comments: