--- 1/draft-ietf-teas-te-service-mapping-yang-02.txt 2020-03-08 05:14:13.697492651 -0700 +++ 2/draft-ietf-teas-te-service-mapping-yang-03.txt 2020-03-08 05:14:13.777494686 -0700 @@ -1,25 +1,25 @@ TEAS Working Group Y. Lee, Ed. -Internet-Draft SKKU +Internet-Draft Samsung Electronics Intended status: Standards Track D. Dhody, Ed. -Expires: March 12, 2020 G. Fioccola +Expires: September 9, 2020 G. Fioccola Q. Wu, Ed. Huawei Technologies D. Ceccarelli Ericsson J. Tantsura Apstra - September 9, 2019 + March 8, 2020 Traffic Engineering (TE) and Service Mapping Yang Model - draft-ietf-teas-te-service-mapping-yang-02 + draft-ietf-teas-te-service-mapping-yang-03 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). This model is referred to as TE Service Mapping Model and is applicable generically to the operator's need for seamless control and management of their VPN services with TE tunnel support. @@ -35,69 +35,79 @@ 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 March 12, 2020. + This Internet-Draft will expire on September 9, 2020. Copyright Notice - Copyright (c) 2019 IETF Trust and the persons identified as the + Copyright (c) 2020 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 and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 - 1.2. Tree diagram . . . . . . . . . . . . . . . . . . . . . . 4 - 1.3. Prefixes in Data Node Names . . . . . . . . . . . . . . . 4 - 2. TE and Service Related Parameters . . . . . . . . . . . . . . 5 - 2.1. VN/Tunnel Selection Requirements . . . . . . . . . . . . 5 - 2.2. Availability Requirement . . . . . . . . . . . . . . . . 6 + 1.2. Tree diagram . . . . . . . . . . . . . . . . . . . . . . 5 + 1.3. Prefixes in Data Node Names . . . . . . . . . . . . . . . 5 + 2. TE and Service Related Parameters . . . . . . . . . . . . . . 6 + 2.1. VN/Tunnel Selection Requirements . . . . . . . . . . . . 6 + 2.2. Availability Requirement . . . . . . . . . . . . . . . . 7 3. YANG Modeling Approach . . . . . . . . . . . . . . . . . . . 7 3.1. Forward Compatibility . . . . . . . . . . . . . . . . . . 8 - 4. L3VPN Architecture in the ACTN Context . . . . . . . . . . . 8 - 4.1. Service Mapping . . . . . . . . . . . . . . . . . . . . . 11 - 4.2. Site Mapping . . . . . . . . . . . . . . . . . . . . . . 11 - 5. Applicability of TE-Service Mapping in Generic context . . . 12 - 6. YANG Data Trees . . . . . . . . . . . . . . . . . . . . . . . 12 - 6.1. L3SM . . . . . . . . . . . . . . . . . . . . . . . . . . 12 - 6.2. L2SM . . . . . . . . . . . . . . . . . . . . . . . . . . 13 - 6.3. L1CSM . . . . . . . . . . . . . . . . . . . . . . . . . . 14 - 7. YANG Data Models . . . . . . . . . . . . . . . . . . . . . . 15 - 7.1. ietf-te-service-mapping-types . . . . . . . . . . . . . . 15 - 7.2. ietf-l3sm-te-service-mapping . . . . . . . . . . . . . . 21 - 7.3. ietf-l2sm-te-service-mapping . . . . . . . . . . . . . . 23 - 7.4. ietf-l1csm-te-service-mapping . . . . . . . . . . . . . . 25 - 8. Security Considerations . . . . . . . . . . . . . . . . . . . 27 - 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 - 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 29 - 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 29 - 11.1. Normative References . . . . . . . . . . . . . . . . . . 29 - 11.2. Informative References . . . . . . . . . . . . . . . . . 31 - Appendix A. Contributor Addresses . . . . . . . . . . . . . . . 32 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 32 + 3.2. TE and Network Models . . . . . . . . . . . . . . . . . . 8 + 4. L3VPN Architecture in the ACTN Context . . . . . . . . . . . 9 + 4.1. Service Mapping . . . . . . . . . . . . . . . . . . . . . 12 + 4.2. Site Mapping . . . . . . . . . . . . . . . . . . . . . . 12 + 5. Applicability of TE-Service Mapping in Generic context . . . 13 + 6. YANG Data Trees . . . . . . . . . . . . . . . . . . . . . . . 13 + 6.1. Service Models . . . . . . . . . . . . . . . . . . . . . 13 + 6.1.1. L3SM . . . . . . . . . . . . . . . . . . . . . . . . 13 + 6.1.2. L2SM . . . . . . . . . . . . . . . . . . . . . . . . 14 + 6.1.3. L1CSM . . . . . . . . . . . . . . . . . . . . . . . . 15 + 6.2. Network Models . . . . . . . . . . . . . . . . . . . . . 16 + 6.2.1. L3NM . . . . . . . . . . . . . . . . . . . . . . . . 16 + 6.2.2. L2NM . . . . . . . . . . . . . . . . . . . . . . . . 17 + 7. YANG Data Models . . . . . . . . . . . . . . . . . . . . . . 18 + 7.1. ietf-te-service-mapping-types . . . . . . . . . . . . . . 18 + 7.2. Service Models . . . . . . . . . . . . . . . . . . . . . 24 + 7.2.1. ietf-l3sm-te-service-mapping . . . . . . . . . . . . 24 + 7.2.2. ietf-l2sm-te-service-mapping . . . . . . . . . . . . 26 + 7.2.3. ietf-l1csm-te-service-mapping . . . . . . . . . . . . 28 + 7.3. Network Models . . . . . . . . . . . . . . . . . . . . . 30 + 7.3.1. ietf-l3nm-te-service-mapping . . . . . . . . . . . . 30 + 7.3.2. ietf-l2nm-te-service-mapping . . . . . . . . . . . . 32 + + 8. Security Considerations . . . . . . . . . . . . . . . . . . . 34 + 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36 + 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 37 + 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 37 + 11.1. Normative References . . . . . . . . . . . . . . . . . . 37 + 11.2. Informative References . . . . . . . . . . . . . . . . . 39 + Appendix A. Contributor Addresses . . . . . . . . . . . . . . . 40 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40 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 modelling of a variety of network devices, protocol instances, and network services. YANG data models have been classified in [RFC8199] and [RFC8309]. @@ -155,20 +165,25 @@ service orchestration functions such as multi-destination load balancing, guarantees of service quality, bandwidth and throughput. It also includes notifications for service fault and performance degradation and so forth. Section 2 describes a set of TE and service related parameters that this document addresses as "new and advanced parameters" that are not included in generic service models. Section 3 discusses YANG modelling approach. + Apart from the service model, the TE mapping is equally applicable to + the Network Models (L3 VPN Service Network Model (L3NM) + [I-D.ietf-opsawg-l3sm-l3nm], L2 VPN Service Network Model (L2NM) + [I-D.barguil-opsawg-l2sm-l2nm] etc.). See Section 3.2 for details. + 1.1. Terminology Refer to [RFC8453], [RFC7926], and [RFC8309] for the key terms used in this document. The terminology for describing YANG data models is found in [RFC7950]. 1.2. Tree diagram @@ -198,20 +213,26 @@ | l2-tsm | ietf-l2sm-te-service- | [RFCXXXX] | | | mapping | | | l3-tsm | ietf-l3sm-te-service- | [RFCXXXX] | | | mapping | | | vn | ietf-vn | [I-D.ietf-teas-actn-vn-yan | | | | g] | | nw | ietf-network | [RFC8345] | | te- | ietf-te-types | [I-D.ietf-teas-yang-te-typ | | types | | es] | | te | ietf-te | [I-D.ietf-teas-yang-te] | + | l1csm | ietf-l1csm | [I-D.ietf-ccamp-l1csm-yang | + | | | ] | + | l2vpn- | ietf-l2vpn-ntw | [I-D.barguil-opsawg-l2sm-l | + | ntw | | 2nm] | + | l3vpn- | ietf-l3vpn-ntw | [I-D.ietf-opsawg-l3sm-l3nm | + | ntw | | ] | +---------+----------------------------+----------------------------+ Table 1: Prefixes and corresponding YANG modules Note: The RFC Editor should replace XXXX with the number assigned to the RFC once this draft becomes an RFC. 2. TE and Service Related Parameters While L1/L2/L3 service models (L1CSM, L2SM, L3SM) are intended to @@ -338,23 +359,55 @@ 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. +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 containts 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.barguil-opsawg-l2sm-l2nm]) are + augmented to include the TE and Service mapping parameters. Figure 2 + shows the scope of the Augmented LxNM Model. + + +--------------+ +----------------------+ +----------+ + | LxNM |o-------| | . . . . | ACTN VN | + +--------------+ augment| | +----------+ + | | +----------+ + +--------------+ | Augmented LxNM Model | . . . . | TE-topo | + | TE & Service |------->| | +----------+ + | Mapping Types| import | | +----------+ + +--------------+ | | . . . . | TE-tunnel| + +----------------------+ +----------+ + reference + + Figure 2: Augmented LxNM Model + + The Augmented LxNM model (where x=2,3) augments the basic LxNM model + while importing the common TE mapping related parameters (defined in + Section 2) grouping information from TE and Service Mapping Types. + The role of the augmented LxNM network model is to expose the mapping + relationship between network models and TE models. + 4. L3VPN Architecture in the ACTN Context - Figure 2 shows the architectural context of this document referencing + Figure 3 shows the architectural context of this document referencing the ACTN components and interfaces. +----------------------------+ | Customer Service Manager | | +-----------------------+ | | | CNC + | | +-+-------------------+-+ | +----|-------------------|---+ | | |CMI(Augmented L3SM)|CMI(VN) @@ -391,24 +444,24 @@ | | V | SBI +---------------------+ | / IP/MPLS Network \ | +-------------------------+ | V +---------------------+ / Optical Network \ +-------------------------+ - Figure 2: L3VPN Architecture from the IP+Optical Network Perspective + Figure 3: L3VPN Architecture from the IP+Optical Network Perspective There are three main entities in the ACTN architecture and shown in - Figure 2. + Figure 3. o CNC: The Customer Network Controller is responsible for generating service requests. In the context of an L3VPN, the CNC uses the Augmented L3SM to express the service request and communicate it to the network operator. o MDSC: This entity is responsible for coordinating a L3VPN service request (expressed via the Augmented L3SM) with the IP/MPLS PNC and the Transport PNC. For TE services, one of the key responsibilities of the MDSC is to coordinate with both the IP PNC @@ -543,21 +596,23 @@ As discussed in the Introduction Section, the models presented in this document are also applicable generically outside of the ACTN architecture. [RFC8309] defines Customer Service Model between Customer and Service Orchestrator and Service Delivery Model between Service Orchestrator and Network Orchestrator(s). TE-Service mapping models defined in this document can be regarded primarily as Customer Service Model and secondarily as Service Deliver Model. 6. YANG Data Trees -6.1. L3SM +6.1. Service Models + +6.1.1. L3SM module: ietf-l3sm-te-service-mapping augment /l3vpn-svc:l3vpn-svc/l3vpn-svc:vpn-services /l3vpn-svc:vpn-service: +--rw te-service-mapping! +--rw te-mapping +--rw map-type? identityref +--rw availability-type? identityref +--rw (te)? +--:(vn) | +--rw vn-ref? -> /vn:vn/vn-list/vn-id @@ -570,21 +625,21 @@ augment /l3vpn-svc:l3vpn-svc/l3vpn-svc:sites/l3vpn-svc:site /l3vpn-svc:site-network-accesses /l3vpn-svc:site-network-access: +--rw (te)? +--:(vn) | +--rw vn-ref? | -> /vn:ap/access-point-list/access-point-id +--:(te) +--rw ltp? te-types:te-tp-id -6.2. L2SM +6.1.2. L2SM module: ietf-l2sm-te-service-mapping augment /l2vpn-svc:l2vpn-svc/l2vpn-svc:vpn-services /l2vpn-svc:vpn-service: +--rw te-service-mapping! +--rw te-mapping +--rw map-type? identityref +--rw availability-type? identityref +--rw (te)? +--:(vn) | +--rw vn-ref? -> /vn:vn/vn-list/vn-id @@ -597,21 +652,21 @@ augment /l2vpn-svc:l2vpn-svc/l2vpn-svc:sites/l2vpn-svc:site /l2vpn-svc:site-network-accesses /l2vpn-svc:site-network-access: +--rw (te)? +--:(vn) | +--rw vn-ref? | -> /vn:ap/access-point-list/access-point-id +--:(te) +--rw ltp? te-types:te-tp-id -6.3. L1CSM +6.1.3. L1CSM module: ietf-l1csm-te-service-mapping augment /l1csm:l1-connectivity/l1csm:services/l1csm:service: +--rw te-service-mapping! +--rw te-mapping +--rw map-type? identityref +--rw availability-type? identityref +--rw (te)? +--:(vn) | +--rw vn-ref? -> /vn:vn/vn-list/vn-id +--:(te-topo) @@ -621,66 +676,117 @@ +--:(te-tunnel) +--rw te-tunnel-list* te:tunnel-ref augment /l1csm:l1-connectivity/l1csm:access/l1csm:unis/l1csm:uni: +--rw (te)? +--:(vn) | +--rw vn-ref? | -> /vn:ap/access-point-list/access-point-id +--:(te) +--rw ltp? te-types:te-tp-id +6.2. Network Models + +6.2.1. L3NM + module: ietf-l3nm-te-service-mapping + augment /l3vpn-ntw:l3vpn-ntw/l3vpn-ntw:vpn-services + /l3vpn-ntw:vpn-service: + +--rw te-service-mapping! + +--rw te-mapping + +--rw map-type? identityref + +--rw availability-type? identityref + +--rw (te)? + +--:(vn) + | +--rw vn-ref? -> /vn:vn/vn-list/vn-id + +--:(te-topo) + | +--rw vn-topology-id? te-types:te-topology-id + | +--rw abstract-node? + | -> /nw:networks/network/node/node-id + +--:(te-tunnel) + +--rw te-tunnel-list* te:tunnel-ref + augment /l3vpn-ntw:l3vpn-ntw/l3vpn-ntw:vpn-services + /l3vpn-ntw:vpn-service/l3vpn-ntw:vpn-nodes + /l3vpn-ntw:vpn-node/l3vpn-ntw:vpn-network-accesses + /l3vpn-ntw:vpn-network-access: + +--rw (te)? + +--:(vn) + | +--rw vn-ref? + | -> /vn:ap/access-point-list/access-point-id + +--:(te) + +--rw ltp? te-types:te-tp-id + +6.2.2. L2NM + module: ietf-l2nm-te-service-mapping + augment /l2vpn-ntw:l2vpn-ntw/l2vpn-ntw:vpn-services + /l2vpn-ntw:vpn-svc: + +--rw te-service-mapping! + +--rw te-mapping + +--rw map-type? identityref + +--rw availability-type? identityref + +--rw (te)? + +--:(vn) + | +--rw vn-ref? -> /vn:vn/vn-list/vn-id + +--:(te-topo) + | +--rw vn-topology-id? te-types:te-topology-id + | +--rw abstract-node? + | -> /nw:networks/network/node/node-id + +--:(te-tunnel) + +--rw te-tunnel-list* te:tunnel-ref + augment /l2vpn-ntw:l2vpn-ntw/l2vpn-ntw:vpn-services + /l2vpn-ntw:vpn-svc/l2vpn-ntw:vpn-nodes + /l2vpn-ntw:vpn-node/l2vpn-ntw:vpn-network-accesses + /l2vpn-ntw:vpn-network-access: + +--rw (te)? + +--:(vn) + | +--rw vn-ref? + | -> /vn:ap/access-point-list/access-point-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@2019-09-09.yang" - + file "ietf-te-service-mapping-types@2020-03-08.yang" module ietf-te-service-mapping-types { - yang-version 1.1; - - namespace "urn:ietf:params:xml:ns:yang:ietf-te-service-mapping-types"; - + namespace + "urn:ietf:params:xml:ns:yang:ietf-te-service-mapping-types"; prefix tsm; import ietf-te-types { prefix te-types; reference "I-D.ietf-teas-yang-te-types: Traffic Engineering Common YANG Types"; } - import ietf-network { prefix nw; reference "RFC 8345: A YANG Data Model for Network Topologies"; } - import ietf-te { prefix te; reference "I-D.ietf-teas-yang-te: A YANG Data Model for Traffic Engineering Tunnels and Interfaces"; } - import ietf-vn { prefix vn; reference "I-D.ietf-teas-actn-vn-yang: A Yang Data Model for VN Operation"; } organization "IETF Traffic Engineering Architecture and Signaling (TEAS) Working Group"; - contact "WG Web: WG List: Editor: Young Lee Editor: Dhruv Dhody Editor: Qin Wu "; @@ -677,40 +783,45 @@ contact "WG Web: WG List: Editor: Young Lee Editor: Dhruv Dhody Editor: Qin Wu "; - description "This module contains a YANG module for TE & Service mapping parameters and policies as a common grouping applicable to variuous service models (e.g., L1CSM, L2SM, L3SM, etc.) - Copyright (c) 2019 IETF Trust and the persons identified as + Copyright (c) 2020 IETF Trust and the persons identified as authors of the code. All rights reserved. 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 + 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."; + RFC itself for full legal notices. - revision 2019-09-09 { + The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL + NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', + 'MAY', and 'OPTIONAL' in this document are to be interpreted as + described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, + they appear in all capitals, as shown here."; + + revision 2020-03-08 { description "Initial revision."; reference "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; } /* * Identity for map-type */ @@ -843,21 +955,23 @@ leaf-list te-tunnel-list { type te:tunnel-ref; description "Reference to TE Tunnels"; reference "I-D.ietf-teas-yang-te: A YANG Data Model for Traffic Engineering Tunnels and Interfaces"; } } } - }//grouping + } + + //grouping grouping te-endpoint-ref { description "The reference to TE endpoints."; choice te { description "The TE"; case vn { leaf vn-ref { type leafref { @@ -874,21 +988,23 @@ leaf ltp { type te-types:te-tp-id; description "Reference LTP in the TE-topology"; reference "I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic Engineering (TE) Topologies"; } } } - }//grouping + } + + //grouping grouping te-mapping { description "Mapping between Services and TE"; container te-mapping { description "Mapping between Services and TE"; leaf map-type { type identityref { base map-type; @@ -899,55 +1015,56 @@ } leaf availability-type { type identityref { base availability-type; } description "Availability Requirement for the Service"; } uses te-ref; } - }//grouping -}//module + } + + //grouping + } -7.2. ietf-l3sm-te-service-mapping +7.2. Service Models - file "ietf-l3sm-te-service-mapping@2019-09-09.yang" - module ietf-l3sm-te-service-mapping { +7.2.1. ietf-l3sm-te-service-mapping + file "ietf-l3sm-te-service-mapping@2020-03-08.yang" + module ietf-l3sm-te-service-mapping { yang-version 1.1; - - namespace "urn:ietf:params:xml:ns:yang:ietf-l3sm-te-service-mapping"; - + namespace + "urn:ietf:params:xml:ns:yang:ietf-l3sm-te-service-mapping"; prefix l3-tsm; import ietf-te-service-mapping-types { prefix tsm-types; reference "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; } - import ietf-l3vpn-svc { prefix l3vpn-svc; reference "RFC 8299: YANG Data Model for L3VPN Service Delivery"; } organization "IETF Traffic Engineering Architecture and Signaling (TEAS) Working Group"; - contact "WG Web: WG List: + Editor: Young Lee Editor: Dhruv Dhody Editor: Qin Wu "; description "This module contains a YANG module for the mapping of Layer 3 Service Model (L3SM) to the TE and VN. @@ -944,85 +1061,92 @@ Editor: Young Lee Editor: Dhruv Dhody Editor: Qin Wu "; description "This module contains a YANG module for the mapping of Layer 3 Service Model (L3SM) to the TE and VN. - Copyright (c) 2019 IETF Trust and the persons identified as + Copyright (c) 2020 IETF Trust and the persons identified as authors of the code. All rights reserved. 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 + 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."; + RFC itself for full legal notices. - revision 2019-09-09 { + The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL + NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', + 'MAY', and 'OPTIONAL' in this document are to be interpreted as + described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, + they appear in all capitals, as shown here."; + + revision 2020-03-08 { description "Initial revision."; reference "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; } /* * Augmentation to L3SM */ + augment "/l3vpn-svc:l3vpn-svc/l3vpn-svc:vpn-services" + "/l3vpn-svc:vpn-service" { description "L3SM augmented to include TE parameters and mapping"; container te-service-mapping { - presence - "Indicates L3 service to TE mapping"; + presence "Indicates L3 service to TE mapping"; description "Container to augment l3sm to TE parameters and mapping"; uses tsm-types:te-mapping; } - }//augment + } + + //augment augment "/l3vpn-svc:l3vpn-svc/l3vpn-svc:sites/l3vpn-svc:site" + "/l3vpn-svc:site-network-accesses" + "/l3vpn-svc:site-network-access" { description "This augment is only valid for TE mapping of L3SM network-access to TE endpoints"; uses tsm-types:te-endpoint-ref; - }//augment - }//module + } + + //augment + } -7.3. ietf-l2sm-te-service-mapping +7.2.2. ietf-l2sm-te-service-mapping - file "ietf-l2sm-te-service-mapping@2019-09-09.yang" + file "ietf-l2sm-te-service-mapping@2020-03-08.yang" module ietf-l2sm-te-service-mapping { - yang-version 1.1; - - namespace "urn:ietf:params:xml:ns:yang:ietf-l2sm-te-service-mapping"; - + namespace + "urn:ietf:params:xml:ns:yang:ietf-l2sm-te-service-mapping"; prefix l2-tsm; import ietf-te-service-mapping-types { prefix tsm-types; reference "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; } - import ietf-l2vpn-svc { prefix l2vpn-svc; reference "RFC 8466: A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery"; } organization "IETF Traffic Engineering Architecture and Signaling (TEAS) Working Group"; @@ -1030,90 +1153,96 @@ contact "WG Web: WG List: Editor: Young Lee Editor: Dhruv Dhody Editor: Qin Wu "; - description "This module contains a YANG module for the mapping of Layer 2 Service Model (L2SM) to the TE and VN. - Copyright (c) 2019 IETF Trust and the persons identified as + Copyright (c) 2020 IETF Trust and the persons identified as authors of the code. All rights reserved. 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 + 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."; + RFC itself for full legal notices. - revision 2019-09-09 { + The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL + NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', + 'MAY', and 'OPTIONAL' in this document are to be interpreted as + described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, + they appear in all capitals, as shown here."; + + revision 2020-03-08 { description "Initial revision."; reference "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; } /* * Augmentation to L3SM */ + augment "/l2vpn-svc:l2vpn-svc/l2vpn-svc:vpn-services/" + "l2vpn-svc:vpn-service" { description "L2SM augmented to include TE parameters and mapping"; container te-service-mapping { - presence - "indicates L2 service to te mapping"; + presence "indicates L2 service to te mapping"; description "Container to augment L2SM to TE parameters and mapping"; uses tsm-types:te-mapping; } - }//augment + } + + //augment augment "/l2vpn-svc:l2vpn-svc/l2vpn-svc:sites/l2vpn-svc:site" + "/l2vpn-svc:site-network-accesses" + "/l2vpn-svc:site-network-access" { description "This augment is only valid for TE mapping of L2SM network-access to TE endpoints"; - uses tsm-types:te-endpoint-ref; - }//augment - }//module + } + + //augment + } + -7.4. ietf-l1csm-te-service-mapping +7.2.3. ietf-l1csm-te-service-mapping - file "ietf-l1csm-te-service-mapping@2019-09-09.yang" + file "ietf-l1csm-te-service-mapping@2020-03-08.yang" module ietf-l1csm-te-service-mapping { - yang-version 1.1; - - namespace "urn:ietf:params:xml:ns:yang:ietf-l1csm-te-service-mapping"; - + namespace + "urn:ietf:params:xml:ns:yang:ietf-l1csm-te-service-mapping"; prefix l1-tsm; import ietf-te-service-mapping-types { prefix tsm-types; reference "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; } - import ietf-l1csm { prefix l1csm; reference "I-D.ietf-ccamp-l1csm-yang: A YANG Data Model for L1 Connectivity Service Model (L1CSM)"; } organization "IETF Traffic Engineering Architecture and Signaling (TEAS) Working Group"; @@ -1121,69 +1249,278 @@ contact "WG Web: WG List: Editor: Young Lee Editor: Dhruv Dhody Editor: Qin Wu "; - description "This module contains a YANG module for the mapping of Layer 1 Connectivity Service Module (L1CSM) to the TE and VN - Copyright (c) 2019 IETF Trust and the persons identified as + + Copyright (c) 2020 IETF Trust and the persons identified as authors of the code. All rights reserved. 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 + 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."; + RFC itself for full legal notices. - revision 2019-09-09 { + The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL + NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', + 'MAY', and 'OPTIONAL' in this document are to be interpreted as + described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, + they appear in all capitals, as shown here."; + + revision 2020-03-08 { description "Initial revision."; reference "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; } /* * Augmentation to L1CSM */ + augment "/l1csm:l1-connectivity/l1csm:services/l1csm:service" { description "L1CSM augmented to include TE parameters and mapping"; container te-service-mapping { - presence - "Indicates L1 service to TE mapping"; + presence "Indicates L1 service to TE mapping"; description "Container to augment L1CSM to TE parameters and mapping"; uses tsm-types:te-mapping; } - }//augment + } + + //augment augment "/l1csm:l1-connectivity/l1csm:access/l1csm:unis/" + "l1csm:uni" { description "This augment is only valid for TE mapping of L1CSM UNI to TE endpoints"; uses tsm-types:te-endpoint-ref; - }//augment -}//module + } + + //augment + } + + + +7.3. Network Models + +7.3.1. ietf-l3nm-te-service-mapping + + file "ietf-l3nm-te-service-mapping@2020-03-08.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 tsm-types; + reference + "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; + } + import ietf-l3vpn-ntw { + prefix l3vpn-ntw; + reference + "I-D.ietf-opsawg-l3sm-l3nm: A Layer 3 VPN Network YANG Model"; + + } + + organization + "IETF Traffic Engineering Architecture and Signaling (TEAS) + Working Group"; + contact + "WG Web: + WG List: + + Editor: Young Lee + + Editor: Dhruv Dhody + + Editor: Qin Wu + "; + description + "This module contains a YANG module for the mapping of Layer 3 + Network Model (L3NM) to the TE and VN. + + Copyright (c) 2020 IETF Trust and the persons identified as + authors of the code. All rights reserved. + + 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. + + The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL + NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', + 'MAY', and 'OPTIONAL' in this document are to be interpreted as + described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, + they appear in all capitals, as shown here."; + + revision 2020-03-08 { + description + "Initial revision."; + reference + "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; + } + + /* + * Augmentation to L3NM + */ + + augment "/l3vpn-ntw:l3vpn-ntw/l3vpn-ntw:vpn-services" + + "/l3vpn-ntw:vpn-service" { + description + "L3SM augmented to include TE parameters and mapping"; + container te-service-mapping { + presence "Indicates L3 network to TE mapping"; + description + "Container to augment l3nm to TE parameters and mapping"; + uses tsm-types:te-mapping; + } + } + + //augment + + augment "/l3vpn-ntw:l3vpn-ntw/l3vpn-ntw:vpn-services" + + "/l3vpn-ntw:vpn-service" + + "/l3vpn-ntw:vpn-nodes/l3vpn-ntw:vpn-node" + + "/l3vpn-ntw:vpn-network-accesses" + + "/l3vpn-ntw:vpn-network-access" { + description + "This augment is only valid for TE mapping of L3NM network-access + to TE endpoints"; + uses tsm-types:te-endpoint-ref; + } + + //augment + } + +7.3.2. ietf-l2nm-te-service-mapping + + file "ietf-l2nm-te-service-mapping@2020-03-08.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 tsm-types; + reference + "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; + } + import ietf-l2vpn-ntw { + prefix l2vpn-ntw; + reference + "I-D.-barguil-opsawg-l2sm-l2nm: A Layer 2 VPN Network YANG Model"; + + } + + organization + "IETF Traffic Engineering Architecture and Signaling (TEAS) + Working Group"; + contact + "WG Web: + WG List: + + Editor: Young Lee + + Editor: Dhruv Dhody + + Editor: Qin Wu + "; + description + "This module contains a YANG module for the mapping of Layer 2 + Network Model (L2NM) to the TE and VN. + + Copyright (c) 2020 IETF Trust and the persons identified as + authors of the code. All rights reserved. + + 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. + + The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL + NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', + 'MAY', and 'OPTIONAL' in this document are to be interpreted as + described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, + they appear in all capitals, as shown here."; + + revision 2020-03-08 { + description + "Initial revision."; + reference + "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; + } + + /* + * Augmentation to L2NM + */ + + augment "/l2vpn-ntw:l2vpn-ntw/l2vpn-ntw:vpn-services" + + "/l2vpn-ntw:vpn-svc" { + description + "L2SM augmented to include TE parameters and mapping"; + container te-service-mapping { + presence "Indicates L2 network to TE mapping"; + description + "Container to augment l2nm to TE parameters and mapping"; + uses tsm-types:te-mapping; + } + } + + //augment + + augment "/l2vpn-ntw:l2vpn-ntw/l2vpn-ntw:vpn-services" + + "/l2vpn-ntw:vpn-svc" + + "/l2vpn-ntw:vpn-nodes/l2vpn-ntw:vpn-node" + + "/l2vpn-ntw:vpn-network-accesses" + + "/l2vpn-ntw:vpn-network-access" { + description + "This augment is only valid for TE mapping of L2NM network-access + to TE endpoints"; + uses tsm-types:te-endpoint-ref; + } + + //augment +} + + + 8. Security Considerations The YANG modules defined in this document is designed to be accessed via network management protocol such as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer is the secure transport layer and the mandatory-to-implement secure transport is SSH [RFC6242]. The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS [RFC8446] The NETCONF access control model [RFC8341] provides the means to @@ -1210,20 +1547,34 @@ o /l2vpn-svc/sites/site/site-network-accesses/site-network-access/ te/ - configure TE Endpoint mapping. o /l1-connectivity/services/service/te-service-mapping/te-mapping/ - configure TE Service mapping. o /l1-connectivity/access/unis/uni/te/ - configure TE Endpoint mapping. + o /l3vpn-ntw/vpn-services/vpn-service/te-service-mapping/te-mapping/ + - configure TE Network mapping. + + o /l3vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/vpn- + network-accesses/vpn-network-access/te/ - configure TE Endpoint + mapping. + + o /l2vpn-ntw/vpn-services/vpn-service/te-service-mapping/te-mapping/ + - configure TE Network mapping. + + o /l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/vpn- + network-accesses/vpn-network-access/te/ - configure TE Endpoint + mapping. + Unauthorized access to above list can adversely affect the VPN service. Some of the readable data nodes in the YANG module may be considered sensitive or vulnerable in some network environments. It is thus important to control read access (e.g., via get, get-config, or notification) to these data nodes. The TE related parameters attached to the VPN service can leak sensitive information about the network. This is apploicable to all elements in the yang models defined in this document. @@ -1245,20 +1596,28 @@ XML: N/A, the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:ietf-l2sm-te-service-mapping Registrant Contact: The IESG. XML: N/A, the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:ietf-l1csm-te-service-mapping Registrant Contact: The IESG. XML: N/A, the requested URI is an XML namespace. + URI: urn:ietf:params:xml:ns:yang:ietf-l3nm-te-service-mapping + Registrant Contact: The IESG. + XML: N/A, the requested URI is an XML namespace. + + URI: urn:ietf:params:xml:ns:yang:ietf-l2nm-te-service-mapping + Registrant Contact: The IESG. + XML: N/A, the requested URI is an XML namespace. + This document request the IANA to register four YANG modules in the "YANG Module Names" registry [RFC6020], as follows - Name: ietf-te-service-mapping-types Namespace: urn:ietf:params:xml:ns:yang:ietf-te-service-mapping-types Prefix: tsm Reference: [This.I-D] Name: ietf-l3sm-te-service-mapping Namespace: urn:ietf:params:xml:ns:yang:ietf-l3sm-te-service-mapping Prefix: l3-tsm @@ -1267,24 +1626,35 @@ Name: ietf-l2sm-te-service-mapping Namespace: urn:ietf:params:xml:ns:yang:ietf-l2sm-te-service-mapping Prefix: l2-tsm Reference: [This.I-D] Name: ietf-l1csm-te-service-mapping Namespace: urn:ietf:params:xml:ns:yang:ietf-l1csm-te-service-mapping Prefix: l1-tsm Reference: [This.I-D] + Name: ietf-l3nm-te-service-mapping + Namespace: urn:ietf:params:xml:ns:yang:ietf-l3nm-te-service-mapping + Prefix: l3nm-tsm + Reference: [This.I-D] + + Name: ietf-l2nm-te-service-mapping + Namespace: urn:ietf:params:xml:ns:yang:ietf-l2nm-te-service-mapping + Prefix: l2nm-tsm + Reference: [This.I-D] + 10. Acknowledgements - We thank Diego Caviglia and Igor Bryskin for useful discussions and - motivation for this work. + We thank Diego Caviglia, Igor Bryskin, Oscar Gonzalez de Dios, and + Samier Barguil Giraldo for useful discussions and motivation for this + work. 11. References 11.1. Normative References [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, . [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure @@ -1336,32 +1706,42 @@ [I-D.ietf-ccamp-l1csm-yang] Lee, Y., Lee, K., Zheng, H., Dhody, D., Dios, O., and D. Ceccarelli, "A YANG Data Model for L1 Connectivity Service Model (L1CSM)", draft-ietf-ccamp-l1csm-yang-10 (work in progress), September 2019. [I-D.ietf-teas-actn-vn-yang] Lee, Y., Dhody, D., Ceccarelli, D., Bryskin, I., and B. Yoon, "A Yang Data Model for VN Operation", draft-ietf- - teas-actn-vn-yang-06 (work in progress), July 2019. + teas-actn-vn-yang-07 (work in progress), October 2019. [I-D.ietf-teas-yang-te] Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, "A YANG Data Model for Traffic Engineering Tunnels and - Interfaces", draft-ietf-teas-yang-te-21 (work in - progress), April 2019. + Interfaces", draft-ietf-teas-yang-te-22 (work in + progress), November 2019. [I-D.ietf-teas-yang-te-types] Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, "Traffic Engineering Common YANG Types", draft-ietf-teas- - yang-te-types-10 (work in progress), July 2019. + yang-te-types-13 (work in progress), November 2019. + + [I-D.ietf-opsawg-l3sm-l3nm] + Aguado, A., Dios, O., Lopezalvarez, V., Voyer, D., and L. + Munoz, "A Layer 3 VPN Network YANG Model", draft-ietf- + opsawg-l3sm-l3nm-01 (work in progress), November 2019. + + [I-D.barguil-opsawg-l2sm-l2nm] + Barguil, S., Dios, O., Lopezalvarez, V., Munoz, L., and L. + Jalil, "A Layer 2 VPN Network Yang Model", draft-barguil- + opsawg-l2sm-l2nm-00 (work in progress), December 2019. 11.2. Informative References [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, DOI 10.17487/RFC6020, October 2010, . [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A. Bierman, Ed., "Network Configuration Protocol @@ -1389,22 +1769,22 @@ [I-D.ietf-teas-yang-te-topo] Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and O. Dios, "YANG Data Model for Traffic Engineering (TE) Topologies", draft-ietf-teas-yang-te-topo-22 (work in progress), June 2019. [I-D.ietf-teas-actn-yang] Lee, Y., Zheng, H., Ceccarelli, D., Yoon, B., Dios, O., Shin, J., and S. Belotti, "Applicability of YANG models for Abstraction and Control of Traffic Engineered - Networks", draft-ietf-teas-actn-yang-04 (work in - progress), August 2019. + Networks", draft-ietf-teas-actn-yang-05 (work in + progress), February 2020. Appendix A. Contributor Addresses Adrian Farrel Old Dog Consulting EMail: adrian@olddog.co.uk Italo Busi Huawei Technologies @@ -1412,24 +1792,23 @@ EMail: Italo.Busi@huawei.com Haomian Zheng Huawei Technologies EMail: zhenghaomian@huawei.com Authors' Addresses Young Lee (editor) - SKKU + Samsung Electronics Email: younglee.tx@gmail.com - Dhruv Dhody (editor) Huawei Technologies Email: dhruv.ietf@gmail.com Giuseppe Fioccola Huawei Technologies Email: giuseppe.fioccola@huawei.com