idnits 2.17.1 draft-zheng-ccamp-client-tunnel-yang-04.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 (February 28, 2019) is 1884 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 (-36) exists of draft-ietf-teas-yang-te-19 == Outdated reference: A later version (-20) exists of draft-ietf-ccamp-otn-tunnel-model-06 == Outdated reference: A later version (-09) exists of draft-ietf-ccamp-wson-tunnel-model-02 Summary: 0 errors (**), 0 flaws (~~), 4 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 1, 2019 Huawei Technologies 6 Y. Xu 7 CAICT 8 Y. Zhao 9 China Mobile 10 X. Liu 11 Jabil 12 February 28, 2019 14 A YANG Data Model for Client-layer Tunnel 15 draft-zheng-ccamp-client-tunnel-yang-04 17 Abstract 19 A transport network is a server-layer network to provide connectivity 20 services to its client. In this draft the tunnel of client is 21 described, with the definition of client tunnel YANG model. 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). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at https://datatracker.ietf.org/drafts/current/. 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 This Internet-Draft will expire on September 1, 2019. 40 Copyright Notice 42 Copyright (c) 2019 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (https://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 58 2. Terminology and Notations . . . . . . . . . . . . . . . . . . 3 59 3. YANG Model for Client-layer Tunnel . . . . . . . . . . . . . 3 60 3.1. YANG Tree for Ethernet Tunnel . . . . . . . . . . . . . . 3 61 3.2. YANG Tree for Tunnel of other Client Signal Model . . . . 4 62 4. YANG Code for Client-layer Tunnel . . . . . . . . . . . . . . 4 63 4.1. The ETH Tunnel YANG Code . . . . . . . . . . . . . . . . 4 64 4.2. Other Client-layer Tunnel YANG Code . . . . . . . . . . . 6 65 5. Considerations and Open Issue . . . . . . . . . . . . . . . . 6 66 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 67 7. Manageability Considerations . . . . . . . . . . . . . . . . 6 68 8. Security Considerations . . . . . . . . . . . . . . . . . . . 6 69 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 70 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 7 71 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 72 11.1. Normative References . . . . . . . . . . . . . . . . . . 7 73 11.2. Informative References . . . . . . . . . . . . . . . . . 8 74 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 76 1. Introduction 78 A transport network is a server-layer network designed to provide 79 connectivity services for a client-layer network to carry the client 80 traffic transparently across the server-layer network resources. The 81 tunnel model in Traffic-Engineered network has been defined in both 82 generic way and technology-specific way. The generic model, which is 83 the base TE tunnel YANG model, can be found at 84 [I-D.ietf-teas-yang-te]. Technology-specific models, such as OTN/ 85 WSON tunnel model, have also been defined in 86 [I-D.ietf-ccamp-otn-tunnel-model] and 87 [I-D.ietf-ccamp-wson-tunnel-model] respectively. Corresponding 88 tunnel on client-layer is also required, to have a complete topology 89 view from the perspective of network controllers. 91 This document defines a data model of all client-layer tunnel, using 92 YANG language defined in [RFC7950]. The model is augmenting the 93 generic TE tunnel model, and can be used by applications exposing to 94 a network controller via a REST interface. Furthermore, it can be 95 used by an application to describe the client tunnel that constructed 96 above the server-layer network. It is also worth noting that the 97 client layer network will only need the tunnel model when there is a 98 demand for switching techniques, such as Carrier Ethernet and MPLS- 99 TP. The transparent signals do not need this model. 101 2. Terminology and Notations 103 A simplified graphical representation of the data model is used in 104 this document. The meaning of the symbols in the YANG data tree 105 presented later in this document is defined in [RFC8340]. They are 106 provided below for reference. 108 o Brackets "[" and "]" enclose list keys. 110 o Abbreviations before data node names: "rw" means configuration 111 (read-write) and "ro" state data (read-only). 113 o Symbols after data node names: "?" means an optional node, "!" 114 means a presence container, and "*" denotes a list and leaf-list. 116 o Parentheses enclose choice and case nodes, and case nodes are also 117 marked with a colon (":"). 119 o Ellipsis ("...") stands for contents of subtrees that are not 120 shown. 122 3. YANG Model for Client-layer Tunnel 124 3.1. YANG Tree for Ethernet Tunnel 125 module: ietf-eth-te-tunnel 126 augment /te:te/te:tunnels/te:tunnel: 127 +--rw src-eth-tunnel-endpoint 128 | +--rw vlanid? etht-types:vlanid 129 | +--rw tag-type? etht-types:eth-tag-type 130 +--rw dst-eth-tunnel-endpoint 131 | +--rw vlanid? etht-types:vlanid 132 | +--rw tag-type? etht-types:eth-tag-type 133 +--rw bandwidth-profile 134 +--rw bandwidth-profile-name? string 135 +--rw bandwidth-profile-type? etht-types:bandwidth-profile-type 136 +--rw CIR? uint64 137 +--rw CBS? uint64 138 +--rw EIR? uint64 139 +--rw EBS? uint64 140 +--rw color-aware? boolean 141 +--rw coupling-flag? boolean 143 3.2. YANG Tree for Tunnel of other Client Signal Model 145 This section will be completed later. 147 4. YANG Code for Client-layer Tunnel 149 4.1. The ETH Tunnel YANG Code 151 file "ietf-eth-te-tunnel@2018-03-01.yang" 153 module ietf-eth-te-tunnel { 155 namespace "urn:ietf:params:xml:ns:yang:ietf-eth-te-tunnel"; 157 prefix "eth-tunnel"; 159 import ietf-te { 160 prefix "te"; 161 } 163 import ietf-eth-tran-types { 164 prefix "etht-types"; 165 } 167 organization 168 "Internet Engineering Task Force (IETF) CCAMP WG"; 169 contact 170 " 171 WG List: 173 ID-draft editor: 174 Haomian Zheng (zhenghaomian@huawei.com); 175 Italo Busi (italo.busi@huawei.com); 176 Aihua Guo (aihuaguo@huawei.com); 177 Yunbin Xu (xuyunbin@ritt.cn); 178 Yang Zhao (zhaoyangyjy@chinamobile.com); 179 Xufeng Liu (Xufeng_Liu@jabil.com); 180 "; 182 description 183 "This module defines a model for ETH transport tunnel"; 185 revision 2018-03-01 { 186 description 187 "Initial revision"; 188 reference 189 "draft-zheng-ccamp-client-tunnel-yang"; 190 } 192 grouping eth-tunnel-endpoint { 193 description "Parameters for ETH tunnel."; 195 leaf vlanid { 196 type etht-types:vlanid; 197 description 198 "VLAN tag id."; 199 } 201 leaf tag-type { 202 type etht-types:eth-tag-type; 203 description "VLAN tag type."; 204 } 205 } 207 augment "/te:te/te:tunnels/te:tunnel" { 208 description 209 "Augment with additional parameters required for ETH 210 service."; 212 container src-eth-tunnel-endpoint { 213 description 214 "Source ETH tunnel endpoint."; 216 uses eth-tunnel-endpoint; 217 } 219 container dst-eth-tunnel-endpoint { 220 description 221 "Destination ETH tunnel endpoint."; 223 uses eth-tunnel-endpoint; 224 } 226 container bandwidth-profile { 227 description 228 "ETH tunnel bandwidth profile specification."; 230 uses etht-types:etht-bandwidth-profiles; 231 } 232 } 233 } 235 237 4.2. Other Client-layer Tunnel YANG Code 239 TBD. 241 5. Considerations and Open Issue 243 Editor Notes: This section is used to note temporary discussion/ 244 conclusion that to be fixed in the future version, and will be 245 removed before publication. This is a part of L2 work, need to 246 discuss how to go with other L2 network models. The expectation is 247 to include all potential L2 TE part in this work. 249 6. IANA Considerations 251 TBD. 253 7. Manageability Considerations 255 TBD. 257 8. Security Considerations 259 The data following the model defined in this document is exchanged 260 via, for example, the interface between an orchestrator and a 261 transport network controller. The security concerns mentioned in 262 [I-D.ietf-teas-yang-te] also applies to this document. 264 The YANG module defined in this document can be accessed via the 265 RESTCONF protocol defined in [RFC8040], or maybe via the NETCONF 266 protocol [RFC6241]. 268 9. Acknowledgements 270 We would like to thank Igor Bryskin and Daniel King for their 271 comments and discussions. 273 10. Contributors 275 Yanlei Zheng 276 China Unicom 277 Email: zhengyl@dimpt.com 279 Zhe Liu 280 Huawei Technologies, 281 Email: liuzhe123@huawei.com 283 Zheyu Fan 284 Huawei Technologies, 285 Email: fanzheyu2@huawei.com 287 Sergio Belotti 288 Nokia, 289 Email: sergio.belotti@nokia.com 291 Yingxi Yao 292 Shanghai Bell, 293 yingxi.yao@nokia-sbell.com 295 Giuseppe Fioccola 296 Huawei Technologies 297 giuseppe.fioccola@huawei.com 299 11. References 301 11.1. Normative References 303 [I-D.ietf-teas-yang-te] 304 Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, 305 "A YANG Data Model for Traffic Engineering Tunnels and 306 Interfaces", draft-ietf-teas-yang-te-19 (work in 307 progress), February 2019. 309 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 310 and A. Bierman, Ed., "Network Configuration Protocol 311 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 312 . 314 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 315 RFC 7950, DOI 10.17487/RFC7950, August 2016, 316 . 318 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 319 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 320 . 322 11.2. Informative References 324 [I-D.ietf-ccamp-otn-tunnel-model] 325 Zheng, H., Guo, A., Busi, I., Sharma, A., Rao, R., 326 Belotti, S., Lopezalvarez, V., Li, Y., and Y. Xu, "OTN 327 Tunnel YANG Model", draft-ietf-ccamp-otn-tunnel-model-06 328 (work in progress), February 2019. 330 [I-D.ietf-ccamp-wson-tunnel-model] 331 Lee, Y., Dhody, D., Guo, A., Lopezalvarez, V., King, D., 332 Yoon, B., and R. Vilata, "A Yang Data Model for WSON 333 Tunnel", draft-ietf-ccamp-wson-tunnel-model-02 (work in 334 progress), October 2018. 336 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 337 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 338 . 340 Authors' Addresses 342 Haomian Zheng 343 Huawei Technologies 344 H1-1-A043S Huawei Industrial Base, Songshanhu 345 Dongguan, Guangdong 523808 346 China 348 Email: zhenghaomian@huawei.com 350 Aihua Guo 351 Huawei Technologies 353 Email: aihuaguo@huawei.com 354 Italo Busi 355 Huawei Technologies 357 Email: Italo.Busi@huawei.com 359 Yunbin Xu 360 CAICT 362 Email: xuyunbin@ritt.cn 364 Yang Zhao 365 China Mobile 367 Email: zhaoyangyjy@chinamobile.com 369 Xufeng Liu 370 Jabil 372 Email: Xufeng_Liu@jabil.com