YANG Module for IS-IS Reverse MetricLabN Consulting, L.L.C.chopps@chopps.orgThis document defines a YANG module for managing the reverse metric
extension to the Intermediate System to Intermediate System
intra-domain routeing information exchange protocol (IS-IS).This document defines a YANG module for managing the reverse metric
extension to IS-IS , . Please refer to for the
description and definition of the functionality managed by this
module.The YANG data model described in this document conforms to the
Network Management Datastore Architecture defined in .The following is the YANG tree diagram () for the IS-IS
reverse metric extension additions.The following is the YANG module for managing the IS-IS reverse
metric functionality defined in . It imports modules from the
following RFCs: , .This YANG module uses the same "Per-Level" hierarchical configuration
structure as is defined in the augmented base module. file "ietf-isis-reverse-metric@2022-01-01.yang"
module ietf-isis-reverse-metric {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-isis-reverse-metric";
prefix isis-rmetric;
import ietf-routing {
prefix rt;
reference
"RFC8349:
A YANG Data Model for Routing Management (NMDA Version)";
}
import ietf-isis {
prefix isis;
reference
"draft-ietf-isis-yang-isis-cfg-42:
YANG Data Model for IS-IS Protocol";
}
organization
"IETF LSR Working Group (LSR)";
contact
"WG Web:
WG List:
Author: Christian Hopps
";
// RFC Ed.: replace XXXX with actual RFC number and
// remove this note.
description
"This module defines the configuration and operational state for
managing the IS-IS reverse metric functionality [RFC8500].
Copyright (c) 2022 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX
(https://www.rfc-editor.org/info/rfcXXXX>); see the RFC itself
for full legal notices.";
revision 2022-01-01 {
description "Initial Revision";
reference "RFC XXXX: YANG IS-IS Reverse Metric";
}
grouping reverse-metric-data {
description "IS-IS reverse metric data.";
leaf metric {
type isis:wide-metric;
description "The reverse metric value.";
reference "RFC8500, Section 2";
}
container flags {
description "The reverse metric flag values.";
leaf whole-lan {
type boolean;
description
"The 'whole LAN' or W-bit. If true then a DIS processing
this reverse metric will add the metric value to all the
nodes it advertises in the pseudo-node LSP for this
interface. Otherwise, it will only increment the metric
for the advertising node in the pseudo-node LSP for this
interface.";
reference "RFC8500, Section 2";
}
leaf allow-unreachable {
type boolean;
description
"The 'allow-unreachable' or U-bit. If true it allows the
neighbor to increment the overall metric up to 2^24-1
rather than the lesser maximum of 2^24-2. If the metric
is then set by the neighbor to 2^24-1, it will cause
traffic to stop using, rather than avoid using, the
interface.";
reference "RFC8500, Section 2";
}
}
}
grouping reverse-metric-if-config-data {
description "IS-IS reverse metric config data.";
uses reverse-metric-data;
leaf exclude-te-metric {
type boolean;
default false;
description
"If true and there is a TE metric defined for this
interface then do not send the TE metric sub-TLV in the
reverse metric TLV.";
reference "RFC8500, Section 2";
}
}
grouping tlv16-reverse-metric {
description "IS-IS reverse metric TLV data.";
uses reverse-metric-data;
leaf te-metric {
type uint32;
description
"The TE metric value from the sub-TLV if present.";
reference "RFC8500, Section 2";
}
}
augment "/rt:routing/rt:control-plane-protocols/"
+"rt:control-plane-protocol/"
+"isis:isis" {
when "derived-from-or-self(../rt:type, 'isis:isis')" {
description
"This augment is only valid when routing protocol instance
type is 'isis'.";
}
description
"The reverse metric configuration for an IS-IS instance.";
container reverse-metric {
description "Global reverse metric configuration.";
leaf enable-receive {
type boolean;
default false;
description
"Enable handling of reverse metric announcements from
neighbors. By default, reverse metric handling is disabled
and must be explicitly enabled through this
configuration.";
}
}
}
augment "/rt:routing/rt:control-plane-protocols/"
+"rt:control-plane-protocol/"
+"isis:isis/isis:interfaces/isis:interface" {
when "derived-from-or-self(../../../rt:type, 'isis:isis')" {
description
"This augment is only valid when routing protocol instance
type is 'isis'.";
}
description
"The reverse metric configuration for an interface.";
container reverse-metric {
description
"Announce a reverse metric to neighbors. The configuration
is hierarchical and follows the same behavior as defined
for 'Per-Level' values in the augmented base module.
Reverse metric operation is enabled by the configuration of
a reverse-metric metric value at either the top level or
under a level-specific container node. If a reverse-metric
metric value is only specified under a level-specific
container node then operation is only enabled at the
specified level.
As the reverse metric is advertised in IIH PDUs, level
specific configuration is only available for broadcast
interface types";
uses reverse-metric-if-config-data {
refine "flags/whole-lan" {
default false;
}
refine "flags/allow-unreachable" {
default false;
}
}
container level-1 {
when '../../isis:interface-type = "broadcast"';
description
"Announce a reverse metric to level-1 neighbors.";
uses reverse-metric-if-config-data;
}
container level-2 {
when '../../isis:interface-type = "broadcast"';
description
"Announce a reverse metric to level-2 neighbors.";
uses reverse-metric-if-config-data;
}
}
}
augment "/rt:routing/rt:control-plane-protocols/"
+"rt:control-plane-protocol/"
+"isis:isis/isis:interfaces/isis:interface/"
+"isis:adjacencies/isis:adjacency" {
when "derived-from-or-self(../../../../../rt:type,
'isis:isis')" {
description
"This augment is only valid when routing protocol instance
type is 'isis'";
}
description
"The reverse metric state advertised by an adjacency.";
container reverse-metric {
description "IS-IS reverse metric TLV data.";
uses tlv16-reverse-metric;
}
}
}
]]>This document registers a URI in the "IETF XML Registry" .
Following the format in , the following registration has been
made:
RFC XXXX (RFC Ed.: replace XXX with actual RFC number and remove this note.)
The YANG module specified in this document defines a schema for data
that is designed to be accessed via network management protocols such
as NETCONF or RESTCONF . The lowest NETCONF layer
is the secure transport layer, and the mandatory-to-implement secure
transport is Secure Shell (SSH) . The lowest RESTCONF layer
is HTTPS, and the mandatory-to-implement secure transport is TLS
.The NETCONF access control model provides the means to
restrict access for particular NETCONF or RESTCONF users to a
preconfigured subset of all available NETCONF or RESTCONF protocol
operations and content.The YANG module defined in this document can enable, disable and
modify the behavior of metrics used by routing. For the security
implications regarding these types of changes consult
which defines the functionality as well as
.There are a number of data nodes defined in this YANG module that are
writable/creatable/deletable (i.e., "config true", which is the
default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., edit-config) to
these data nodes without proper protection can have a negative effect
on network operations. These YANG nodes correspond directly to the
RFC 8500 functionality and the security considerations of the
functionality are described in RFC 8500.These are the subtrees and data nodes:Some of the readable data nodes in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus
important to control read access (e.g., via get, get-config, or
notification) to these data nodes. These YANG nodes correspond
directly to the RFC 8500 functionality and the security
considerations of the functionality are described in RFC 8500. These
are the subtrees and data nodes:Intermediate System to Intermediate System intra-domain routeing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode network service (ISO 8473)International Organization for StandardizationISO Standard 10589:2002The IETF XML RegistryThis document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas.YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)YANG is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF), NETCONF remote procedure calls, and NETCONF notifications. [STANDARDS-TRACK]Network Configuration Access Control ModelThe standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) or the RESTCONF protocol requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability. There is a need for standard mechanisms to restrict NETCONF or RESTCONF protocol access for particular users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. This document defines such an access control model.This document obsoletes RFC 6536.Network Management Datastore Architecture (NMDA)Datastores are a fundamental concept binding the data models written in the YANG data modeling language to network management protocols such as the Network Configuration Protocol (NETCONF) and RESTCONF. This document defines an architectural framework for datastores based on the experience gained with the initial simpler model, addressing requirements that were not well supported in the initial model. This document updates RFC 7950.A YANG Data Model for Routing Management (NMDA Version)This document specifies three YANG modules and one submodule. Together, they form the core routing data model that serves as a framework for configuring and managing a routing subsystem. It is expected that these modules will be augmented by additional YANG modules defining data models for control-plane protocols, route filters, and other functions. The core routing data model provides common building blocks for such extensions -- routes, Routing Information Bases (RIBs), and control-plane protocols.The YANG modules in this document conform to the Network Management Datastore Architecture (NMDA). This document obsoletes RFC 8022.IS-IS Routing with Reverse MetricThis 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.YANG Data Model for IS-IS ProtocolCisco SystemsArrcus, IncCisco SystemsJuniper NetworksCZ.NIC This document defines a YANG data model that can be used to configure
and manage the IS-IS protocol on network elements.
Network Configuration Protocol (NETCONF)The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK]Using the NETCONF Protocol over Secure Shell (SSH)This document describes a method for invoking and running the Network Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as an SSH subsystem. This document obsoletes RFC 4742. [STANDARDS-TRACK]JSON Encoding of Data Modeled with YANGThis document defines encoding rules for representing configuration data, state data, parameters of Remote Procedure Call (RPC) operations or actions, and notifications defined using YANG as JavaScript Object Notation (JSON) text.RESTCONF ProtocolThis document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF).YANG Tree DiagramsThis document captures the current syntax used in YANG module tree diagrams. The purpose of this document is to provide a single location for this definition. This syntax may be updated from time to time based on the evolution of the YANG language.The Transport Layer Security (TLS) Protocol Version 1.3This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery.This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961. This document also specifies new requirements for TLS 1.2 implementations.Below is an example of XML YANG instance data to enable
reverse metric processing.Below is an example of XML YANG instance data for the
ietf-isis-reverse-metric module.Below is an example of JSON YANG instance data for the
ietf-isis-reverse-metric module.