MPLS Working Group T. Saad
Internet-Draft Juniper Networks
Intended status: Standards Track K. Raza
Expires: March 15, 2020 R. Gandhi
Cisco Systems Inc
X. Liu
Volta Networks
V. Beeram
Juniper Networks
September 12, 2019
A YANG Data Model for MPLS Base
draft-ietf-mpls-base-yang-11
Abstract
This document contains a specification of the MPLS base YANG model.
The MPLS base YANG model serves as a base framework for configuring
and managing an MPLS switching subsystem on an MPLS-enabled router.
It is expected that other MPLS YANG models (e.g. MPLS LSP Static,
LDP or RSVP-TE YANG models) will augment the MPLS base YANG model.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 15, 2020.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
Saad, et al. Expires March 15, 2020 [Page 1]
Internet-Draft MPLS Base YANG Data Model September 2019
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Acronyms and Abbreviations . . . . . . . . . . . . . . . 3
2. MPLS Base Model . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Model Overview . . . . . . . . . . . . . . . . . . . . . 3
2.2. Model Organization . . . . . . . . . . . . . . . . . . . 4
2.3. Model Tree Diagram . . . . . . . . . . . . . . . . . . . 5
2.4. Model YANG Module . . . . . . . . . . . . . . . . . . . . 7
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
4. Security Considerations . . . . . . . . . . . . . . . . . . . 16
5. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 16
6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 16
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
7.1. Normative References . . . . . . . . . . . . . . . . . . 17
7.2. Informative References . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
1. Introduction
A core routing data model is defined in [RFC8349], and it provides a
basis for the development of data models for routing protocols. The
MPLS base model augments core routing data model with additional data
specific to MPLS technology as described in the MPLS architecture
document [RFC3031].
The MPLS base model serves as a basis for future development of MPLS
data models covering more-sophisticated MPLS feature(s) and sub-
system(s). The main purpose is to provide essential building blocks
for the more-complicated data models involving different control-
plane protocols, and advanced MPLS functions.
To this end, it is expected that the MPLS base data model will be
augmented by a number of other modules developed at IETF (e.g. by
TEAS and MPLS working groups).
The YANG module in this document conforms to the Network Management
Datastore Architecture (NMDA) [RFC8342].
Saad, et al. Expires March 15, 2020 [Page 2]
Internet-Draft MPLS Base YANG Data Model September 2019
1.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
The terminology for describing YANG data models is found in
[RFC7950].
1.2. Acronyms and Abbreviations
MPLS: Multiprotocol Label Switching
RIB: Routing Information Base
LSP: Label Switched Path
LSR: Label Switching Router
LER: Label Edge Router
FEC: Forwarding Equivalence Class
NHLFE: Next Hop Label Forwarding Entry
ILM: Incoming Label Map
2. MPLS Base Model
This document describes the ietf-mpls YANG module that provides base
components of the MPLS data model. It is expected that other MPLS
YANG modules will augment the ietf-mpls base module for other MPLS
extension to provision LSP(s) (e.g. MPLS Static, MPLS LDP or MPLS
RSVP-TE LSP(s)).
2.1. Model Overview
This document defines a mechanism to model MPLS labeled routes as an
augmentation of the routing RIB data model defined in [RFC8349] for
IP prefix routes that are MPLS labeled.
The other MPLS route(s) that are non-IP prefix routes are modelled by
introducing a new "mpls" address-family RIB as per recommendation .
Saad, et al. Expires March 15, 2020 [Page 3]
Internet-Draft MPLS Base YANG Data Model September 2019
2.2. Model Organization
Routing module +---------------+ v: import
| ietf-routing | o: augment
+---------------+
o
|
v
MPLS base +-----------+ v: import
module | ietf-mpls | o: augment
+-----------+
o o------+
| \
v v
+-------------------+ +---------------------+
MPLS Static | ietf-mpls-static@ | | ietf-mpls-ldp.yang@ | . .
LSP module +-------------------+ +---------------------+
@: not in this document, shown for illustration only
Figure 1: Relationship between MPLS modules
ietf-mpls module contains the following high-level types and
groupings:
label-block-alloc-mode:
A base YANG identity for supported label block allocation mode(s).
mpls-operations-type:
An enumeration type that represents support possible MPLS
operation types (impose-and-forward, pop-and-forward, pop-impose-
and-forward, and pop-and-lookup)
nhlfe-role:
An enumeration type that represents the role of the NHLFE entry.
nhlfe-single-contents:
A YANG grouping that describes single NHLFE and its associated
parameters as described in the MPLS architecture document
[RFC3031].
nhlfe-multiple-contents:
Saad, et al. Expires March 15, 2020 [Page 4]
Internet-Draft MPLS Base YANG Data Model September 2019
A YANG grouping that describes a set of NHLFE(s) and their
associated parameters as described in the MPLS architecture
document [RFC3031].
interface-mpls-properties:
A YANG grouping that describes the properties of an MPLS interface
on a device.
interfaces-mpls:
A YANG grouping that describes the list of MPLS enabled interfaces
on a device.
label-block-properties:
A YANG grouping that describes the properties of an MPLS label
block.
label-blocks:
A YANG grouping that describes the list of MPLS enabled interfaces
on a device.
2.3. Model Tree Diagram
The MPLS base tree diagram that follows the notation defined in
[RFC8340] is shown in Figure 2.
module: ietf-mpls
augment /rt:routing:
+--rw mpls
+--rw ttl-propagate? boolean
+--rw label-blocks
| +--rw label-block* [index]
| +--rw index string
| +--rw start-label? rt-types:mpls-label
| +--rw end-label? rt-types:mpls-label
| +--rw block-allocation-mode? identityref
| +--ro free-labels-count? yang:counter32
| +--ro inuse-labels-count? yang:counter32
+--rw interface* [name]
+--rw name if:interface-ref
+--rw enabled? boolean
+--rw mtu? uint32
augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route:
+--ro mpls-enabled? boolean
+--ro local-label? rt-types:mpls-label
Saad, et al. Expires March 15, 2020 [Page 5]
Internet-Draft MPLS Base YANG Data Model September 2019
augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop
/rt:next-hop-options/rt:simple-next-hop:
+--ro mpls-label-stack
+--ro entry* [id]
+--ro id uint8
+--ro label? rt-types:mpls-label
+--ro ttl? uint8
+--ro traffic-class? uint8
augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop
/rt:next-hop-options/rt:next-hop-list/rt:next-hop-list
/rt:next-hop:
+--ro index? string
+--ro backup-index? string
+--ro loadshare? uint16
+--ro role? nhlfe-role
+--ro mpls-label-stack
+--ro entry* [id]
+--ro id uint8
+--ro label? rt-types:mpls-label
+--ro ttl? uint8
+--ro traffic-class? uint8
augment /rt:routing/rt:ribs/rt:rib/rt:active-route/rt:input:
+---w local-label? rt-types:mpls-label
augment /rt:routing/rt:ribs/rt:rib/rt:active-route/rt:output/rt:route
/rt:next-hop/rt:next-hop-options/rt:simple-next-hop:
+-- mpls-label-stack
+-- entry* [id]
+-- id uint8
+-- label? rt-types:mpls-label
+-- ttl? uint8
+-- traffic-class? uint8
augment /rt:routing/rt:ribs/rt:rib/rt:active-route/rt:output/rt:route
/rt:next-hop/rt:next-hop-options/rt:next-hop-list
/rt:next-hop-list/rt:next-hop:
+-- index? string
+-- backup-index? string
+-- loadshare? uint16
+-- role? nhlfe-role
+-- mpls-label-stack
+-- entry* [id]
+-- id uint8
+-- label? rt-types:mpls-label
+-- ttl? uint8
+-- traffic-class? uint8
Figure 2: MPLS Base tree diagram
Saad, et al. Expires March 15, 2020 [Page 6]
Internet-Draft MPLS Base YANG Data Model September 2019
2.4. Model YANG Module
This section describes the "ietf-mpls" YANG module that provides base
components of the MPLS data model. Other YANG module(s) may import
and augment the base MPLS module to add feature specific data.
The ietf-mpls module imports the following modules:
o ietf-routing defined in [RFC8349]
o ietf-routing-types defined in [RFC8294]
o ietf-interfaces defined in [RFC8343]
<CODE BEGINS> file "ietf-mpls@2019-09-11.yang"
module ietf-mpls {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-mpls";
/* Replace with IANA when assigned */
prefix "mpls";
import ietf-routing {
prefix "rt";
reference "RFC8349: A YANG Data Model for Routing Management";
}
import ietf-routing-types {
prefix "rt-types";
reference "RFC8294:Common YANG Data Types for the Routing Area";
}
import ietf-yang-types {
prefix "yang";
reference "RFC6991: Common YANG Data Types";
}
import ietf-interfaces {
prefix "if";
reference "RFC8343: A YANG Data Model for Interface Management";
}
organization "IETF MPLS Working Group";
contact
"WG Web: <http://tools.ietf.org/wg/mpls/>
Saad, et al. Expires March 15, 2020 [Page 7]
Internet-Draft MPLS Base YANG Data Model September 2019
WG List: <mailto:mpls@ietf.org>
Editor: Tarek Saad
<mailto:tsaad@cisco.com>
Editor: Kamran Raza
<mailto:skraza@cisco.com>
Editor: Rakesh Gandhi
<mailto:rgandhi@cisco.com>
Editor: Xufeng Liu
<mailto: xufeng.liu.ietf@gmail.com>
Editor: Vishnu Pavan Beeram
<mailto:vbeeram@juniper.net>";
description
"This YANG module defines the essential components for the
management of the MPLS subsystem. The model fully conforms
to the Network Management Datastore Architecture (NMDA).
Copyright (c) 2018 IETF Trust and the persons
identified as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.";
// RFC Ed.: replace XXXX with actual RFC number and remove this
// note.
// RFC Ed.: update the date below with the date of RFC publication
// and remove this note.
revision "2019-09-11" {
description
"Latest revision:
- Addressed review comments";
reference "RFC XXXX: A YANG Data Model for base MPLS";
}
/* Identities */
Saad, et al. Expires March 15, 2020 [Page 8]
Internet-Draft MPLS Base YANG Data Model September 2019
identity mpls {
base rt:address-family;
description
"This identity represents the MPLS address family.";
}
identity label-block-alloc-mode {
description
"Base identity label-block allocation mode";
}
identity label-block-alloc-mode-manager {
base label-block-alloc-mode;
description
"Label block allocation on reserved block
is managed by label manager";
}
identity label-block-alloc-mode-application {
base label-block-alloc-mode;
description
"Label block allocation on reserved block
is managed by application";
}
/**
* Typedefs
*/
typedef mpls-operations-type {
type enumeration {
enum impose-and-forward {
description
"Operation impose outgoing label(s) and forward to
next-hop";
}
enum pop-and-forward {
description
"Operation pop incoming label and forward to next-hop";
}
enum pop-impose-and-forward {
description
"Operation pop incoming label, impose one or more
outgoing label(s) and forward to next-hop";
}
enum swap-and-forward {
description
"Operation swap incoming label, with outgoing label and
forward to next-hop";
Saad, et al. Expires March 15, 2020 [Page 9]
Internet-Draft MPLS Base YANG Data Model September 2019
}
enum pop-and-lookup {
description
"Operation pop incoming label and perform a lookup";
}
}
description "MPLS operations types";
}
typedef nhlfe-role {
type enumeration {
enum PRIMARY {
description
"Next-hop acts as primary traffic carrying";
}
enum BACKUP {
description
"Next-hop acts as backup";
}
enum PRIMARY_AND_BACKUP {
description
"Next-hop acts as primary and backup simultaneously";
}
}
description "The next-hop role";
}
grouping nhlfe-single-contents {
description
"MPLS simple NHLFE contents";
uses rt-types:mpls-label-stack;
}
grouping nhlfe-multiple-contents {
description
"MPLS NHLFE contents";
leaf index {
type string;
description
"A user-specified identifier utilised to uniquely
reference the next-hop entry in the next-hop list.
The value of this index has no semantic meaning
other than for referencing the entry.";
}
leaf backup-index {
type string;
description
Saad, et al. Expires March 15, 2020 [Page 10]
Internet-Draft MPLS Base YANG Data Model September 2019
"A user-specified identifier utilised to uniquely
reference the backup next-hop entry in the NHLFE list.
The value of this index has no semantic meaning
other than for referencing the entry.";
}
leaf loadshare {
type uint16;
description
"This value is used to compute a loadshare to perform un-equal
load balancing when multiple outgoing next-hop(s) are
specified. A share is computed as a ratio of this number to the
total under all next-hops(s).";
}
leaf role {
type nhlfe-role;
description "NHLFE role";
}
uses nhlfe-single-contents;
}
grouping interface-mpls-properties {
description "MPLS interface contents grouping";
leaf enabled {
type boolean;
description
"'true' if mpls encapsulation is enabled on the
interface. 'false' if mpls encapsulation is enabled
on the interface.";
}
leaf mtu {
type uint32;
description
"MPLS Maximum Transmission Unit (MTU) in bytes";
}
}
grouping interfaces-mpls {
description "List of MPLS interfaces";
list interface {
key "name";
description "List of MPLS interfaces";
leaf name {
type if:interface-ref;
description
"The name of a configured MPLS interface";
Saad, et al. Expires March 15, 2020 [Page 11]
Internet-Draft MPLS Base YANG Data Model September 2019
}
uses interface-mpls-properties;
}
}
grouping label-block-properties {
description "Label-block configuration items";
leaf index {
type string;
description
"A user-specified identifier utilised to uniquely
reference an MPLS label block";
}
leaf start-label {
type rt-types:mpls-label;
must '. >= ../end-label' {
error-message
"The start-label must be less than or equal " +
"to end-label";
}
description "Label-block start";
}
leaf end-label {
type rt-types:mpls-label;
must '. <= ../start-label' {
error-message
"The end-label must be greater than or equal " +
"to start-label";
}
description "Label-block end";
}
leaf block-allocation-mode {
type identityref {
base label-block-alloc-mode;
}
description "Label-block allocation mode";
}
}
grouping label-block_state {
description "Label-block state items";
leaf free-labels-count {
when "../block-allocation-mode = " +
"'label-block-alloc-mode-manager'";
type yang:counter32;
config false;
description "Label-block free labels count";
}
Saad, et al. Expires March 15, 2020 [Page 12]
Internet-Draft MPLS Base YANG Data Model September 2019
leaf inuse-labels-count {
when "../block-allocation-mode = " +
"'label-block-alloc-mode-manager'";
type yang:counter32;
config false;
description "Label-block inuse labels count";
}
}
grouping globals {
description "MPLS global configuration grouping";
leaf ttl-propagate {
type boolean;
default 'true';
description "Propagate TTL between IP and MPLS";
}
}
grouping label-blocks {
description "Label-block allocation grouping";
container label-blocks {
description "Label-block allocation container";
list label-block {
key index;
unique "start-label end-label";
description "List of MPLS label-blocks";
uses label-block-properties;
uses label-block_state;
}
}
}
augment "/rt:routing" {
description "MPLS augmentation.";
container mpls {
description
"MPLS container, to be used as an augmentation target node
other MPLS sub-features config, e.g. MPLS static LSP, MPLS
LDP LSPs, and Trafic Engineering MPLS LSP Tunnels, etc.";
uses globals;
uses label-blocks;
uses interfaces-mpls;
}
}
/* MPLS routes augmentation */
augment "/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route" {
description
"This is augmentation for all MPLS routes.";
Saad, et al. Expires March 15, 2020 [Page 13]
Internet-Draft MPLS Base YANG Data Model September 2019
leaf mpls-enabled {
type boolean;
default 'false';
description
"Indicates whether MPLS is enabled for this route";
}
leaf local-label {
when "../mpls-enabled = 'true'";
type rt-types:mpls-label;
description "MPLS local label associated with the route.";
}
}
/* MPLS simple-next-hop augmentation */
augment "/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route/"
+ "rt:next-hop/rt:next-hop-options/rt:simple-next-hop" {
description
"Augment 'simple-next-hop' case in IP unicast routes.";
uses nhlfe-single-contents {
when "/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route" +
"/mpls:mpls-enabled = 'true'";
}
}
/* MPLS next-hop-list augmentation */
augment "/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route/"
+ "rt:next-hop/rt:next-hop-options/rt:next-hop-list/"
+ "rt:next-hop-list/rt:next-hop" {
description
"This leaf augments the 'next-hop-list' case of IP unicast
routes.";
uses nhlfe-multiple-contents {
when "/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route" +
"/mpls:mpls-enabled = 'true'";
}
}
/* MPLS RPC input augmentation */
augment
"/rt:routing/rt:ribs/rt:rib/rt:active-route/rt:input" {
description
"Input MPLS augmentation for the 'active-route' action
statement.";
leaf local-label {
type rt-types:mpls-label;
description
"MPLS local label.";
}
Saad, et al. Expires March 15, 2020 [Page 14]
Internet-Draft MPLS Base YANG Data Model September 2019
}
/* MPLS RPC output augmentation */
augment "/rt:routing/rt:ribs/rt:rib/rt:active-route/"
+ "rt:output/rt:route/"
+ "rt:next-hop/rt:next-hop-options/rt:simple-next-hop" {
description
"Output MPLS augmentation for the 'active-route' action
statement.";
uses nhlfe-single-contents;
}
augment "/rt:routing/rt:ribs/rt:rib/rt:active-route/"
+ "rt:output/rt:route/"
+ "rt:next-hop/rt:next-hop-options/rt:next-hop-list/"
+ "rt:next-hop-list/rt:next-hop" {
description
"Output MPLS augmentation for the 'active-route' action
statement.";
uses nhlfe-multiple-contents;
}
}
<CODE ENDS>
Figure 3: MPLS base YANG module
3. IANA Considerations
This document registers the following URIs in the IETF XML registry
[RFC3688]. Following the format in [RFC3688], the following
registration is requested to be made.
URI: urn:ietf:params:xml:ns:yang:ietf-mpls
Registrant Contact: The MPLS WG of the IETF.
XML: N/A, the requested URI is an XML namespace.
This document registers a YANG module in the YANG Module Names
registry [RFC6020].
name: ietf-mpls
namespace: urn:ietf:params:xml:ns:yang:ietf-mpls
prefix: ietf-mpls
// RFC Ed.: replace XXXX with RFC number and remove this note
reference: RFCXXXX
Saad, et al. Expires March 15, 2020 [Page 15]
Internet-Draft MPLS Base YANG Data Model September 2019
4. Security Considerations
The YANG modules specified in this document define a schema for data
that is designed to be accessed via network management protocols such
as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer
is the secure transport layer, and the mandatory-to-implement secure
transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
is HTTPS, and the mandatory-to-implement secure transport is TLS
[RFC8446].
The NETCONF access control model [RFC8341] 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.
Some of the readable data nodes in these YANG modules 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:
/rt:routing/rt:ribs/rt:rib/rt:active-route/rt:output/rt:route: this
path is augmented by additional MPLS leaf(s) defined in this model.
Access to this information may disclose the per prefix and/or other
information.
/rt:routing/rt:ribs/rt:rib/rt:active-route/rt:output/rt:route/
rt:next-hop/rt:next-hop-options/rt:simple-next-hop: this path is
augmented by additional MPLS leaf(s) defined in this model. Access
to this information may disclose the next-hop or path per prefix and/
or other information.
5. Acknowledgement
The authors would like to thank the members of the multi-vendor YANG
design team who are involved in the definition of this model.
6. Contributors
Igor Bryskin
Huawei Technologies
email: Igor.Bryskin@huawei.com
Himanshu Shah
Ciena
email: hshah@ciena.com
Saad, et al. Expires March 15, 2020 [Page 16]
Internet-Draft MPLS Base YANG Data Model September 2019
7. References
7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/info/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<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>.
[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>.
Saad, et al. Expires March 15, 2020 [Page 17]
Internet-Draft MPLS Base YANG Data Model September 2019
[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>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>.
[RFC8343] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,
<https://www.rfc-editor.org/info/rfc8343>.
[RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for
Routing Management (NMDA Version)", RFC 8349,
DOI 10.17487/RFC8349, March 2018,
<https://www.rfc-editor.org/info/rfc8349>.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>.
7.2. Informative References
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol
Label Switching Architecture", RFC 3031,
DOI 10.17487/RFC3031, January 2001,
<https://www.rfc-editor.org/info/rfc3031>.
Authors' Addresses
Tarek Saad
Juniper Networks
Email: tsaad@juniper.net
Kamran Raza
Cisco Systems Inc
Email: skraza@cisco.com
Rakesh Gandhi
Cisco Systems Inc
Email: rgandhi@cisco.com
Saad, et al. Expires March 15, 2020 [Page 18]
Internet-Draft MPLS Base YANG Data Model September 2019
Xufeng Liu
Volta Networks
Email: xufeng.liu.ietf@gmail.com
Vishnu Pavan Beeram
Juniper Networks
Email: vbeeram@juniper.net
Saad, et al. Expires March 15, 2020 [Page 19]
