--- 1/draft-ietf-teas-te-service-mapping-yang-08.txt 2021-10-24 06:13:13.282995378 -0700 +++ 2/draft-ietf-teas-te-service-mapping-yang-09.txt 2021-10-24 06:13:13.374997687 -0700 @@ -1,25 +1,25 @@ TEAS Working Group Y. Lee, Ed. Internet-Draft Samsung Electronics Intended status: Standards Track D. Dhody, Ed. -Expires: 1 March 2022 G. Fioccola +Expires: 27 April 2022 G. Fioccola Q. Wu, Ed. Huawei Technologies D. Ceccarelli Ericsson J. Tantsura Microsoft - 28 August 2021 + 24 October 2021 - Traffic Engineering (TE) and Service Mapping Yang Model - draft-ietf-teas-te-service-mapping-yang-08 + Traffic Engineering (TE) and Service Mapping YANG Model + draft-ietf-teas-te-service-mapping-yang-09 Abstract This document provides a YANG data model to map customer service models (e.g., the L3VPN Service Model (L3SM)) to Traffic Engineering (TE) models (e.g., the TE Tunnel or the Virtual Network (VN) model). These models are referred to as TE Service Mapping Model and are applicable generically to the operator's need for seamless control and management of their VPN services with underlying TE support. @@ -35,21 +35,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on 1 March 2022. + This Internet-Draft will expire on 27 April 2022. Copyright Notice Copyright (c) 2021 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights @@ -66,52 +66,51 @@ 1.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 6 1.4. Tree diagram . . . . . . . . . . . . . . . . . . . . . . 6 1.5. Prefixes in Data Node Names . . . . . . . . . . . . . . . 6 2. TE and Service Related Parameters . . . . . . . . . . . . . . 8 2.1. VN/Tunnel Selection Requirements . . . . . . . . . . . . 8 2.2. TE Policy . . . . . . . . . . . . . . . . . . . . . . . . 9 2.2.1. Availability Requirement . . . . . . . . . . . . . . 9 3. YANG Modeling Approach . . . . . . . . . . . . . . . . . . . 9 3.1. Forward Compatibility . . . . . . . . . . . . . . . . . . 11 3.2. TE and Network Models . . . . . . . . . . . . . . . . . . 11 - 4. L3VPN Architecture in the ACTN Context . . . . . . . . . . . 11 - 4.1. Service Mapping . . . . . . . . . . . . . . . . . . . . . 15 - 4.2. Site Mapping . . . . . . . . . . . . . . . . . . . . . . 15 - 5. Applicability of TE-Service Mapping in Generic context . . . 16 - 6. YANG Data Trees . . . . . . . . . . . . . . . . . . . . . . . 16 - 6.1. Service Mapping Types . . . . . . . . . . . . . . . . . . 16 - 6.2. Service Models . . . . . . . . . . . . . . . . . . . . . 17 - 6.2.1. L3SM . . . . . . . . . . . . . . . . . . . . . . . . 17 - 6.2.2. L2SM . . . . . . . . . . . . . . . . . . . . . . . . 18 - 6.2.3. L1CSM . . . . . . . . . . . . . . . . . . . . . . . . 19 - 6.3. Network Models . . . . . . . . . . . . . . . . . . . . . 20 - 6.3.1. L3NM . . . . . . . . . . . . . . . . . . . . . . . . 20 - 6.3.2. L2NM . . . . . . . . . . . . . . . . . . . . . . . . 21 - 7. YANG Data Models . . . . . . . . . . . . . . . . . . . . . . 22 - 7.1. ietf-te-service-mapping-types . . . . . . . . . . . . . . 22 - 7.2. Service Models . . . . . . . . . . . . . . . . . . . . . 31 - 7.2.1. ietf-l3sm-te-service-mapping . . . . . . . . . . . . 32 - 7.2.2. ietf-l2sm-te-service-mapping . . . . . . . . . . . . 34 - 7.2.3. ietf-l1csm-te-service-mapping . . . . . . . . . . . . 36 + 4. L3VPN Architecture in the ACTN Context . . . . . . . . . . . 12 + 4.1. Service Mapping . . . . . . . . . . . . . . . . . . . . . 16 + 4.2. Site Mapping . . . . . . . . . . . . . . . . . . . . . . 16 + 5. Applicability of TE-Service Mapping in Generic context . . . 17 + 6. YANG Data Trees . . . . . . . . . . . . . . . . . . . . . . . 17 + 6.1. Service Mapping Types . . . . . . . . . . . . . . . . . . 17 + 6.2. Service Models . . . . . . . . . . . . . . . . . . . . . 18 + 6.2.1. L3SM . . . . . . . . . . . . . . . . . . . . . . . . 18 + 6.2.2. L2SM . . . . . . . . . . . . . . . . . . . . . . . . 19 + 6.2.3. L1CSM . . . . . . . . . . . . . . . . . . . . . . . . 20 + 6.3. Network Models . . . . . . . . . . . . . . . . . . . . . 21 + 6.3.1. L3NM . . . . . . . . . . . . . . . . . . . . . . . . 21 + 6.3.2. L2NM . . . . . . . . . . . . . . . . . . . . . . . . 22 + 7. YANG Data Models . . . . . . . . . . . . . . . . . . . . . . 23 + 7.1. ietf-te-service-mapping-types . . . . . . . . . . . . . . 23 + 7.2. Service Models . . . . . . . . . . . . . . . . . . . . . 32 + 7.2.1. ietf-l3sm-te-service-mapping . . . . . . . . . . . . 33 + 7.2.2. ietf-l2sm-te-service-mapping . . . . . . . . . . . . 35 + 7.2.3. ietf-l1csm-te-service-mapping . . . . . . . . . . . . 37 - 7.3. Network Models . . . . . . . . . . . . . . . . . . . . . 38 - 7.3.1. ietf-l3nm-te-service-mapping . . . . . . . . . . . . 38 - 7.3.2. ietf-l2nm-te-service-mapping . . . . . . . . . . . . 40 - 8. Security Considerations . . . . . . . . . . . . . . . . . . . 42 - 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 43 - 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 45 - 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 45 - 11.1. Normative References . . . . . . . . . . . . . . . . . . 45 - 11.2. Informative References . . . . . . . . . . . . . . . . . 48 - Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 49 - Appendix B. Discussion . . . . . . . . . . . . . . . . . . . . . 51 - Appendix C. Contributor Addresses . . . . . . . . . . . . . . . 51 + 7.3. Network Models . . . . . . . . . . . . . . . . . . . . . 39 + 7.3.1. ietf-l3nm-te-service-mapping . . . . . . . . . . . . 39 + 7.3.2. ietf-l2nm-te-service-mapping . . . . . . . . . . . . 41 + 8. Security Considerations . . . . . . . . . . . . . . . . . . . 43 + 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 44 + 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 46 + 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 46 + 11.1. Normative References . . . . . . . . . . . . . . . . . . 46 + 11.2. Informative References . . . . . . . . . . . . . . . . . 49 + Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 50 + Appendix B. Contributor Addresses . . . . . . . . . . . . . . . 52 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 52 1. Introduction Data models are a representation of objects that can be configured or monitored within a system. Within the IETF, YANG [RFC7950] is the language of choice for documenting data models, and YANG models have been produced to allow configuration or modeling of a variety of network devices, protocol instances, and network services. YANG data models have been classified in [RFC8199] and [RFC8309]. @@ -447,20 +446,31 @@ The YANG module defined in this document supports three existing service models via augmenting while sharing the common TE and Service Mapping Types. It is possible that new service models will be defined at some future time and that it will be desirable to map them to underlying TE constructs in the same way as the three existing models are augmented. + Scheduling is currently out of scope, although an operator could use + their own scheduling mechanism on top of this YANG model. In future + augmentations to this model might also be designed to integrate + scheduling and calendering. + + Note that the mechanism to map traffic (for example the enterprise + customer can tell, the traffic from source X on port Y should go on a + path with delay less than Z) can be via local configuration or + through a YANG model developed in the future (See one such attempt at + [I-D.dhody-teas-te-traffic-yang]). + 3.2. TE and Network Models The L2/L3 network models (L2NM, L3NM) are intended to describe a VPN Service in the Service Provider Network. It contains information of the Service Provider network and might include allocated resources. It can be used by network controllers to manage and control the VPN Service configuration in the Service Provider network. Similar to service model, the existing network models (i.e., [I-D.ietf-opsawg-l3sm-l3nm], and [I-D.ietf-opsawg-l2nm]) are @@ -984,21 +994,21 @@ +--:(vn) | +--rw vn-ap* -> /vn:access-point/ap/vn-ap/vn-ap-id +--:(te) +--rw ltp? te-types:te-tp-id 7. YANG Data Models The YANG codes are as follows: 7.1. ietf-te-service-mapping-types - file "ietf-te-service-mapping-types@2021-08-28.yang" + file "ietf-te-service-mapping-types@2021-10-24.yang" module ietf-te-service-mapping-types { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-te-service-mapping-types"; prefix tsmt; /* Import te-types */ import ietf-te-types { prefix te-types; @@ -1071,21 +1081,21 @@ Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; - revision 2021-08-28 { + revision 2021-10-24 { description "Initial revision."; reference "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; } /* * Features */ @@ -1418,21 +1428,21 @@ description "List for templates."; } } } 7.2. Service Models 7.2.1. ietf-l3sm-te-service-mapping - file "ietf-l3sm-te-service-mapping@2021-08-28.yang" + file "ietf-l3sm-te-service-mapping@2021-10-24.yang" module ietf-l3sm-te-service-mapping { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-l3sm-te-service-mapping"; prefix l3-tsm; import ietf-te-service-mapping-types { prefix tsmt; reference "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; @@ -1465,21 +1475,21 @@ Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; - revision 2021-08-28 { + revision 2021-10-24 { description "Initial revision."; reference "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; } /* * Augmentation to L3SM */ @@ -1529,21 +1539,21 @@ description "This augment is for per-class in site-network-access for custom QoS profile"; uses tsmt:te-endpoint-ref; } } 7.2.2. ietf-l2sm-te-service-mapping - file "ietf-l2sm-te-service-mapping@2021-08-28.yang" + file "ietf-l2sm-te-service-mapping@2021-10-24.yang" module ietf-l2sm-te-service-mapping { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-l2sm-te-service-mapping"; prefix l2-tsm; import ietf-te-service-mapping-types { prefix tsmt; reference "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; @@ -1578,21 +1588,21 @@ Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; - revision 2021-08-28 { + revision 2021-10-24 { description "Initial revision."; reference "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; } /* * Augmentation to L2SM */ @@ -1646,21 +1656,21 @@ description "This augment is for per-class in site-network-access for custom QoS profile"; uses tsmt:te-endpoint-ref; } } 7.2.3. ietf-l1csm-te-service-mapping - file "ietf-l1csm-te-service-mapping@2021-08-28.yang" + file "ietf-l1csm-te-service-mapping@2021-10-24.yang" module ietf-l1csm-te-service-mapping { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-l1csm-te-service-mapping"; prefix l1-tsm; import ietf-te-service-mapping-types { prefix tsmt; reference "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; @@ -1695,21 +1705,21 @@ Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; - revision 2021-08-28 { + revision 2021-10-24 { description "Initial revision."; reference "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; } /* * Augmentation to L1CSM */ @@ -1735,21 +1745,21 @@ } //augment } 7.3. Network Models 7.3.1. ietf-l3nm-te-service-mapping - file "ietf-l3nm-te-service-mapping@2021-08-28.yang" + file "ietf-l3nm-te-service-mapping@2021-10-24.yang" module ietf-l3nm-te-service-mapping { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-l3nm-te-service-mapping"; prefix l3nm-tsm; import ietf-te-service-mapping-types { prefix tsmt; reference "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; @@ -1782,21 +1792,21 @@ Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; - revision 2021-08-28 { + revision 2021-10-24 { description "Initial revision."; reference "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; } /* * Augmentation to L3NM */ @@ -1825,21 +1835,21 @@ to TE endpoints when underlying TE is used"; uses tsmt:te-endpoint-ref; } //augment } 7.3.2. ietf-l2nm-te-service-mapping - file "ietf-l2nm-te-service-mapping@2021-08-28.yang" + file "ietf-l2nm-te-service-mapping@2021-10-24.yang" module ietf-l2nm-te-service-mapping { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-l2nm-te-service-mapping"; prefix l2nm-tsm; import ietf-te-service-mapping-types { prefix tsmt; reference "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; @@ -1874,21 +1884,21 @@ Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; - revision 2021-08-28 { + revision 2021-10-24 { description "Initial revision."; reference "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; } /* * Augmentation to L2NM */ @@ -2055,52 +2065,52 @@ motivation for this work. 11. References 11.1. Normative References [I-D.ietf-ccamp-l1csm-yang] Lee, Y., Lee, K., Zheng, H., Dios, O. G. D., and D. Ceccarelli, "A YANG Data Model for L1 Connectivity Service Model (L1CSM)", Work in Progress, Internet-Draft, draft- - ietf-ccamp-l1csm-yang-14, 20 February 2021, + ietf-ccamp-l1csm-yang-15, 8 September 2021, . + l1csm-yang-15>. [I-D.ietf-opsawg-l2nm] Barguil, S., Dios, O. G. D., Boucadair, M., and L. A. Munoz, "A Layer 2 VPN Network YANG Model", Work in - Progress, Internet-Draft, draft-ietf-opsawg-l2nm-04, 28 - July 2021, . + Progress, Internet-Draft, draft-ietf-opsawg-l2nm-09, 20 + October 2021, . [I-D.ietf-opsawg-l3sm-l3nm] Barguil, S., Dios, O. G. D., Boucadair, M., Munoz, L. A., and A. Aguado, "A Layer 3 VPN Network YANG Model", Work in - Progress, Internet-Draft, draft-ietf-opsawg-l3sm-l3nm-10, - 15 July 2021, . + Progress, Internet-Draft, draft-ietf-opsawg-l3sm-l3nm-18, + 8 October 2021, . [I-D.ietf-spring-sr-policy-yang] Raza, K., Sawaya, R., Shunwan, Z., Voyer, D., Durrani, M., Matsushima, S., and V. P. Beeram, "YANG Data Model for Segment Routing Policy", Work in Progress, Internet-Draft, draft-ietf-spring-sr-policy-yang-01, 7 April 2021, . [I-D.ietf-teas-actn-vn-yang] Lee, Y., Dhody, D., Ceccarelli, D., Bryskin, I., and B. Y. Yoon, "A YANG Data Model for VN Operation", Work in - Progress, Internet-Draft, draft-ietf-teas-actn-vn-yang-12, - 25 August 2021, . + Progress, Internet-Draft, draft-ietf-teas-actn-vn-yang-13, + 23 October 2021, . [I-D.ietf-teas-yang-te] Saad, T., Gandhi, R., Liu, X., Beeram, V. P., Bryskin, I., and O. G. D. Dios, "A YANG Data Model for Traffic Engineering Tunnels, Label Switched Paths and Interfaces", Work in Progress, Internet-Draft, draft-ietf-teas-yang-te- 27, 8 July 2021, . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, @@ -2175,27 +2185,34 @@ . [RFC8795] Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and O. Gonzalez de Dios, "YANG Data Model for Traffic Engineering (TE) Topologies", RFC 8795, DOI 10.17487/RFC8795, August 2020, . 11.2. Informative References + [I-D.dhody-teas-te-traffic-yang] + Dhody, D., "Traffic Mapping YANG model for Traffic + Engineering (TE)", Work in Progress, Internet-Draft, + draft-dhody-teas-te-traffic-yang-00, 24 October 2021, + . + [I-D.ietf-teas-actn-yang] Lee, Y., Zheng, H., Ceccarelli, D., Yoon, B. Y., and S. Belotti, "Applicability of YANG models for Abstraction and Control of Traffic Engineered Networks", Work in Progress, - Internet-Draft, draft-ietf-teas-actn-yang-07, 21 February + Internet-Draft, draft-ietf-teas-actn-yang-08, 8 September 2021, . + teas-actn-yang-08>. [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A. Bierman, Ed., "Network Configuration Protocol (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, . [RFC8199] Bogdanovic, D., Claise, B., and C. Moberg, "YANG Module Classification", RFC 8199, DOI 10.17487/RFC8199, July 2017, . @@ -2285,31 +2302,22 @@ Example 4: A VPN service may want different optimization criteria for some of its sites. The template does not allow for such a case but it can be achieved by creating the TE resources separately and then mapping them to the service. -Appendix B. Discussion - - * While the support to bind a tunnel to the VPN is supported. We do - not have a mechanism to map traffic to a path. The input can come - from the user. E.g. the enterprise customer can tell, the traffic - from source X on port Y should go with delay less than Z. Further - discussion is required on how and where to model these. - - * Support for Calendaring and scheduling TE resources. +Appendix B. Contributor Addresses -Appendix C. Contributor Addresses Adrian Farrel Old Dog Consulting EMail: adrian@olddog.co.uk Italo Busi Huawei Technologies EMail: Italo.Busi@huawei.com