MPLS Working Group T. Saad
Internet-Draft K. Raza
Intended status: Standards Track R. Gandhi
Expires: January 6, 2017 Cisco Systems Inc
X. Liu
Ericsson
V. Beeram
Juniper Networks
H. Shah
Ciena
I. Bryskin
X. Chen
Huawei Technologies
R. Jones
Brocade
B. Wen
Comcast
July 05, 2016
A YANG Data Model for MPLS Base
draft-ietf-mpls-base-yang-01
Abstract
This document contains a specification of the the MPLS base YANG
model. The MPLS base YANG module serves as a base framework for
configuring and managing an MPLS switching subsystem. It is expected
that other MPLS technology YANG models (e.g. MPLS LSP Static, LDP or
RSVP-TE 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 http://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 January 6, 2017.
Saad, et al. Expires January 6, 2017 [Page 1]
Internet-Draft MPLS Base YANG Data Model July 2016
Copyright Notice
Copyright (c) 2016 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
(http://trustee.ietf.org/license-info) in effect on the date of
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. MPLS Base Tree Diagram . . . . . . . . . . . . . . . . . 3
1.3. MPLS Base Module . . . . . . . . . . . . . . . . . . . . 4
2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
3. Security Considerations . . . . . . . . . . . . . . . . . . . 7
4. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.1. Normative References . . . . . . . . . . . . . . . . . . 8
4.2. Informative References . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction
A core routing data model is defined in
[I-D.ietf-netmod-routing-cfg], and it provides a basis for the
development of data models for routing protocols. The MPLS base
model augments this model with additional data specific to MPLS
switching [RFC3031]. The interface data model is defined in
[RFC7223] and is used for referencing interface from the MPLS base
model.
The MPLS base YANG module augments the "routing" read-write (rw) and
"routing-state" read-only (ro) branches of the ietf-routing module.
The approach described in [I-D.openconfig-netmod-opstate] is adopted
to represent data pertaining to configuration intended, applied state
and derived state data elements. Each container in the model holds a
"config" and "state" sub-container. The "config" sub-container
contains the intended configuration data, and the state sub-container
contains both the applied configuration and any derived state, such
as counters or statistical information.
Saad, et al. Expires January 6, 2017 [Page 2]
Internet-Draft MPLS Base YANG Data Model July 2016
This document defines the specification for 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 model to define data models for other MPLS technologies (e.g.
MPLS LDP or MPLS RSVP-TE).
1.1. Terminology
In this document, the key words "MUST", "MUST NOT", "REQUIRED",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
and "OPTIONAL" are to be interpreted as described in BCP 14, RFC 2119
[RFC2119].
The following terms are defined in [RFC6020]:
o augment,
o configuration data,
o data model,
o data node,
o feature,
o mandatory node,
o module,
o schema tree,
o state data,
o RPC operation.
1.2. MPLS Base Tree Diagram
The MPLS base tree diagram is shown in Figure 1.
Saad, et al. Expires January 6, 2017 [Page 3]
Internet-Draft MPLS Base YANG Data Model July 2016
module: ietf-mpls
augment /rt:routing:
+--rw mpls
+--rw interface* [name]
+--rw name if:interface-ref
+--rw config
| +--rw enabled? boolean
| +--rw mtu? uint32
+--ro state
+--ro enabled? boolean
+--ro mtu? uint32
augment /rt:routing-state:
+--ro mpls
Figure 1: MPLS Base tree diagram
1.3. MPLS Base Module
<CODE BEGINS>file "ietf-mpls@2016-07-05.yang"
module ietf-mpls {
namespace "urn:ietf:params:xml:ns:yang:ietf-mpls";
prefix "mpls";
import ietf-routing {
prefix "rt";
}
import ietf-interfaces {
prefix "if";
}
organization "IETF MPLS Working Group";
contact
"WG Web: <http://tools.ietf.org/wg/mpls/>
WG List: <mailto:mpls@ietf.org>
WG Chair: Loa Andersson
<mailto:loa@pi.nu>
WG Chair: Ross Callon
<mailto:rcallon@juniper.net>
Saad, et al. Expires January 6, 2017 [Page 4]
Internet-Draft MPLS Base YANG Data Model July 2016
WG Chair: George Swallow
<mailto:swallow.ietf@gmail.com>
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>
Editor: Himanshu Shah
<mailto:hshah@ciena.com>
Editor: Igor Bryskin
<mailto: Igor.Bryskin@huawei.com>
Editor: Xia Chen
<mailto:jescia.chenxia@huawei.com>
Editor: Raqib Jones
<mailto:raqib@Brocade.com>
Editor: Bin Wen
<mailto:Bin_Wen@cable.comcast.com>";
description
"This YANG module defines the essential components for the
management of the MPLS subsystem.";
revision "2016-07-05" {
description
"Latest revision:
- Addressed MPLS-RT review comments";
reference "RFC 3031: A YANG Data Model for base MPLS";
}
typedef mpls-label {
type uint32 {
range "0..1048575";
}
Saad, et al. Expires January 6, 2017 [Page 5]
Internet-Draft MPLS Base YANG Data Model July 2016
description
"The MPLS label range";
}
grouping interface-mpls {
description "MPLS interface properties 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)";
}
}
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.";
list interface {
key "name";
description "List of MPLS interfaces";
leaf name {
type if:interface-ref;
description
"The name of a configured MPLS interface";
}
container config {
description "Holds intended configuration";
uses interface-mpls;
}
container state {
config false;
description "Holds inuse configuration";
uses interface-mpls;
}
}
}
}
Saad, et al. Expires January 6, 2017 [Page 6]
Internet-Draft MPLS Base YANG Data Model July 2016
augment "/rt:routing-state" {
description "MPLS augmentation.";
container mpls {
config false;
description
"MPLS container, to be used as an augmentation target node
other MPLS sub-features state";
}
}
}
<CODE ENDS>
Figure 2: MPLS base YANG module
2. 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 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 reference: RFC3031
3. Security Considerations
The YANG module defined in this document is designed to be accessed
via the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the
secure transport layer and the mandatory-to-implement secure
transport is SSH [RFC6242]. The NETCONF access control model
[RFC6536] provides means to restrict access for particular NETCONF
users to a pre-configured subset of all available NETCONF protocol
operations and content.
There are a number of data nodes defined in the YANG module which 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.
Saad, et al. Expires January 6, 2017 [Page 7]
Internet-Draft MPLS Base YANG Data Model July 2016
4. References
4.1. Normative References
[I-D.ietf-netmod-routing-cfg]
Lhotka, L. and A. Lindem, "A YANG Data Model for Routing
Management", draft-ietf-netmod-routing-cfg-22 (work in
progress), July 2016.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol
Label Switching Architecture", RFC 3031, DOI 10.17487/
RFC3031, January 2001,
<http://www.rfc-editor.org/info/rfc3031>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004,
<http://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,
<http://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,
<http://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,
<http://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,
<http://www.rfc-editor.org/info/rfc6536>.
[RFC7223] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 7223, DOI 10.17487/RFC7223, May 2014,
<http://www.rfc-editor.org/info/rfc7223>.
Saad, et al. Expires January 6, 2017 [Page 8]
Internet-Draft MPLS Base YANG Data Model July 2016
4.2. Informative References
[I-D.openconfig-netmod-opstate]
Shakir, R., Shaikh, A., and M. Hines, "Consistent Modeling
of Operational State Data in YANG", draft-openconfig-
netmod-opstate-01 (work in progress), July 2015.
Authors' Addresses
Tarek Saad
Cisco Systems Inc
Email: tsaad@cisco.com
Kamran Raza
Cisco Systems Inc
Email: skraza@cisco.com
Rakesh Gandhi
Cisco Systems Inc
Email: rgandhi@cisco.com
Xufeng Liu
Ericsson
Email: xufeng.liu.ietf@gmail.com
Vishnu Pavan Beeram
Juniper Networks
Email: vbeeram@juniper.net
Himanshu Shah
Ciena
Email: tsaad@cisco.com
Saad, et al. Expires January 6, 2017 [Page 9]
Internet-Draft MPLS Base YANG Data Model July 2016
Igor Bryskin
Huawei Technologies
Email: Igor.Bryskin@huawei.com
Xia Chen
Huawei Technologies
Email: jescia.chenxia@huawei.com
Raqib Jones
Brocade
Email: raqib@Brocade.com
Bin Wen
Comcast
Email: Bin_Wen@cable.comcast.com
Saad, et al. Expires January 6, 2017 [Page 10]
