draft-ietf-teas-yang-sr-te-topo-02.txt   draft-ietf-teas-yang-sr-te-topo-03.txt 
Network Working Group X. Liu Network Working Group X. Liu
Internet-Draft Volta Networks Internet-Draft Volta Networks
Intended status: Standards Track I. Bryskin Intended status: Standards Track I. Bryskin
Expires: January 2, 2019 Huawei Technologies Expires: April 25, 2019 Huawei Technologies
V. Beeram V. Beeram
Juniper Networks Juniper Networks
T. Saad T. Saad
Cisco Systems Inc Cisco Systems Inc
H. Shah H. Shah
Ciena Ciena
S. Litkowski S. Litkowski
Orange Business Service Orange Business Service
July 1, 2018 October 22, 2018
YANG Data Model for SR and SR TE Topologies YANG Data Model for SR and SR TE Topologies
draft-ietf-teas-yang-sr-te-topo-02 draft-ietf-teas-yang-sr-te-topo-03
Abstract Abstract
This document defines a YANG data model for Segment Routing (SR) This document defines a YANG data model for Segment Routing (SR)
topology and Segment Routing (SR) traffic engineering (TE) topology. topology and Segment Routing (SR) traffic engineering (TE) topology.
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.
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 January 2, 2019. This Internet-Draft will expire on April 25, 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
(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
skipping to change at page 2, line 23 skipping to change at page 2, line 23
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3
2. Modeling Considerations . . . . . . . . . . . . . . . . . . . 3 2. Modeling Considerations . . . . . . . . . . . . . . . . . . . 3
2.1. Segment Routing (SR) Topology . . . . . . . . . . . . . . 3 2.1. Segment Routing (SR) Topology . . . . . . . . . . . . . . 3
2.2. Segment Routing (SR) TE Topology . . . . . . . . . . . . 3 2.2. Segment Routing (SR) TE Topology . . . . . . . . . . . . 3
2.3. Relations to ietf-segment-routing . . . . . . . . . . . . 4 2.3. Relations to ietf-segment-routing . . . . . . . . . . . . 4
2.4. Topology Type Modeling . . . . . . . . . . . . . . . . . 5 2.4. Topology Type Modeling . . . . . . . . . . . . . . . . . 5
2.5. Topology Attributes . . . . . . . . . . . . . . . . . . . 5 2.5. Topology Attributes . . . . . . . . . . . . . . . . . . . 5
2.6. Node Attributes . . . . . . . . . . . . . . . . . . . . . 5 2.6. Node Attributes . . . . . . . . . . . . . . . . . . . . . 5
2.7. Link Termination Point Attributes . . . . . . . . . . . . 6 2.7. Link Attributes . . . . . . . . . . . . . . . . . . . . . 6
2.8. Link in the Topology Model . . . . . . . . . . . . . . . 7
3. Model Structure . . . . . . . . . . . . . . . . . . . . . . . 7 3. Model Structure . . . . . . . . . . . . . . . . . . . . . . . 7
4. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 9 4. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 8
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
6. Security Considerations . . . . . . . . . . . . . . . . . . . 15 6. Security Considerations . . . . . . . . . . . . . . . . . . . 16
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.1. Normative References . . . . . . . . . . . . . . . . . . 16 7.1. Normative References . . . . . . . . . . . . . . . . . . 18
7.2. Informative References . . . . . . . . . . . . . . . . . 16 7.2. Informative References . . . . . . . . . . . . . . . . . 19
Appendix A. Companion YANG Model for Non-NMDA Compliant Appendix A. Companion YANG Model for Non-NMDA Compliant
Implementations . . . . . . . . . . . . . . . . . . 18 Implementations . . . . . . . . . . . . . . . . . . 20
A.1. SR Topology State Module . . . . . . . . . . . . . . . . 18 A.1. SR Topology State Module . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 Appendix B. Data Tree Example . . . . . . . . . . . . . . . . . 23
Appendix C. Contributors . . . . . . . . . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 30
1. Introduction 1. Introduction
This document defines a YANG [RFC7950] data model for describing the This document defines a YANG [RFC7950] data model for describing the
presentations of Segment Routing (SR) topology and Segment Routing presentations of Segment Routing (SR) topology and Segment Routing
(SR) traffic engineering (TE) topology. The version of the model (SR) traffic engineering (TE) topology. The version of the model
limits the transport type to an MPLS dataplane. limits the transport type to an MPLS dataplane.
1.1. Terminology 1.1. Terminology
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14, [RFC2119]. 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
The following terms are defined in [RFC7950] and are not redefined The following terms are defined in [RFC7950] and are not redefined
here: here:
o augment o augment
o data model o data model
o data node o data node
skipping to change at page 4, line 32 skipping to change at page 4, line 32
L3 Topology: L3 Topology:
/nd:networks/nd:network/nd:network-types/l3-unicast-topology /nd:networks/nd:network/nd:network-types/l3-unicast-topology
L3 TE Topology: L3 TE Topology:
/nd:networks/nd:network/nd:network-types/l3-unicast-topology/l3-te /nd:networks/nd:network/nd:network-types/l3-unicast-topology/l3-te
SR Topology: SR Topology:
/nd:networks/nd:network/nd:network-types/l3-unicast-topology/sr /nd:networks/nd:network/nd:network-types/l3-unicast-topology/sr-mpls
SR TE Topology: (multiple inheritance) SR TE Topology: (multiple inheritance)
/nd:networks/nd:network/nd:network-types/l3-unicast-topology/l3-te /nd:networks/nd:network/nd:network-types/l3-unicast-topology/l3-te
/nd:networks/nd:network/nd:network-types/l3-unicast-topology/sr /nd:networks/nd:network/nd:network-types/l3-unicast-topology/sr-mpls
2.3. Relations to ietf-segment-routing 2.3. Relations to ietf-segment-routing
[I-D.ietf-spring-sr-yang] defines ietf-segment-routing that is a [I-D.ietf-spring-sr-yang] defines ietf-segment-routing that is a
model intended to be used on network elements to configure or operate model intended to be used on network elements to configure or operate
segment routing; ietf-sr-topology defined in this document is segment routing; ietf-sr-topology defined in this document is
intended to be used on a controller for the network-wide operations intended to be used on a controller for the network-wide operations
such as path computation. such as path computation.
SR topology model shares many modeling constructs defined in ietf- SR topology model shares many modeling constructs defined in ietf-
segment-routing. The module ietf-sr-topology uses the types and segment-routing. The module ietf-sr-topology uses the types and
groupings defined in ietf-segment-routing. groupings defined in ietf-segment-routing.
2.4. Topology Type Modeling 2.4. Topology Type Modeling
A new topology type is defined in this document, to indicate a A new topology type is defined in this document, to indicate a
topology that is a Segment Routing (SR) topology. topology that is a Segment Routing (SR) topology on an MPLS
dataplane.
augment /nw:networks/nw:network/nw:network-types augment /nw:networks/nw:network/nw:network-types
/l3t:l3-unicast-topology: /l3t:l3-unicast-topology:
+--rw sr! +--rw sr-mpls!
2.5. Topology Attributes 2.5. Topology Attributes
The Segment Routing attributes with topology-wide impacts are modeled The Segment Routing attributes with topology-wide impacts are modeled
by augmenting the container "l3-topology-attributes" in the L3 by augmenting the container "l3-topology-attributes" in the L3
topology model. SRGB (Segment Routing Global Block) is covered in topology model. SRGB (Segment Routing Global Block) is covered in
this augmentation. A SR domain is mapped to a topology in this this augmentation. A SR domain is mapped to a topology in this
model. model.
augment /nw:networks/nw:network/l3t:l3-topology-attributes: augment /nw:networks/nw:network/l3t:l3-topology-attributes:
skipping to change at page 6, line 13 skipping to change at page 6, line 13
attributes are learned: attributes are learned:
augment /nw:networks/nw:network/nw:node/l3t:l3-node-attributes: augment /nw:networks/nw:network/nw:node/l3t:l3-node-attributes:
+--rw sr +--rw sr
+--rw srgb* [lower-bound upper-bound] +--rw srgb* [lower-bound upper-bound]
| +--rw lower-bound uint32 | +--rw lower-bound uint32
| +--rw upper-bound uint32 | +--rw upper-bound uint32
+--rw srlb* [lower-bound upper-bound] +--rw srlb* [lower-bound upper-bound]
| +--rw lower-bound uint32 | +--rw lower-bound uint32
| +--rw upper-bound uint32 | +--rw upper-bound uint32
+--rw node-capabilities +--ro node-capabilities
| +--rw transport-planes* [transport-plane] | +--ro transport-planes* [transport-plane]
| | +--rw transport-plane identityref | | +--ro transport-plane identityref
| +--rw readable-label-stack-depth? uint8 | +--ro entropy-readable-label-depth? uint8
+--rw msd? uint8 {msd}?
+--ro information-source? enumeration +--ro information-source? enumeration
+--ro information-source-state +--ro information-source-state
+--ro credibility-preference? uint16 +--ro credibility-preference? uint16
The SR attributes that are related to a IGP-Prefix segment are The SR attributes that are related to a IGP-Prefix segment are
modeled by augmenting the list entry "prefix" in the L3 topology modeled by augmenting the list entry "prefix" in the L3 topology
model: model:
augment /nw:networks/nw:network/nw:node/l3t:l3-node-attributes augment /nw:networks/nw:network/nw:node/l3t:l3-node-attributes
/l3t:prefix: /l3t:prefix:
+--rw sr! +--rw sr!
+--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 last-hop-behavior? enumeration +--rw last-hop-behavior? enumeration
| {sid-last-hop-behavior}? | {sid-last-hop-behavior}?
+--rw is-local? boolean +--rw is-local? boolean
+--rw is-node? boolean
+--ro is-readvertisment? boolean
2.7. Link Termination Point Attributes 2.7. Link Attributes
A link termination point in the topology model is mapped to an A link in the topology model connects the termination point on the
interface from the Segment Routing perspective. The Adjacency source node to the termination point on the destination node. When
Segment attributes on an interface are modeled within a link such a link is instantiated, the bindings between the nodes and the
termination point. The modeling structure is as follows: corresponding Adj-SIDs are formed, and the resulting FIB entries are
installed.
augment /nw:networks/nw:network/nw:node/nt:termination-point A link in the topology model is mapped to an SR Adjacency Segment,
/l3t:l3-termination-point-attributes: formed by a pair of interfaces on two respective adjacent nodes. The
SR Adjacency Segment attributes are modeled by augmenting the link
attributes of the L3 topology model. The modeling structure is as
follows:
augment /nw:networks/nw:network/nt:link/l3t:l3-link-attributes:
+--rw sr! +--rw sr!
+--rw value-type? enumeration +--rw value-type? enumeration
+--rw sid uint32 +--rw sid uint32
+--rw advertise-protection? enumeration +--rw advertise-protection? enumeration
+--rw is-local? boolean +--rw is-local? boolean
+--ro is-backup? boolean +--rw msd? uint8 {msd}?
+--ro is-part-of-set? boolean +--rw address-family? enumeration
+--ro is-on-lan? boolean +--rw is-backup? boolean
+--rw is-part-of-set? boolean
+--rw is-persistent? boolean
+--rw is-on-lan? boolean
+--ro information-source? enumeration +--ro information-source? enumeration
+--ro information-source-state +--ro information-source-state
+--ro credibility-preference? uint16 +--ro credibility-preference? uint16
The usage of the leaf "advertise-protection" is described in The usage of the leaf "advertise-protection" is described in
[I-D.ietf-spring-sr-yang]. [I-D.ietf-spring-sr-yang].
Since YANG models are usually implemented with persistent
configuration datastores, this model supports only persistent
Adjacency Segments.
Both IGP and BGP can be supported by the model, the leaf Both IGP and BGP can be supported by the model, the leaf
"information-source" is used to indicate where the information is "information-source" is used to indicate where the information is
from. from.
The bundling capability of the Adjacency Segemnt is achieved by re- The bundling capability of the Adjacency Segemnt is achieved by re-
using the existing modeling construct (i.e. "bundle-stack-level") using the existing modeling construct (i.e. "bundle-stack-level")
under /nw:networks/nw:network/nt:link/tet:te under /nw:networks/nw:network/nt:link/tet:te
[I-D.ietf-teas-yang-te-topo] [I-D.ietf-teas-yang-te-topo]
2.8. Link in the Topology Model
A link in the topology model connects the termination point on the
source node to the termination point on the destination node. When
such a link is instantiated, the bindings between the nodes and the
corresponding Adj-SIDs are formed, and the resulting FIB entries are
installed.
3. Model Structure 3. Model Structure
The model tree structure of the Segment Routing (SR) topology module The model tree structure of the Segment Routing (SR) topology module
is as shown below: is as shown below:
module: ietf-sr-topology module: ietf-sr-topology
augment /nw:networks/nw:network/nw:network-types augment /nw:networks/nw:network/nw:network-types
/l3t:l3-unicast-topology: /l3t:l3-unicast-topology:
+--rw sr! +--rw sr-mpls!
augment /nw:networks/nw:network/l3t:l3-topology-attributes: augment /nw:networks/nw:network/l3t:l3-topology-attributes:
+--rw sr +--rw sr
+--rw srgb* [lower-bound upper-bound] +--rw srgb* [lower-bound upper-bound]
+--rw lower-bound uint32 +--rw lower-bound uint32
+--rw upper-bound uint32 +--rw upper-bound uint32
augment /nw:networks/nw:network/nw:node/l3t:l3-node-attributes: augment /nw:networks/nw:network/nw:node/l3t:l3-node-attributes:
+--rw sr +--rw sr
+--rw srgb* [lower-bound upper-bound] +--rw srgb* [lower-bound upper-bound]
| +--rw lower-bound uint32 | +--rw lower-bound uint32
| +--rw upper-bound uint32 | +--rw upper-bound uint32
+--rw srlb* [lower-bound upper-bound] +--rw srlb* [lower-bound upper-bound]
| +--rw lower-bound uint32 | +--rw lower-bound uint32
| +--rw upper-bound uint32 | +--rw upper-bound uint32
+--rw node-capabilities +--ro node-capabilities
| +--rw transport-planes* [transport-plane] | +--ro transport-planes* [transport-plane]
| | +--rw transport-plane identityref | | +--ro transport-plane identityref
| +--rw readable-label-stack-depth? uint8 | +--ro entropy-readable-label-depth? uint8
+--rw msd? uint8 {msd}?
+--ro information-source? enumeration +--ro information-source? enumeration
+--ro information-source-state +--ro information-source-state
+--ro credibility-preference? uint16 +--ro credibility-preference? uint16
augment /nw:networks/nw:network/nw:node/l3t:l3-node-attributes augment /nw:networks/nw:network/nw:node/l3t:l3-node-attributes
/l3t:prefix: /l3t:prefix:
+--rw sr! +--rw sr!
+--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 last-hop-behavior? enumeration +--rw last-hop-behavior? enumeration
| {sid-last-hop-behavior}? | {sid-last-hop-behavior}?
+--rw is-local? boolean +--rw is-local? boolean
augment /nw:networks/nw:network/nw:node/nt:termination-point +--rw is-node? boolean
/l3t:l3-termination-point-attributes: +--ro is-readvertisment? boolean
augment /nw:networks/nw:network/nt:link/l3t:l3-link-attributes:
+--rw sr! +--rw sr!
+--rw value-type? enumeration +--rw value-type? enumeration
+--rw sid uint32 +--rw sid uint32
+--rw advertise-protection? enumeration +--rw advertise-protection? enumeration
+--rw is-local? boolean +--rw is-local? boolean
+--ro is-backup? boolean +--rw msd? uint8 {msd}?
+--ro is-part-of-set? boolean +--rw address-family? enumeration
+--ro is-on-lan? boolean +--rw is-backup? boolean
+--rw is-part-of-set? boolean
+--rw is-persistent? boolean
+--rw is-on-lan? boolean
+--ro information-source? enumeration +--ro information-source? enumeration
+--ro information-source-state +--ro information-source-state
+--ro credibility-preference? uint16 +--ro credibility-preference? uint16
4. YANG Module 4. YANG Module
<CODE BEGINS> file "ietf-sr-topology@2018-06-22.yang" <CODE BEGINS> file "ietf-sr-topology@2018-10-03.yang"
module ietf-sr-topology { module ietf-sr-topology {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-sr-topology"; namespace "urn:ietf:params:xml:ns:yang:ietf-sr-topology";
prefix "srt"; prefix "srt";
import ietf-network { import ietf-network {
prefix "nw"; prefix "nw";
reference "RFC 8345: A YANG Data Model for Network Topologies"; reference "RFC 8345: A YANG Data Model for Network Topologies";
} }
import ietf-network-topology { import ietf-network-topology {
skipping to change at page 10, line 26 skipping to change at page 10, line 20
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the This version of this YANG module is part of RFC XXXX; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
revision 2018-06-22 { revision 2018-10-03 {
description "Initial revision"; description "Initial revision";
reference reference
"RFC XXXX: YANG Data Model for SR and SR TE Topologies"; "RFC XXXX: YANG Data Model for SR and SR TE Topologies";
} }
feature msd {
description
"Support of signaling MSD (Maximum SID Depth) in IGP.";
}
grouping sr-topology-type { grouping sr-topology-type {
description description
"Identifies the SR topology type."; "Identifies the SR-MPLS topology type. This type of network
container sr { toplogies use Segment Routing (SR) technology over the MPLS
presence "Indiates SR Topology"; data plane";
container sr-mpls {
presence "Indiates SR-MPLS topology";
description description
"Its presence identifies the SR topology type."; "Its presence identifies the SR topology type.";
} }
} }
augment "/nw:networks/nw:network/nw:network-types/" augment "/nw:networks/nw:network/nw:network-types/"
+ "l3t:l3-unicast-topology" { + "l3t:l3-unicast-topology" {
description description
"Defines the SR topology type."; "Defines the SR topology type.";
uses sr-topology-type; uses sr-topology-type;
} }
augment "/nw:networks/nw:network/l3t:l3-topology-attributes" { augment "/nw:networks/nw:network/l3t:l3-topology-attributes" {
when "../nw:network-types/l3t:l3-unicast-topology/srt:sr" { when "../nw:network-types/l3t:l3-unicast-topology/srt:sr-mpls" {
description "Augment only for SR topology."; description "Augment only for SR topology.";
} }
description "Augment topology configuration"; description "Augment topology configuration";
uses sr-topology-attributes; uses sr-topology-attributes;
} }
augment "/nw:networks/nw:network/nw:node/l3t:l3-node-attributes" { augment "/nw:networks/nw:network/nw:node/l3t:l3-node-attributes" {
when "../../nw:network-types/l3t:l3-unicast-topology/srt:sr" { when "../../nw:network-types/l3t:l3-unicast-topology/"
+ "srt:sr-mpls" {
description "Augment only for SR topology."; description "Augment only for SR topology.";
} }
description "Augment node configuration."; description "Augment node configuration.";
uses sr-node-attributes; uses sr-node-attributes;
} }
augment "/nw:networks/nw:network/nw:node/l3t:l3-node-attributes" augment "/nw:networks/nw:network/nw:node/l3t:l3-node-attributes"
+ "/l3t:prefix" { + "/l3t:prefix" {
when "../../../nw:network-types/l3t:l3-unicast-topology/srt:sr" { when "../../../nw:network-types/l3t:l3-unicast-topology/"
+ "srt:sr-mpls" {
description "Augment only for SR topology."; description "Augment only for SR topology.";
} }
description "Augment node prefix."; description "Augment node prefix.";
uses sr-node-prefix-attributes; uses sr-node-prefix-attributes;
} }
augment "/nw:networks/nw:network/nw:node/nt:termination-point/" augment "/nw:networks/nw:network/nt:link/l3t:l3-link-attributes" {
+ "l3t:l3-termination-point-attributes" { when "../../nw:network-types/l3t:l3-unicast-topology/"
when "../../../nw:network-types/l3t:l3-unicast-topology/" + "srt:sr-mpls" {
+ "srt:sr" {
description "Augment only for SR topology."; description "Augment only for SR topology.";
} }
description "Augment termination point configuration"; description "Augment link configuration";
uses sr-tp-attributes; uses sr-link-attributes;
} }
grouping sr-topology-attributes { grouping sr-topology-attributes {
description "SR topology scope attributes."; description "SR topology scope attributes.";
container sr { container sr {
description description
"Containing SR attributes."; "Containing SR attributes.";
uses sr-cmn:srgb-cfg; uses sr-cmn:srgb-cfg;
} // sr } // sr
} // sr-topology-attributes } // sr-topology-attributes
skipping to change at page 13, line 6 skipping to change at page 13, line 8
} // information-source-attributes } // information-source-attributes
grouping sr-node-attributes { grouping sr-node-attributes {
description "SR node scope attributes."; description "SR node scope attributes.";
container sr { container sr {
description description
"Containing SR attributes."; "Containing SR attributes.";
uses sr-cmn:srgb-cfg; uses sr-cmn:srgb-cfg;
uses sr-cmn:srlb-cfg; uses sr-cmn:srlb-cfg;
uses sr-cmn:node-capabilities; uses sr-cmn:node-capabilities;
leaf msd {
if-feature "msd";
type uint8;
description
"Node MSD is the lowest MSD supported by the node.";
}
// Operational state data // Operational state data
uses information-source-attributes; uses information-source-attributes;
} // sr } // sr
} // sr-node-attributes } // sr-node-attributes
grouping sr-node-prefix-attributes { grouping sr-node-prefix-attributes {
description "Containing SR attributes for a prefix."; description "Containing SR attributes for a prefix.";
container sr { container sr {
presence "Presence indicates SR is enabled."; presence "Presence indicates SR is enabled.";
description description
"Containing SR attributes for a prefix."; "Containing SR attributes for a prefix.";
uses sr-cmn:prefix-sid-attributes; uses sr-cmn:prefix-sid-attributes;
uses sr-cmn:last-hop-behavior; uses sr-cmn:last-hop-behavior;
leaf is-local { leaf is-local {
type boolean; type boolean;
default false;
description description
"'true' if the SID is local."; "'true' if the SID is local.";
} }
leaf is-node {
type boolean;
default false;
description
"'true' if the Prefix-SID refers to the router identified
by the prefix. Typically, the leaf 'is-node' (N-Flag)
is set on Prefix-SIDs attached to a router loopback
address.";
}
leaf is-readvertisment {
type boolean;
config false;
description
"'true' if the prefix to which this Prefix-SID is attached,
has been propagated by the router from another
topology by redistribution.";
}
} // sr } // sr
} // sr-node-prefix-attributes } // sr-node-prefix-attributes
grouping sr-link-attributes {
grouping sr-tp-attributes { description "SR link scope attributes";
description "SR termination point scope attributes";
container sr { container sr {
presence "Presence indicates SR is enabled."; presence "Presence indicates SR is enabled.";
description description
"Containing SR attributes."; "Containing SR attributes.";
uses sr-cmn:sid-value-type; uses sr-cmn:sid-value-type;
leaf sid { leaf sid {
type uint32; type uint32;
mandatory true; mandatory true;
description description
"Adjacency SID, which can be either IGP-Adjacency SID "Adjacency SID, which can be either IGP-Adjacency SID
skipping to change at page 14, line 14 skipping to change at page 14, line 39
with the adjacency if interface with the adjacency if interface
is protected. In this case is protected. In this case
one will be enforced with one will be enforced with
backup flag set, the other backup flag set, the other
will be enforced to backup flag unset. will be enforced to backup flag unset.
In case, protection is not configured, In case, protection is not configured,
a single Adj-SID will be advertised a single Adj-SID will be advertised
with backup flag unset."; with backup flag unset.";
} }
} }
default "single";
description description
"If set, the Adj-SID refers to an "If set, the Adj-SID refers to an
adjacency being protected."; adjacency being protected.";
} }
leaf is-local { leaf is-local {
type boolean; type boolean;
default false;
description description
"'true' if the SID is local."; "'true' if the SID is local.";
} }
leaf msd {
if-feature "msd";
type uint8;
description
"SID depth of the interface associated with the link.";
}
leaf address-family {
type enumeration {
enum "ipv4" {
description
"The Adj-SID refers to an adjacency with outgoing IPv4
encapsulation.";
}
enum "ipv6" {
description
"The Adj-SID refers to an adjacency with outgoing IPv6
encapsulation.";
}
}
default "ipv4";
description
"This leaf defines the F-Flag (Address-Family flag) of the
SID.";
}
leaf is-backup { leaf is-backup {
type boolean; type boolean;
config false; default false;
description description
"'true' if the SID is a backup."; "'true' if the SID is a backup.";
} }
leaf is-part-of-set { leaf is-part-of-set {
type boolean; type boolean;
config false; default false;
description description
"'true' if the SID is part of a set."; "'true' if the SID is part of a set.";
} }
leaf is-persistent {
type boolean;
default true;
description
"'true' if the SID is persistently allocated.";
}
leaf is-on-lan { leaf is-on-lan {
type boolean; type boolean;
config false; default false;
description description
"'true' if on a lan."; "'true' if on a lan.";
} }
uses information-source-attributes; uses information-source-attributes;
} // sr } // sr
} // sr-tp-attributes } // sr-tp-attributes
} }
<CODE ENDS> <CODE ENDS>
5. IANA Considerations 5. IANA Considerations
RFC Ed.: In this section, replace all occurrences of 'XXXX' with the RFC Ed.: In this section, replace all occurrences of 'XXXX' with the
actual RFC number (and remove this note). actual RFC number (and remove this note).
This document registers the following namespace URIs in the IETF XML This document registers the following namespace URIs in the IETF XML
skipping to change at page 15, line 44 skipping to change at page 16, line 48
-------------------------------------------------------------------- --------------------------------------------------------------------
name: ietf-sr-topology-state name: ietf-sr-topology-state
namespace: urn:ietf:params:xml:ns:yang:ietf-sr-topology-state namespace: urn:ietf:params:xml:ns:yang:ietf-sr-topology-state
prefix: srt-s prefix: srt-s
reference: RFC XXXX reference: RFC XXXX
-------------------------------------------------------------------- --------------------------------------------------------------------
6. Security Considerations 6. Security Considerations
The configuration, state, action and notification data defined in The YANG module specified in this document defines a schema for data
this document are designed to be accessed via the NETCONF protocol that is designed to be accessed via network management protocols such
[RFC6241]. The data-model by itself does not create any security as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer
implications. The security considerations for the NETCONF protocol is the secure transport layer, and the mandatory-to-implement secure
are applicable. The NETCONF protocol used for sending the data transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
supports authentication and encryption. is HTTPS, and the mandatory-to-implement secure transport is TLS
[RFC5246].
The NETCONF access control model [RFC6536] 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.
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 are the subtrees and data nodes
and their sensitivity/vulnerability:
nw:network-types/l3t:l3-unicast-topology/sr-mpls
This subtree specifies the SR topology type. Modifying the
configurations can make SR topology type invalid and cause
interruption to all SR networks.
/nw:networks/nw:network/l3t:l3-topology-attributes/sr
This subtree specifies the topology-wide configurations, including
the SRGB (Segment Routing Global Block). Modifying the
configurations here can cause traffic disabled or rerouted in this
topology and the connected topologies.
/nw:networks/nw:network/nw:node/l3t:l3-node-attributes
This subtree specifies the SR configurations for nodes. Modifying
the configurations in this subtree can add, remove, or modify SR
nodes, causing traffic disabled or rerouted in the specified nodes
and the related TE topologies.
/nw:networks/nw:network/nt:link/l3t:l3-link-attributes/sr
This subtree specifies the configurations for SR Adjacency
Segments. Modifying the configurations in this subtree can add,
remove, or modify SR Adjacency Segments causing traffic disabled
or rerouted on the specified SR adjacencies, the related nodes,
and the related SR topologies.
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 are the subtrees and data
nodes and their sensitivity/vulnerability:
nw:network-types/l3t:l3-unicast-topology/sr-mpls
Unauthorized access to this subtree can disclose the SR topology
type.
/nw:networks/nw:network/l3t:l3-topology-attributes/sr
Unauthorized access to this subtree can disclose the topology-wide
configurations, including the SRGB (Segment Routing Global Block).
/nw:networks/nw:network/nw:node/l3t:l3-node-attributes
Unauthorized access to this subtree can disclose the operational
state information of the SR nodes.
/nw:networks/nw:network/nt:link/l3t:l3-link-attributes/sr
Unauthorized access to this subtree can disclose the operational
state information of SR Adjacency Segments.
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246,
DOI 10.17487/RFC5246, August 2008,
<https://www.rfc-editor.org/info/rfc5246>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/info/rfc6242>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536,
DOI 10.17487/RFC6536, March 2012,
<https://www.rfc-editor.org/info/rfc6536>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>. <https://www.rfc-editor.org/info/rfc8342>.
7.2. Informative References 7.2. Informative References
[RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG",
RFC 7951, DOI 10.17487/RFC7951, August 2016,
<https://www.rfc-editor.org/info/rfc7951>.
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>. <https://www.rfc-editor.org/info/rfc8340>.
[RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N., [RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N.,
Ananthakrishnan, H., and X. Liu, "A YANG Data Model for Ananthakrishnan, H., and X. Liu, "A YANG Data Model for
Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March
2018, <https://www.rfc-editor.org/info/rfc8345>. 2018, <https://www.rfc-editor.org/info/rfc8345>.
[RFC8346] Clemm, A., Medved, J., Varga, R., Liu, X., [RFC8346] Clemm, A., Medved, J., Varga, R., Liu, X.,
skipping to change at page 17, line 8 skipping to change at page 19, line 47
[I-D.ietf-teas-yang-te-topo] [I-D.ietf-teas-yang-te-topo]
Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and
O. Dios, "YANG Data Model for Traffic Engineering (TE) O. Dios, "YANG Data Model for Traffic Engineering (TE)
Topologies", draft-ietf-teas-yang-te-topo-18 (work in Topologies", draft-ietf-teas-yang-te-topo-18 (work in
progress), June 2018. progress), June 2018.
[I-D.ietf-spring-sr-yang] [I-D.ietf-spring-sr-yang]
Litkowski, S., Qu, Y., Sarkar, P., and J. Tantsura, "YANG Litkowski, S., Qu, Y., Sarkar, P., and J. Tantsura, "YANG
Data Model for Segment Routing", draft-ietf-spring-sr- Data Model for Segment Routing", draft-ietf-spring-sr-
yang-08 (work in progress), December 2017. yang-09 (work in progress), June 2018.
Appendix A. Companion YANG Model for Non-NMDA Compliant Implementations Appendix A. Companion YANG Model for Non-NMDA Compliant Implementations
The YANG module ietf-sr-topology defined in this document is designed The YANG module ietf-sr-topology defined in this document is designed
to be used in conjunction with implementations that support the to be used in conjunction with implementations that support the
Network Management Datastore Architecture (NMDA) defined in Network Management Datastore Architecture (NMDA) defined in
[RFC8342]. In order to allow implementations to use the model even [RFC8342]. In order to allow implementations to use the model even
in cases when NMDA is not supported, the following companion module, in cases when NMDA is not supported, the following companion module,
ietf-sr-topology-state, is defined as state model, which mirrors the ietf-sr-topology-state, is defined as state model, which mirrors the
module ietf-sr-topology defined earlier in this document. However, module ietf-sr-topology defined earlier in this document. However,
skipping to change at page 18, line 27 skipping to change at page 20, line 27
The companion module, ietf-sr-topology-state, is redundant and SHOULD The companion module, ietf-sr-topology-state, is redundant and SHOULD
NOT be supported by implementations that support NMDA. NOT be supported by implementations that support NMDA.
As the structure of the companion module mirrors that of the As the structure of the companion module mirrors that of the
coorespinding NMDA model, the YANG tree of the companion module is coorespinding NMDA model, the YANG tree of the companion module is
not depicted separately. not depicted separately.
A.1. SR Topology State Module A.1. SR Topology State Module
<CODE BEGINS> file "ietf-sr-topology-state@2018-06-22.yang" <CODE BEGINS> file "ietf-sr-topology-state@2018-10-03.yang"
module ietf-sr-topology-state { module ietf-sr-topology-state {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-sr-topology-state"; namespace "urn:ietf:params:xml:ns:yang:ietf-sr-topology-state";
prefix "srt-s"; prefix "srt-s";
import ietf-sr-topology { import ietf-sr-topology {
prefix "srt"; prefix "srt";
} }
import ietf-network-state { import ietf-network-state {
prefix "nw-s"; prefix "nw-s";
skipping to change at page 19, line 50 skipping to change at page 21, line 50
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the This version of this YANG module is part of RFC XXXX; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
revision 2018-06-22 { revision 2018-10-03 {
description "Initial revision"; description "Initial revision";
reference reference
"RFC XXXX: YANG Data Model for SR and SR TE Topologies"; "RFC XXXX: YANG Data Model for SR and SR TE Topologies";
} }
augment "/nw-s:networks/nw-s:network/nw-s:network-types/" augment "/nw-s:networks/nw-s:network/nw-s:network-types/"
+ "l3t-s:l3-unicast-topology" { + "l3t-s:l3-unicast-topology" {
description description
"Defines the SR topology type."; "Defines the SR topology type.";
uses srt:sr-topology-type; uses srt:sr-topology-type;
} }
augment "/nw-s:networks/nw-s:network/" augment "/nw-s:networks/nw-s:network/"
+ "l3t-s:l3-topology-attributes" { + "l3t-s:l3-topology-attributes" {
when "../nw-s:network-types/l3t-s:l3-unicast-topology/srt-s:sr" { when "../nw-s:network-types/l3t-s:l3-unicast-topology/"
+ "srt-s:sr-mpls" {
description "Augment only for SR topology."; description "Augment only for SR topology.";
} }
description "Augment topology configuration"; description "Augment topology configuration";
uses srt:sr-topology-attributes; uses srt:sr-topology-attributes;
} }
augment "/nw-s:networks/nw-s:network/nw-s:node/" augment "/nw-s:networks/nw-s:network/nw-s:node/"
+ "l3t-s:l3-node-attributes" { + "l3t-s:l3-node-attributes" {
when "../../nw-s:network-types/l3t-s:l3-unicast-topology/" when "../../nw-s:network-types/l3t-s:l3-unicast-topology/"
+ "srt-s:sr" { + "srt-s:sr-mpls" {
description "Augment only for SR topology."; description "Augment only for SR topology.";
} }
description "Augment node configuration."; description "Augment node configuration.";
uses srt:sr-node-attributes; uses srt:sr-node-attributes;
} }
augment "/nw-s:networks/nw-s:network/nw-s:node/" augment "/nw-s:networks/nw-s:network/nw-s:node/"
+ "l3t-s:l3-node-attributes/l3t-s:prefix" { + "l3t-s:l3-node-attributes/l3t-s:prefix" {
when "../../../nw-s:network-types/l3t-s:l3-unicast-topology/" when "../../../nw-s:network-types/l3t-s:l3-unicast-topology/"
+ "srt-s:sr" { + "srt-s:sr-mpls" {
description "Augment only for SR topology."; description "Augment only for SR topology.";
} }
description "Augment node prefix."; description "Augment node prefix.";
uses srt:sr-node-prefix-attributes; uses srt:sr-node-prefix-attributes;
} }
augment "/nw-s:networks/nw-s:network/nw-s:node/" augment "/nw-s:networks/nw-s:network/nt-s:link/"
+ "nt-s:termination-point/" + "l3t-s:l3-link-attributes" {
+ "l3t-s:l3-termination-point-attributes" { when "../../nw-s:network-types/l3t-s:l3-unicast-topology/"
when "../../../nw-s:network-types/l3t-s:l3-unicast-topology/" + "srt-s:sr-mpls" {
+ "srt-s:sr" {
description "Augment only for SR topology."; description "Augment only for SR topology.";
} }
description "Augment termination point configuration"; description "Augment link configuration";
uses srt:sr-tp-attributes; uses srt:sr-link-attributes;
} }
grouping sr-topology-attributes { grouping sr-topology-attributes {
description "SR topology scope attributes."; description "SR topology scope attributes.";
container sr { container sr {
description description
"Containing SR attributes."; "Containing SR attributes.";
uses sr-cmn:srgb-cfg; uses sr-cmn:srgb-cfg;
} // sr } // sr
} // sr-topology-attributes } // sr-topology-attributes
} }
<CODE ENDS> <CODE ENDS>
Appendix B. Data Tree Example
This section contains an example of an instance data tree in the JSON
encoding [RFC7951]. The example instantiates "ietf-sr-topology" for
the topology that is depicted in the following diagram.
+------------+ +------------+
| D1 | | D2 |
/-\ /-\ /-\ /-\
| | 1-0-1 | |---------------->| | 2-1-1 | |
| | 1-2-1 | |<----------------| | 2-0-1 | |
\-/ 1-3-1 \-/ \-/ 2-3-1 \-/
| /----\ | | /----\ |
+---| |---+ +---| |---+
\----/ \----/
A | A |
| | | |
| | | |
| | +------------+ | |
| | | D3 | | |
| | /-\ /-\ | |
| +----->| | 3-1-1 | |-------+ |
+---------| | 3-2-1 | |<---------+
\-/ \-/
| |
+------------+
The corresponding instance data tree is depicted below. Note that
some lines have been wrapped to adhere to the 72-character line
limitation of RFCs.
{
"ietf-network:networks": {
"network": [
{
"network-types": {
"ietf-l3-unicast-topology:l3-unicast-topology": {
"ietf-sr-topology:sr-mpls": {}
}
},
"network-id": "sr-topo-example",
"ietf-l3-unicast-topology:l3-topology-attributes": {
"ietf-sr-topology:sr": {
"srgb": [
{
"lower-bound": 16000,
"upper-bound": 23999
}
]
}
},
"node": [
{
"node-id": "D1",
"ietf-network-topology:termination-point": [
{
"tp-id": "1-0-1",
"ietf-l3-unicast-topology:l3-termination-point-attributes": {
"unnumbered-id": 101
}
},
{
"tp-id": "1-2-1",
"ietf-l3-unicast-topology:l3-termination-point-attributes": {
"unnumbered-id": 121
}
},
{
"tp-id": "1-3-1",
"ietf-l3-unicast-topology:l3-termination-point-attributes": {
"unnumbered-id": 131
}
}
],
"ietf-l3-unicast-topology:l3-node-attributes": {
"router-id": ["203.0.113.1"],
"prefix": [
{
"prefix": "203.0.113.1/32",
"ietf-sr-topology:sr": {
"start-sid": 101,
"range": 1,
"is-local": false,
"is-node": true
}
}
],
"ietf-sr-topology:sr": {
"srgb": [
{
"lower-bound": 16000,
"upper-bound": 23999
}
],
"srlb": [
{
"lower-bound": 15000,
"upper-bound": 15999
}
]
}
}
},
{
"node-id": "D2",
"ietf-network-topology:termination-point": [
{
"tp-id": "2-0-1",
"ietf-l3-unicast-topology:l3-termination-point-attributes": {
"unnumbered-id": 201
}
},
{
"tp-id": "2-1-1",
"ietf-l3-unicast-topology:l3-termination-point-attributes": {
"unnumbered-id": 211
}
},
{
"tp-id": "2-3-1",
"ietf-l3-unicast-topology:l3-termination-point-attributes": {
"unnumbered-id": 231
}
}
],
"ietf-l3-unicast-topology:l3-node-attributes": {
"router-id": ["203.0.113.2"],
"prefix": [
{
"prefix": "203.0.113.2/32",
"ietf-sr-topology:sr": {
"start-sid": 102,
"range": 1,
"is-local": false,
"is-node": true
}
}
],
"ietf-sr-topology:sr": {
"srgb": [
{
"lower-bound": 16000,
"upper-bound": 23999
}
],
"srlb": [
{
"lower-bound": 15000,
"upper-bound": 15999
}
]
}
}
},
{
"node-id": "D3",
"ietf-network-topology:termination-point": [
{
"tp-id": "3-1-1",
"ietf-l3-unicast-topology:l3-termination-point-attributes": {
"unnumbered-id": 311
}
},
{
"tp-id": "3-2-1",
"ietf-l3-unicast-topology:l3-termination-point-attributes": {
"unnumbered-id": 321
}
}
],
"ietf-l3-unicast-topology:l3-node-attributes": {
"router-id": ["203.0.113.3"],
"prefix": [
{
"prefix": "203.0.113.3/32",
"ietf-sr-topology:sr": {
"start-sid": 101,
"range": 1,
"is-local": false,
"is-node": true
}
}
],
"ietf-sr-topology:sr": {
"srgb": [
{
"lower-bound": 16000,
"upper-bound": 23999
}
],
"srlb": [
{
"lower-bound": 15000,
"upper-bound": 15999
}
]
}
}
}
],
"ietf-network-topology:link": [
{
"link-id": "D1,1-2-1,D2,2-1-1",
"source": {
"source-node": "D1",
"source-tp": "1-2-1"
},
"destination": {
"dest-node": "D2",
"dest-tp": "2-1-1"
},
"ietf-l3-unicast-topology:l3-link-attributes": {
"metric1": "100",
"ietf-sr-topology:sr": {
"sid": 121,
"is-local": true
}
}
},
{
"link-id": "D2,2-1-1,D1,1-2-1",
"source": {
"source-node": "D2",
"source-tp": "2-1-1"
},
"destination": {
"dest-node": "D1",
"dest-tp": "1-2-1"
},
"ietf-l3-unicast-topology:l3-link-attributes": {
"metric1": "100",
"ietf-sr-topology:sr": {
"sid": 211,
"is-local": true
}
}
},
{
"link-id": "D1,1-3-1,D3,3-1-1",
"source": {
"source-node": "D1",
"source-tp": "1-3-1"
},
"destination": {
"dest-node": "D3",
"dest-tp": "3-1-1"
},
"ietf-l3-unicast-topology:l3-link-attributes": {
"metric1": "100",
"ietf-sr-topology:sr": {
"sid": 131,
"is-local": true
}
}
},
{
"link-id": "D3,3-1-1,D1,1-3-1",
"source": {
"source-node": "D3",
"source-tp": "3-1-1"
},
"destination": {
"dest-node": "D1",
"dest-tp": "1-3-1"
},
"ietf-l3-unicast-topology:l3-link-attributes": {
"metric1": "100",
"ietf-sr-topology:sr": {
"sid": 311,
"is-local": true
}
}
},
{
"link-id": "D2,2-3-1,D3,3-2-1",
"source": {
"source-node": "D2",
"source-tp": "2-3-1"
},
"destination": {
"dest-node": "D3",
"dest-tp": "3-2-1"
},
"ietf-l3-unicast-topology:l3-link-attributes": {
"metric1": "100",
"ietf-sr-topology:sr": {
"sid": 231,
"is-local": true
}
}
},
{
"link-id": "D3,3-2-1,D2,2-3-1",
"source": {
"source-node": "D3",
"source-tp": "3-2-1"
},
"destination": {
"dest-node": "D2",
"dest-tp": "2-3-1"
},
"ietf-l3-unicast-topology:l3-link-attributes": {
"metric1": "100",
"ietf-sr-topology:sr": {
"sid": 321,
"is-local": true
}
}
}
]
}
]
}
}
Appendix C. Contributors
Jeff Tantsura
Email: jefftant.ietf@gmail.com
Yingzhen Qu
Email: yingzhen.qu@huawei.com
Authors' Addresses Authors' Addresses
Xufeng Liu Xufeng Liu
Volta Networks Volta Networks
EMail: xufeng.liu.ietf@gmail.com EMail: xufeng.liu.ietf@gmail.com
Igor Bryskin Igor Bryskin
Huawei Technologies Huawei Technologies
 End of changes. 61 change blocks. 
97 lines changed or deleted 578 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/