--- 1/draft-ietf-isis-reverse-metric-13.txt	2018-10-16 16:13:34.026860317 -0700
+++ 2/draft-ietf-isis-reverse-metric-14.txt	2018-10-16 16:13:34.058861090 -0700
@@ -1,21 +1,21 @@
 
 Networking Working Group                                         N. Shen
 Internet-Draft                                             Cisco Systems
 Intended status: Standards Track                               S. Amante
-Expires: April 5, 2019                                       Apple, Inc.
+Expires: April 19, 2019                                      Apple, Inc.
                                                           M. Abrahamsson
                                                         T-Systems Nordic
-                                                         October 2, 2018
+                                                        October 16, 2018
 
                    IS-IS Routing with Reverse Metric
-                   draft-ietf-isis-reverse-metric-13
+                   draft-ietf-isis-reverse-metric-14
 
 Abstract
 
    This document describes a mechanism to allow IS-IS routing to quickly
    and accurately shift traffic away from either a point-to-point or
    multi-access LAN interface during network maintenance or other
    operational events.  This is accomplished by signaling adjacent IS-IS
    neighbors with a higher reverse metric, i.e., the metric towards the
    signaling IS-IS router.
 
@@ -27,21 +27,21 @@
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF).  Note that other groups may also distribute
    working documents as Internet-Drafts.  The list of current Internet-
    Drafts is at http://datatracker.ietf.org/drafts/current/.
 
    Internet-Drafts are draft documents valid for a maximum of six months
    and may be updated, replaced, or obsoleted by other documents at any
    time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."
 
-   This Internet-Draft will expire on April 5, 2019.
+   This Internet-Draft will expire on April 19, 2019.
 
 Copyright Notice
 
    Copyright (c) 2018 IETF Trust and the persons identified as the
    document authors.  All rights reserved.
 
    This document is subject to BCP 78 and the IETF Trust's Legal
    Provisions Relating to IETF Documents
    (http://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
@@ -381,24 +381,23 @@
    described in [RFC5443], it SHOULD advertise the maximum metric offset
    value in the Reverse Metric TLV in its IIH PDU sent on the LAN.  It
    SHOULD continue this advertisement until it completes all the LDP
    label binding exchanges with all the neighbors over this LAN, either
    by receiving the LDP End-of-LIB [RFC5919] for all the sessions or by
    exceeding the provisioned timeout value for the node LDP/IGP
    synchronization.
 
 3.5.  Operational Guidelines
 
-   A router MUST advertise a Reverse Metric TLV toward a neighbor only
-   for the operational maintenance window period during which it wants a
-   neighbor to temporarily update its IS-IS metric or Traffic
-   Engineering parameters towards it.
+   For the use case in Section 1.1, a router SHOULD limit the duration
+   of advertising a Reverse Metric TLV towards a neighbor only for the
+   period of operational window.
 
    The use of Reverse Metric does not alter IS-IS metric parameters
    stored in a router's persistent provisioning database.
 
    Routers that receive a Reverse Metric TLV MAY send a syslog message
    or SNMP trap, in order to assist in rapidly identifying the node in
    the network that is advertising an IS-IS metric or Traffic
    Engineering parameters different from that which is configured
    locally on the device.