draft-ietf-teas-yang-rsvp-te-03.txt   draft-ietf-teas-yang-rsvp-te-04.txt 
TEAS Working Group V. Beeram TEAS Working Group V. Beeram
Internet-Draft Juniper Networks Internet-Draft Juniper Networks
Intended status: Standards Track T. Saad, Ed. Intended status: Standards Track T. Saad
Expires: August 23, 2018 R. Gandhi Expires: April 23, 2019 R. Gandhi
Cisco Systems, Inc. Cisco Systems, Inc.
X. Liu X. Liu
Jabil Volta Networks
I. Bryskin I. Bryskin
Huawei Technologies Huawei Technologies
H. Shah H. Shah
Ciena Ciena
February 19, 2018 October 20, 2018
A YANG Data Model for RSVP-TE A YANG Data Model for RSVP-TE
draft-ietf-teas-yang-rsvp-te-03 draft-ietf-teas-yang-rsvp-te-04
Abstract Abstract
This document defines a YANG data model for the configuration and This document defines a YANG data model for the configuration and
management of RSVP (Resource Reservation Protocol) to establish management of RSVP (Resource Reservation Protocol) to establish
Traffic-Engineered (TE) Label-Switched Paths (LSPs) for MPLS (Multi- Traffic-Engineered (TE) Label-Switched Paths (LSPs) for MPLS (Multi-
Protocol Label Switching) and other technologies. Protocol Label Switching) and other technologies.
The model defines a generic RSVP-TE module for signaling LSPs that is The model defines a generic RSVP-TE module for signaling LSPs that is
technology agnostic. The generic RSVP-TE module is to be augmented technology agnostic. The generic RSVP-TE module is to be augmented
by technology specific RSVP-TE modules that define technology by technology specific RSVP-TE modules that define technology
specific data. This document defines the augmentation for RSVP-TE specific data. This document also defines the augmentation for RSVP-
MPLS LSPs model. TE MPLS LSPs model.
This model covers data for the configuration, operational state, This model covers data for the configuration, operational state,
remote procedural calls, and event notifications. remote procedural calls, and event notifications.
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 August 23, 2018. This Internet-Draft will expire on April 23, 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
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. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Prefixes in Data Node Names . . . . . . . . . . . . . . . 3
1.3. Prefixes in Data Node Names . . . . . . . . . . . . . . . 4 2. Model Overview . . . . . . . . . . . . . . . . . . . . . . . 4
2. Design Considerations . . . . . . . . . . . . . . . . . . . . 5 2.1. Module Relationship . . . . . . . . . . . . . . . . . . . 4
2.1. Module Hierarchy . . . . . . . . . . . . . . . . . . . . 5 2.2. Model Tree Diagrams . . . . . . . . . . . . . . . . . . . 5
2.2. RSVP-TE Generic Model . . . . . . . . . . . . . . . . . . 6 2.2.1. RSVP-TE Model Tree Diagram . . . . . . . . . . . . . 5
2.2.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . 6 2.2.2. RSVP-TE MPLS Model Tree Diagram . . . . . . . . . . . 13
2.2.2. YANG Module . . . . . . . . . . . . . . . . . . . . . 14 2.3. YANG Modules . . . . . . . . . . . . . . . . . . . . . . 16
2.3. RSVP-TE MPLS Model . . . . . . . . . . . . . . . . . . . 26 2.3.1. RSVP-TE YANG Module . . . . . . . . . . . . . . . . . 16
2.3.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . 26 2.3.2. RSVP-TE MPLS YANG Module . . . . . . . . . . . . . . 27
2.3.2. YANG Module . . . . . . . . . . . . . . . . . . . . . 28 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 40
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 41 4. Security Considerations . . . . . . . . . . . . . . . . . . . 40
4. Security Considerations . . . . . . . . . . . . . . . . . . . 41 5. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 41
5. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 42 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 41
6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 42
7. Normative References . . . . . . . . . . . . . . . . . . . . 42 7. Normative References . . . . . . . . . . . . . . . . . . . . 42
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 43 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 44
1. Introduction 1. Introduction
YANG [RFC6020] is a data definition language that was introduced to YANG [RFC7950] is a data modeling language that was introduced to
define the contents of a conceptual data store that allows networked define the contents of a conceptual data store that allows networked
devices to be managed using NETCONF [RFC6241]. YANG is proving devices to be managed using NETCONF [RFC6241]. YANG has proved
relevant beyond its initial confines, as bindings to other interfaces relevant beyond its initial confines, as bindings to other interfaces
(e.g. ReST) and encoding other than XML (e.g. JSON) are being (e.g. RESTCONF [RFC8040]) and encoding other than XML (e.g. JSON)
defined. Furthermore, YANG data models can be used as the basis of are being defined. Furthermore, YANG data models can be used as the
implementation for other interfaces, such as CLI and programmatic basis of implementation for other interfaces, such as CLI and
APIs. programmatic APIs.
This document defines a generic YANG data model for configuring and This document defines a generic YANG data model for configuring and
managing RSVP-TE LSP(s) [RFC3209]. The RSVP-TE generic model managing RSVP-TE LSP(s) [RFC3209]. The RSVP-TE generic model
augments the RSVP base and extended models defined in augments the RSVP base and extended models defined in
[I-D.ietf-teas-yang-rsvp], and adds TE extensions to the RSVP [I-D.ietf-teas-yang-rsvp], and adds TE extensions to the RSVP
protocol [RFC2205] model configuration and state data. The protocol [RFC2205] model configuration and state data. The
technology specific RSVP-TE models augment the generic RSVP-TE model technology specific RSVP-TE models augment the generic RSVP-TE model
with additional technology specific parameters. For example, this with additional technology specific parameters. For example, this
document also defines the MPLS RSVP-TE model for configuring and document also defines the MPLS RSVP-TE model for configuring and
managing MPLS RSVP TE LSP(s). managing MPLS RSVP TE LSP(s).
In addition to augmenting the RSVP YANG module, the modules defined In addition to augmenting the RSVP YANG module, the modules defined
in this document augment the TE Interfaces, Tunnels and LSP(s) YANG in this document augment the TE Interfaces, Tunnels and LSP(s) YANG
module defined in [I-D.ietf-teas-yang-te] to define additional module defined in [I-D.ietf-teas-yang-te] to define additional
parameters to enable signaling for RSVP-TE. parameters to enable signaling for RSVP-TE.
1.1. Terminology 1.1. Terminology
In this document, the key words "MUST", "MUST NOT", "REQUIRED", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
and "OPTIONAL" are to be interpreted as described in BCP 14, RFC 2119 "OPTIONAL" in this document are to be interpreted as described in BCP
[RFC2119]. 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
1.2. Tree Diagram The terminology for describing YANG data models is found in
[RFC7950].
A simplified graphical representation of the data model is presented 1.2. Prefixes in Data Node Names
in each section of the model. The following notations are used for
the YANG model data tree representation.
<status> <flags> <name> <opts> <type> In this document, names of data nodes and other data model objects
are prefixed using the standard prefix associated with the
corresponding YANG imported modules, as shown in Table 1.
<status> is one of: +---------------+--------------------+-------------------------------+
+ for current | Prefix | YANG module | Reference |
x for deprecated +---------------+--------------------+-------------------------------+
o for obsolete | yang | ietf-yang-types | [RFC6991] |
| inet | ietf-inet-types | [RFC6991] |
| te | ietf-te | [I-D.ietf-teas-yang-te] |
| rsvp | ietf-rsvp | [I-D.ietf-teas-yang-rsvp] |
| te-dev | ietf-te-device | [I-D.ietf-teas-yang-te] |
| te-types | ietf-te-types | [I-D.ietf-teas-yang-te-types] |
| te-mpls-types | ietf-te-mpls-types | [I-D.ietf-teas-yang-te-types] |
| rsvp-te | ietf-rsvp-te | this document |
| rsvp-te-mpls | ietf-rsvp-te-mpls | this document |
+---------------+--------------------+-------------------------------+
<flags> is one of: Table 1: Prefixes and corresponding YANG modules
rw for read-write configuration data
ro for read-only non-configuration data
-x for execution rpcs
-n for notifications
<name> is the name of the node 2. Model Overview
If the node is augmented into the tree from another module, its name The RSVP-TE generic model augments the RSVP base and extended YANG
is printed as <prefix>:<name> models defined in [I-D.ietf-teas-yang-rsvp]. It also augments the TE
tunnels and interfaces module defined in [I-D.ietf-teas-yang-te] to
cover parameters specific to the configuration and management of
RSVP-TE interfaces, tunnels and LSP(s).
<opts> is one of: The RSVP-TE MPLS YANG model augments the RSVP-TE generic model with
? for an optional leaf or node parameters to configure and manage signaling of MPLS RSVP-TE LSPs.
! for a presence container RSVP-TE model augmentation for other dataplane technologies (e.g.
* for a leaf-list or list OTN or WDM) are outside the scope of this document.
Brackets [<keys>] for a list's keys
Curly braces {<condition>} for optional feature that make node
conditional
Colon : for marking case nodes
Ellipses ("...") subtree contents not shown
Parentheses enclose choice and case nodes, and case nodes are also There are three types of configuration and state data nodes in
marked with a colon (":"). module(s) defined in this document:
<type> is the name of the type for leafs and leaf-lists. o those augmenting or extending the base RSVP module that is defined
in [I-D.ietf-teas-yang-rsvp]
1.3. Prefixes in Data Node Names o those augmenting or extending the base TE module defined in
[I-D.ietf-teas-yang-te]
In this document, names of data nodes and other data model objects o those that are specific to the RSVP-TE and RSVP-TE MPLS modules
are prefixed using the standard prefix associated with the defined in this document.
corresponding YANG imported modules, as shown in Table 1.
+---------------+--------------------+---------------+ 2.1. Module Relationship
| Prefix | YANG module | Reference |
+---------------+--------------------+---------------+
| yang | ietf-yang-types | [RFC6991] |
| inet | ietf-inet-types | [RFC6991] |
| te | ietf-te | this document |
| te-types | ietf-te-types | this document |
| te-mpls-types | ietf-te-mpls-types | this document |
| te-dev | ietf-te-device | this document |
| te-mpls | ietf-te-mpls | this document |
| te-sr-mpls | ietf-te-sr-mpls | this document |
+---------------+--------------------+---------------+
Table 1: Prefixes and corresponding YANG modules The data pertaining to RSVP-TE in this document is divided into two
modules: a technology agnostic RSVP-TE module that holds generic
parameters for RSVP-TE applicable to all technologies, and a MPLS
technology specific RSVP-TE module that holds parameters specific to
MPLS technology.
2. Design Considerations The RSVP-TE generic YANG module "ietf-rsvp-te" imports the following
modules:
2.1. Module Hierarchy o ietf-rsvp defined in [I-D.ietf-teas-yang-rsvp]
The data pertaining to RSVP-TE in this document is divided into two o ietf-routing-types defined in [RFC8294]
modules: a technology agnostic RSVP-TE module that holds generic
parameters for RSVP-TE applicable to all technologies, and a
technology specific RSVP-TE module (e.g. for MPLS RSVP-TE) that holds
parameters specific to the technology.
This document defines YANG data models for RSVP-TE, and RSVP-TE MPLS o ietf-te-types defined in [I-D.ietf-teas-yang-te-types]
configuration, state, notification and RPCs. The relationship
between the different modules is depicted in Figure 1.
TE basic +---------+ ^: import o ietf-te and ietf-te-dev defined in [I-D.ietf-teas-yang-te]
The RSVP-TE MPLS YANG module "ietf-te-device" imports the following
module(s):
o ietf-rsvp defined in [I-D.ietf-teas-yang-rsvp]
o ietf-routing-types defined in [RFC8294]
o ietf-te-mpls-types defined in [I-D.ietf-teas-yang-te-types]
o ietf-te and ietf-te-dev defined in [I-D.ietf-teas-yang-te]
The relationship between the different modules is shown in Figure 1.
TE basic +---------+
module | ietf-te | o: augment module | ietf-te | o: augment
+---------+ +---------+
| o o
| | |
v | |
+--------------+ +--------------+
RSVP-TE module | ietf-rsvp-te |o . . . RSVP-TE module | ietf-rsvp-te |o . . .
+--------------+ \ +--------------+ \
^ | \ | \
| o +-------------------+ o +--------------------+
+-----------+ | ietf-rsvp-otn-te | +-----------+ | ietf-rsvp-te-mpls |
RSVP module | ietf-rsvp | +-------------------+ RSVP module | ietf-rsvp | +--------------------+
+-----------+ RSVP-TE with OTN +-----------+ RSVP-TE with MPLS
o extensions o
| (shown for illustration |
RSVP extended | not in this document) RSVP extended |
module +--------------------+ module +--------------------+
| ietf-rsvp-extended | | ietf-rsvp-extended |
+--------------------+ +--------------------+
Figure 1: Relationship of RSVP and RSVP-TE modules with other Figure 1: Relationship of RSVP and RSVP-TE modules with other
protocol modules protocol modules
2.2. RSVP-TE Generic Model 2.2. Model Tree Diagrams
The RSVP-TE generic module augments the RSVP base and extended YANG
modules defined in [I-D.ietf-teas-yang-rsvp] as well as the TE
tunnels and interfaces module [I-D.ietf-teas-yang-te] to cover
parameters specific to the configuration and management of RSVP-TE
interfaces, tunnels and LSP(s).
2.2.1. Tree Diagram
There are three types of configuration and state data nodes in this
module:
o those augmenting or extending the base RSVP module
o those augmenting or extending the base TE module A full tree diagram of the module(s) defined in this document as per
the syntax defined in [RFC8340] are given in subsequent sections.
o those that are specific to the RSVP-TE module 2.2.1. RSVP-TE Model Tree Diagram
Below is a YANG tree representation for data items defined in the Figure 2 shows the YANG tree diagram of the RSVP-TE generic YANG
RSVP-TE generic module: model defined in module ietf-rsvp-te.yang.
module: ietf-rsvp-te module: ietf-rsvp-te
augment augment
/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/
rsvp:rsvp/rsvp:globals: rsvp:rsvp/rsvp:globals:
+--rw global-soft-preemption! +--rw global-soft-preemption!
+--rw soft-preemption-timeout? uint16 +--rw soft-preemption-timeout? uint16
augment augment
/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/
rsvp:rsvp/rsvp:interfaces: rsvp:rsvp/rsvp:interfaces:
+--rw rsvp-te-interface-attributes +--rw rsvp-te-interface-attributes
+--ro state +--ro state
augment augment
/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/
rsvp:rsvp/rsvp:interfaces/rsvp:interface: rsvp:rsvp/rsvp:interfaces/rsvp:interface:
+--rw rsvp-te-interface-attributes +--rw rsvp-te-interface-attributes
+--ro state +--ro state
skipping to change at page 14, line 43 skipping to change at page 13, line 39
+--:(unnumbered) +--:(unnumbered)
| +--ro node-id? te-types:te-node-id | +--ro node-id? te-types:te-node-id
| +--ro link-tp-id? te-types:te-tp-id | +--ro link-tp-id? te-types:te-tp-id
+--:(label) +--:(label)
+--ro value? rt-types:generalized-label +--ro value? rt-types:generalized-label
+--ro label-flags? binary +--ro label-flags? binary
augment /te:te/te-dev:interfaces/te-dev:interface: augment /te:te/te-dev:interfaces/te-dev:interface:
Figure 2: RSVP-TE model Tree diagram Figure 2: RSVP-TE model Tree diagram
2.2.2. YANG Module 2.2.2. RSVP-TE MPLS Model Tree Diagram
<CODE BEGINS> file "ietf-rsvp-te@2018-02-19.yang" Figure 5 shows the YANG tree diagram of the RSVP-TE MPLS YANG model
defined in module ietf-rsvp-te-mpls.yang and that augments RSVP-TE
module as well as RSVP and TE YANG modules.
module: ietf-rsvp-te-mpls
augment /rt:routing/rt:control-plane-protocols/
rt:control-plane-protocol/rsvp:rsvp:
+--rw fast-reroute-local-revertive
+--rw rsvp-frr-local-revert-delay? uint32
augment /rt:routing/rt:control-plane-protocols/
rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces:
augment /rt:routing/rt:control-plane-protocols/
rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/rsvp:interface:
augment /rt:routing/rt:control-plane-protocols/
rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/
rsvp:sessions/rsvp:session/rsvp:state:
augment /rt:routing/rt:control-plane-protocols/
rt:control-plane-protocol/rsvp:rsvp/rsvp:neighbors:
augment /te:te/te:tunnels/te:tunnel:
+--rw local-protection-desired? empty
+--rw bandwidth-protection-desired? empty
+--rw node-protection-desired? empty
+--rw non-php-desired? empty
+--rw entropy-label-cap? empty
+--rw oam-mep-entities-desired? empty
+--rw oam-mip-entities-desired? empty
augment /te:te/te:lsps-state/te:lsp:
+--ro state
| +--ro local-protection-desired? empty
| +--ro bandwidth-protection-desired? empty
| +--ro node-protection-desired? empty
| +--ro non-php-desired? empty
| +--ro entropy-label-cap? empty
| +--ro oam-mep-entities-desired? empty
| +--ro oam-mip-entities-desired? empty
+--ro backup-info
+--ro state
+--ro backup-tunnel-name? string
+--ro backup-frr-on? uint8
+--ro backup-protected-lsp-num? uint32
augment /te:te/te:tunnels/te:tunnel/te:p2p-primary-paths/
te:p2p-primary-path/te:state/te:lsps/te:lsp:
+--ro state
| +--ro local-protection-desired? empty
| +--ro bandwidth-protection-desired? empty
| +--ro node-protection-desired? empty
| +--ro non-php-desired? empty
| +--ro entropy-label-cap? empty
| +--ro oam-mep-entities-desired? empty
| +--ro oam-mip-entities-desired? empty
+--ro backup-info
+--ro state
+--ro backup-tunnel-name? string
+--ro backup-frr-on? uint8
+--ro backup-protected-lsp-num? uint32
augment /te:te/te:tunnels/te:tunnel/te:p2p-secondary-paths/
te:p2p-secondary-path/te:state/te:lsps/te:lsp:
+--ro state
| +--ro local-protection-desired? empty
| +--ro bandwidth-protection-desired? empty
| +--ro node-protection-desired? empty
| +--ro non-php-desired? empty
| +--ro entropy-label-cap? empty
| +--ro oam-mep-entities-desired? empty
| +--ro oam-mip-entities-desired? empty
+--ro backup-info
+--ro state
+--ro backup-tunnel-name? string
+--ro backup-frr-on? uint8
+--ro backup-protected-lsp-num? uint32
augment /te:te/te-dev:interfaces/te-dev:interface:
+--rw bandwidth-mpls-reservable
+--rw (bandwidth-value)?
| +--:(absolute)
| | +--rw absolute-value? uint32
| +--:(percentage)
| +--rw percent-value? uint32
+--rw (bc-model-type)?
+--:(bc-model-rdm)
| +--rw bc-model-rdm
| +--rw bandwidth-mpls-constraints
| +--rw maximum-reservable? uint32
| +--rw bc-value* uint32
+--:(bc-model-mam)
| +--rw bc-model-mam
| +--rw bandwidth-mpls-constraints
| +--rw maximum-reservable? uint32
| +--rw bc-value* uint32
+--:(bc-model-mar)
+--rw bc-model-mar
+--rw bandwidth-mpls-constraints
+--rw maximum-reservable? uint32
+--rw bc-value* uint32
augment /te:te/te-dev:interfaces/te-dev:interface:
+--rw rsvp-te-frr-backups
+--rw (type)?
+--:(static-tunnel)
| +--rw static-backups
| +--rw static-backup* [backup-tunnel-name]
| +--rw backup-tunnel-name ->
/te:te/tunnels/tunnel/name
+--:(auto-tunnel)
+--rw auto-tunnel-backups
+--rw auto-backup-protection? identityref
+--rw auto-backup-path-computation? identityref
Figure 3: RSVP-TE MPLS Tree diagram
2.3. YANG Modules
2.3.1. RSVP-TE YANG Module
<CODE BEGINS> file "ietf-rsvp-te@2018-10-20.yang"
module ietf-rsvp-te { module ietf-rsvp-te {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-rsvp-te"; namespace "urn:ietf:params:xml:ns:yang:ietf-rsvp-te";
prefix "rsvp-te"; prefix "rsvp-te";
import ietf-rsvp { import ietf-rsvp {
prefix rsvp; prefix rsvp;
reference "draft-ietf-teas-yang-rsvp: A YANG Data Model for
Resource Reservation Protocol (RSVP)";
} }
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
reference "RFC8349: A YANG Data Model for Routing Management";
} }
import ietf-routing-types { import ietf-routing-types {
prefix rt-types; prefix rt-types;
reference "RFC8294: Common YANG Data Types for the Routing Area";
} }
import ietf-te { import ietf-te {
prefix te; prefix te;
reference "draft-ietf-teas-yang-te: A YANG Data Model for Traffic
Engineering Tunnels and Interfaces";
} }
import ietf-te-device { import ietf-te-device {
prefix te-dev; prefix te-dev;
reference "draft-ietf-teas-yang-te: A YANG Data Model for Traffic
Engineering Tunnels and Interfaces";
} }
/* Import TE generic types */ /* Import TE generic types */
import ietf-te-types { import ietf-te-types {
prefix te-types; prefix te-types;
reference "draft-ietf-teas-yang-te-types: A YANG Data Model for
Common Traffic Engineering Types";
} }
organization organization
"IETF Traffic Engineering Architecture and Signaling (TEAS) "IETF Traffic Engineering Architecture and Signaling (TEAS)
Working Group"; Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/teas/> "WG Web: <http://tools.ietf.org/wg/teas/>
WG List: <mailto:teas@ietf.org> WG List: <mailto:teas@ietf.org>
skipping to change at page 16, line 9 skipping to change at page 17, line 30
Editor: Tarek Saad Editor: Tarek Saad
<mailto:tsaad@cisco.com> <mailto:tsaad@cisco.com>
Editor: Rakesh Gandhi Editor: Rakesh Gandhi
<mailto:rgandhi@cisco.com> <mailto:rgandhi@cisco.com>
Editor: Himanshu Shah Editor: Himanshu Shah
<mailto:hshah@ciena.com> <mailto:hshah@ciena.com>
Editor: Xufeng Liu Editor: Xufeng Liu
<mailto:xliu@kuatrotech.com> <mailto: xufeng.liu.ietf@gmail.com>
Editor: Xia Chen Editor: Xia Chen
<mailto:jescia.chenxia@huawei.com> <mailto:jescia.chenxia@huawei.com>
Editor: Raqib Jones Editor: Raqib Jones
<mailto:raqib@Brocade.com> <mailto:raqib@Brocade.com>
Editor: Bin Wen Editor: Bin Wen
<mailto:Bin_Wen@cable.comcast.com>"; <mailto:Bin_Wen@cable.comcast.com>";
description description
"This module contains the RSVP-TE YANG generic data model."; "This module contains the RSVP-TE YANG generic data model.";
revision "2018-02-19" { revision "2018-10-20" {
description "Latest revision to RSVP-TE generic YANG module"; description "Latest revision to RSVP-TE generic YANG module";
reference "RFC2205, RFC3209, etc."; reference "RFC2205, RFC3209, etc.";
} }
/** /**
* RSVP-TE LSPs groupings. * RSVP-TE LSPs groupings.
*/ */
grouping lsp-record-route-information_state { grouping lsp-record-route-information_state {
description "recorded route information grouping"; description "recorded route information grouping";
container incoming-record-route-subobjects { container incoming-record-route-subobjects {
description "RSVP recorded route object incoming information"; description "RSVP recorded route object incoming information";
list incoming-record-route-subobject { list incoming-record-route-subobject {
when "../../te:origin-type != 'ingress'" { when "../../te:origin-type != 'ingress'" {
description "Applicable on non-ingress LSPs only"; description "Applicable on non-ingress LSPs only";
} }
skipping to change at page 18, line 7 skipping to change at page 19, line 30
leaf index { leaf index {
type leafref { type leafref {
path "../state/index"; path "../state/index";
} }
description "ERO subobject index"; description "ERO subobject index";
} }
container state { container state {
config false; config false;
description description
"State parameters for the explicit route hop"; "State parameters for the explicit route hop";
leaf index {
type uint32;
description "ERO subobject index";
}
uses te-types:explicit-route-hop; uses te-types:explicit-route-hop;
} }
} }
list outgoing-explicit-route-hop { list outgoing-explicit-route-hop {
when "../../te:origin-type != 'egress'" { when "../../te:origin-type != 'egress'" {
description "Applicable on non-egress LSPs only"; description "Applicable on non-egress LSPs only";
} }
key "index"; key "index";
description description
"List of outgoing RSVP Path explicit-route objects"; "List of outgoing RSVP Path explicit-route objects";
leaf index { leaf index {
type leafref { type leafref {
path "../state/index"; path "../state/index";
} }
description "ERO subobject index"; description "ERO subobject index";
} }
container state { container state {
config false; config false;
description description
"State parameters for the explicit route hop"; "State parameters for the explicit route hop";
leaf index {
type uint32;
description "ERO subobject index";
}
uses te-types:explicit-route-hop; uses te-types:explicit-route-hop;
} }
} }
} }
} }
grouping lsp-attributes-flags_config { grouping lsp-attributes-flags_config {
description description
"Configuration parameters relating to RSVP-TE LSP "Configuration parameters relating to RSVP-TE LSP
attribute flags"; attribute flags";
skipping to change at page 26, line 16 skipping to change at page 27, line 45
/* TE interface augmentation */ /* TE interface augmentation */
augment "/te:te/te-dev:interfaces/te-dev:interface" { augment "/te:te/te-dev:interfaces/te-dev:interface" {
description description
"RSVP-TE generic data augmentation pertaining to specific TE "RSVP-TE generic data augmentation pertaining to specific TE
interface"; interface";
} }
} }
<CODE ENDS> <CODE ENDS>
Figure 3: RSVP TE generic YANG module Figure 4: RSVP TE generic YANG module
2.3. RSVP-TE MPLS Model
The MPLS RSVP-TE YANG module augments the RSVP-TE generic module with
parameters to configure and manage signaling of MPLS RSVP-TE LSPs.
RSVP-TE YANG modules for other dataplane technologies (e.g. OTN or
WDM) are outside the scope of this document and are defined in other
documents.
2.3.1. Tree Diagram
The following are possible types of configuration and state data
nodes in this module:
o those augmenting or extending the generic RSVP-TE module
o those augmenting or extending the TE module
o those that are specific to the RSVP-TE MPLS module
Below is a YANG tree representation for data items defined in the
RSVP-TE MPLS module:
module: ietf-rsvp-te-mpls
augment /rt:routing/rt:control-plane-protocols/
rt:control-plane-protocol/rsvp:rsvp:
+--rw fast-reroute-local-revertive
+--rw rsvp-frr-local-revert-delay? uint32
augment /rt:routing/rt:control-plane-protocols/
rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces:
augment /rt:routing/rt:control-plane-protocols/
rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/rsvp:interface:
augment /rt:routing/rt:control-plane-protocols/
rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/
rsvp:sessions/rsvp:session/rsvp:state:
augment /rt:routing/rt:control-plane-protocols/
rt:control-plane-protocol/rsvp:rsvp/rsvp:neighbors:
augment /te:te/te:tunnels/te:tunnel:
+--rw local-protection-desired? empty
+--rw bandwidth-protection-desired? empty
+--rw node-protection-desired? empty
+--rw non-php-desired? empty
+--rw entropy-label-cap? empty
+--rw oam-mep-entities-desired? empty
+--rw oam-mip-entities-desired? empty
augment /te:te/te:lsps-state/te:lsp:
+--ro state
| +--ro local-protection-desired? empty
| +--ro bandwidth-protection-desired? empty
| +--ro node-protection-desired? empty
| +--ro non-php-desired? empty
| +--ro entropy-label-cap? empty
| +--ro oam-mep-entities-desired? empty
| +--ro oam-mip-entities-desired? empty
+--ro backup-info
+--ro state
+--ro backup-tunnel-name? string
+--ro backup-frr-on? uint8
+--ro backup-protected-lsp-num? uint32
augment /te:te/te:tunnels/te:tunnel/te:p2p-primary-paths/
te:p2p-primary-path/te:state/te:lsps/te:lsp:
+--ro state
| +--ro local-protection-desired? empty
| +--ro bandwidth-protection-desired? empty
| +--ro node-protection-desired? empty
| +--ro non-php-desired? empty
| +--ro entropy-label-cap? empty
| +--ro oam-mep-entities-desired? empty
| +--ro oam-mip-entities-desired? empty
+--ro backup-info
+--ro state
+--ro backup-tunnel-name? string
+--ro backup-frr-on? uint8
+--ro backup-protected-lsp-num? uint32
augment /te:te/te:tunnels/te:tunnel/te:p2p-secondary-paths/
te:p2p-secondary-path/te:state/te:lsps/te:lsp:
+--ro state
| +--ro local-protection-desired? empty
| +--ro bandwidth-protection-desired? empty
| +--ro node-protection-desired? empty
| +--ro non-php-desired? empty
| +--ro entropy-label-cap? empty
| +--ro oam-mep-entities-desired? empty
| +--ro oam-mip-entities-desired? empty
+--ro backup-info
+--ro state
+--ro backup-tunnel-name? string
+--ro backup-frr-on? uint8
+--ro backup-protected-lsp-num? uint32
augment /te:te/te-dev:interfaces/te-dev:interface:
+--rw bandwidth-mpls-reservable
+--rw (bandwidth-value)?
| +--:(absolute)
| | +--rw absolute-value? uint32
| +--:(percentage)
| +--rw percent-value? uint32
+--rw (bc-model-type)?
+--:(bc-model-rdm)
| +--rw bc-model-rdm
| +--rw bandwidth-mpls-constraints
| +--rw maximum-reservable? uint32
| +--rw bc-value* uint32
+--:(bc-model-mam)
| +--rw bc-model-mam
| +--rw bandwidth-mpls-constraints
| +--rw maximum-reservable? uint32
| +--rw bc-value* uint32
+--:(bc-model-mar)
+--rw bc-model-mar
+--rw bandwidth-mpls-constraints
+--rw maximum-reservable? uint32
+--rw bc-value* uint32
augment /te:te/te-dev:interfaces/te-dev:interface:
+--rw rsvp-te-frr-backups
+--rw (type)?
+--:(static-tunnel)
| +--rw static-backups
| +--rw static-backup* [backup-tunnel-name]
| +--rw backup-tunnel-name ->
/te:te/tunnels/tunnel/name
+--:(auto-tunnel)
+--rw auto-tunnel-backups
+--rw auto-backup-protection? identityref
+--rw auto-backup-path-computation? identityref
Figure 4: RSVP-TE MPLS Tree diagram
2.3.2. YANG Module 2.3.2. RSVP-TE MPLS YANG Module
<CODE BEGINS> file "ietf-rsvp-te-mpls@2018-02-19.yang" <CODE BEGINS> file "ietf-rsvp-te-mpls@2018-10-20.yang"
module ietf-rsvp-te-mpls { module ietf-rsvp-te-mpls {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-rsvp-te-mpls"; namespace "urn:ietf:params:xml:ns:yang:ietf-rsvp-te-mpls";
prefix "rsvp-te-mpls"; prefix "rsvp-te-mpls";
import ietf-rsvp { import ietf-rsvp {
prefix "rsvp"; prefix "rsvp";
reference "draft-ietf-teas-yang-rsvp: A YANG Data Model for
Resource Reservation Protocol (RSVP)";
} }
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
reference "RFC8349: A YANG Data Model for Routing Management";
} }
import ietf-te-mpls-types { import ietf-te-mpls-types {
prefix "te-mpls-types"; prefix "te-mpls-types";
reference "draft-ietf-teas-yang-te-types: A YANG Data Model for
Common Traffic Engineering Types";
} }
import ietf-te-types { import ietf-te-types {
prefix "te-types"; prefix "te-types";
reference "draft-ietf-teas-yang-te-types: A YANG Data Model for
Common Traffic Engineering Types";
} }
import ietf-te { import ietf-te {
prefix "te"; prefix "te";
reference "draft-ietf-teas-yang-te: A YANG Data Model for Traffic
Engineering Tunnels and Interfaces";
} }
import ietf-te-device { import ietf-te-device {
prefix "te-dev"; prefix "te-dev";
reference "draft-ietf-teas-yang-te: A YANG Data Model for Traffic
Engineering Tunnels and Interfaces";
} }
organization organization
"IETF Traffic Engineering Architecture and Signaling (TEAS) "IETF Traffic Engineering Architecture and Signaling (TEAS)
Working Group"; Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/teas/> "WG Web: <http://tools.ietf.org/wg/teas/>
WG List: <mailto:teas@ietf.org> WG List: <mailto:teas@ietf.org>
skipping to change at page 30, line 12 skipping to change at page 29, line 22
Editor: Tarek Saad Editor: Tarek Saad
<mailto:tsaad@cisco.com> <mailto:tsaad@cisco.com>
Editor: Rakesh Gandhi Editor: Rakesh Gandhi
<mailto:rgandhi@cisco.com> <mailto:rgandhi@cisco.com>
Editor: Himanshu Shah Editor: Himanshu Shah
<mailto:hshah@ciena.com> <mailto:hshah@ciena.com>
Editor: Xufeng Liu Editor: Xufeng Liu
<mailto:xliu@kuatrotech.com> <mailto: xufeng.liu.ietf@gmail.com>
Editor: Xia Chen Editor: Xia Chen
<mailto:jescia.chenxia@huawei.com> <mailto:jescia.chenxia@huawei.com>
Editor: Raqib Jones Editor: Raqib Jones
<mailto:raqib@Brocade.com> <mailto:raqib@Brocade.com>
Editor: Bin Wen Editor: Bin Wen
<mailto:Bin_Wen@cable.comcast.com>"; <mailto:Bin_Wen@cable.comcast.com>";
description description
"Latest update to MPLS RSVP-TE YANG data model."; "Latest update to MPLS RSVP-TE YANG data model.";
revision "2018-02-19" { revision "2018-10-20" {
description "Update to MPLS RSVP-TE YANG initial revision."; description "Update to MPLS RSVP-TE YANG initial revision.";
reference "RFC3209, RFC6511, RFC6790, RFC7260, RFC4859, RFC4090"; reference "RFC3209, RFC6511, RFC6790, RFC7260, RFC4859, RFC4090";
} }
/* RSVP-TE MPLS LSPs groupings */ /* RSVP-TE MPLS LSPs groupings */
grouping lsp-attributes-flags-mpls_config { grouping lsp-attributes-flags-mpls_config {
description description
"Configuration parameters relating to RSVP-TE MPLS LSP "Configuration parameters relating to RSVP-TE MPLS LSP
attribute flags"; attribute flags";
leaf non-php-desired { leaf non-php-desired {
skipping to change at page 40, line 42 skipping to change at page 40, line 4
"/te:p2p-secondary-paths/te:p2p-secondary-path/" + "/te:p2p-secondary-paths/te:p2p-secondary-path/" +
"te:path-setup-protocol = 'te-types:path-setup-rsvp'" { "te:path-setup-protocol = 'te-types:path-setup-rsvp'" {
description description
"When the signaling protocol is RSVP-TE "; "When the signaling protocol is RSVP-TE ";
} }
description description
"RSVP-TE MPLS LSP state properties"; "RSVP-TE MPLS LSP state properties";
uses lsp-properties-mpls; uses lsp-properties-mpls;
uses lsp-backup-info; uses lsp-backup-info;
} }
augment "/te:te/te-dev:interfaces/te-dev:interface" { augment "/te:te/te-dev:interfaces/te-dev:interface" {
description description
"RSVP reservable bandwidth configuration properties"; "RSVP reservable bandwidth configuration properties";
uses bandwidth-mpls-reservable; uses bandwidth-mpls-reservable;
} }
augment "/te:te/te-dev:interfaces/te-dev:interface" { augment "/te:te/te-dev:interfaces/te-dev:interface" {
description description
"RSVP reservable bandwidth configuration properties"; "RSVP reservable bandwidth configuration properties";
uses rsvp-te-frr-backups; uses rsvp-te-frr-backups;
} }
} }
<CODE ENDS> <CODE ENDS>
Figure 5: RSVP TE MPLS YANG module Figure 5: RSVP TE MPLS YANG module
Figure 5 shows the YANG tree representation of the RSVP TE MPLS
module that augments RSVP-TE module as well as RSVP and TE YANG
modules.
3. IANA Considerations 3. IANA Considerations
This document registers the following URIs in the IETF XML registry This document registers the following URIs in the IETF XML registry
[RFC3688]. Following the format in [RFC3688], the following [RFC3688]. Following the format in [RFC3688], the following
registration is requested to be made. registration is requested to be made.
URI: urn:ietf:params:xml:ns:yang:ietf-rsvp-te XML: N/A, the requested URI: urn:ietf:params:xml:ns:yang:ietf-rsvp-te XML: N/A, the requested
URI is an XML namespace. URI is an XML namespace.
URI: urn:ietf:params:xml:ns:yang:ietf-rsvp-te-mpls XML: N/A, the URI: urn:ietf:params:xml:ns:yang:ietf-rsvp-te-mpls XML: N/A, the
skipping to change at page 41, line 43 skipping to change at page 40, line 47
name: ietf-rsvp-te namespace: urn:ietf:params:xml:ns:yang:ietf-rsvp- name: ietf-rsvp-te namespace: urn:ietf:params:xml:ns:yang:ietf-rsvp-
te-mpls prefix: ietf-rsvp-te reference: RFC3209 te-mpls prefix: ietf-rsvp-te reference: RFC3209
4. Security Considerations 4. Security Considerations
The YANG module defined in this memo is designed to be accessed via The YANG module defined in this memo is designed to be accessed via
the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the
secure transport layer and the mandatory-to-implement secure secure transport layer and the mandatory-to-implement secure
transport is SSH [RFC6242]. The NETCONF access control model transport is SSH [RFC6242]. The NETCONF access control model
[RFC6536] provides means to restrict access for particular NETCONF [RFC8341] provides means to restrict access for particular NETCONF
users to a pre-configured subset of all available NETCONF protocol users to a pre-configured subset of all available NETCONF protocol
operations and content. operations and content.
There are a number of data nodes defined in the YANG module which are There are a number of data nodes defined in the YANG module(s)
writable/creatable/deletable (i.e., config true, which is the defined in this document which are writable/creatable/deletable
default). These data nodes may be considered sensitive or vulnerable (i.e., config true, which is the default). These data nodes may be
in some network environments. Write operations (e.g., <edit-config>) considered sensitive or vulnerable in some network environments.
to these data nodes without proper protection can have a negative Write operations (e.g., <edit-config>) to these data nodes without
effect on network operations. proper protection can have a negative effect on network operations.
/rt:routing/rt:control-plane-protocols/rt:control-plane-
protocol/rsvp:rsvp/globals: The data nodes defined defined in this
document and under this branch are applicable device-wide and can
affect all RSVP established sessions. Unauthorized access to this
container can potentially cause disruptive event(s) on all
established sessions.
/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/
rsvp:rsvp/rsvp:globals/rsvp:sessions: The data nodes defined in this
document and under this branch are applicable to one or all RSVP-TE
session(s). Unauthorized access to this container can potentially
affect the impacted RSVP session(s).
/rt:routing/rt:control-plane-protocols/rt:control-plane-
protocol/rsvp:rsvp/rsvp:interfaces: The data nodes defined defined in
this document and under this branch are applicable to one or all RSVP
interfaces. Unauthorized access to this container can potentially
affect established session(s) over impacted interface(s).
5. Acknowledgement 5. Acknowledgement
The authors would like to thank Lou Berger for reviewing and The authors would like to thank Lou Berger for reviewing and
providing valuable feedback on this document. providing valuable feedback on this document.
6. Contributors 6. Contributors
Xia Chen Xia Chen
Huawei Technologies Huawei Technologies
Email: jescia.chenxia@huawei.com Email: jescia.chenxia@huawei.com
Raqib Jones Raqib Jones
Brocade Brocade
Email: raqib@Brocade.com Email: raqib@Brocade.com
skipping to change at page 42, line 34 skipping to change at page 42, line 24
Bin Wen Bin Wen
Comcast Comcast
Email: Bin_Wen@cable.comcast.com Email: Bin_Wen@cable.comcast.com
7. Normative References 7. Normative References
[I-D.ietf-teas-yang-rsvp] [I-D.ietf-teas-yang-rsvp]
Beeram, V., Saad, T., Gandhi, R., Liu, X., Bryskin, I., Beeram, V., Saad, T., Gandhi, R., Liu, X., Bryskin, I.,
and H. Shah, "A YANG Data Model for Resource Reservation and H. Shah, "A YANG Data Model for Resource Reservation
Protocol (RSVP)", draft-ietf-teas-yang-rsvp-08 (work in Protocol (RSVP)", draft-ietf-teas-yang-rsvp-09 (work in
progress), October 2017. progress), May 2018.
[I-D.ietf-teas-yang-te] [I-D.ietf-teas-yang-te]
Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., and Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., and
I. Bryskin, "A YANG Data Model for Traffic Engineering I. Bryskin, "A YANG Data Model for Traffic Engineering
Tunnels and Interfaces", draft-ietf-teas-yang-te-11 (work Tunnels and Interfaces", draft-ietf-teas-yang-te-17 (work
in progress), February 2018. in progress), October 2018.
[I-D.ietf-teas-yang-te-types]
Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,
"Traffic Engineering Common YANG Types", draft-ietf-teas-
yang-te-types-01 (work in progress), October 2018.
[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>.
[RFC2205] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and S. [RFC2205] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and S.
Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1 Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1
Functional Specification", RFC 2205, DOI 10.17487/RFC2205, Functional Specification", RFC 2205, DOI 10.17487/RFC2205,
September 1997, <https://www.rfc-editor.org/info/rfc2205>. September 1997, <https://www.rfc-editor.org/info/rfc2205>.
skipping to change at page 43, line 33 skipping to change at page 43, line 28
[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 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/info/rfc6242>. <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>.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
RFC 6991, DOI 10.17487/RFC6991, July 2013, RFC 6991, DOI 10.17487/RFC6991, July 2013,
<https://www.rfc-editor.org/info/rfc6991>. <https://www.rfc-editor.org/info/rfc6991>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016,
<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>.
[RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger,
"Common YANG Data Types for the Routing Area", RFC 8294,
DOI 10.17487/RFC8294, December 2017,
<https://www.rfc-editor.org/info/rfc8294>.
[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>.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018,
<https://www.rfc-editor.org/info/rfc8341>.
Authors' Addresses Authors' Addresses
Vishnu Pavan Beeram Vishnu Pavan Beeram
Juniper Networks Juniper Networks
Email: vbeeram@juniper.net Email: vbeeram@juniper.net
Tarek Saad (editor)
Tarek Saad
Cisco Systems, Inc. Cisco Systems, Inc.
Email: tsaad@cisco.com Email: tsaad@cisco.com
Rakesh Gandhi Rakesh Gandhi
Cisco Systems, Inc. Cisco Systems, Inc.
Email: rgandhi@cisco.com Email: rgandhi@cisco.com
Xufeng Liu Xufeng Liu
Jabil Volta Networks
Email: Xufeng_Liu@jabil.com Email: xufeng.liu.ietf@gmail.com
Igor Bryskin Igor Bryskin
Huawei Technologies Huawei Technologies
Email: Igor.Bryskin@huawei.com Email: Igor.Bryskin@huawei.com
Himanshu Shah Himanshu Shah
Ciena Ciena
Email: hshah@ciena.com Email: hshah@ciena.com
 End of changes. 78 change blocks. 
281 lines changed or deleted 335 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/