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

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/