idnits 2.17.1 draft-zheng-ccamp-client-tunnel-yang-02.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 : ---------------------------------------------------------------------------- ** There are 2 instances of too long lines in the document, the longest one being 6 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 5, 2018) is 2242 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) == Unused Reference: 'I-D.ietf-ccamp-otn-topo-yang' is defined on line 303, but no explicit reference was found in the text == Unused Reference: 'RFC7139' is defined on line 326, but no explicit reference was found in the text == Unused Reference: 'I-D.zhang-teas-transport-service-model' is defined on line 353, but no explicit reference was found in the text == Unused Reference: 'RFC7062' is defined on line 359, but no explicit reference was found in the text == Outdated reference: A later version (-18) exists of draft-ietf-ccamp-otn-topo-yang-02 == Outdated reference: A later version (-20) exists of draft-ietf-ccamp-otn-tunnel-model-01 == Outdated reference: A later version (-36) exists of draft-ietf-teas-yang-te-13 Summary: 1 error (**), 0 flaws (~~), 8 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 CCAMP Working Group H. Zheng 3 Internet-Draft A. Guo 4 Intended status: Standards Track I. Busi 5 Expires: September 6, 2018 Huawei Technologies 6 Y. Xu 7 CAICT 8 Y. Zhao 9 China Mobile 10 X. Liu 11 Jabil 12 G. Fioccola 13 Telecom Italia 14 March 5, 2018 16 A YANG Data Model for Client-layer Tunnel 17 draft-zheng-ccamp-client-tunnel-yang-02 19 Abstract 21 A transport network is a server-layer network to provide connectivity 22 services to its client. In this draft the tunnel of client is 23 described, with the definition of client tunnel YANG model. 25 Status of This Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at https://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on September 6, 2018. 42 Copyright Notice 44 Copyright (c) 2018 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (https://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 60 2. Terminology and Notations . . . . . . . . . . . . . . . . . . 3 61 3. YANG Model for Client-layer Tunnel . . . . . . . . . . . . . 3 62 3.1. YANG Tree for Ethernet Tunnel . . . . . . . . . . . . . . 3 63 3.2. YANG Tree for Tunnel of other Client Signal Model . . . . 4 64 4. YANG Code for Client-layer Tunnel . . . . . . . . . . . . . . 4 65 4.1. The ETH Tunnel YANG Code . . . . . . . . . . . . . . . . 4 66 4.2. Other Client-layer Tunnel YANG Code . . . . . . . . . . . 6 67 5. Considerations and Open Issue . . . . . . . . . . . . . . . . 6 68 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 69 7. Manageability Considerations . . . . . . . . . . . . . . . . 6 70 8. Security Considerations . . . . . . . . . . . . . . . . . . . 6 71 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 72 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 7 73 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 74 11.1. Normative References . . . . . . . . . . . . . . . . . . 7 75 11.2. Informative References . . . . . . . . . . . . . . . . . 8 76 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 78 1. Introduction 80 A transport network is a server-layer network designed to provide 81 connectivity services for a client-layer network to carry the client 82 traffic transparently across the server-layer network resources. The 83 tunnel model in Traffic-Engineered network has been defined in both 84 generic way and technology-specific way. The generic model, which is 85 the base TE tunnel YANG model, can be found at 86 [I-D.ietf-teas-yang-te]. Technology-specific models, such as OTN/ 87 WSON tunnel model, have also been defined in 88 [I-D.ietf-ccamp-otn-tunnel-model] and 89 [I-D.lee-ccamp-wson-tunnel-model] respectively. Corresponding tunnel 90 on client-layer is also required, to have a complete topology view 91 from the perspective of network controllers. 93 This document defines a data model of all client-layer tunnel, using 94 YANG language defined in [RFC7950]. The model is augmenting the 95 generic TE tunnel model, and can be used by applications exposing to 96 a network controller via a REST interface. Furthermore, it can be 97 used by an application to describe the client tunnel that constructed 98 above the server-layer network. It is also worth noting that the 99 client layer network will only need the tunnel model when there is a 100 demand for switching techniques, such as Carrier Ethernet and MPLS- 101 TP. The transparent signals do not need this model. 103 2. Terminology and Notations 105 A simplified graphical representation of the data model is used in 106 this document. The meaning of the symbols in the YANG data tree 107 presented later in this document is defined in 108 [I-D.ietf-netmod-yang-tree-diagrams]. They are provided below for 109 reference. 111 o Brackets "[" and "]" enclose list keys. 113 o Abbreviations before data node names: "rw" means configuration 114 (read-write) and "ro" state data (read-only). 116 o Symbols after data node names: "?" means an optional node, "!" 117 means a presence container, and "*" denotes a list and leaf-list. 119 o Parentheses enclose choice and case nodes, and case nodes are also 120 marked with a colon (":"). 122 o Ellipsis ("...") stands for contents of subtrees that are not 123 shown. 125 3. YANG Model for Client-layer Tunnel 127 3.1. YANG Tree for Ethernet Tunnel 128 module: ietf-eth-te-tunnel 129 augment /te:te/te:tunnels/te:tunnel: 130 +--rw src-eth-tunnel-endpoint 131 | +--rw vlanid? etht-types:vlanid 132 | +--rw tag-type? etht-types:eth-tag-type 133 +--rw dst-eth-tunnel-endpoint 134 | +--rw vlanid? etht-types:vlanid 135 | +--rw tag-type? etht-types:eth-tag-type 136 +--rw bandwidth-profile 137 +--rw bandwidth-profile-name? string 138 +--rw bandwidth-profile-type? etht-types:bandwidth-profile-type 139 +--rw CIR? uint64 140 +--rw CBS? uint64 141 +--rw EIR? uint64 142 +--rw EBS? uint64 143 +--rw color-aware? boolean 144 +--rw coupling-flag? boolean 146 3.2. YANG Tree for Tunnel of other Client Signal Model 148 This section will be completed later. 150 4. YANG Code for Client-layer Tunnel 152 4.1. The ETH Tunnel YANG Code 154 file "ietf-eth-te-tunnel@2018-03-01.yang" 156 module ietf-eth-te-tunnel { 158 namespace "urn:ietf:params:xml:ns:yang:ietf-eth-te-tunnel"; 160 prefix "eth-tunnel"; 162 import ietf-te { 163 prefix "te"; 164 } 166 import ietf-eth-tran-types { 167 prefix "etht-types"; 168 } 170 organization 171 "Internet Engineering Task Force (IETF) CCAMP WG"; 172 contact 173 " 174 WG List: 176 ID-draft editor: 177 Haomian Zheng (zhenghaomian@huawei.com); 178 Italo Busi (italo.busi@huawei.com); 179 Aihua Guo (aihuaguo@huawei.com); 180 Yunbin Xu (xuyunbin@ritt.cn); 181 Yang Zhao (zhaoyangyjy@chinamobile.com); 182 Xufeng Liu (Xufeng_Liu@jabil.com); 183 Giuseppe Fioccola (giuseppe.fioccola@telecomitalia.it); 184 "; 186 description 187 "This module defines a model for ETH transport tunnel"; 189 revision 2018-03-01 { 190 description 191 "Initial revision"; 192 reference 193 "draft-zheng-ccamp-client-tunnel-yang-02"; 194 } 196 grouping eth-tunnel-endpoint { 197 description "Parameters for ETH tunnel."; 199 leaf vlanid { 200 type etht-types:vlanid; 201 description 202 "VLAN tag id."; 203 } 205 leaf tag-type { 206 type etht-types:eth-tag-type; 207 description "VLAN tag type."; 208 } 209 } 211 augment "/te:te/te:tunnels/te:tunnel" { 212 description 213 "Augment with additional parameters required for ETH 214 service."; 216 container src-eth-tunnel-endpoint { 217 description 218 "Source ETH tunnel endpoint."; 220 uses eth-tunnel-endpoint; 221 } 223 container dst-eth-tunnel-endpoint { 224 description 225 "Destination ETH tunnel endpoint."; 227 uses eth-tunnel-endpoint; 228 } 230 container bandwidth-profile { 231 description 232 "ETH tunnel bandwidth profile specification."; 234 uses etht-types:etht-bandwidth-profiles; 235 } 236 } 237 } 239 241 4.2. Other Client-layer Tunnel YANG Code 243 TBD. 245 5. Considerations and Open Issue 247 Editor Notes: This section is used to note temporary discussion/ 248 conclusion that to be fixed in the future version, and will be 249 removed before publication. This is a part of L2 work, need to 250 discuss how to go with other L2 network models. The expectation is 251 to include all potential L2 TE part in this work. 253 6. IANA Considerations 255 TBD. 257 7. Manageability Considerations 259 TBD. 261 8. Security Considerations 263 The data following the model defined in this document is exchanged 264 via, for example, the interface between an orchestrator and a 265 transport network controller. The security concerns mentioned in 266 [I-D.ietf-teas-yang-te] also applies to this document. 268 The YANG module defined in this document can be accessed via the 269 RESTCONF protocol defined in [RFC8040], or maybe via the NETCONF 270 protocol [RFC6241]. 272 9. Acknowledgements 274 We would like to thank Igor Bryskin and Daniel King for their 275 comments and discussions. 277 10. Contributors 279 Yanlei Zheng 280 China Unicom 281 Email: zhengyl@dimpt.com 283 Zhe Liu 284 Huawei Technologies, 285 Email: liuzhe123@huawei.com 287 Zheyu Fan 288 Huawei Technologies, 289 Email: fanzheyu2@huawei.com 291 Sergio Belotti 292 Nokia, 293 Email: sergio.belotti@nokia.com 295 Yingxi Yao 296 Shanghai Bell, 297 yingxi.yao@nokia-sbell.com 299 11. References 301 11.1. Normative References 303 [I-D.ietf-ccamp-otn-topo-yang] 304 zhenghaomian@huawei.com, z., Fan, Z., Sharma, A., Liu, X., 305 Belotti, S., Xu, Y., Wang, L., and O. Dios, "A YANG Data 306 Model for Optical Transport Network Topology", draft-ietf- 307 ccamp-otn-topo-yang-02 (work in progress), October 2017. 309 [I-D.ietf-ccamp-otn-tunnel-model] 310 zhenghaomian@huawei.com, z., Fan, Z., Sharma, A., Rao, R., 311 Belotti, S., Lopezalvarez, V., Li, Y., and Y. Xu, "OTN 312 Tunnel YANG Model", draft-ietf-ccamp-otn-tunnel-model-01 313 (work in progress), October 2017. 315 [I-D.ietf-teas-yang-te] 316 Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., and 317 I. Bryskin, "A YANG Data Model for Traffic Engineering 318 Tunnels and Interfaces", draft-ietf-teas-yang-te-13 (work 319 in progress), March 2018. 321 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 322 and A. Bierman, Ed., "Network Configuration Protocol 323 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 324 . 326 [RFC7139] Zhang, F., Ed., Zhang, G., Belotti, S., Ceccarelli, D., 327 and K. Pithewan, "GMPLS Signaling Extensions for Control 328 of Evolving G.709 Optical Transport Networks", RFC 7139, 329 DOI 10.17487/RFC7139, March 2014, 330 . 332 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 333 RFC 7950, DOI 10.17487/RFC7950, August 2016, 334 . 336 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 337 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 338 . 340 11.2. Informative References 342 [I-D.ietf-netmod-yang-tree-diagrams] 343 Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft- 344 ietf-netmod-yang-tree-diagrams-06 (work in progress), 345 February 2018. 347 [I-D.lee-ccamp-wson-tunnel-model] 348 Lee, Y., Dhody, D., Lopezalvarez, V., King, D., Yoon, B., 349 and R. Vilata, "A Yang Data Model for WSON Tunnel", draft- 350 lee-ccamp-wson-tunnel-model-04 (work in progress), January 351 2018. 353 [I-D.zhang-teas-transport-service-model] 354 Zhang, X. and J. Ryoo, "A Service YANG Model for 355 Connection-oriented Transport Networks", draft-zhang-teas- 356 transport-service-model-01 (work in progress), October 357 2016. 359 [RFC7062] Zhang, F., Ed., Li, D., Li, H., Belotti, S., and D. 360 Ceccarelli, "Framework for GMPLS and PCE Control of G.709 361 Optical Transport Networks", RFC 7062, 362 DOI 10.17487/RFC7062, November 2013, 363 . 365 Authors' Addresses 367 Haomian Zheng 368 Huawei Technologies 369 F3 R&D Center, Huawei Industrial Base, Bantian, Longgang District 370 Shenzhen, Guangdong 518129 371 P.R.China 373 Email: zhenghaomian@huawei.com 375 Aihua Guo 376 Huawei Technologies 378 Email: aihuaguo@huawei.com 380 Italo Busi 381 Huawei Technologies 383 Email: Italo.Busi@huawei.com 385 Yunbin Xu 386 CAICT 388 Email: xuyunbin@ritt.cn 390 Yang Zhao 391 China Mobile 393 Email: zhaoyangyjy@chinamobile.com 394 Xufeng Liu 395 Jabil 397 Email: Xufeng_Liu@jabil.com 399 Giuseppe Fioccola 400 Telecom Italia 402 Email: giuseppe.fioccola@telecomitalia.it