idnits 2.17.1 draft-ietf-mpls-base-yang-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 05, 2016) is 2823 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-25) exists of draft-ietf-netmod-routing-cfg-22 ** Obsolete normative reference: RFC 6536 (Obsoleted by RFC 8341) ** Obsolete normative reference: RFC 7223 (Obsoleted by RFC 8343) Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 MPLS Working Group T. Saad 3 Internet-Draft K. Raza 4 Intended status: Standards Track R. Gandhi 5 Expires: January 6, 2017 Cisco Systems Inc 6 X. Liu 7 Ericsson 8 V. Beeram 9 Juniper Networks 10 H. Shah 11 Ciena 12 I. Bryskin 13 X. Chen 14 Huawei Technologies 15 R. Jones 16 Brocade 17 B. Wen 18 Comcast 19 July 05, 2016 21 A YANG Data Model for MPLS Base 22 draft-ietf-mpls-base-yang-01 24 Abstract 26 This document contains a specification of the the MPLS base YANG 27 model. The MPLS base YANG module serves as a base framework for 28 configuring and managing an MPLS switching subsystem. It is expected 29 that other MPLS technology YANG models (e.g. MPLS LSP Static, LDP or 30 RSVP-TE models) will augment the MPLS base YANG model. 32 Status of This Memo 34 This Internet-Draft is submitted in full conformance with the 35 provisions of BCP 78 and BCP 79. 37 Internet-Drafts are working documents of the Internet Engineering 38 Task Force (IETF). Note that other groups may also distribute 39 working documents as Internet-Drafts. The list of current Internet- 40 Drafts is at http://datatracker.ietf.org/drafts/current/. 42 Internet-Drafts are draft documents valid for a maximum of six months 43 and may be updated, replaced, or obsoleted by other documents at any 44 time. It is inappropriate to use Internet-Drafts as reference 45 material or to cite them other than as "work in progress." 47 This Internet-Draft will expire on January 6, 2017. 49 Copyright Notice 51 Copyright (c) 2016 IETF Trust and the persons identified as the 52 document authors. All rights reserved. 54 This document is subject to BCP 78 and the IETF Trust's Legal 55 Provisions Relating to IETF Documents 56 (http://trustee.ietf.org/license-info) in effect on the date of 57 publication of this document. Please review these documents 58 carefully, as they describe your rights and restrictions with respect 59 to this document. Code Components extracted from this document must 60 include Simplified BSD License text as described in Section 4.e of 61 the Trust Legal Provisions and are provided without warranty as 62 described in the Simplified BSD License. 64 Table of Contents 66 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 67 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 68 1.2. MPLS Base Tree Diagram . . . . . . . . . . . . . . . . . 3 69 1.3. MPLS Base Module . . . . . . . . . . . . . . . . . . . . 4 70 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 71 3. Security Considerations . . . . . . . . . . . . . . . . . . . 7 72 4. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 73 4.1. Normative References . . . . . . . . . . . . . . . . . . 8 74 4.2. Informative References . . . . . . . . . . . . . . . . . 9 75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 77 1. Introduction 79 A core routing data model is defined in 80 [I-D.ietf-netmod-routing-cfg], and it provides a basis for the 81 development of data models for routing protocols. The MPLS base 82 model augments this model with additional data specific to MPLS 83 switching [RFC3031]. The interface data model is defined in 84 [RFC7223] and is used for referencing interface from the MPLS base 85 model. 87 The MPLS base YANG module augments the "routing" read-write (rw) and 88 "routing-state" read-only (ro) branches of the ietf-routing module. 89 The approach described in [I-D.openconfig-netmod-opstate] is adopted 90 to represent data pertaining to configuration intended, applied state 91 and derived state data elements. Each container in the model holds a 92 "config" and "state" sub-container. The "config" sub-container 93 contains the intended configuration data, and the state sub-container 94 contains both the applied configuration and any derived state, such 95 as counters or statistical information. 97 This document defines the specification for the "ietf-mpls" YANG 98 module that provides base components of the MPLS data model. It is 99 expected that other MPLS YANG modules will augment the "ietf-mpls" 100 base model to define data models for other MPLS technologies (e.g. 101 MPLS LDP or MPLS RSVP-TE). 103 1.1. Terminology 105 In this document, the key words "MUST", "MUST NOT", "REQUIRED", 106 "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", 107 and "OPTIONAL" are to be interpreted as described in BCP 14, RFC 2119 108 [RFC2119]. 110 The following terms are defined in [RFC6020]: 112 o augment, 114 o configuration data, 116 o data model, 118 o data node, 120 o feature, 122 o mandatory node, 124 o module, 126 o schema tree, 128 o state data, 130 o RPC operation. 132 1.2. MPLS Base Tree Diagram 134 The MPLS base tree diagram is shown in Figure 1. 136 module: ietf-mpls 137 augment /rt:routing: 138 +--rw mpls 139 +--rw interface* [name] 140 +--rw name if:interface-ref 141 +--rw config 142 | +--rw enabled? boolean 143 | +--rw mtu? uint32 144 +--ro state 145 +--ro enabled? boolean 146 +--ro mtu? uint32 147 augment /rt:routing-state: 148 +--ro mpls 150 Figure 1: MPLS Base tree diagram 152 1.3. MPLS Base Module 154 file "ietf-mpls@2016-07-05.yang" 155 module ietf-mpls { 157 namespace "urn:ietf:params:xml:ns:yang:ietf-mpls"; 159 prefix "mpls"; 161 import ietf-routing { 162 prefix "rt"; 163 } 165 import ietf-interfaces { 166 prefix "if"; 167 } 169 organization "IETF MPLS Working Group"; 171 contact 172 "WG Web: 174 WG List: 176 WG Chair: Loa Andersson 177 179 WG Chair: Ross Callon 180 182 WG Chair: George Swallow 183 185 Editor: Tarek Saad 186 188 Editor: Kamran Raza 189 191 Editor: Rakesh Gandhi 192 194 Editor: Xufeng Liu 195 197 Editor: Vishnu Pavan Beeram 198 200 Editor: Himanshu Shah 201 203 Editor: Igor Bryskin 204 206 Editor: Xia Chen 207 209 Editor: Raqib Jones 210 212 Editor: Bin Wen 213 "; 215 description 216 "This YANG module defines the essential components for the 217 management of the MPLS subsystem."; 219 revision "2016-07-05" { 220 description 221 "Latest revision: 222 - Addressed MPLS-RT review comments"; 223 reference "RFC 3031: A YANG Data Model for base MPLS"; 224 } 226 typedef mpls-label { 227 type uint32 { 228 range "0..1048575"; 229 } 230 description 231 "The MPLS label range"; 232 } 234 grouping interface-mpls { 235 description "MPLS interface properties grouping"; 236 leaf enabled { 237 type boolean; 238 description 239 "'true' if mpls encapsulation is enabled on the 240 interface. 'false' if mpls encapsulation is enabled 241 on the interface."; 242 } 243 leaf mtu { 244 type uint32; 245 description 246 "MPLS Maximum Transmission Unit (MTU)"; 247 } 248 } 250 augment "/rt:routing" { 251 description "MPLS augmentation."; 252 container mpls { 253 description 254 "MPLS container, to be used as an augmentation target node 255 other MPLS sub-features config, e.g. MPLS static LSP, MPLS 256 LDP LSPs, and Trafic Engineering MPLS LSP Tunnels, etc."; 258 list interface { 259 key "name"; 260 description "List of MPLS interfaces"; 261 leaf name { 262 type if:interface-ref; 263 description 264 "The name of a configured MPLS interface"; 265 } 266 container config { 267 description "Holds intended configuration"; 268 uses interface-mpls; 269 } 270 container state { 271 config false; 272 description "Holds inuse configuration"; 273 uses interface-mpls; 274 } 275 } 276 } 277 } 278 augment "/rt:routing-state" { 279 description "MPLS augmentation."; 280 container mpls { 281 config false; 282 description 283 "MPLS container, to be used as an augmentation target node 284 other MPLS sub-features state"; 285 } 286 } 287 } 288 290 Figure 2: MPLS base YANG module 292 2. IANA Considerations 294 This document registers the following URIs in the IETF XML registry 295 [RFC3688]. Following the format in [RFC3688], the following 296 registration is requested to be made. 298 URI: urn:ietf:params:xml:ns:yang:ietf-mpls XML: N/A, the requested 299 URI is an XML namespace. 301 This document registers a YANG module in the YANG Module Names 302 registry [RFC6020]. 304 name: ietf-mpls namespace: urn:ietf:params:xml:ns:yang:ietf-mpls 305 prefix: ietf-mpls reference: RFC3031 307 3. Security Considerations 309 The YANG module defined in this document is designed to be accessed 310 via the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the 311 secure transport layer and the mandatory-to-implement secure 312 transport is SSH [RFC6242]. The NETCONF access control model 313 [RFC6536] provides means to restrict access for particular NETCONF 314 users to a pre-configured subset of all available NETCONF protocol 315 operations and content. 317 There are a number of data nodes defined in the YANG module which are 318 writable/creatable/deletable (i.e., config true, which is the 319 default). These data nodes may be considered sensitive or vulnerable 320 in some network environments. Write operations (e.g., ) 321 to these data nodes without proper protection can have a negative 322 effect on network operations. 324 4. References 326 4.1. Normative References 328 [I-D.ietf-netmod-routing-cfg] 329 Lhotka, L. and A. Lindem, "A YANG Data Model for Routing 330 Management", draft-ietf-netmod-routing-cfg-22 (work in 331 progress), July 2016. 333 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 334 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 335 RFC2119, March 1997, 336 . 338 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 339 Label Switching Architecture", RFC 3031, DOI 10.17487/ 340 RFC3031, January 2001, 341 . 343 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 344 DOI 10.17487/RFC3688, January 2004, 345 . 347 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 348 the Network Configuration Protocol (NETCONF)", RFC 6020, 349 DOI 10.17487/RFC6020, October 2010, 350 . 352 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 353 and A. Bierman, Ed., "Network Configuration Protocol 354 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 355 . 357 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 358 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 359 . 361 [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration 362 Protocol (NETCONF) Access Control Model", RFC 6536, DOI 363 10.17487/RFC6536, March 2012, 364 . 366 [RFC7223] Bjorklund, M., "A YANG Data Model for Interface 367 Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, 368 . 370 4.2. Informative References 372 [I-D.openconfig-netmod-opstate] 373 Shakir, R., Shaikh, A., and M. Hines, "Consistent Modeling 374 of Operational State Data in YANG", draft-openconfig- 375 netmod-opstate-01 (work in progress), July 2015. 377 Authors' Addresses 379 Tarek Saad 380 Cisco Systems Inc 382 Email: tsaad@cisco.com 384 Kamran Raza 385 Cisco Systems Inc 387 Email: skraza@cisco.com 389 Rakesh Gandhi 390 Cisco Systems Inc 392 Email: rgandhi@cisco.com 394 Xufeng Liu 395 Ericsson 397 Email: xufeng.liu.ietf@gmail.com 399 Vishnu Pavan Beeram 400 Juniper Networks 402 Email: vbeeram@juniper.net 404 Himanshu Shah 405 Ciena 407 Email: tsaad@cisco.com 408 Igor Bryskin 409 Huawei Technologies 411 Email: Igor.Bryskin@huawei.com 413 Xia Chen 414 Huawei Technologies 416 Email: jescia.chenxia@huawei.com 418 Raqib Jones 419 Brocade 421 Email: raqib@Brocade.com 423 Bin Wen 424 Comcast 426 Email: Bin_Wen@cable.comcast.com