idnits 2.17.1 draft-zheng-ccamp-client-tunnel-yang-10.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 (7 March 2022) is 774 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-29 == Outdated reference: A later version (-20) exists of draft-ietf-ccamp-otn-tunnel-model-14 == Outdated reference: A later version (-09) exists of draft-ietf-ccamp-wson-tunnel-model-06 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 Huawei Technologies 4 Intended status: Standards Track A. Guo 5 Expires: 8 September 2022 Futurewei 6 I. Busi 7 Huawei Technologies 8 Y. Xu 9 CAICT 10 Y. Zhao 11 China Mobile 12 X. Liu 13 Volta Networks 14 7 March 2022 16 A YANG Data Model for Client-layer Tunnel 17 draft-zheng-ccamp-client-tunnel-yang-10 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 8 September 2022. 42 Copyright Notice 44 Copyright (c) 2022 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 (https://trustee.ietf.org/ 49 license-info) in effect on the date of publication of this document. 50 Please review these documents carefully, as they describe your rights 51 and restrictions with respect to this document. Code Components 52 extracted from this document must include Revised BSD License text as 53 described in Section 4.e of the Trust Legal Provisions and are 54 provided without warranty as described in the Revised BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 59 2. Terminology and Notations . . . . . . . . . . . . . . . . . . 3 60 3. YANG Model for Client-layer Tunnel . . . . . . . . . . . . . 3 61 3.1. YANG Tree for Ethernet Tunnel . . . . . . . . . . . . . . 3 62 3.2. YANG Tree for Tunnel of other Client Signal Model . . . . 4 63 4. YANG Code for Client-layer Tunnel . . . . . . . . . . . . . . 4 64 4.1. The ETH Tunnel YANG Code . . . . . . . . . . . . . . . . 4 65 4.2. Other Client-layer Tunnel YANG Code . . . . . . . . . . . 6 66 5. Considerations and Open Issue . . . . . . . . . . . . . . . . 6 67 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 68 7. Manageability Considerations . . . . . . . . . . . . . . . . 6 69 8. Security Considerations . . . . . . . . . . . . . . . . . . . 6 70 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 71 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 7 72 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 73 11.1. Normative References . . . . . . . . . . . . . . . . . . 7 74 11.2. Informative References . . . . . . . . . . . . . . . . . 7 75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 77 1. Introduction 79 A transport network is a server-layer network designed to provide 80 connectivity services for a client-layer network to carry the client 81 traffic transparently across the server-layer network resources. The 82 tunnel model in Traffic-Engineered network has been defined in both 83 generic way and technology-specific way. The generic model, which is 84 the base TE tunnel YANG model, can be found at 85 [I-D.ietf-teas-yang-te]. Technology-specific models, such as OTN/ 86 WSON tunnel model, have also been defined in 87 [I-D.ietf-ccamp-otn-tunnel-model] and 88 [I-D.ietf-ccamp-wson-tunnel-model] respectively. Corresponding 89 tunnel on client-layer is also required, to have a complete topology 90 view from the perspective of network controllers. 92 This document defines a data model of all client-layer tunnel, using 93 YANG language defined in [RFC7950]. The model is augmenting the 94 generic TE tunnel model, and can be used by applications exposing to 95 a network controller via a REST interface. Furthermore, it can be 96 used by an application to describe the client tunnel that constructed 97 above the server-layer network. It is also worth noting that the 98 client layer network will only need the tunnel model when there is a 99 demand for switching techniques, such as Carrier Ethernet and MPLS- 100 TP. The transparent signals do not need this model. 102 2. Terminology and Notations 104 A simplified graphical representation of the data model is used in 105 this document. The meaning of the symbols in the YANG data tree 106 presented later in this document is defined in [RFC8340]. They are 107 provided below for reference. 109 * Brackets "[" and "]" enclose list keys. 111 * Abbreviations before data node names: "rw" means configuration 112 (read-write) and "ro" state data (read-only). 114 * Symbols after data node names: "?" means an optional node, "!" 115 means a presence container, and "*" denotes a list and leaf-list. 117 * Parentheses enclose choice and case nodes, and case nodes are also 118 marked with a colon (":"). 120 * Ellipsis ("...") stands for contents of subtrees that are not 121 shown. 123 3. YANG Model for Client-layer Tunnel 125 3.1. YANG Tree for Ethernet Tunnel 126 module: ietf-eth-te-tunnel 127 augment /te:te/te:tunnels/te:tunnel: 128 +--rw src-eth-tunnel-endpoint 129 | +--rw vlanid? etht-types:vlanid 130 | +--rw tag-type? etht-types:eth-tag-type 131 +--rw dst-eth-tunnel-endpoint 132 | +--rw vlanid? etht-types:vlanid 133 | +--rw tag-type? etht-types:eth-tag-type 134 +--rw bandwidth-profile 135 +--rw bandwidth-profile-name? string 136 +--rw bandwidth-profile-type? etht-types:bandwidth-profile-type 137 +--rw CIR? uint64 138 +--rw CBS? uint64 139 +--rw EIR? uint64 140 +--rw EBS? uint64 141 +--rw color-aware? boolean 142 +--rw coupling-flag? boolean 144 3.2. YANG Tree for Tunnel of other Client Signal Model 146 This section will be completed later. 148 4. YANG Code for Client-layer Tunnel 150 4.1. The ETH Tunnel YANG Code 152 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.ietf@gmail.com); 177 Yunbin Xu (xuyunbin@caict.ac.cn); 178 Yang Zhao (zhaoyangyjy@chinamobile.com); 179 Xufeng Liu (xufeng.liu.ietf@gmail.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 } 218 container dst-eth-tunnel-endpoint { 219 description 220 "Destination ETH tunnel endpoint."; 222 uses eth-tunnel-endpoint; 223 } 225 container bandwidth-profile { 226 description 227 "ETH tunnel bandwidth profile specification."; 229 uses etht-types:etht-bandwidth-profiles; 230 } 231 } 232 } 233 235 4.2. Other Client-layer Tunnel YANG Code 237 TBD. 239 5. Considerations and Open Issue 241 Editor Notes: This section is used to note temporary discussion/ 242 conclusion that to be fixed in the future version, and will be 243 removed before publication. This is a part of L2 work, need to 244 discuss how to go with other L2 network models. The expectation is 245 to include all potential L2 TE part in this work. 247 6. IANA Considerations 249 TBD. 251 7. Manageability Considerations 253 TBD. 255 8. Security Considerations 257 The data following the model defined in this document is exchanged 258 via, for example, the interface between an orchestrator and a 259 transport network controller. The security concerns mentioned in 260 [I-D.ietf-teas-yang-te] also applies to this document. 262 The YANG module defined in this document can be accessed via the 263 RESTCONF protocol defined in [RFC8040], or maybe via the NETCONF 264 protocol [RFC6241]. 266 9. Acknowledgements 268 We would like to thank Igor Bryskin and Daniel King for their 269 comments and discussions. 271 10. Contributors 273 Yanlei Zheng China Unicom Email: zhengyl@dimpt.com 275 Zhe Liu Huawei Technologies, Email: liuzhe123@huawei.com 277 Sergio Belotti Nokia, Email: sergio.belotti@nokia.com 279 Yingxi Yao Shanghai Bell, yingxi.yao@nokia-sbell.com 281 Giuseppe Fioccola Huawei Technologies giuseppe.fioccola@huawei.com 283 11. References 285 11.1. Normative References 287 [I-D.ietf-teas-yang-te] 288 Saad, T., Gandhi, R., Liu, X., Beeram, V. P., Bryskin, I., 289 and O. G. D. Dios, "A YANG Data Model for Traffic 290 Engineering Tunnels, Label Switched Paths and Interfaces", 291 Work in Progress, Internet-Draft, draft-ietf-teas-yang-te- 292 29, 7 February 2022, . 295 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 296 and A. Bierman, Ed., "Network Configuration Protocol 297 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 298 . 300 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 301 RFC 7950, DOI 10.17487/RFC7950, August 2016, 302 . 304 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 305 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 306 . 308 11.2. Informative References 310 [I-D.ietf-ccamp-otn-tunnel-model] 311 Zheng, H., Busi, I., Belotti, S., Lopez, V., and Y. Xu, 312 "OTN Tunnel YANG Model", Work in Progress, Internet-Draft, 313 draft-ietf-ccamp-otn-tunnel-model-14, 12 July 2021, 314 . 317 [I-D.ietf-ccamp-wson-tunnel-model] 318 Lee, Y., Zheng, H., Guo, A., Lopez, V., King, D., Yoon, B. 319 Y., and R. Vilalta, "A Yang Data Model for WSON Tunnel", 320 Work in Progress, Internet-Draft, draft-ietf-ccamp-wson- 321 tunnel-model-06, 22 October 2021, 322 . 325 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 326 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 327 . 329 Authors' Addresses 331 Haomian Zheng 332 Huawei Technologies 333 H1, XiliuBeipo Village, Songshan Lake 334 Dongguan 335 Guangdong, 523808 336 China 337 Email: zhenghaomian@huawei.com 339 Aihua Guo 340 Futurewei 341 Email: aihuaguo.ietf@gmail.com 343 Italo Busi 344 Huawei Technologies 345 Email: Italo.Busi@huawei.com 347 Yunbin Xu 348 CAICT 349 Email: xuyunbin@caict.ca.cn 351 Yang Zhao 352 China Mobile 353 Email: zhaoyangyjy@chinamobile.com 354 Xufeng Liu 355 Volta Networks 356 Email: xufeng.liu.ietf@gmail.com