idnits 2.17.1 draft-zheng-ccamp-client-tunnel-yang-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 : ---------------------------------------------------------------------------- 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 (October 19, 2017) is 2378 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 332, but no explicit reference was found in the text == Unused Reference: 'RFC7139' is defined on line 355, but no explicit reference was found in the text == Unused Reference: 'I-D.zhang-teas-transport-service-model' is defined on line 382, but no explicit reference was found in the text == Unused Reference: 'RFC7062' is defined on line 388, but no explicit reference was found in the text == Outdated reference: A later version (-18) exists of draft-ietf-ccamp-otn-topo-yang-01 == Outdated reference: A later version (-20) exists of draft-ietf-ccamp-otn-tunnel-model-00 == Outdated reference: A later version (-36) exists of draft-ietf-teas-yang-te-08 == Outdated reference: A later version (-06) exists of draft-ietf-netmod-yang-tree-diagrams-01 == Outdated reference: A later version (-04) exists of draft-lee-ccamp-wson-tunnel-model-01 Summary: 0 errors (**), 0 flaws (~~), 10 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: April 22, 2018 Huawei Technologies 6 Y. Xu 7 CAICT 8 Y. Zhao 9 China Mobile 10 October 19, 2017 12 A YANG Data Model for Client-layer Tunnel 13 draft-zheng-ccamp-client-tunnel-yang-00 15 Abstract 17 A transport network is a server-layer network to provide connectivity 18 services to its client. In this draft the tunnel of client is 19 described, with the definition of client tunnel YANG model. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at https://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on April 22, 2018. 38 Copyright Notice 40 Copyright (c) 2017 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (https://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 56 2. Terminology and Notations . . . . . . . . . . . . . . . . . . 3 57 3. YANG Model for Client-layer Tunnel . . . . . . . . . . . . . 3 58 3.1. YANG Tree for Ethernet Tunnel . . . . . . . . . . . . . . 3 59 3.2. YANG Tree for Tunnel of other Client Signal Model . . . . 4 60 4. YANG Code for Client-layer Tunnel . . . . . . . . . . . . . . 4 61 4.1. The ETH Tunnel YANG Code . . . . . . . . . . . . . . . . 4 62 4.2. Other Client-layer Tunnel YANG Code . . . . . . . . . . . 7 63 5. Considerations and Open Issue . . . . . . . . . . . . . . . . 7 64 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 65 7. Manageability Considerations . . . . . . . . . . . . . . . . 7 66 8. Security Considerations . . . . . . . . . . . . . . . . . . . 7 67 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 68 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 8 69 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 70 11.1. Normative References . . . . . . . . . . . . . . . . . . 8 71 11.2. Informative References . . . . . . . . . . . . . . . . . 9 72 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 74 1. Introduction 76 A transport network is a server-layer network designed to provide 77 connectivity services for a client-layer network to carry the client 78 traffic transparently across the server-layer network resources. The 79 tunnel model in Traffic-Engineered network has been defined in both 80 generic way and technology-specific way. The generic model, which is 81 the base TE tunnel YANG model, can be found at 82 [I-D.ietf-teas-yang-te]. Technology-specific models, such as OTN/ 83 WSON tunnel model, have also been defined in 84 [I-D.ietf-ccamp-otn-tunnel-model] and 85 [I-D.lee-ccamp-wson-tunnel-model] respectively. Corresponding tunnel 86 on client-layer is also required, to have a complete topology view 87 from the perspective of network controllers. 89 This document defines a data model of all client-layer tunnel, using 90 YANG language defined in [RFC7950]. The model is augmenting the 91 generic TE tunnel model, and can be used by applications exposing to 92 a network controller via a REST interface. Furthermore, it can be 93 used by an application to describe the client tunnel that constructed 94 above the server-layer network. 96 2. Terminology and Notations 98 A simplified graphical representation of the data model is used in 99 this document. The meaning of the symbols in the YANG data tree 100 presented later in this document is defined in 101 [I-D.ietf-netmod-yang-tree-diagrams]. They are provided below for 102 reference. 104 o Brackets "[" and "]" enclose list keys. 106 o Abbreviations before data node names: "rw" means configuration 107 (read-write) and "ro" state data (read-only). 109 o Symbols after data node names: "?" means an optional node, "!" 110 means a presence container, and "*" denotes a list and leaf-list. 112 o Parentheses enclose choice and case nodes, and case nodes are also 113 marked with a colon (":"). 115 o Ellipsis ("...") stands for contents of subtrees that are not 116 shown. 118 3. YANG Model for Client-layer Tunnel 120 3.1. YANG Tree for Ethernet Tunnel 121 module: ietf-eth-te-tunnel 122 augment /te:te/te:tunnels/te:tunnel/te:config: 123 +--rw src-eth-tunnel-endpoint 124 | +--rw vlanid? etht-types:vlanid 125 | +--rw tag-type? etht-types:eth-tag-type 126 +--rw dst-eth-tunnel-endpoint 127 | +--rw vlanid? etht-types:vlanid 128 | +--rw tag-type? etht-types:eth-tag-type 129 +--rw bandwidth-profile 130 +--rw bandwidth-profile-name? string 131 +--rw bandwidth-profile-type? etht-types:bandwidth-profile-type 132 +--rw CIR? uint64 133 +--rw CBS? uint64 134 +--rw EIR? uint64 135 +--rw EBS? uint64 136 +--rw color-aware? boolean 137 +--rw coupling-flag? boolean 138 augment /te:te/te:tunnels/te:tunnel/te:state: 139 +--ro src-eth-tunnel-endpoint 140 | +--ro vlanid? etht-types:vlanid 141 | +--ro tag-type? etht-types:eth-tag-type 142 +--ro dst-eth-tunnel-endpoint 143 | +--ro vlanid? etht-types:vlanid 144 | +--ro tag-type? etht-types:eth-tag-type 145 +--ro bandwidth-profile 146 +--ro bandwidth-profile-name? string 147 +--ro bandwidth-profile-type? etht-types:bandwidth-profile-type 148 +--ro CIR? uint64 149 +--ro CBS? uint64 150 +--ro EIR? uint64 151 +--ro EBS? uint64 152 +--ro color-aware? boolean 153 +--ro coupling-flag? boolean 155 3.2. YANG Tree for Tunnel of other Client Signal Model 157 This section will be completed later. 159 4. YANG Code for Client-layer Tunnel 161 4.1. The ETH Tunnel YANG Code 163 file "ietf-eth-te-tunnel@2017-09-04.yang" 164 module ietf-eth-te-tunnel { 165 //TODO: FIXME 166 yang-version 1.1; 168 namespace "urn:ietf:params:xml:ns:yang:ietf-eth-tunnel"; 169 prefix "eth-tunnel"; 171 import ietf-te { prefix "te"; } 172 import ietf-eth-tran-types { prefix "etht-types"; } 174 organization 175 "IETF CCAMP Working Group"; 177 contact 178 "WG Web: 179 WG List: 181 ID-draft editor: 182 Haomian Zheng (zhenghaomian@huawei.com); 183 Italo Busi (italo.busi@huawei.com); 184 Aihua Guo (aihuaguo@huawei.com); 185 Yunbin Xu (xuyunbin@ritt.cn); 186 Yang Zhao (zhaoyangyjy@chinamobile.com); 187 "; 189 description 190 "This module defines a model for ETH transport tunnel"; 192 revision "2017-09-04" { 193 description 194 "Revision 0.1"; 195 reference "TBD"; 196 } 198 grouping eth-tunnel-endpoint { 199 description "Parameters for ETH tunnel."; 201 leaf vlanid { 202 type etht-types:vlanid; 203 description 204 "VLAN tag id."; 205 } 207 leaf tag-type { 208 type etht-types:eth-tag-type; 209 description "VLAN tag type."; 210 } 211 } 212 augment "/te:te/te:tunnels/te:tunnel/te:config" { 213 description 214 "Augment with additional parameters required for ETH 215 service."; 217 container src-eth-tunnel-endpoint { 218 description 219 "Source ETH tunnel endpoint."; 221 uses eth-tunnel-endpoint; 222 } 224 container dst-eth-tunnel-endpoint { 225 description 226 "Destination ETH tunnel endpoint."; 228 uses eth-tunnel-endpoint; 229 } 231 container bandwidth-profile { 232 description 233 "ETH tunnel bandwidth profile specification."; 235 uses etht-types:etht-bandwidth-profiles; 236 } 237 } 239 augment "/te:te/te:tunnels/te:tunnel/te:state" { 240 description 241 "Augment with additional parameters required for ETH 242 service."; 244 container src-eth-tunnel-endpoint { 245 description 246 "Source ETH tunnel endpoint."; 248 uses eth-tunnel-endpoint; 249 } 251 container dst-eth-tunnel-endpoint { 252 description 253 "Destination ETH tunnel endpoint."; 255 uses eth-tunnel-endpoint; 256 } 258 container bandwidth-profile { 259 description 260 "ETH tunnel bandwidth profile specification."; 262 uses etht-types:etht-bandwidth-profiles; 263 } 264 } 266 } 268 270 4.2. Other Client-layer Tunnel YANG Code 272 TBD. 274 5. Considerations and Open Issue 276 Editor Notes: This section is used to note temporary discussion/ 277 conclusion that to be fixed in the future version, and will be 278 removed before publication. This is a part of L2 work, need to 279 discuss how to go with other L2 network models. The expectation is 280 to include all potential L2 TE part in this work. 282 6. IANA Considerations 284 TBD. 286 7. Manageability Considerations 288 TBD. 290 8. Security Considerations 292 The data following the model defined in this document is exchanged 293 via, for example, the interface between an orchestrator and a 294 transport network controller. The security concerns mentioned in 295 [I-D.ietf-teas-yang-te] also applies to this document. 297 The YANG module defined in this document can be accessed via the 298 RESTCONF protocol defined in [RFC8040], or maybe via the NETCONF 299 protocol [RFC6241]. 301 9. Acknowledgements 303 We would like to thank Igor Bryskin and Daniel King for their 304 comments and discussions. 306 10. Contributors 308 Yanlei Zheng 309 China Unicom 310 Email: zhengyl@dimpt.com 312 Zhe Liu 313 Huawei Technologies, 314 Email: liuzhe123@huawei.com 316 Zheyu Fan 317 Huawei Technologies, 318 Email: fanzheyu@huawei.com 320 Sergio Belotti 321 Nokia, 322 Email: sergio.belotti@nokia.com 324 Yingxi Yao 325 Shanghai Bell, 326 yingxi.yao@nokia-sbell.com 328 11. References 330 11.1. Normative References 332 [I-D.ietf-ccamp-otn-topo-yang] 333 zhenghaomian@huawei.com, z., Fan, Z., Sharma, A., Liu, X., 334 Belotti, S., Xu, Y., Wang, L., and O. Dios, "A YANG Data 335 Model for Optical Transport Network Topology", draft-ietf- 336 ccamp-otn-topo-yang-01 (work in progress), September 2017. 338 [I-D.ietf-ccamp-otn-tunnel-model] 339 zhenghaomian@huawei.com, z., Fan, Z., Sharma, A., Rao, R., 340 Belotti, S., Lopezalvarez, V., and Y. Li, "OTN Tunnel YANG 341 Model", draft-ietf-ccamp-otn-tunnel-model-00 (work in 342 progress), July 2017. 344 [I-D.ietf-teas-yang-te] 345 Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., and 346 I. Bryskin, "A YANG Data Model for Traffic Engineering 347 Tunnels and Interfaces", draft-ietf-teas-yang-te-08 (work 348 in progress), July 2017. 350 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 351 and A. Bierman, Ed., "Network Configuration Protocol 352 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 353 . 355 [RFC7139] Zhang, F., Ed., Zhang, G., Belotti, S., Ceccarelli, D., 356 and K. Pithewan, "GMPLS Signaling Extensions for Control 357 of Evolving G.709 Optical Transport Networks", RFC 7139, 358 DOI 10.17487/RFC7139, March 2014, 359 . 361 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 362 RFC 7950, DOI 10.17487/RFC7950, August 2016, 363 . 365 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 366 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 367 . 369 11.2. Informative References 371 [I-D.ietf-netmod-yang-tree-diagrams] 372 Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft- 373 ietf-netmod-yang-tree-diagrams-01 (work in progress), June 374 2017. 376 [I-D.lee-ccamp-wson-tunnel-model] 377 Lee, Y., Dhody, D., Lopezalvarez, V., King, D., Yoon, B., 378 and R. Vilata, "A Yang Data Model for WSON Tunnel", draft- 379 lee-ccamp-wson-tunnel-model-01 (work in progress), June 380 2017. 382 [I-D.zhang-teas-transport-service-model] 383 Zhang, X. and J. Ryoo, "A Service YANG Model for 384 Connection-oriented Transport Networks", draft-zhang-teas- 385 transport-service-model-01 (work in progress), October 386 2016. 388 [RFC7062] Zhang, F., Ed., Li, D., Li, H., Belotti, S., and D. 389 Ceccarelli, "Framework for GMPLS and PCE Control of G.709 390 Optical Transport Networks", RFC 7062, 391 DOI 10.17487/RFC7062, November 2013, 392 . 394 Authors' Addresses 396 Haomian Zheng 397 Huawei Technologies 398 F3 R&D Center, Huawei Industrial Base, Bantian, Longgang District 399 Shenzhen, Guangdong 518129 400 P.R.China 402 Email: zhenghaomian@huawei.com 403 Aihua Guo 404 Huawei Technologies 406 Email: aihuaguo@huawei.com 408 Italo Busi 409 Huawei Technologies 411 Email: Italo.Busi@huawei.com 413 Yunbin Xu 414 CAICT 416 Email: xuyunbin@ritt.cn 418 Yang Zhao 419 China Mobile 421 Email: zhaoyangyjy@chinamobile.com