YANG Data Model for IS-IS Segment RoutingOrangestephane.litkowski@orange.comHuaweiyingzhen.qu@huawei.comIndividualpushpasis.ietf@gmail.comJabiling-wher_chen@jabil.comIndividualjefftant.ietf@gmail.comIS-IS Working GroupThis document defines a YANG data model that can be used to configure and manage IS-IS Segment Routing (.The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described
in .YANG is a data definition language used to
define the contents of a conceptual data store that allows networked
devices to be managed using NETCONF . YANG is proving
relevant beyond its initial confines, as bindings to other interfaces
(e.g., ReST) and encodings other than XML (e.g., JSON) are being
defined. Furthermore, YANG data models can be used as the basis for
implementation of other interfaces, such as CLI and programmatic
APIs.
This document defines a YANG data model that can be used to configure
and manage IS-IS Segment Routing and it is an augmentation to the IS-IS
YANG data model.This document defines a model for IS-IS Segment Routing feature. It
is an augmentation of the IS-IS base model.The IS-IS SR YANG module requires support for the base segment routing
module , which defines the global segment
routing configuration independent of any specific routing protocol configuration, and support of IS-IS base model
which defines basic IS-IS configuration and state.The figure below describes the overall structure of the isis-sr
YANG module:
Activation of segment-routing IS-IS is done by setting the "enable" leaf to true.
This triggers advertisement of segment-routing extensions based on the configuration parameters that have been
setup using the base segment routing module.
The base segment routing module defines mapping server policies.
By default, IS-IS will not advertise nor receive any mapping server entry.
The IS-IS segment-routing module allows to advertise one or multiple mapping server policies through the "bindings/advertise/policies"
leaf-list.
The "bindings/receive" leaf allows to enable the reception of mapping server entries.
IS-IS SR model augments the fast-reroute container under interface.
It brings the ability to activate TI-LFA (topology independent LFA) and also enhances remote LFA to use
segment-routing tunneling instead of LDP.
Configuration and state data defined in this document are
designed to be accessed via the NETCONF protocol .As IS-IS is an IGP protocol (critical piece of the network),
ensuring stability and security of the protocol is mandatory for
the network service.Authors recommends to implement NETCONF access control model
() to restrict access to all or part of
the configuration to specific users. Authors would like to thank
Derek Yeung, Acee Lindem, Yi Yang
for their major contributions to the draft.TBD.The IANA is requested to assign two new URIs from the
IETF XML registry (). Authors are suggesting the following URI: This document also requests one new YANG module name in the YANG Module Names registry () with the following suggestion :NMDA compliancy.Added SRLB in configuration and LSDB.Added SR capability in LSDB.Added SR algorithms in LSDB.Added SRMS preference in LSDB.Alignment with iana-rt-types module.Align binding SID with draft-ietf-isis-segment-routing-extensions-13.Added P-Flag in Adj-SID.Separate document for IS-IS SR extensions.Align with new segment routing common module.Fixed XPATH in 'when' expressions.Align to draft-ietf-netmod-routing-cfg-23.Align to draft-ietf-netmod-routing-cfg-21.Key words for use in RFCs to Indicate Requirement LevelsIn many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.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]Network Configuration Protocol (NETCONF) Access Control ModelThe standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) 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 protocol access for particular users to a pre-configured subset of all available NETCONF protocol operations and content. This document defines such an access control model. [STANDARDS-TRACK]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]The 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.The YANG 1.1 Data Modeling LanguageYANG is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols. This document describes the syntax and semantics of version 1.1 of the YANG language. YANG version 1.1 is a maintenance release of the YANG language, addressing ambiguities and defects in the original specification. There are a small number of backward incompatibilities from YANG version 1. This document also specifies the YANG mappings to the Network Configuration Protocol (NETCONF).YANG Data Model for Segment RoutingThis document defines a YANG data model ([RFC6020], [RFC7950]) for segment routing ([I-D.ietf-spring-segment-routing]) configuration and operation. This YANG model is intended to be used on network elements to configure or operate segment routing. This document defines also generic containers that SHOULD be reused by IGP protocol modules to support segment routing.YANG Data Model for IS-IS protocolThis document defines a YANG data model that can be used to configure and manage IS-IS protocol on network elements.IS-IS Extensions for Segment RoutingSegment Routing (SR) allows for a flexible definition of end-to-end paths within IGP topologies by encoding paths as sequences of topological sub-paths, called "segments". These segments are advertised by the link-state routing protocols (IS-IS and OSPF). This draft describes the necessary IS-IS extensions that need to be introduced for Segment Routing operating on an MPLS data-plane.