idnits 2.17.1 draft-liu-teas-yang-l3-te-topo-00.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 (March 20, 2016) is 2953 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 96, but not defined == Unused Reference: 'RFC6021' is defined on line 321, but no explicit reference was found in the text == Unused Reference: 'RFC2234' is defined on line 328, but no explicit reference was found in the text == Unused Reference: 'RFC6087' is defined on line 341, 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: September 20, 2016 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 March 20, 2016 15 YANG Data Model for Layer 3 TE Topologies 16 draft-liu-teas-yang-l3-te-topo-00 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 September 20, 2015. 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................................................3 69 4. Layer 3 TE Topology YANG Module................................4 70 5. Security Considerations........................................8 71 6. References.....................................................8 72 6.1. Normative References......................................8 73 6.2. Informative References....................................8 75 1. Introduction 77 This document defines a YANG [RFC6020] data model for describing the 78 relationship between a layer 3 network topology [YANG-L3-TOPO] and a 79 TE topology [YANG-TE-TOPO]. 81 When traffic engineering is enabled on a layer 3 network topology, 82 there will be a corresponding TE topology. The TE topology may or may 83 not be congruent to the layer 3 network topology. When such a 84 congruent TE topology exists, there will be a one-to-one association 85 between the one modeling element in the layer 3 topology to another 86 element in the TE topology. When such a congruent TE topology does 87 not exist, the association will not be one-to-one. This YANG data 88 model allows both cases. 90 1.1. Terminology 92 The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 93 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 94 "OPTIONAL" in this document are to be interpreted as described in BCP 95 14, [RFC2119]. 97 The following terms are defined in [RFC6020] and are not redefined 98 here: 100 o augment 102 o data model 104 o data node 106 2. Modeling Considerations 108 2.1. Relationship Between Layer 3 Topology and TE topology 110 In general, layer 3 network topology model and TE topology model can 111 be used independently. When traffic engineering is enabled on a layer 112 3 network topology, there will be associations between objects in 113 layer 3 network topologies and objects in TE topologies. The 114 properties of these relations are: 116 o The associations are between objects of the same class, i.e. 117 node to node or link to link. 119 o The multiplicity of such an association is: 0..1 to 0..1. An 120 object in a layer 3 network may have zero or one associated 121 object in the corresponding TE network. 123 2.2. Relationship Modeling 125 YANG data type leafref is used to model the association relationship 126 between a layer 3 network topology and a TE topology. YANG must 127 statements are used to enforce the referenced objects are in the 128 topologies of proper type. 130 3. Model Structure 132 The model tree structure proposed by this document is as shown below: 134 module: ietf-l3-te-topology 135 augment /nw:networks/nw:network/nw:network-types/l3t:l3-unicast-igp- 136 topology: 137 +--rw l3-te! 138 augment /nw:networks/nw:network/l3t:igp-topology-attributes: 139 +--rw l3-te-topology-attributes 140 +--rw network-ref? leafref 141 augment /nw:networks/nw:network/nw:node/l3t:igp-node-attributes: 142 +--rw l3-te-node-attributes 143 +--rw node-ref? leafref 144 +--rw network-ref? leafref 145 augment /nw:networks/nw:network/nw:node/nt:termination-point/l3t:igp- 146 termination-point-attributes: 147 +--rw l3-te-tp-attributes 148 +--rw tp-ref? leafref 149 +--rw node-ref? leafref 150 +--rw network-ref? leafref 151 augment /nw:networks/nw:network/nt:link/l3t:igp-link-attributes: 152 +--rw l3-te-link-attributes 153 +--rw link-ref? leafref 154 +--rw network-ref? leafref 156 4. Layer 3 TE Topology YANG Module 158 file "ietf-l3-te-topology@2016-03-17.yang" 159 module ietf-l3-te-topology { 160 yang-version 1.1; 161 namespace "urn:ietf:params:xml:ns:yang:ietf-l3-te-topology"; 162 prefix "l3te"; 164 import ietf-network { 165 prefix "nw"; 166 } 167 import ietf-network-topology { 168 prefix "nt"; 169 } 170 import ietf-l3-unicast-igp-topology { 171 prefix "l3t"; 172 } 173 import ietf-te-topology { 174 prefix "tet"; 175 } 176 organization "TBD"; 177 contact "TBD"; 178 description "L3 TE Topology model"; 180 revision "2016-03-17" { 182 description "Initial revision"; 183 reference "TBD"; 184 } 186 grouping l3-te-topology-type { 187 description 188 "Identifies the L3 TE topology type."; 189 container l3-te { 190 presence "indiates L3 TE Topology"; 191 description 192 "Its presence identifies the L3 TE topology type."; 193 } 194 } 196 augment "/nw:networks/nw:network/nw:network-types/" 197 + "l3t:l3-unicast-igp-topology" { 198 description 199 "Defines the OSPF topology type."; 200 uses l3-te-topology-type; 201 } 203 augment "/nw:networks/nw:network/l3t:igp-topology-attributes" { 204 when "../nw:network-types/l3t:l3-unicast-igp-topology/l3-te" { 205 description "Augment only for L3 unicast topology"; 206 } 207 description "Augment topology configuration"; 208 uses l3-te-topology-attributes; 209 } 211 augment "/nw:networks/nw:network/nw:node/l3t:igp-node-attributes" { 212 when "../../nw:network-types/l3t:l3-unicast-igp-topology/l3-te" { 213 description "Augment only for L3 unicast topology"; 214 } 215 description "Augment node configuration"; 216 uses l3-te-node-attributes; 217 } 219 augment "/nw:networks/nw:network/nw:node/nt:termination-point/" 220 + "l3t:igp-termination-point-attributes" { 221 when "../../../nw:network-types/l3t:l3-unicast-igp-topology/" 222 + "l3-te" { 223 description "Augment only for L3 unicast topology"; 224 } 225 description "Augment termination point configuration"; 226 uses l3-te-tp-attributes; 227 } 229 augment "/nw:networks/nw:network/nt:link/l3t:igp-link-attributes" { 230 when "../../nw:network-types/l3t:l3-unicast-igp-topology/l3-te" { 231 description "Augment only for L3 unicast topology"; 232 } 233 description "Augment link configuration"; 234 uses l3-te-link-attributes; 235 } 237 grouping l3-te-topology-attributes { 238 description "L3 TE topology scope attributes"; 239 container l3-te-topology-attributes { 240 must "/nw:networks/nw:network" 241 + "[nw:network-id = current()/network-ref]/nw:network-types/" 242 + "tet:te-topology" { 243 error-message 244 "The referenced network must be a TE topology."; 245 description 246 "The referenced network must be a TE topology."; 247 } 248 description "Containing TE topology references"; 249 uses nw:network-ref; 250 } // l3-te-topology-attributes 251 } // l3-te-topology-attributes 253 grouping l3-te-node-attributes { 254 description "L3 TE node scope attributes"; 255 container l3-te-node-attributes { 256 must "/nw:networks/nw:network" 257 + "[nw:network-id = current()/network-ref]/nw:network-types/" 258 + "tet:te-topology" { 259 error-message 260 "The referenced network must be a TE topology."; 261 description 262 "The referenced network must be a TE topology."; 263 } 264 description "Containing TE node references"; 265 uses nw:node-ref; 266 } // l3-te 267 } // l3-te-node-attributes 269 grouping l3-te-tp-attributes { 270 description "L3 TE termination point scope attributes"; 271 container l3-te-tp-attributes { 272 must "/nw:networks/nw:network" 273 + "[nw:network-id = current()/network-ref]/nw:network-types/" 274 + "tet:te-topology" { 275 error-message 276 "The referenced network must be a TE topology."; 277 description 278 "The referenced network must be a TE topology."; 279 } 280 description "Containing TE termination point references"; 281 uses nt:tp-ref; 282 } // l3-te 283 } // l3-te-tp-attributes 285 grouping l3-te-link-attributes { 286 description "L3 TE link scope attributes"; 287 container l3-te-link-attributes { 288 must "/nw:networks/nw:network" 289 + "[nw:network-id = current()/network-ref]/nw:network-types/" 290 + "tet:te-topology" { 291 error-message 292 "The referenced network must be a TE topology."; 293 description 294 "The referenced network must be a TE topology."; 295 } 296 description "Containing TE link references"; 297 uses nt:link-ref; 299 } 300 } // l3-te-link-attributes 301 } 302 304 5. Security Considerations 306 The configuration, state, action and notification data defined in 307 this document are designed to be accessed via the NETCONF protocol 308 [RFC6241]. The data-model by itself does not create any security 309 implications. The security considerations for the NETCONF protocol 310 are applicable. The NETCONF protocol used for sending the data 311 supports authentication and encryption. 313 6. References 315 6.1. Normative References 317 [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the 318 Network Configuration Protocol (NETCONF)", RFC 6020, 319 October 2010. 321 [RFC6021] Schoenwaelder, J., "Common YANG Data Types", RFC 6021, 322 October 2010. 324 [RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A. Bierman, 325 "Network Configuration Protocol (NETCONF)", RFC 6241, June 326 2011. 328 [RFC2234] Crocker, D. and Overell, P.(Editors), "Augmented BNF for 329 Syntax Specifications: ABNF", RFC 2234, Internet Mail 330 Consortium and Demon Internet Ltd., November 1997. 332 [YANG-L3-TOPO] Clemm, A., et al., "A YANG Data Model for Layer 3 333 Topologies", draft-ietf-i2rs-yang-l3-topology, (Work in 334 Progress). 336 [YANG-TE-TOPO] Liu, X., et al., "YANG Data Model for TE Topologies", 337 draft-ietf-teas-yang-te-topo, Work in Progress). 339 6.2. Informative References 341 [RFC6087] Bierman, A., "Guidelines for Authors and Reviewers of YANG 342 Data Model Documents", RFC 6087, January 2011. 344 Authors' Addresses 346 Xufeng Liu 347 Ericsson / Kuatro Technologies Inc. 348 8281 Greensboro Drive, Suite 200 349 McLean, VA 22102 350 USA 352 Email: xliu@kuatrotech.com 354 Igor Bryskin 355 Huawei Technologies 356 Email: Igor.Bryskin@huawei.com 358 Vishnu Pavan Beeram 359 Juniper Networks 360 Email: vbeeram@juniper.net 362 Tarek Saad 363 Cisco Systems Inc 364 Email: tsaad@cisco.com 366 Himanshu Shah 367 Ciena 368 Email: hshah@ciena.com 370 Oscar Gonzalez de Dios 371 Telefonica 372 Email: oscar.gonzalezdedios@telefonica.com