draft-ietf-mpls-base-yang-00.txt   draft-ietf-mpls-base-yang-01.txt 
MPLS Working Group T. Saad MPLS Working Group T. Saad
Internet-Draft K. Raza Internet-Draft K. Raza
Intended status: Standards Track R. Gandhi Intended status: Standards Track R. Gandhi
Expires: December 13, 2016 Cisco Systems Inc Expires: January 6, 2017 Cisco Systems Inc
X. Liu X. Liu
Ericsson Ericsson
V. Beeram V. Beeram
Juniper Networks Juniper Networks
H. Shah H. Shah
Ciena Ciena
I. Bryskin I. Bryskin
X. Chen X. Chen
Huawei Technologies Huawei Technologies
R. Jones R. Jones
Brocade Brocade
B. Wen B. Wen
Comcast Comcast
June 11, 2016 July 05, 2016
A YANG Data Model for MPLS Base A YANG Data Model for MPLS Base
draft-ietf-mpls-base-yang-00 draft-ietf-mpls-base-yang-01
Abstract Abstract
This document contains a specification of the the MPLS base YANG This document contains a specification of the the MPLS base YANG
model. The MPLS base YANG module serves as a base framework for model. The MPLS base YANG module serves as a base framework for
configuring and managing an MPLS switching subsystem. It is expected configuring and managing an MPLS switching subsystem. It is expected
that other MPLS technology YANG models (e.g. MPLS LSP Static, LDP or that other MPLS technology YANG models (e.g. MPLS LSP Static, LDP or
RSVP-TE models) will augment the MPLS base YANG model. RSVP-TE models) will augment the MPLS base YANG model.
Status of This Memo Status of This Memo
skipping to change at page 1, line 48 skipping to change at page 1, line 48
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 December 13, 2016. This Internet-Draft will expire on January 6, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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 4, line 23 skipping to change at page 4, line 23
+--ro state +--ro state
+--ro enabled? boolean +--ro enabled? boolean
+--ro mtu? uint32 +--ro mtu? uint32
augment /rt:routing-state: augment /rt:routing-state:
+--ro mpls +--ro mpls
Figure 1: MPLS Base tree diagram Figure 1: MPLS Base tree diagram
1.3. MPLS Base Module 1.3. MPLS Base Module
<CODE BEGINS>file "ietf-mpls@2016-05-11.yang" <CODE BEGINS>file "ietf-mpls@2016-07-05.yang"
module ietf-mpls { module ietf-mpls {
namespace "urn:ietf:params:xml:ns:yang:ietf-mpls"; namespace "urn:ietf:params:xml:ns:yang:ietf-mpls";
prefix "mpls"; prefix "mpls";
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
} }
import ietf-interfaces { import ietf-interfaces {
prefix "if"; prefix "if";
} }
organization "IETF MPLS Working Group"; organization "IETF MPLS Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/teas/> "WG Web: <http://tools.ietf.org/wg/mpls/>
WG List: <mailto:teas@ietf.org>
WG List: <mailto:mpls@ietf.org>
WG Chair: Loa Andersson WG Chair: Loa Andersson
<mailto:loa@pi.nu> <mailto:loa@pi.nu>
WG Chair: Ross Callon WG Chair: Ross Callon
<mailto:rcallon@juniper.net> <mailto:rcallon@juniper.net>
WG Chair: George Swallow WG Chair: George Swallow
<mailto:swallow.ietf@gmail.com> <mailto:swallow.ietf@gmail.com>
Editor: Tarek Saad Editor: Tarek Saad
<mailto:tsaad@cisco.com> <mailto:tsaad@cisco.com>
Editor: Kamran Raza Editor: Kamran Raza
<mailto:vbeeram@juniper.net> <mailto:skraza@cisco.com>
Editor: Rakesh Gandhi Editor: Rakesh Gandhi
<mailto:rgandhi@cisco.com> <mailto:rgandhi@cisco.com>
Editor: Xufeng Liu Editor: Xufeng Liu
<mailto:xufeng.liu.ietf@gmail.com> <mailto: xufeng.liu.ietf@gmail.com>
Editor: Vishnu Pavan Beeram Editor: Vishnu Pavan Beeram
<mailto:vbeeram@juniper.net> <mailto:vbeeram@juniper.net>
Editor: Himanshu Shah Editor: Himanshu Shah
<mailto:hshah@ciena.com> <mailto:hshah@ciena.com>
Editor: Igor Bryskin Editor: Igor Bryskin
<mailto: Igor.Bryskin@huawei.com> <mailto: Igor.Bryskin@huawei.com>
skipping to change at page 5, line 42 skipping to change at page 5, line 42
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 YANG module defines the essential components for the "This YANG module defines the essential components for the
management of the MPLS subsystem."; management of the MPLS subsystem.";
revision "2016-05-11" { revision "2016-07-05" {
description description
"Latest revision: "Latest revision:
- Addressed MPLS-RT review comments"; - Addressed MPLS-RT review comments";
reference "RFC 3031: A YANG Data Model for base MPLS"; reference "RFC 3031: A YANG Data Model for base MPLS";
} }
typedef mpls-label { typedef mpls-label {
type uint32 { type uint32 {
range "0..1048575"; range "0..1048575";
} }
description description
"The MPLS label range"; "The MPLS label range";
} }
grouping interface-mpls { grouping interface-mpls {
description "MPLS interface properties grouping"; description "MPLS interface properties grouping";
leaf enabled { leaf enabled {
type boolean; type boolean;
description description
"'true' if mpls encapsulation is enabled on the "'true' if mpls encapsulation is enabled on the
interface. 'false' if mpls encapsulation is not enabled interface. 'false' if mpls encapsulation is enabled
on the interface."; on the interface.";
} }
leaf mtu { leaf mtu {
type uint32; type uint32;
description description
"MPLS Maximum Transmission Unit (MTU)"; "MPLS Maximum Transmission Unit (MTU)";
} }
} }
augment "/rt:routing" { augment "/rt:routing" {
skipping to change at page 8, line 11 skipping to change at page 8, line 11
in some network environments. Write operations (e.g., <edit-config>) in some network environments. Write operations (e.g., <edit-config>)
to these data nodes without proper protection can have a negative to these data nodes without proper protection can have a negative
effect on network operations. effect on network operations.
4. References 4. References
4.1. Normative References 4.1. Normative References
[I-D.ietf-netmod-routing-cfg] [I-D.ietf-netmod-routing-cfg]
Lhotka, L. and A. Lindem, "A YANG Data Model for Routing Lhotka, L. and A. Lindem, "A YANG Data Model for Routing
Management", draft-ietf-netmod-routing-cfg-21 (work in Management", draft-ietf-netmod-routing-cfg-22 (work in
progress), March 2016. progress), July 2016.
[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, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997, RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol
Label Switching Architecture", RFC 3031, DOI 10.17487/ Label Switching Architecture", RFC 3031, DOI 10.17487/
RFC3031, January 2001, RFC3031, January 2001,
<http://www.rfc-editor.org/info/rfc3031>. <http://www.rfc-editor.org/info/rfc3031>.
skipping to change at page 9, line 42 skipping to change at page 9, line 42
Email: xufeng.liu.ietf@gmail.com Email: xufeng.liu.ietf@gmail.com
Vishnu Pavan Beeram Vishnu Pavan Beeram
Juniper Networks Juniper Networks
Email: vbeeram@juniper.net Email: vbeeram@juniper.net
Himanshu Shah Himanshu Shah
Ciena Ciena
Email: hshah@ciena.com Email: tsaad@cisco.com
Igor Bryskin Igor Bryskin
Huawei Technologies Huawei Technologies
Email: Igor.Bryskin@huawei.com Email: Igor.Bryskin@huawei.com
Xia Chen Xia Chen
Huawei Technologies Huawei Technologies
Email: jescia.chenxia@huawei.com Email: jescia.chenxia@huawei.com
 End of changes. 12 change blocks. 
15 lines changed or deleted 15 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/