draft-ietf-spring-sr-yang-10.txt   draft-ietf-spring-sr-yang-11.txt 
SPRING Working Group S. Litkowski SPRING Working Group S. Litkowski
Internet-Draft Orange Business Service Internet-Draft Orange Business Service
Intended status: Standards Track Y. Qu Intended status: Standards Track Y. Qu
Expires: July 4, 2019 Huawei Expires: August 19, 2019 Huawei
P. Sarkar P. Sarkar
Individual Individual
J. Tantsura J. Tantsura
Apstra Apstra
A. Lindem A. Lindem
Cisco Cisco
December 31, 2018 February 15, 2019
YANG Data Model for Segment Routing YANG Data Model for Segment Routing
draft-ietf-spring-sr-yang-10 draft-ietf-spring-sr-yang-11
Abstract Abstract
This document defines a YANG data model ([RFC6020], [RFC7950]) for This document defines a YANG data model ([RFC6020], [RFC7950]) for
segment routing ([I-D.ietf-spring-segment-routing]) configuration and segment routing ([RFC8402]) configuration and operation. This YANG
operation. This YANG model is intended to be used on network model is intended to be used on network elements to configure or
elements to configure or operate segment routing. This document operate segment routing. This document defines also generic
defines also generic containers that SHOULD be reused by IGP protocol containers that SHOULD be reused by IGP protocol modules to support
modules to support segment routing. segment routing.
Requirements Language
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 [RFC2119].
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 July 4, 2019. This Internet-Draft will expire on August 19, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Tree diagram . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology and Notation . . . . . . . . . . . . . . . . . . 3
2. Design of the Data Model . . . . . . . . . . . . . . . . . . 3 2.1. Tree diagram . . . . . . . . . . . . . . . . . . . . . . 3
3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . 5 2.2. Prefixes in Data Node Names . . . . . . . . . . . . . . . 3
4. IGP Control plane configuration . . . . . . . . . . . . . . . 6 3. Design of the Data Model . . . . . . . . . . . . . . . . . . 3
4.1. IGP interface configuration . . . . . . . . . . . . . . . 6 4. Configuration . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1.1. Adjacency SID properties . . . . . . . . . . . . . . 7 5. IGP Control plane configuration . . . . . . . . . . . . . . . 6
4.1.1.1. Bundling . . . . . . . . . . . . . . . . . . . . 7 5.1. IGP interface configuration . . . . . . . . . . . . . . . 7
4.1.1.2. Protection . . . . . . . . . . . . . . . . . . . 7 5.1.1. Adjacency SID properties . . . . . . . . . . . . . . 7
5. States . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 5.1.1.1. Bundling . . . . . . . . . . . . . . . . . . . . 7
6. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 8 5.1.1.2. Protection . . . . . . . . . . . . . . . . . . . 8
7. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 8 6. States . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
8. Security Considerations . . . . . . . . . . . . . . . . . . . 28 7. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 8
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 28 8. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 8
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 9. Security Considerations . . . . . . . . . . . . . . . . . . . 28
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 28 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 28
11.1. Normative References . . . . . . . . . . . . . . . . . . 28 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
11.2. Informative References . . . . . . . . . . . . . . . . . 29 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29 12.1. Normative References . . . . . . . . . . . . . . . . . . 28
12.2. Informative References . . . . . . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 30
1. Introduction 1. Introduction
This document defines a YANG data model for segment routing This document defines a YANG data model for segment routing
configuration and operation. This document does not define the IGP configuration and operation. This document does not define the IGP
extensions to support segment routing but defines generic groupings extensions to support segment routing but defines generic groupings
that SHOULD be reused by IGP extension modules. The reason of this that SHOULD be reused by IGP extension modules. The reason of this
design choice is to not require implementations to support all IGP design choice is to not require implementations to support all IGP
extensions. For example, an implementation may support IS-IS extensions. For example, an implementation may support IS-IS
extension but not OSPF. extension but not OSPF.
1.1. Tree diagram The YANG modules in this document conform to the Network Management
Datastore Architecture (NMDA) [RFC8342].
2. Terminology and Notation
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 [RFC2119].
2.1. Tree diagram
Tree diagrams used in this document follow the notation defined in Tree diagrams used in this document follow the notation defined in
[I-D.ietf-netmod-yang-tree-diagrams]. [RFC8340].
2. Design of the Data Model 2.2. Prefixes in Data Node Names
In this document, names of data nodes, actions, and other data model
objects are often used without a prefix, as long as it is clear from
the context in which YANG module each name is defined. Otherwise,
names are prefixed using the standard prefix associated with the
corresponding YANG module, as shown in Table 1.
+----------+--------------------+-----------+
| Prefix | YANG module | Reference |
+----------+--------------------+-----------+
| if | ietf-interfaces | [RFC8343] |
| rt | ietf-routing | [RFC8349] |
| rt-types | ietf-routing-types | [RFC8294] |
| yang | ietf-yang-types | [RFC6991] |
| inet | ietf-inet-types | [RFC6991] |
+----------+--------------------+-----------+
Table 1: Prefixes and Corresponding YANG Modules
3. Design of the Data Model
As the module definition is just starting, it is expected that there As the module definition is just starting, it is expected that there
will be changes as the module matures. will be changes as the module matures.
module: ietf-segment-routing module: ietf-segment-routing
augment /rt:routing: augment /rt:routing:
+--rw segment-routing +--rw segment-routing
+--rw transport-type? identityref +--rw transport-type? identityref
+--ro node-capabilities +--ro node-capabilities
| +--ro transport-planes* [transport-plane] | +--ro transport-planes* [transport-plane]
| | +--ro transport-plane identityref | | +--ro transport-plane identityref
| +--ro entropy-readable-label-depth? uint8 | +--ro entropy-readable-label-depth? uint8
+--rw msd {msd}? +--rw msd {max-sid-depth}?
| +--rw node-msd? uint8 | +--rw node-msd? uint8
| +--rw link-msd | +--rw link-msd
| +--rw link-msds* [interface] | +--rw link-msds* [interface]
| +--rw interface if:interface-ref | +--rw interface if:interface-ref
| +--rw msd? uint8 | +--rw msd? uint8
+--rw bindings +--rw bindings
| +--rw mapping-server {mapping-server}? | +--rw mapping-server {mapping-server}?
| | +--rw policy* [name] | | +--rw policy* [name]
| | +--rw name string | | +--rw name string
| | +--rw ipv4 | | +--rw entries
| | | +--rw mapping-entry* [prefix algorithm] | | +--rw mapping-entry* [prefix algorithm]
| | | +--rw prefix inet:ipv4-prefix | | +--rw prefix inet:ip-prefix
| | | +--rw value-type? enumeration | | +--rw value-type? enumeration
| | | +--rw start-sid uint32 | | +--rw start-sid uint32
| | | +--rw range? uint32 | | +--rw range? uint32
| | | +--rw algorithm identityref | | +--rw algorithm identityref
| | +--rw ipv6 | +--rw connected-prefix-sid-map
| | +--rw mapping-entry* [prefix algorithm] | | +--rw connected-prefix-sid* [prefix algorithm]
| | +--rw prefix inet:ipv6-prefix | | +--rw prefix inet:ip-prefix
| | +--rw value-type? enumeration | | +--rw value-type? enumeration
| | +--rw start-sid uint32 | | +--rw start-sid uint32
| | +--rw range? uint32 | | +--rw range? uint32
| | +--rw algorithm identityref | | +--rw algorithm identityref
| +--rw connected-prefix-sid-map | | +--rw last-hop-behavior? enumeration
| | +--rw ipv4 | | {sid-last-hop-behavior}?
| | | +--rw ipv4-prefix-sid* [prefix algorithm] | +--rw local-prefix-sid
| | | +--rw prefix inet:ipv4-prefix | +--rw local-prefix-sid* [prefix algorithm]
| | | +--rw value-type? enumeration | +--rw prefix inet:ip-prefix
| | | +--rw start-sid uint32 | +--rw value-type? enumeration
| | | +--rw range? uint32 | +--rw start-sid uint32
| | | +--rw algorithm identityref | +--rw range? uint32
| | | +--rw last-hop-behavior? enumeration {sid-last-hop-behavior}? | +--rw algorithm identityref
| | +--rw ipv6 +--rw global-srgb
| | +--rw ipv6-prefix-sid* [prefix algorithm] | +--rw srgb* [lower-bound upper-bound]
| | +--rw prefix inet:ipv6-prefix | +--rw lower-bound uint32
| | +--rw value-type? enumeration | +--rw upper-bound uint32
| | +--rw start-sid uint32 +--rw srlb
| | +--rw range? uint32 | +--rw srlb* [lower-bound upper-bound]
| | +--rw algorithm identityref | +--rw lower-bound uint32
| | +--rw last-hop-behavior? enumeration {sid-last-hop-behavior}? | +--rw upper-bound uint32
| +--rw local-prefix-sid +--ro label-blocks*
| +--rw ipv4 | +--ro lower-bound? uint32
| | +--rw ipv4-prefix-sid-local* [prefix algorithm] | +--ro upper-bound? uint32
| | +--rw prefix inet:ipv4-prefix | +--ro size? uint32
| | +--rw value-type? enumeration | +--ro free? uint32
| | +--rw start-sid uint32 | +--ro used? uint32
| | +--rw range? uint32 | +--ro scope? enumeration
| | +--rw algorithm identityref +--ro sid-list
| +--rw ipv6 +--ro sid* [target sid source source-protocol binding-type]
| +--rw ipv6-prefix-sid-local* [prefix algorithm] +--ro target string
| +--rw prefix inet:ipv6-prefix +--ro sid uint32
| +--rw value-type? enumeration +--ro algorithm? uint8
| +--rw start-sid uint32 +--ro source inet:ip-address
| +--rw range? uint32 +--ro used? boolean
| +--rw algorithm identityref +--ro source-protocol -> /rt:routing
+--rw global-srgb /control-plane-protocols
| +--rw srgb* [lower-bound upper-bound] /control-plane-protocol/name
| +--rw lower-bound uint32 +--ro binding-type enumeration
| +--rw upper-bound uint32 +--ro scope? enumeration
+--rw srlb
| +--rw srlb* [lower-bound upper-bound]
| +--rw lower-bound uint32
| +--rw upper-bound uint32
+--ro label-blocks*
| +--ro lower-bound? uint32
| +--ro upper-bound? uint32
| +--ro size? uint32
| +--ro free? uint32
| +--ro used? uint32
| +--ro scope? enumeration
+--ro sid-list
+--ro sid* [target sid source source-protocol binding-type]
+--ro target string
+--ro sid uint32
+--ro algorithm? uint8
+--ro source inet:ip-address
+--ro used? boolean
+--ro source-protocol -> /rt:routing/control-plane-protocols
+ /control-plane-protocol/name
+--ro binding-type enumeration
+--ro scope? enumeration
notifications: notifications:
+---n segment-routing-global-srgb-collision +---n segment-routing-global-srgb-collision
| +--ro srgb-collisions* | +--ro srgb-collisions*
| +--ro lower-bound? uint32 | +--ro lower-bound? uint32
| +--ro upper-bound? uint32 | +--ro upper-bound? uint32
| +--ro routing-protocol? -> /rt:routing/control-plane-protocols | +--ro routing-protocol? -> /rt:routing
| /control-plane-protocol/name | /control-plane-protocols
| +--ro originating-rtr-id? router-id | /control-plane-protocol/name
+---n segment-routing-global-sid-collision | +--ro originating-rtr-id? router-id
| +--ro received-target? string +---n segment-routing-global-sid-collision
| +--ro new-sid-rtr-id? router-id | +--ro received-target? string
| +--ro original-target? string | +--ro new-sid-rtr-id? router-id
| +--ro original-sid-rtr-id? router-id | +--ro original-target? string
| +--ro index? uint32 | +--ro original-sid-rtr-id? router-id
| +--ro routing-protocol? -> /rt:routing/control-plane-protocols | +--ro index? uint32
| /control-plane-protocol/name | +--ro routing-protocol? -> /rt:routing
+---n segment-routing-index-out-of-range | /control-plane-protocols
+--ro received-target? string | /control-plane-protocol/name
+--ro received-index? uint32 +---n segment-routing-index-out-of-range
+--ro routing-protocol? -> /rt:routing/control-plane-protocols +--ro received-target? string
/control-plane-protocol/name +--ro received-index? uint32
+--ro routing-protocol? -> /rt:routing
/control-plane-protocols
/control-plane-protocol/name
3. Configuration 4. Configuration
This module augments the "/rt:routing:" with a segment-routing This module augments the "/rt:routing:" with a segment-routing
container. This container defines all the configuration parameters container. This container defines all the configuration parameters
related to segment-routing. related to segment-routing.
The segment-routing configuration is split in global configuration The segment-routing configuration is split in global configuration
and interface configuration. and interface configuration.
The global configuration includes : The global configuration includes :
skipping to change at page 6, line 8 skipping to change at page 6, line 16
control plane used. Only a single transport-type is supported in control plane used. Only a single transport-type is supported in
this version of the model. this version of the model.
o bindings : Defines prefix to SID mappings. The operator can o bindings : Defines prefix to SID mappings. The operator can
control advertisement of Prefix-SID independently for IPv4 and control advertisement of Prefix-SID independently for IPv4 and
IPv6. Two types of mappings are available : IPv6. Two types of mappings are available :
* Mapping-server : maps non local prefixes to a segment ID. * Mapping-server : maps non local prefixes to a segment ID.
Configuration of bindings does not automatically allow Configuration of bindings does not automatically allow
advertisement of those bindings. Advertisement must be advertisement of those bindings. Advertisement must be
controlled by each routing-protocol instance (see Section 4). controlled by each routing-protocol instance (see Section 5).
Multiple mapping policies may be defined. Multiple mapping policies may be defined.
* Connected prefixes : maps connected prefixes to a segment ID. * Connected prefixes : maps connected prefixes to a segment ID.
Advertisement of the mapping will be done by IGP when enabled Advertisement of the mapping will be done by IGP when enabled
for segment routing (see Section 4). The SID value can be for segment routing (see Section 5). The SID value can be
expressed as an index (default), or an absolute value. The expressed as an index (default), or an absolute value. The
"last-hop-behavior" configuration dictates the PHP behavior: "last-hop-behavior" configuration dictates the PHP behavior:
"explicit-null", "php", or "non-php". "explicit-null", "php", or "non-php".
o SRGB (Segment Routing Global Block): Defines a list of label o SRGB (Segment Routing Global Block): Defines a list of label
blocks represented by a pair of lower-bound/upper-bound labels. blocks represented by a pair of lower-bound/upper-bound labels.
The SRGB is also agnostic to the control plane used. So all The SRGB is also agnostic to the control plane used. So all
routing-protocol instance will have to advertise the same SRGB. routing-protocol instance will have to advertise the same SRGB.
o SRLB (Segment Routing Local Block): Defines a list of label blocks o SRLB (Segment Routing Local Block): Defines a list of label blocks
represented by a pair of lower-bound/upper-bound labels, reserved represented by a pair of lower-bound/upper-bound labels, reserved
for lcoal SIDs. for lcoal SIDs.
4. IGP Control plane configuration 5. IGP Control plane configuration
Support of segment-routing extensions for a particular IGP control Support of segment-routing extensions for a particular IGP control
plane is done by augmenting routing-protocol configuration with plane is done by augmenting routing-protocol configuration with
segment-routing extensions. This augmentation SHOULD be part of segment-routing extensions. This augmentation SHOULD be part of
separate YANG modules in order to not create any dependency for separate YANG modules in order to not create any dependency for
implementations to support all protocol extensions. implementations to support all protocol extensions.
This module defines groupings that SHOULD be used by IGP segment This module defines groupings that SHOULD be used by IGP segment
routing modules. routing modules.
The "controlplane-cfg" grouping defines the generic global The "controlplane-cfg" grouping defines the generic global
configuration for the IGP. configuration for the IGP.
The "enabled" leaf enables segment-routing extensions for the The "enabled" leaf enables segment-routing extensions for the
routing-protocol instance. routing-protocol instance.
The "bindings" container controls the routing-protocol instance's The "bindings" container controls the routing-protocol instance's
advertisement of local bindings and the processing of received advertisement of local bindings and the processing of received
bindings. bindings.
4.1. IGP interface configuration 5.1. IGP interface configuration
The interface configuration is part of the "igp-interface-cfg" The interface configuration is part of the "igp-interface-cfg"
grouping and includes Adjacency SID properties. grouping and includes Adjacency SID properties.
4.1.1. Adjacency SID properties 5.1.1. Adjacency SID properties
4.1.1.1. Bundling 5.1.1.1. Bundling
This section is a first proposal on how to use S-bit in Adj-SID to This section is a first proposal on how to use S-bit in Adj-SID to
create bundles. Authors would like to trigger discussion based on create bundles. Authors would like to trigger discussion based on
this first proposal. this first proposal.
In case of parallel IP links between routers, an additional Adjacency In case of parallel IP links between routers, an additional Adjacency
SID may be advertised representing more than one adjacency (i.e., a SID may be advertised representing more than one adjacency (i.e., a
bundle of adjacencies). The "advertise-adj-group-sid" configuration bundle of adjacencies). The "advertise-adj-group-sid" configuration
controls whether or not an additional adjacency SID is advertised. controls whether or not an additional adjacency SID is advertised.
skipping to change at page 7, line 42 skipping to change at page 8, line 5
bundles of links. We can imagine two different bundles : L1/L2 and bundles of links. We can imagine two different bundles : L1/L2 and
L2/L3. To achieve this behavior, the service provider will configure L2/L3. To achieve this behavior, the service provider will configure
a "group-id" X for both interfaces L1 and L2 and a "group-id" Y for a "group-id" X for both interfaces L1 and L2 and a "group-id" Y for
both interfaces L3 and L3. This will result in R1 advertising an both interfaces L3 and L3. This will result in R1 advertising an
additional Adj-SID for each adjacency, for example a Adj-SID with S additional Adj-SID for each adjacency, for example a Adj-SID with S
flag set and value of 400 will be added to L1 and L2. A Adj-SID with flag set and value of 400 will be added to L1 and L2. A Adj-SID with
S flag set and value of 500 will be added to L3 and L4. As L1/L2 and S flag set and value of 500 will be added to L3 and L4. As L1/L2 and
L3/L4 does not share the same "group-id", a different SID value will L3/L4 does not share the same "group-id", a different SID value will
be allocated. be allocated.
4.1.1.2. Protection 5.1.1.2. Protection
The "advertise-protection" defines how protection for an interface is The "advertise-protection" defines how protection for an interface is
advertised. It does not control the activation or deactivation of advertised. It does not control the activation or deactivation of
protection. If the "single" option is used, a single Adj-SID will be protection. If the "single" option is used, a single Adj-SID will be
advertised for the interface. If the interface is protected, the advertised for the interface. If the interface is protected, the
B-Flag for the Adj-SID advertisement will be set. If the "dual" B-Flag for the Adj-SID advertisement will be set. If the "dual"
option is used and if the interface is protected, two Adj-SIDs will option is used and if the interface is protected, two Adj-SIDs will
be advertised for the interface adjacencies. One Adj-SID will always be advertised for the interface adjacencies. One Adj-SID will always
have the B-Flag set and the other will have the B-Flag clear. This have the B-Flag set and the other will have the B-Flag clear. This
option is intended to be used in the case of traffic engineering option is intended to be used in the case of traffic engineering
where a path must use either protected segments or non-protected where a path must use either protected segments or non-protected
segments. segments.
5. States 6. States
The operational states contains information reflecting the usage of The operational states contains information reflecting the usage of
allocated SRGB labels. allocated SRGB labels.
It also includes a list of all global SIDs, their associated It also includes a list of all global SIDs, their associated
bindings, and other information such as the source protocol and bindings, and other information such as the source protocol and
algorithm. algorithm.
6. Notifications 7. Notifications
The model defines the following notifications for segment-routing. The model defines the following notifications for segment-routing.
o segment-routing-global-srgb-collision: Rasied when a control plan o segment-routing-global-srgb-collision: Rasied when a control plan
advertised SRGB blocks have conflicts. advertised SRGB blocks have conflicts.
o segment-routing-global-sid-collision: Raised when a control plane o segment-routing-global-sid-collision: Raised when a control plane
advertised index is already associated with another target (in advertised index is already associated with another target (in
this version, the only defined targets are IPv4 and IPv6 this version, the only defined targets are IPv4 and IPv6
prefixes). prefixes).
o segment-routing-index-out-of-range: Raised when a control plane o segment-routing-index-out-of-range: Raised when a control plane
advertised index fall outside the range of SRGBs configured for advertised index fall outside the range of SRGBs configured for
the network device. the network device.
7. YANG Module 8. YANG Module
<CODE BEGINS> file "ietf-segment-routing-common@2018-06-25.yang"
module ietf-segment-routing-common {
namespace "urn:ietf:params:xml:ns:yang:ietf-segment-routing-common";
prefix sr-cmn;
import ietf-inet-types {
prefix inet;
}
organization
"IETF SPRING - SPRING Working Group";
contact
"WG Web: <http://tools.ietf.org/wg/spring/>
WG List: <mailto:spring@ietf.org>
Editor: Stephane Litkowski The following RFCs and drafts are not referenced in the document text
<mailto:stephane.litkowski@orange.com> but are referenced in the ietf-segment-rouuting-common.yang and/or
Editor: Yingzhen Qu ietf-segment-routing.yang module: [RFC6991], [RFC8294], and
<mailto:yingzhen.qu@huawei.com> [RFC8476].
Author: Acee Lindem <CODE BEGINS> file "ietf-segment-routing-common@2019-02-15.yang"
<mailto:acee@cisco.com> module ietf-segment-routing-common {
Author: Pushpasis Sarkar namespace "urn:ietf:params:xml:ns:yang:ietf-segment-routing-common";
<mailto:pushpasis.ietf@gmail.com> prefix sr-cmn;
Author: Jeff Tantsura
<jefftant.ietf@gmail.com>
"; import ietf-inet-types {
description prefix inet;
"The YANG module defines a collection of types and groupings for }
Segment routing.
Copyright (c) 2017 IETF Trust and the persons identified as organization
authors of the code. All rights reserved. "IETF SPRING - SPRING Working Group";
Redistribution and use in source and binary forms, with or contact
without modification, is permitted pursuant to, and subject "WG Web: <http://tools.ietf.org/wg/spring/>
to the license terms contained in, the Simplified BSD License WG List: <mailto:spring@ietf.org>
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; Editor: Stephane Litkowski
see the RFC itself for full legal notices."; <mailto:stephane.litkowski@orange.com>
Editor: Yingzhen Qu
<mailto:yingzhen.qu@huawei.com>
reference "RFC XXXX"; Author: Acee Lindem
<mailto:acee@cisco.com>
Author: Pushpasis Sarkar
<mailto:pushpasis.ietf@gmail.com>
Author: Jeff Tantsura
<jefftant.ietf@gmail.com>
revision 2018-06-25 {
description
"
* Renamed readable-label-stack-depth to entropy-readable-label-depth;
"; ";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
revision 2017-07-01 {
description description
" "The YANG module defines a collection of types and groupings for
*Conform to RFC6087BIS Appendix C Segment routing.
";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
revision 2017-03-10 {
description
"
* Add support of SRLB
";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
revision 2016-10-28 {
description
"
* Add support of MSD (Maximum SID Depth)
* Update contact info
";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
revision 2016-10-24 {
description
"Initial";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
feature sid-last-hop-behavior {
description
"Configurable last hop behavior.";
}
identity segment-routing-transport { Copyright (c) 2017 IETF Trust and the persons identified as
description authors of the code. All rights reserved.
"Base identity for segment routing transport.";
}
identity segment-routing-transport-mpls { Redistribution and use in source and binary forms, with or
base segment-routing-transport; without modification, is permitted pursuant to, and subject
description to the license terms contained in, the Simplified BSD License
"This identity represents MPLS transport for segment set forth in Section 4.c of the IETF Trust's Legal Provisions
routing."; Relating to IETF Documents
} (http://trustee.ietf.org/license-info).
identity segment-routing-transport-ipv6 { This version of this YANG module is part of RFC XXXX;
base segment-routing-transport; see the RFC itself for full legal notices.";
description
"This identity represents IPv6 transport for segment
routing.";
}
identity prefix-sid-algorithm { reference "RFC XXXX";
description
"Base identity for prefix-sid algorithm.";
}
identity prefix-sid-algorithm-shortest-path { revision 2019-02-15 {
base prefix-sid-algorithm; description
description "
"The default behavior of prefix-sid algorithm."; * Addressed YANG Doctor's review comments;
} ";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
identity prefix-sid-algorithm-strict-spf { revision 2018-06-25 {
base prefix-sid-algorithm; description
description "
"This algorithm mandates that the packet is forwared * Renamed readable-label-stack-depth to
according to ECMP-aware SPF algorithm."; * entropy-readable-label-depth;
} ";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
revision 2017-07-01 {
description
"
*Conform to RFC6087BIS Appendix C
";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
revision 2017-03-10 {
description
"
* Add support of SRLB
";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
revision 2016-10-28 {
description
"
* Add support of MSD (Maximum SID Depth)
* Update contact info
";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
revision 2016-10-24 {
description
"Initial";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
grouping srlr { feature sid-last-hop-behavior {
description description
"Grouping for SR Label Range configuration."; "Configurable last hop behavior.";
leaf lower-bound { }
type uint32;
description
"Lower value in the block.";
}
leaf upper-bound {
type uint32;
description
"Upper value in the block.";
}
}
grouping srgb-cfg { identity segment-routing-transport {
description
"Grouping for SR Label Range configuration.";
list srgb {
key "lower-bound upper-bound";
ordered-by user;
description description
"List of global blocks to be "Base identity for segment routing transport.";
advertised.";
uses srlr;
} }
}
grouping srlb-cfg { identity segment-routing-transport-mpls {
description base segment-routing-transport;
"Grouping for SR Local Block range configuration.";
list srlb {
key "lower-bound upper-bound";
ordered-by user;
description description
"List of SRLBs."; "This identity represents MPLS transport for segment
routing.";
}
uses srlr; identity segment-routing-transport-ipv6 {
base segment-routing-transport;
description
"This identity represents IPv6 transport for segment
routing.";
} }
}
grouping sid-value-type { identity prefix-sid-algorithm {
description
"Defines how the SID value is expressed.";
leaf value-type {
type enumeration {
enum "index" {
description
"The value will be
interpreted as an index.";
}
enum "absolute" {
description
"The value will become
interpreted as an absolute
value.";
}
}
default "index";
description description
"This leaf defines how value "Base identity for prefix-sid algorithm.";
must be interpreted.";
} }
}
grouping ipv4-sid-cfg { identity prefix-sid-algorithm-shortest-path {
description base prefix-sid-algorithm;
"This grouping defines cfg of prefix SID.";
leaf prefix {
type inet:ipv4-prefix;
description description
"connected prefix sid."; "The default behavior of prefix-sid algorithm.";
} }
uses prefix-sid-attributes;
} identity prefix-sid-algorithm-strict-spf {
grouping ipv6-sid-cfg { base prefix-sid-algorithm;
description
"This grouping defines cfg of prefix SID.";
leaf prefix {
type inet:ipv6-prefix;
description description
"connected prefix sid."; "This algorithm mandates that the packet is forwared
according to ECMP-aware SPF algorithm.";
} }
uses prefix-sid-attributes;
} grouping srlr {
grouping last-hop-behavior { description
description "Grouping for SR Label Range configuration.";
"Defines last hop behavior"; leaf lower-bound {
leaf last-hop-behavior { type uint32;
if-feature "sid-last-hop-behavior";
type enumeration {
enum "explicit-null" {
description
"Use explicit-null for the SID.";
}
enum "no-php" {
description description
"Do no use PHP for the SID."; "Lower value in the block.";
} }
enum "php" { leaf upper-bound {
type uint32;
description description
"Use PHP for the SID."; "Upper value in the block.";
} }
} }
grouping srgb {
description description
"Configure last hop behavior."; "Grouping for SR Global Label range.";
list srgb {
key "lower-bound upper-bound";
ordered-by user;
description
"List of global blocks to be
advertised.";
uses srlr;
}
} }
}
grouping node-capabilities { grouping srlb {
description
"Containing SR node capabilities.";
container node-capabilities {
config false;
description description
"Shows the SR capability of the node."; "Grouping for SR Local Block range.";
list transport-planes { list srlb {
key "transport-plane"; key "lower-bound upper-bound";
ordered-by user;
description description
"List of supported transport planes."; "List of SRLBs.";
leaf transport-plane { uses srlr;
type identityref { }
base segment-routing-transport; }
grouping sid-value-type {
description
"Defines how the SID value is expressed.";
leaf value-type {
type enumeration {
enum "index" {
description
"The value will be
interpreted as an index.";
}
enum "absolute" {
description
"The value will become
interpreted as an absolute
value.";
} }
description
"Transport plane supported";
} }
} default "index";
leaf entropy-readable-label-depth {
type uint8;
description description
"Maximum label statck depth that "This leaf defines how value
the router can read. "; must be interpreted.";
}
}
grouping prefix-sid {
description
"This grouping defines cfg of prefix SID.";
leaf prefix {
type inet:ip-prefix;
description
"connected prefix sid.";
} }
uses prefix-sid-attributes;
} }
}
grouping prefix-sid-attributes { grouping ipv4-sid {
description
"Containing SR attributes for a prefix.";
uses sid-value-type;
leaf start-sid {
type uint32;
mandatory true;
description description
"Value associated with "This grouping defines ipv4 prefix SID.";
prefix. The value must leaf prefix {
be interpreted in the type inet:ipv4-prefix;
context of value-type."; description
"connected prefix sid.";
}
uses prefix-sid-attributes;
} }
leaf range { grouping ipv6-sid {
type uint32;
description description
"Describes how many SIDs could be "This grouping defines ipv6 prefix SID.";
allocated."; leaf prefix {
type inet:ipv6-prefix;
description
"connected prefix sid.";
}
uses prefix-sid-attributes;
} }
leaf algorithm {
type identityref { grouping last-hop-behavior {
base prefix-sid-algorithm; description
"Defines last hop behavior";
leaf last-hop-behavior {
if-feature "sid-last-hop-behavior";
type enumeration {
enum "explicit-null" {
description
"Use explicit-null for the SID.";
}
enum "no-php" {
description
"Do no use PHP for the SID.";
}
enum "php" {
description
"Use PHP for the SID.";
}
}
description
"Configure last hop behavior.";
} }
}
grouping node-capabilities {
description description
"Prefix-sid algorithm."; "Containing SR node capabilities.";
container node-capabilities {
config false;
description
"Shows the SR capability of the node.";
list transport-planes {
key "transport-plane";
description
"List of supported transport planes.";
leaf transport-plane {
type identityref {
base segment-routing-transport;
}
description
"Transport plane supported";
}
}
leaf entropy-readable-label-depth {
type uint8;
description
"Maximum label statck depth that
the router can read. ";
}
}
} }
}
}
<CODE ENDS>
<CODE BEGINS> file "ietf-segment-routing@2018-06-25.yang"
module ietf-segment-routing {
namespace "urn:ietf:params:xml:ns:yang:ietf-segment-routing";
prefix sr;
import ietf-inet-types { grouping prefix-sid-attributes {
prefix inet; description
} "Containing SR attributes for a prefix.";
import ietf-yang-types { uses sid-value-type;
prefix yang; leaf start-sid {
} type uint32;
import ietf-routing { mandatory true;
prefix rt; description
} "Value associated with
import ietf-interfaces { prefix. The value must
prefix if; be interpreted in the
} context of value-type.";
import ietf-routing-types { }
prefix rt-types; leaf range {
} type uint32;
import ietf-segment-routing-common { description
prefix sr-cmn; "Describes how many SIDs could be
allocated.";
}
leaf algorithm {
type identityref {
base prefix-sid-algorithm;
}
description
"Prefix-sid algorithm.";
}
}
} }
<CODE ENDS>
<CODE BEGINS> file "ietf-segment-routing@2019-02-15.yang"
module ietf-segment-routing {
namespace "urn:ietf:params:xml:ns:yang:ietf-segment-routing";
prefix sr;
organization import ietf-inet-types {
"IETF SPRING - SPRING Working Group"; prefix inet;
contact }
"WG Web: <http://tools.ietf.org/wg/spring/> import ietf-yang-types {
WG List: <mailto:spring@ietf.org> prefix yang;
}
import ietf-routing {
prefix rt;
}
import ietf-interfaces {
prefix if;
}
import ietf-routing-types {
prefix rt-types;
}
import ietf-segment-routing-common {
prefix sr-cmn;
}
Editor: Stephane Litkowski organization
<mailto:stephane.litkowski@orange.com> "IETF SPRING - SPRING Working Group";
Editor: Yingzhen Qu contact
<mailto:yingzhen.qu@huawei.com> "WG Web: <http://tools.ietf.org/wg/spring/>
WG List: <mailto:spring@ietf.org>
Author: Acee Lindem Editor: Stephane Litkowski
<mailto:acee@cisco.com> <mailto:stephane.litkowski@orange.com>
Author: Pushpasis Sarkar Editor: Yingzhen Qu
<mailto:pushpasis.ietf@gmail.com> <mailto:yingzhen.qu@huawei.com>
Author: Jeff Tantsura
<jefftant.ietf@gmail.com>
"; Author: Acee Lindem
description <mailto:acee@cisco.com>
"The YANG module defines a generic configuration model for Author: Pushpasis Sarkar
Segment routing common across all of the vendor <mailto:pushpasis.ietf@gmail.com>
implementations. Author: Jeff Tantsura
<jefftant.ietf@gmail.com>
Copyright (c) 2018 IETF Trust and the persons identified as ";
authors of the code. All rights reserved. description
"The YANG module defines a generic configuration model for
Segment routing common across all of the vendor
implementations.
Redistribution and use in source and binary forms, with or Copyright (c) 2018 IETF Trust and the persons identified as
without modification, is permitted pursuant to, and subject authors of the code. All rights reserved.
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
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; Redistribution and use in source and binary forms, with or
see the RFC itself for full legal notices."; 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
(http://trustee.ietf.org/license-info).
reference "RFC XXXX"; This version of this YANG module is part of RFC XXXX;
revision 2018-06-25 { see the RFC itself for full legal notices.";
description
"";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
revision 2017-07-01 {
description
"
* Implement NMDA model
*Conform to RFC6087BIS Appendix C
";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
revision 2017-03-10 { reference "RFC XXXX";
description
"
* Change global-sid-list to sid-list and add a leaf scope
* Added support of SRLB
* Added support of local sids
* fixed indentations
";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
revision 2016-10-28 {
description
"
* Add support of MSD (Maximum SID Depth)
* Update contact info
";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
revision 2016-10-24 {
description
"
* Moved common SR types and groupings to a seperate module
";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
revision 2016-07-07 {
description
"
* Add support of prefix-sid algorithm configuration
* change routing-protocols to control-plane-protocols
";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
revision 2016-03-17 {
description
"
* Add notification segment-routing-global-srgb-collision
* Add router-id to segment-routing-global-sid-collision
* Remove routing-instance
* Add typedef router-id
";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
revision 2015-10-17 {
description
"
* Add per-protocol SRGB config feature
* Move SRBG config to a grouping
";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
revision 2015-06-22 {
description
"
* Prefix SID config moved to
connected-prefix-sid-map in global SR cfg
rather than IGP.
";
reference "draft-litkowski-spring-sr-yang-01";
}
revision 2015-04-23 {
description
"
* Node flag deprecated from prefixSID
* SR interface cfg moved to protocol
* Adding multiple binding policies for SRMS
";
reference "";
}
revision 2015-02-27 {
description
"Initial";
reference "draft-litkowski-spring-sr-yang-00";
}
feature mapping-server { revision 2019-02-15 {
description description
"Support of SRMS."; "
} * Addressed YANG Doctor's review comments;
";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
feature protocol-srgb { revision 2018-06-25 {
description description
"Support per-protocol srgb configuration."; "";
} reference "RFC XXXX: YANG Data Model for Segment Routing.";
feature msd { }
description revision 2017-07-01 {
"Support of signaling MSD (Maximum SID Depth) in IGP."; description
} "
* Implement NMDA model
*Conform to RFC6087BIS Appendix C
";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
typedef system-id { revision 2017-03-10 {
type string { description
pattern "[0-9A-Fa-f]{4}\\.[0-9A-Fa-f]{4}\\.[0-9A-Fa-f]{4}\\.00"; "
* Change global-sid-list to sid-list and add a leaf scope
* Added support of SRLB
* Added support of local sids
* fixed indentations
";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
revision 2016-10-28 {
description
"
* Add support of MSD (Maximum SID Depth)
* Update contact info
";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
revision 2016-10-24 {
description
"
* Moved common SR types and groupings to a seperate module
";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
revision 2016-07-07 {
description
"
* Add support of prefix-sid algorithm configuration
* change routing-protocols to control-plane-protocols
";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
revision 2016-03-17 {
description
"
* Add notification segment-routing-global-srgb-collision
* Add router-id to segment-routing-global-sid-collision
* Remove routing-instance
* Add typedef router-id
";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
revision 2015-10-17 {
description
"
* Add per-protocol SRGB config feature
* Move SRBG config to a grouping
";
reference "RFC XXXX: YANG Data Model for Segment Routing.";
}
revision 2015-06-22 {
description
"
* Prefix SID config moved to
connected-prefix-sid-map in global SR cfg
rather than IGP.
";
reference "draft-litkowski-spring-sr-yang-01";
}
revision 2015-04-23 {
description
"
* Node flag deprecated from prefixSID
* SR interface cfg moved to protocol
* Adding multiple binding policies for SRMS
";
reference "";
}
revision 2015-02-27 {
description
"Initial";
reference "draft-litkowski-spring-sr-yang-00";
} }
description
"This type defines ISIS system id using pattern,
system id looks like : 0143.0438.AeF0.00";
}
typedef router-id { feature mapping-server {
type union { description
type system-id; "Support of Segment Routing Mapping Server (SRMS).";
type rt-types:router-id;
} }
description
"OSPF/BGP router id or ISIS system ID.";
}
grouping controlplane-cfg { feature protocol-srgb {
description
"Defines protocol configuration.";
container segment-routing {
description description
"segment routing global config."; "Support per-protocol Segment Routing Global Block (SRGB)
leaf enabled { configuration.";
type boolean; }
default "false"; feature max-sid-depth {
description description
"Enables segment-routing "Support of signaling MSD (Maximum SID Depth) in IGP.";
protocol extensions."; }
typedef system-id {
type string {
pattern "[0-9A-Fa-f]{4}\\.[0-9A-Fa-f]{4}\\.[0-9A-Fa-f]{4}\\.00";
} }
container bindings { description
"This type defines ISIS system id using pattern,
system id looks like : 0143.0438.AeF0.00";
}
typedef router-id {
type union {
type system-id;
type rt-types:router-id;
}
description
"OSPF/BGP router id or ISIS system ID.";
}
grouping sr-controlplane {
description
"Defines protocol configuration.";
container segment-routing {
description description
"Control of binding advertisement "segment routing global config.";
and reception."; leaf enabled {
container advertise { type boolean;
default "false";
description description
"Authorize the advertise "Enables segment-routing
of local mappings in binding TLV."; protocol extensions.";
leaf-list policies {
type string;
description
"List of policies to be advertised.";
}
} }
leaf receive { container bindings {
type boolean;
default "true";
description description
"Authorize the reception and usage "Control of binding advertisement
of binding TLV."; and reception.";
container advertise {
description
"Authorize the advertise
of local mappings in binding TLV.";
leaf-list policies {
type string;
description
"List of policies to be advertised.";
}
}
leaf receive {
type boolean;
default "true";
description
"Authorize the reception and usage
of binding TLV.";
}
} }
} }
} }
}
grouping igp-interface-cfg { grouping igp-interface {
description
"Grouping for IGP interface cfg.";
container segment-routing {
description description
"container for SR interface cfg."; "Grouping for IGP interface cfg.";
container adjacency-sid { container segment-routing {
description description
"Defines the adjacency SID properties."; "container for SR interface cfg.";
list advertise-adj-group-sid { container adjacency-sid {
key "group-id";
description description
"Control advertisement of S flag. "Defines the adjacency SID properties.";
Enable to advertise a common Adj-SID list advertise-adj-group-sid {
for parallel links."; key "group-id";
leaf group-id {
type uint32;
description description
"The value is an internal value to identify "Control advertisement of S flag.
a group-ID. Interfaces with the same Enable to advertise a common Adj-SID
group-ID will be bundled together."; for parallel links.";
} leaf group-id {
} type uint32;
leaf advertise-protection {
type enumeration {
enum "single" {
description description
"A single Adj-SID is associated "The value is an internal value to identify
with the adjacency and reflects a group-ID. Interfaces with the same
the protection configuration."; group-ID will be bundled together.";
} }
enum "dual" { }
description leaf advertise-protection {
"Two Adj-SIDs will be associated type enumeration {
with the adjacency if interface enum "single" {
is protected. In this case description
one will be enforced with "A single Adj-SID is associated
backup flag set, the other with the adjacency and reflects
will be enforced to backup flag unset. the protection configuration.";
In case, protection is not configured, }
a single Adj-SID will be advertised enum "dual" {
with backup flag unset."; description
"Two Adj-SIDs will be associated
with the adjacency if interface
is protected. In this case
one will be enforced with
backup flag set, the other
will be enforced to backup flag unset.
In case, protection is not configured,
a single Adj-SID will be advertised
with backup flag unset.";
}
} }
description
"If set, the Adj-SID refers to an
adjacency being protected.";
} }
description
"If set, the Adj-SID refers to an
adjacency being protected.";
} }
} }
} }
}
grouping msd-cfg { grouping max-sid-depth {
description
"MSD configuration grouping.";
leaf node-msd {
type uint8;
description
"Node MSD is the lowest MSD supported by the node.";
}
container link-msd {
description description
"Link MSD is a number represetns the particular link MSD value."; "MSD configuration grouping.";
list link-msds { leaf node-msd {
key "interface"; type uint8;
description description
"List of link MSDs."; "Node MSD is the lowest MSD supported by the node.";
leaf interface { }
type if:interface-ref; container link-msd {
description description
"Name of the interface."; "Link MSD is a number representing the particular link
} MSD value.";
leaf msd { list link-msds {
type uint8; key "interface";
description description
"SID depth of the interface associated with the link."; "List of link MSDs.";
leaf interface {
type if:interface-ref;
description
"Name of the interface.";
}
leaf msd {
type uint8;
description
"SID depth of the interface associated with the link.";
}
} }
} }
} }
}
augment "/rt:routing" { augment "/rt:routing" {
description
"This augments routing data model (RFC 8349)
with segment-routing.";
container segment-routing {
description description
"segment routing global config."; "This augments routing data model (RFC 8349)
leaf transport-type { with segment-routing.";
type identityref { container segment-routing {
base sr-cmn:segment-routing-transport;
}
default "sr-cmn:segment-routing-transport-mpls";
description
"Dataplane to be used.";
}
uses sr-cmn:node-capabilities;
container msd {
if-feature "msd";
description
"MSD configuration.";
uses msd-cfg;
}
container bindings {
description description
"List of bindings."; "segment routing global config.";
container mapping-server { leaf transport-type {
if-feature "mapping-server"; type identityref {
base sr-cmn:segment-routing-transport;
}
default "sr-cmn:segment-routing-transport-mpls";
description description
"Configuration of mapping-server "Dataplane to be used.";
local entries."; }
list policy { uses sr-cmn:node-capabilities;
key "name"; container msd {
if-feature "max-sid-depth";
description
"MSD configuration.";
uses max-sid-depth;
}
container bindings {
description
"List of bindings.";
container mapping-server {
if-feature "mapping-server";
description description
"Definition of mapping policy."; "Configuration of mapping-server
leaf name { local entries.";
type string; list policy {
description key "name";
"Name of the mapping policy.";
}
container ipv4 {
description description
"IPv4 mapping entries."; "Definition of mapping policy.";
list mapping-entry { leaf name {
key "prefix algorithm"; type string;
description description
"Mapping entries."; "Name of the mapping policy.";
uses sr-cmn:ipv4-sid-cfg;
} }
container entries {
}
container ipv6 {
description
"IPv6 mapping entries.";
list mapping-entry {
key "prefix algorithm";
description description
"Mapping entries."; "IPv4/IPv6 mapping entries.";
uses sr-cmn:ipv6-sid-cfg; list mapping-entry {
key "prefix algorithm";
description
"Mapping entries.";
uses sr-cmn:prefix-sid;
}
} }
} }
} }
} container connected-prefix-sid-map {
container connected-prefix-sid-map {
description
"Prefix SID configuration.";
container ipv4 {
description
"Parameters associated with IPv4 prefix SID";
list ipv4-prefix-sid {
key "prefix algorithm";
description
"List of prefix SID
mapped to IPv4 local prefixes.";
uses sr-cmn:ipv4-sid-cfg;
uses sr-cmn:last-hop-behavior;
}
}
container ipv6 {
description description
"Parameters associated with IPv6 prefix SID"; "Prefix SID configuration.";
list ipv6-prefix-sid { list connected-prefix-sid {
key "prefix algorithm"; key "prefix algorithm";
description description
"List of prefix SID "List of prefix SID mapped to
mapped to IPv6 local prefixes."; ipv4/ipv6 local prefixes.";
uses sr-cmn:ipv6-sid-cfg; uses sr-cmn:prefix-sid;
uses sr-cmn:last-hop-behavior; uses sr-cmn:last-hop-behavior;
} }
} }
} container local-prefix-sid {
container local-prefix-sid {
description
"Local sid configuration.";
container ipv4 {
description
"List of local ipv4 sids.";
list ipv4-prefix-sid-local {
key "prefix algorithm";
description
"List of local prefix-sid.";
uses sr-cmn:ipv4-sid-cfg;
}
}
container ipv6 {
description description
"List of local ipv6 sids."; "Local sid configuration.";
list ipv6-prefix-sid-local { list local-prefix-sid {
key "prefix algorithm"; key "prefix algorithm";
description description
"List of local prefix-sid."; "List of local ipv4/ipv6 prefix-sid.";
uses sr-cmn:ipv6-sid-cfg; uses sr-cmn:prefix-sid;
} }
} }
} }
} container global-srgb {
container global-srgb {
description
"Global SRGB configuration.";
uses sr-cmn:srgb-cfg;
}
container srlb {
description
"SR Local Block configuration.";
uses sr-cmn:srlb-cfg;
}
list label-blocks {
config false;
description
"List of labels blocks currently
in use.";
leaf lower-bound {
type uint32;
description description
"Lower bound of the label block."; "Global SRGB configuration.";
uses sr-cmn:srgb;
} }
leaf upper-bound { container srlb {
type uint32;
description description
"Upper bound of the label block."; "SR Local Block configuration.";
uses sr-cmn:srlb;
} }
leaf size {
type uint32;
description
"Number of indexes in the block.";
} list label-blocks {
leaf free { config false;
type uint32;
description
"Number of indexes free in the block.";
}
leaf used {
type uint32;
description
"Number of indexes used in the block.";
}
leaf scope {
type enumeration {
enum "global" {
description
"Global sid.";
}
enum "local" {
description
"Local sid.";
}
}
description
"Scope of this label block.";
}
}
container sid-list {
config false;
description
"List of prefix and SID associations.";
list sid {
key "target sid source source-protocol binding-type";
ordered-by system;
description description
"Binding."; "List of labels blocks currently
leaf target { in use.";
type string; leaf lower-bound {
type uint32;
description description
"Defines the target of the binding. "Lower bound of the label block.";
It can be a prefix or something else.";
} }
leaf sid { leaf upper-bound {
type uint32; type uint32;
description description
"Index associated with the prefix."; "Upper bound of the label block.";
} }
leaf algorithm { leaf size {
type uint8; type uint32;
description description
"Algorithm to be used for the prefix "Number of indexes in the block.";
SID.";
} }
leaf source { leaf free {
type inet:ip-address; type uint32;
description description
"IP address of the router than own "Number of indexes free in the block.";
the binding.";
} }
leaf used { leaf used {
type boolean; type uint32;
description
"Defines if the binding is used
in forwarding plane.";
}
leaf source-protocol {
type leafref {
path "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rt:name";
}
description
"Rtg protocol that owns the binding";
}
leaf binding-type {
type enumeration {
enum "prefix-sid" {
description
"Binding is learned from
a prefix SID.";
}
enum "binding-tlv" {
description
"Binding is learned from
a binding TLV.";
}
}
description description
"Type of binding."; "Number of indexes used in the block.";
} }
leaf scope { leaf scope {
type enumeration { type enumeration {
enum "global" { enum "global" {
description description
"Global sid."; "Global sid.";
} }
enum "local" { enum "local" {
description description
"Local sid."; "Local sid.";
} }
} }
description description
"The sid is local or global."; "Scope of this label block.";
}
}
container sid-list {
config false;
description
"List of prefix and SID associations.";
list sid {
key "target sid source source-protocol binding-type";
ordered-by system;
description
"Binding.";
leaf target {
type string;
description
"Defines the target of the binding.
It can be a prefix or something else.";
}
leaf sid {
type uint32;
description
"Index associated with the prefix.";
}
leaf algorithm {
type uint8;
description
"Algorithm to be used for the prefix
SID.";
}
leaf source {
type inet:ip-address;
description
"IP address of the router than own
the binding.";
}
leaf used {
type boolean;
description
"Defines if the binding is used
in forwarding plane.";
}
leaf source-protocol {
type leafref {
path "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rt:name";
}
description
"Rtg protocol that owns the binding";
}
leaf binding-type {
type enumeration {
enum "prefix-sid" {
description
"Binding is learned from
a prefix SID.";
}
enum "binding-tlv" {
description
"Binding is learned from
a binding TLV.";
}
}
description
"Type of binding.";
}
leaf scope {
type enumeration {
enum "global" {
description
"Global sid.";
}
enum "local" {
description
"Local sid.";
}
}
description
"The sid is local or global.";
}
} }
} }
} }
} }
}
notification segment-routing-global-srgb-collision { notification segment-routing-global-srgb-collision {
description
"This notification is sent when received SRGB blocks from
a router conflict.";
list srgb-collisions {
description description
"List of SRGB blocks that conflict."; "This notification is sent when received SRGB blocks from
leaf lower-bound { a router conflict.";
type uint32; list srgb-collisions {
description description
"Lower value in the block."; "List of SRGB blocks that conflict.";
leaf lower-bound {
type uint32;
description
"Lower value in the block.";
}
leaf upper-bound {
type uint32;
description
"Upper value in the block.";
}
leaf routing-protocol {
type leafref {
path "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rt:name";
}
description
"Routing protocol reference that received the event.";
}
leaf originating-rtr-id {
type router-id;
description
"Originating router id of this SRGB block.";
}
} }
leaf upper-bound { }
notification segment-routing-global-sid-collision {
description
"This notification is sent when a new mapping is learned
, containing mapping
where the SID is already used.
The notification generation must be throttled with at least
a 5 second gap. ";
leaf received-target {
type string;
description
"Target received in the controlplane that
caused SID collision.";
}
leaf new-sid-rtr-id {
type router-id;
description
"Router Id that advertising the conflicting SID.";
}
leaf original-target {
type string;
description
"Target already available in database that have the same SID
as the received target.";
}
leaf original-sid-rtr-id {
type router-id;
description
"Original router ID that advertised the conflicting SID.";
}
leaf index {
type uint32; type uint32;
description description
"Upper value in the block."; "Value of the index used by two different prefixes.";
} }
leaf routing-protocol { leaf routing-protocol {
type leafref { type leafref {
path "/rt:routing/rt:control-plane-protocols/" path "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rt:name"; + "rt:control-plane-protocol/rt:name";
} }
description description
"Routing protocol reference that received the event."; "Routing protocol reference that received the event.";
} }
leaf originating-rtr-id {
type router-id;
description
"Originating router id of this SRGB block.";
}
} }
} notification segment-routing-index-out-of-range {
notification segment-routing-global-sid-collision {
description
"This notification is sent when a new mapping is learned
, containing mapping
where the SID is already used.
The notification generation must be throttled with at least
a 5 second gap. ";
leaf received-target {
type string;
description
"Target received in the controlplane that
caused SID collision.";
}
leaf new-sid-rtr-id {
type router-id;
description
"Router Id that advertising the conflicting SID.";
}
leaf original-target {
type string;
description
"Target already available in database that have the same SID
as the received target.";
}
leaf original-sid-rtr-id {
type router-id;
description
"Original router ID that advertised the conflicting SID.";
}
leaf index {
type uint32;
description description
"Value of the index used by two different prefixes."; "This notification is sent when a binding
} is received, containing a segment index
leaf routing-protocol { which is out of the local configured ranges.
type leafref { The notification generation must be throttled with at least
path "/rt:routing/rt:control-plane-protocols/" a 5 second gap. ";
+ "rt:control-plane-protocol/rt:name"; leaf received-target {
type string;
description
"Target received in the controlplane
that caused SID collision.";
} }
description leaf received-index {
"Routing protocol reference that received the event."; type uint32;
} description
} "Value of the index received.";
notification segment-routing-index-out-of-range { }
description leaf routing-protocol {
"This notification is sent when a binding type leafref {
is received, containing a segment index path "/rt:routing/rt:control-plane-protocols/"
which is out of the local configured ranges. + "rt:control-plane-protocol/rt:name";
The notification generation must be throttled with at least }
a 5 second gap. "; description
leaf received-target { "Routing protocol reference that received the event.";
type string;
description
"Target received in the controlplane
that caused SID collision.";
}
leaf received-index {
type uint32;
description
"Value of the index received.";
}
leaf routing-protocol {
type leafref {
path "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rt:name";
} }
description
"Routing protocol reference that received the event.";
} }
} }
} <CODE ENDS>
<CODE ENDS>
8. Security Considerations 9. Security Considerations
TBD. TBD.
9. Acknowledgements 10. Acknowledgements
Authors would like to thank Derek Yeung, Acee Lindem, Greg Hankins, Authors would like to thank Derek Yeung, Acee Lindem, Greg Hankins,
Hannes Gredler, Uma Chunduri, Jeffrey Zhang, Shradda Hedge, Les Hannes Gredler, Uma Chunduri, Jeffrey Zhang, Shradda Hedge, Les
Ginsberg for their contributions. Ginsberg for their contributions.
10. IANA Considerations 11. IANA Considerations
TBD. TBD.
11. References 12. References
11.1. Normative References 12.1. Normative References
[I-D.ietf-isis-segment-routing-msd] [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Tantsura, J., Chunduri, U., Aldrin, S., and L. Ginsberg, Requirement Levels", BCP 14, RFC 2119,
"Signaling MSD (Maximum SID Depth) using IS-IS", draft- DOI 10.17487/RFC2119, March 1997,
ietf-isis-segment-routing-msd-04 (work in progress), June <https://www.rfc-editor.org/info/rfc2119>.
2017.
[I-D.ietf-ospf-segment-routing-msd] [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
Tantsura, J., Chunduri, U., Aldrin, S., and P. Psenak, the Network Configuration Protocol (NETCONF)", RFC 6020,
"Signaling MSD (Maximum SID Depth) using OSPF", draft- DOI 10.17487/RFC6020, October 2010,
ietf-ospf-segment-routing-msd-05 (work in progress), June <https://www.rfc-editor.org/info/rfc6020>.
2017.
[I-D.ietf-spring-segment-routing] [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
Filsfils, C., Previdi, S., Decraene, B., Litkowski, S., RFC 6991, DOI 10.17487/RFC6991, July 2013,
and R. Shakir, "Segment Routing Architecture", draft-ietf- <https://www.rfc-editor.org/info/rfc6991>.
spring-segment-routing-12 (work in progress), June 2017.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
Requirement Levels", BCP 14, RFC 2119, March 1997. RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>.
[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the [RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger,
Network Configuration Protocol (NETCONF)", RFC 6020, "Common YANG Data Types for the Routing Area", RFC 8294,
October 2010. DOI 10.17487/RFC8294, December 2017,
<https://www.rfc-editor.org/info/rfc8294>.
[RFC7950] Bjorklund, M., "The YANG 1.1 Data Modeling Language", [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
RFC 7950, August 2016. and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>.
11.2. Informative References [RFC8343] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,
<https://www.rfc-editor.org/info/rfc8343>.
[I-D.ietf-netmod-yang-tree-diagrams] [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for
Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft- Routing Management (NMDA Version)", RFC 8349,
ietf-netmod-yang-tree-diagrams-06 (work in progress), DOI 10.17487/RFC8349, March 2018,
February 2018. <https://www.rfc-editor.org/info/rfc8349>.
[RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L.,
Decraene, B., Litkowski, S., and R. Shakir, "Segment
Routing Architecture", RFC 8402, DOI 10.17487/RFC8402,
July 2018, <https://www.rfc-editor.org/info/rfc8402>.
[RFC8476] Tantsura, J., Chunduri, U., Aldrin, S., and P. Psenak,
"Signaling Maximum SID Depth (MSD) Using OSPF", RFC 8476,
DOI 10.17487/RFC8476, December 2018,
<https://www.rfc-editor.org/info/rfc8476>.
[RFC8491] Tantsura, J., Chunduri, U., Aldrin, S., and L. Ginsberg,
"Signaling Maximum SID Depth (MSD) Using IS-IS", RFC 8491,
DOI 10.17487/RFC8491, November 2018,
<https://www.rfc-editor.org/info/rfc8491>.
12.2. Informative References
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>.
Authors' Addresses Authors' Addresses
Stephane Litkowski Stephane Litkowski
Orange Business Service Orange Business Service
Email: stephane.litkowski@orange.com Email: stephane.litkowski@orange.com
Yingzhen Qu Yingzhen Qu
Huawei Huawei
 End of changes. 176 change blocks. 
963 lines changed or deleted 990 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/