idnits 2.17.1 draft-liu-teas-yang-l3-te-topo-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 : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 7, 2016) is 2848 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) == Missing Reference: 'RFC2119' is mentioned on line 100, but not defined == Unused Reference: 'RFC6021' is defined on line 529, but no explicit reference was found in the text == Unused Reference: 'RFC2234' is defined on line 536, but no explicit reference was found in the text == Unused Reference: 'RFC6087' is defined on line 549, but no explicit reference was found in the text ** Obsolete normative reference: RFC 6021 (Obsoleted by RFC 6991) ** Obsolete normative reference: RFC 2234 (Obsoleted by RFC 4234) -- Obsolete informational reference (is this intentional?): RFC 6087 (Obsoleted by RFC 8407) Summary: 3 errors (**), 0 flaws (~~), 5 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group X. Liu 2 Internet-Draft Ericsson 3 Intended status: Standards Track I. Bryskin 4 Expires: January 7, 2017 Huawei Technologies 5 V. Beeram 6 Juniper Networks 7 T. Saad 8 Cisco Systems Inc 9 H. Shah 10 Ciena 11 O. Gonzalez de Dios 12 Telefonica 13 July 7, 2016 15 YANG Data Model for Layer 3 TE Topologies 16 draft-liu-teas-yang-l3-te-topo-01 18 Abstract 20 This document defines a YANG data model for layer 3 traffic 21 engineering topologies. 23 Status of this Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF), its areas, and its working groups. Note that 30 other groups may also distribute working documents as Internet- 31 Drafts. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 The list of current Internet-Drafts can be accessed at 39 http://www.ietf.org/ietf/1id-abstracts.txt 41 The list of Internet-Draft Shadow Directories can be accessed at 42 http://www.ietf.org/shadow.html 44 This Internet-Draft will expire on January 7, 2017. 46 Copyright Notice 48 Copyright (c) 2016 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents 53 (http://trustee.ietf.org/license-info) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in Section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the Simplified BSD License. 61 Table of Contents 63 1. Introduction...................................................2 64 1.1. Terminology...............................................3 65 2. Modeling Considerations........................................3 66 2.1. Relationship Between Layer 3 Topology and TE topology.....3 67 2.2. Relationship Modeling.....................................3 68 3. Model Structure................................................4 69 3.1. Layer 3 TE Topology Module................................4 70 3.2. Packet Switching TE Topology Module.......................4 71 4. YANG Modules...................................................5 72 4.1. Layer 3 TE Topology Module................................5 73 4.2. Packet Switching TE Topology Module.......................9 74 5. Security Considerations.......................................13 75 6. References....................................................13 76 6.1. Normative References.....................................13 77 6.2. Informative References...................................13 79 1. Introduction 81 This document defines a YANG [RFC6020] data model for describing the 82 relationship between a layer 3 network topology [YANG-L3-TOPO] and a 83 TE topology [YANG-TE-TOPO]. 85 When traffic engineering is enabled on a layer 3 network topology, 86 there will be a corresponding TE topology. The TE topology may or may 87 not be congruent to the layer 3 network topology. When such a 88 congruent TE topology exists, there will be a one-to-one association 89 between the one modeling element in the layer 3 topology to another 90 element in the TE topology. When such a congruent TE topology does 91 not exist, the association will not be one-to-one. This YANG data 92 model allows both cases. 94 1.1. Terminology 96 The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 97 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 98 "OPTIONAL" in this document are to be interpreted as described in BCP 99 14, [RFC2119]. 101 The following terms are defined in [RFC6020] and are not redefined 102 here: 104 o augment 106 o data model 108 o data node 110 2. Modeling Considerations 112 2.1. Relationship Between Layer 3 Topology and TE topology 114 In general, layer 3 network topology model and TE topology model can 115 be used independently. When traffic engineering is enabled on a layer 116 3 network topology, there will be associations between objects in 117 layer 3 network topologies and objects in TE topologies. The 118 properties of these relations are: 120 o The associations are between objects of the same class, i.e. 121 node to node or link to link. 123 o The multiplicity of such an association is: 0..1 to 0..1. An 124 object in a layer 3 network may have zero or one associated 125 object in the corresponding TE network. 127 2.2. Relationship Modeling 129 YANG data type leafref is used to model the association relationship 130 between a layer 3 network topology and a TE topology. YANG must 131 statements are used to enforce the referenced objects are in the 132 topologies of proper type. 134 3. Model Structure 136 3.1. Layer 3 TE Topology Module 138 The model tree structure of the layer 3 TE topology module is as 139 shown below: 141 module: ietf-l3-te-topology 142 augment /nw:networks/nw:network/nw:network-types/l3t:l3-unicast-igp- 143 topology: 144 +--rw l3-te! 145 augment /nw:networks/nw:network/l3t:igp-topology-attributes: 146 +--rw l3-te-topology-attributes 147 +--rw network-ref? leafref 148 augment /nw:networks/nw:network/nw:node/l3t:igp-node-attributes: 149 +--rw l3-te-node-attributes 150 +--rw node-ref? leafref 151 +--rw network-ref? leafref 152 augment /nw:networks/nw:network/nw:node/nt:termination-point/l3t:igp- 153 termination-point-attributes: 154 +--rw l3-te-tp-attributes 155 +--rw tp-ref? leafref 156 +--rw node-ref? leafref 157 +--rw network-ref? leafref 158 augment /nw:networks/nw:network/nt:link/l3t:igp-link-attributes: 159 +--rw l3-te-link-attributes 160 +--rw link-ref? leafref 161 +--rw network-ref? leafref 163 3.2. Packet Switching TE Topology Module 165 This is an augmentation to base TE topology model. 167 module: ietf-te-topology-psc 168 augment /nw:networks/tet:te/tet:templates/tet:link-template/tet:te- 169 link-attributes/tet:interface-switching-capability: 170 +--rw packet-switch-capable 171 +--rw minimum-lsp-bandwidth? decimal64 172 +--rw interface-mtu? uint16 173 augment /nw:networks/nw:network/nt:link/tet:te/tet:config/tet:te- 174 link-attributes/tet:interface-switching-capability: 175 +--rw packet-switch-capable 176 +--rw minimum-lsp-bandwidth? decimal64 177 +--rw interface-mtu? uint16 179 augment /nw:networks/nw:network/nt:link/tet:te/tet:state/tet:te-link- 180 attributes/tet:interface-switching-capability: 181 +--ro packet-switch-capable 182 +--ro minimum-lsp-bandwidth? decimal64 183 +--ro interface-mtu? uint16 184 augment 185 /nw:networks/nw:network/nt:link/tet:te/tet:state/tet:information- 186 source-entry/tet:interface-switching-capability: 187 +--ro packet-switch-capable 188 +--ro minimum-lsp-bandwidth? decimal64 189 +--ro interface-mtu? uint16 190 augment /tet:te-link-event/tet:te-link-attributes/tet:interface- 191 switching-capability: 192 +---- packet-switch-capable 193 +---- minimum-lsp-bandwidth? decimal64 194 +---- interface-mtu? uint16 195 augment /tet:te-link-event/tet:information-source- 196 entry/tet:interface-switching-capability: 197 +---- packet-switch-capable 198 +---- minimum-lsp-bandwidth? decimal64 199 +---- interface-mtu? uint16 201 4. YANG Modules 203 4.1. Layer 3 TE Topology Module 205 file "ietf-l3-te-topology@2016-06-15.yang" 206 module ietf-l3-te-topology { 207 yang-version 1.1; 208 namespace "urn:ietf:params:xml:ns:yang:ietf-l3-te-topology"; 209 prefix "l3te"; 211 import ietf-network { 212 prefix "nw"; 213 } 214 import ietf-network-topology { 215 prefix "nt"; 216 } 217 import ietf-l3-unicast-igp-topology { 218 prefix "l3t"; 219 } 220 import ietf-te-topology { 221 prefix "tet"; 222 } 223 organization "TBD"; 224 contact "TBD"; 225 description "L3 TE Topology model"; 227 revision "2016-06-15" { 229 description "Initial revision"; 230 reference "TBD"; 231 } 233 grouping l3-te-topology-type { 234 description 235 "Identifies the L3 TE topology type."; 236 container l3-te { 237 presence "indiates L3 TE Topology"; 238 description 239 "Its presence identifies the L3 TE topology type."; 240 } 241 } 243 augment "/nw:networks/nw:network/nw:network-types/" 244 + "l3t:l3-unicast-igp-topology" { 245 description 246 "Defines the L3 TE topology type."; 247 uses l3-te-topology-type; 248 } 250 augment "/nw:networks/nw:network/l3t:igp-topology-attributes" { 251 when "../nw:network-types/l3t:l3-unicast-igp-topology/l3-te" { 252 description "Augment only for L3 TE topology"; 253 } 254 description "Augment topology configuration"; 255 uses l3-te-topology-attributes; 256 } 258 augment "/nw:networks/nw:network/nw:node/l3t:igp-node-attributes" { 259 when "../../nw:network-types/l3t:l3-unicast-igp-topology/l3-te" { 260 description "Augment only for L3 TE topology"; 261 } 262 description "Augment node configuration"; 263 uses l3-te-node-attributes; 264 } 266 augment "/nw:networks/nw:network/nw:node/nt:termination-point/" 267 + "l3t:igp-termination-point-attributes" { 268 when "../../../nw:network-types/l3t:l3-unicast-igp-topology/" 269 + "l3-te" { 270 description "Augment only for L3 TE topology"; 271 } 272 description "Augment termination point configuration"; 273 uses l3-te-tp-attributes; 274 } 276 augment "/nw:networks/nw:network/nt:link/l3t:igp-link-attributes" { 277 when "../../nw:network-types/l3t:l3-unicast-igp-topology/l3-te" { 278 description "Augment only for L3 TE topology"; 279 } 280 description "Augment link configuration"; 281 uses l3-te-link-attributes; 282 } 284 grouping l3-te-topology-attributes { 285 description "L3 TE topology scope attributes"; 286 container l3-te-topology-attributes { 287 must "/nw:networks/nw:network" 288 + "[nw:network-id = current()/network-ref]/nw:network-types/" 289 + "tet:te-topology" { 290 error-message 291 "The referenced network must be a TE topology."; 292 description 293 "The referenced network must be a TE topology."; 294 } 295 description "Containing TE topology references"; 296 uses nw:network-ref; 297 } // l3-te-topology-attributes 298 } // l3-te-topology-attributes 300 grouping l3-te-node-attributes { 301 description "L3 TE node scope attributes"; 302 container l3-te-node-attributes { 303 must "/nw:networks/nw:network" 304 + "[nw:network-id = current()/network-ref]/nw:network-types/" 305 + "tet:te-topology" { 306 error-message 307 "The referenced network must be a TE topology."; 308 description 309 "The referenced network must be a TE topology."; 310 } 311 description "Containing TE node references"; 312 uses nw:node-ref; 313 } // l3-te 314 } // l3-te-node-attributes 316 grouping l3-te-tp-attributes { 317 description "L3 TE termination point scope attributes"; 318 container l3-te-tp-attributes { 319 must "/nw:networks/nw:network" 320 + "[nw:network-id = current()/network-ref]/nw:network-types/" 321 + "tet:te-topology" { 322 error-message 323 "The referenced network must be a TE topology."; 324 description 325 "The referenced network must be a TE topology."; 326 } 327 description "Containing TE termination point references"; 328 uses nt:tp-ref; 329 } // l3-te 330 } // l3-te-tp-attributes 332 grouping l3-te-link-attributes { 333 description "L3 TE link scope attributes"; 334 container l3-te-link-attributes { 335 must "/nw:networks/nw:network" 336 + "[nw:network-id = current()/network-ref]/nw:network-types/" 337 + "tet:te-topology" { 338 error-message 339 "The referenced network must be a TE topology."; 340 description 341 "The referenced network must be a TE topology."; 342 } 343 description "Containing TE link references"; 344 uses nt:link-ref; 346 } 347 } // l3-te-link-attributes 348 } 349 351 4.2. Packet Switching TE Topology Module 353 file "ietf-te-topology-psc@2016-07-01.yang" 354 module ietf-te-topology-psc { 355 yang-version 1; 356 namespace "urn:ietf:params:xml:ns:yang:ietf-te-topology-psc"; 357 // replace with IANA namespace when assigned 359 prefix "tet-psc"; 361 import ietf-network { 362 prefix "nw"; 363 } 365 import ietf-network-topology { 366 prefix "nt"; 367 } 369 import ietf-te-topology { 370 prefix "tet"; 371 } 373 organization 374 "Traffic Engineering Architecture and Signaling (TEAS) 375 Working Group"; 377 contact 378 "WG Web: 379 WG List: 381 WG Chair: Lou Berger 382 384 WG Chair: Vishnu Pavan Beeram 385 387 Editors: Xufeng Liu 388 390 Igor Bryskin 391 393 Vishnu Pavan Beeram 394 396 Tarek Saad 397 399 Himanshu Shah 400 402 Oscar Gonzalez De Dios 403 "; 405 description "TE topology model"; 407 revision "2016-07-01" { 408 description "Initial revision"; 409 reference "TBD"; 410 } 412 /* 413 * Groupings 414 */ 415 grouping packet-switch-capable-container { 416 description 417 "The container of packet switch capable attributes."; 418 container packet-switch-capable { 419 description 420 "Interface has packet-switching capabilities."; 421 leaf minimum-lsp-bandwidth { 422 type decimal64 { 423 fraction-digits 2; 424 } 425 description 426 "Minimum LSP Bandwidth. Units in bytes per second"; 427 } 428 leaf interface-mtu { 429 type uint16; 430 description 431 "Interface MTU."; 432 } 433 } 434 } 436 /* 437 * Configuration data nodes 438 */ 439 augment "/nw:networks/tet:te/tet:templates/" 440 + "tet:link-template/tet:te-link-attributes/" 441 + "tet:interface-switching-capability" { 442 when "switching-capability = 'switching-psc1' " { 443 description "Valid only for PSC"; 444 } 445 description 446 "Parameters for PSC TE topology."; 447 uses packet-switch-capable-container; 448 } 450 augment "/nw:networks/nw:network/nt:link/tet:te/tet:config/" 451 + "tet:te-link-attributes/" 452 + "tet:interface-switching-capability" { 453 when "switching-capability = 'switching-psc1' " { 454 description "Valid only for PSC"; 455 } 456 description 457 "Parameters for PSC TE topology."; 458 uses packet-switch-capable-container; 459 } 461 /* 462 * Operational state data nodes 463 */ 464 augment "/nw:networks/nw:network/nt:link/tet:te/tet:state/" 465 + "tet:te-link-attributes/" 466 + "tet:interface-switching-capability" { 467 when "switching-capability = 'switching-psc1' " { 468 description "Valid only for PSC"; 470 } 471 description 472 "Parameters for PSC TE topology."; 473 uses packet-switch-capable-container; 474 } 476 augment "/nw:networks/nw:network/nt:link/tet:te/tet:state/" 477 + "tet:information-source-entry/" 478 + "tet:interface-switching-capability" { 479 when "switching-capability = 'switching-psc1' " { 480 description "Valid only for PSC"; 481 } 482 description 483 "Parameters for PSC TE topology."; 484 uses packet-switch-capable-container; 485 } 487 /* 488 * Notifications 489 */ 490 augment "/tet:te-link-event/tet:te-link-attributes/" 491 + "tet:interface-switching-capability" { 492 when "switching-capability = 'switching-psc1' " { 493 description "Valid only for PSC"; 494 } 495 description 496 "Parameters for PSC TE topology."; 497 uses packet-switch-capable-container; 498 } 500 augment "/tet:te-link-event/tet:information-source-entry/" 501 + "tet:interface-switching-capability" { 502 when "switching-capability = 'switching-psc1' " { 503 description "Valid only for PSC"; 504 } 505 description 506 "Parameters for PSC TE topology."; 507 uses packet-switch-capable-container; 508 } 509 } 510 512 5. Security Considerations 514 The configuration, state, action and notification data defined in 515 this document are designed to be accessed via the NETCONF protocol 516 [RFC6241]. The data-model by itself does not create any security 517 implications. The security considerations for the NETCONF protocol 518 are applicable. The NETCONF protocol used for sending the data 519 supports authentication and encryption. 521 6. References 523 6.1. Normative References 525 [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the 526 Network Configuration Protocol (NETCONF)", RFC 6020, 527 October 2010. 529 [RFC6021] Schoenwaelder, J., "Common YANG Data Types", RFC 6021, 530 October 2010. 532 [RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A. Bierman, 533 "Network Configuration Protocol (NETCONF)", RFC 6241, June 534 2011. 536 [RFC2234] Crocker, D. and Overell, P.(Editors), "Augmented BNF for 537 Syntax Specifications: ABNF", RFC 2234, Internet Mail 538 Consortium and Demon Internet Ltd., November 1997. 540 [YANG-L3-TOPO] Clemm, A., et al., "A YANG Data Model for Layer 3 541 Topologies", draft-ietf-i2rs-yang-l3-topology, (Work in 542 Progress). 544 [YANG-TE-TOPO] Liu, X., et al., "YANG Data Model for TE Topologies", 545 draft-ietf-teas-yang-te-topo, Work in Progress). 547 6.2. Informative References 549 [RFC6087] Bierman, A., "Guidelines for Authors and Reviewers of YANG 550 Data Model Documents", RFC 6087, January 2011. 552 Authors' Addresses 554 Xufeng Liu 555 Ericsson / Kuatro Technologies Inc. 556 8281 Greensboro Drive, Suite 200 557 McLean, VA 22102 558 USA 560 Email: xliu@kuatrotech.com 562 Igor Bryskin 563 Huawei Technologies 564 Email: Igor.Bryskin@huawei.com 566 Vishnu Pavan Beeram 567 Juniper Networks 568 Email: vbeeram@juniper.net 570 Tarek Saad 571 Cisco Systems Inc 572 Email: tsaad@cisco.com 574 Himanshu Shah 575 Ciena 576 Email: hshah@ciena.com 578 Oscar Gonzalez de Dios 579 Telefonica 580 Email: oscar.gonzalezdedios@telefonica.com