--- 1/draft-ietf-teas-te-service-mapping-yang-04.txt 2020-11-02 02:13:17.757501514 -0800 +++ 2/draft-ietf-teas-te-service-mapping-yang-05.txt 2020-11-02 02:13:17.841503643 -0800 @@ -1,25 +1,25 @@ TEAS Working Group Y. Lee, Ed. Internet-Draft Samsung Electronics Intended status: Standards Track D. Dhody, Ed. -Expires: January 14, 2021 G. Fioccola +Expires: May 6, 2021 G. Fioccola Q. Wu, Ed. Huawei Technologies D. Ceccarelli Ericsson J. Tantsura Apstra - July 13, 2020 + November 2, 2020 Traffic Engineering (TE) and Service Mapping Yang Model - draft-ietf-teas-te-service-mapping-yang-04 + draft-ietf-teas-te-service-mapping-yang-05 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,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 January 14, 2021. + This Internet-Draft will expire on May 6, 2021. Copyright Notice 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 @@ -73,21 +73,21 @@ 3.1. Forward Compatibility . . . . . . . . . . . . . . . . . . 9 3.2. TE and Network Models . . . . . . . . . . . . . . . . . . 9 4. L3VPN Architecture in the ACTN Context . . . . . . . . . . . 10 4.1. Service Mapping . . . . . . . . . . . . . . . . . . . . . 13 4.2. Site Mapping . . . . . . . . . . . . . . . . . . . . . . 13 5. Applicability of TE-Service Mapping in Generic context . . . 14 6. YANG Data Trees . . . . . . . . . . . . . . . . . . . . . . . 14 6.1. Service Mapping Types . . . . . . . . . . . . . . . . . . 14 6.2. Service Models . . . . . . . . . . . . . . . . . . . . . 16 6.2.1. L3SM . . . . . . . . . . . . . . . . . . . . . . . . 16 - 6.2.2. L2SM . . . . . . . . . . . . . . . . . . . . . . . . 16 + 6.2.2. L2SM . . . . . . . . . . . . . . . . . . . . . . . . 17 6.2.3. L1CSM . . . . . . . . . . . . . . . . . . . . . . . . 17 6.3. Network Models . . . . . . . . . . . . . . . . . . . . . 18 6.3.1. L3NM . . . . . . . . . . . . . . . . . . . . . . . . 18 6.3.2. L2NM . . . . . . . . . . . . . . . . . . . . . . . . 19 7. YANG Data Models . . . . . . . . . . . . . . . . . . . . . . 20 7.1. ietf-te-service-mapping-types . . . . . . . . . . . . . . 20 7.2. Service Models . . . . . . . . . . . . . . . . . . . . . 29 7.2.1. ietf-l3sm-te-service-mapping . . . . . . . . . . . . 29 7.2.2. ietf-l2sm-te-service-mapping . . . . . . . . . . . . 31 7.2.3. ietf-l1csm-te-service-mapping . . . . . . . . . . . . 33 @@ -227,21 +227,21 @@ | | | ] | | nw | ietf-network | [RFC8345] | | te- | ietf-te-types | [RFC8776] | | types | | | | te | ietf-te | [I-D.ietf-teas-yang-te] | | l2vpn- | ietf-l2vpn-ntw | [I-D.ietf-opsawg-l2nm] | | ntw | | | | l3vpn- | ietf-l3vpn-ntw | [I-D.ietf-opsawg-l3sm-l3nm] | | ntw | | | | rt | ietf-routing | [RFC8349] | - | sr- | ietf-sr-policy | [I-D.raza-spring-sr-policy- | + | sr- | ietf-sr-policy | [I-D.ietf-spring-sr-policy- | | policy | | yang] | +---------+---------------------------+-----------------------------+ 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 @@ -358,24 +358,23 @@ customers to access operational state information about how their services are instantiated with the underlying VN, TE topology or TE tunnels provided that the MDSC operator is willing to share that information. This mapping will facilitate a seamless service management operation with underlay-TE network visibility. As seen in Figure 1, the augmented LxSM service model records a mapping between the customer service models and the ACTN VN YANG model. Thus, when the MDSC receives a service request it creates a VN that meets the customer's service objectives with various - constraints via TE-topology model [I-D.ietf-teas-yang-te-topo], and - this relationship is recorded by the Augmented LxSM Model. The model - also supports a mapping between a service model and TE-topology or a - TE-tunnel. + constraints via TE-topology model [RFC8795], and this relationship is + recorded by the Augmented LxSM Model. The model also supports a + mapping between a service model and TE-topology or a TE-tunnel. The YANG models defined in this document conforms to the Network Management Datastore Architecture (NMDA) [RFC8342]. 3.1. Forward Compatibility The YANG module defined in this document supports three existing service models via augmenting while sharing the common TE and Service Mapping Types. @@ -661,154 +660,153 @@ | | +--rw names* string | +--rw disjointness? te-path-disjointness +--rw optimizations +--rw (algorithm)? +--:(metric) {path-optimization-metric}? | +--rw optimization-metric* [metric-type] | | +--rw metric-type | | | identityref | | +--rw weight? uint8 | | +--rw explicit-route-exclude-objects - | | | +--rw route-object-exclude-object* [index] | | | ... | | +--rw explicit-route-include-objects - | | +--rw route-object-include-object* [index] | | ... | +--rw tiebreakers | +--rw tiebreaker* [tiebreaker-type] - | +--rw tiebreaker-type identityref + | ... +--:(objective-function) {path-optimization-objective-function}? +--rw objective-function +--rw objective-function-type? identityref 6.2. Service Models 6.2.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? + | +--rw vn-list* | -> /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 | +--rw sr-policy* | [policy-color-ref policy-endpoint-ref] | {sr-policy}? | +--rw policy-color-ref leafref | +--rw policy-endpoint-ref leafref +--:(te-mapping-template) {template}? +--rw te-mapping-template-ref? leafref 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? + | +--rw ap-list* | -> /vn:ap/access-point-list/access-point-id +--:(te) +--rw ltp? te-types:te-tp-id 6.2.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? + | +--rw vn-list* | -> /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 | +--rw sr-policy* | [policy-color-ref policy-endpoint-ref] | {sr-policy}? | +--rw policy-color-ref leafref | +--rw policy-endpoint-ref leafref +--:(te-mapping-template) {template}? +--rw te-mapping-template-ref? leafref 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? + | +--rw ap-list* | -> /vn:ap/access-point-list/access-point-id +--:(te) +--rw ltp? te-types:te-tp-id 6.2.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? + | +--rw vn-list* | -> /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 | +--rw sr-policy* | [policy-color-ref policy-endpoint-ref] | {sr-policy}? | +--rw policy-color-ref leafref | +--rw policy-endpoint-ref leafref +--:(te-mapping-template) {template}? +--rw te-mapping-template-ref? leafref augment /l1csm:l1-connectivity/l1csm:access/l1csm:unis/l1csm:uni: +--rw (te)? +--:(vn) - | +--rw vn-ref? + | +--rw ap-list* | -> /vn:ap/access-point-list/access-point-id +--:(te) +--rw ltp? te-types:te-tp-id 6.3. Network Models 6.3.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? + | +--rw vn-list* | -> /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 | +--rw sr-policy* | [policy-color-ref policy-endpoint-ref] @@ -816,36 +814,36 @@ | +--rw policy-color-ref leafref | +--rw policy-endpoint-ref leafref +--:(te-mapping-template) {template}? +--rw te-mapping-template-ref? leafref 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? + | +--rw ap-list* | -> /vn:ap/access-point-list/access-point-id +--:(te) +--rw ltp? te-types:te-tp-id 6.3.2. L2NM module: ietf-l2nm-te-service-mapping augment /l2vpn-ntw:l2vpn-ntw/l2vpn-ntw:vpn-services /l2vpn-ntw:vpn-service: +--rw te-service-mapping! +--rw te-mapping +--rw map-type? identityref +--rw availability-type? identityref +--rw (te)? +--:(vn) - | +--rw vn-ref? + | +--rw vn-list* | -> /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 | +--rw sr-policy* | [policy-color-ref policy-endpoint-ref] @@ -853,37 +851,36 @@ | +--rw policy-color-ref leafref | +--rw policy-endpoint-ref leafref +--:(te-mapping-template) {template}? +--rw te-mapping-template-ref? leafref augment /l2vpn-ntw:l2vpn-ntw/l2vpn-ntw:vpn-services /l2vpn-ntw:vpn-service/l2vpn-ntw:vpn-nodes /l2vpn-ntw:vpn-node/l2vpn-ntw:vpn-network-accesses /l2vpn-ntw:vpn-network-access: +--rw (te)? +--:(vn) - | +--rw vn-ref? + | +--rw ap-list* | -> /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@2020-07-13.yang" + file "ietf-te-service-mapping-types@2020-11-02.yang" module ietf-te-service-mapping-types { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-te-service-mapping-types"; - prefix tsm-types; /* Import inet-types */ import ietf-inet-types { prefix inet; reference "RFC 6991: Common YANG Data Types"; } @@ -926,21 +923,21 @@ prefix rt; reference "RFC 8349: A YANG Data Model for Routing Management"; } /* Import SR Policy */ import ietf-sr-policy { prefix sr-policy; reference - "I-D.raza-spring-sr-policy-yang: YANG Data Model for Segment + "I-D.ietf-spring-sr-policy-yang: YANG Data Model for Segment Routing Policy"; } organization "IETF Traffic Engineering Architecture and Signaling (TEAS) Working Group"; contact "WG Web: WG List: @@ -967,21 +964,21 @@ 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-07-13 { + revision 2020-11-02 { description "Initial revision."; reference "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; } /* * Features */ @@ -1105,51 +1106,51 @@ * Groupings */ grouping te-ref { description "The reference to TE."; choice te { description "The TE"; case vn { - leaf vn-ref { + leaf-list vn-list { type leafref { path "/vn:vn/vn:vn-list/vn:vn-id"; } description "The reference to VN"; reference "RFC 8453: Framework for Abstraction and Control of TE Networks (ACTN)"; } } case te-topo { leaf vn-topology-id { type te-types:te-topology-id; description "An identifier to the TE Topology Model where the abstract nodes and links of the Topology can be found for Type 2 VNS"; reference - "I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic - Engineering (TE) Topologies"; + "RFC 8795: YANG Data Model for Traffic Engineering (TE) + Topologies"; } leaf abstract-node { type leafref { path "/nw:networks/nw:network/nw:node/nw:node-id"; } description "A reference to the abstract node in TE Topology"; reference - "I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic - Engineering (TE) Topologies"; + "RFC 8795: YANG Data Model for Traffic Engineering (TE) + Topologies"; } } case te-tunnel { 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"; @@ -1178,58 +1179,59 @@ } description "Reference to sr-policy endpoint"; } } } case te-mapping-template { if-feature "template"; leaf te-mapping-template-ref { type leafref { - path "/te-mapping-templates/te-mapping-template/id"; + path "/tsm-types:te-mapping-templates/" + + "tsm-types:te-mapping-template/tsm-types:id"; } description "An identifier to the TE Mapping Template where the TE constraints and optimization criteria are specified."; } } } } //grouping grouping te-endpoint-ref { description "The reference to TE endpoints."; choice te { description "The TE"; case vn { - leaf vn-ref { + leaf-list ap-list { type leafref { path "/vn:ap/vn:access-point-list/vn:access-point-id"; } description "The reference to VN AP"; reference "RFC 8453: Framework for Abstraction and Control of TE Networks (ACTN)"; } } case te { 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"; + "RFC 8795: YANG Data Model for Traffic Engineering (TE) + Topologies"; } } } } //grouping grouping te-mapping { description "Mapping between Services and TE"; @@ -1270,21 +1270,21 @@ } leaf description { type string; description "Description of the template."; } leaf map-type { type identityref { base map-type; } - must '(. != "template")' { + must "0 = derived-from-or-self(.,'template')" { error-message "The map-type must be other than " + "TE mapping template"; } description "Map type for the VN/Tunnel creation/ selection."; } uses te-types:generic-path-constraints; uses te-types:generic-path-optimization; description @@ -1292,27 +1292,26 @@ } } } 7.2. Service Models 7.2.1. ietf-l3sm-te-service-mapping - file "ietf-l3sm-te-service-mapping@2020-07-13.yang" + file "ietf-l3sm-te-service-mapping@2020-11-02.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 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"; } @@ -1346,24 +1345,23 @@ 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 { + revision 2020-11-02 { 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" { @@ -1388,21 +1386,21 @@ uses tsm-types:te-endpoint-ref; } //augment } 7.2.2. ietf-l2sm-te-service-mapping - file "ietf-l2sm-te-service-mapping@2020-07-13.yang" + file "ietf-l2sm-te-service-mapping@2020-11-02.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 tsm-types; reference "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; @@ -1443,24 +1441,23 @@ 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-07-13 { + revision 2020-11-02 { description "Initial revision."; - reference "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; } /* * Augmentation to L2SM */ augment "/l2vpn-svc:l2vpn-svc/l2vpn-svc:vpn-services/" + "l2vpn-svc:vpn-service" { @@ -1485,27 +1482,26 @@ uses tsm-types:te-endpoint-ref; } //augment } 7.2.3. ietf-l1csm-te-service-mapping - file "ietf-l1csm-te-service-mapping@2020-07-13.yang" + file "ietf-l1csm-te-service-mapping@2020-11-02.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 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)"; @@ -1540,24 +1536,23 @@ 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-07-13 { + revision 2020-11-02 { 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 @@ -1582,27 +1577,26 @@ //augment } 7.3. Network Models 7.3.1. ietf-l3nm-te-service-mapping - file "ietf-l3nm-te-service-mapping@2020-07-13.yang" + file "ietf-l3nm-te-service-mapping@2020-11-02.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"; } @@ -1636,21 +1630,21 @@ 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-07-13 { + revision 2020-11-02 { description "Initial revision."; reference "RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; } /* * Augmentation to L3NM */ @@ -1679,27 +1673,26 @@ uses tsm-types:te-endpoint-ref; } //augment } 7.3.2. ietf-l2nm-te-service-mapping - file "ietf-l2nm-te-service-mapping@2020-07-13.yang" + file "ietf-l2nm-te-service-mapping@2020-11-02.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.ietf-l2nm: A Layer 2 VPN Network YANG Model"; } @@ -1733,24 +1726,23 @@ 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-07-13 { + revision 2020-11-02 { 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-service" { @@ -1913,57 +1905,51 @@ 10. Acknowledgements We thank Diego Caviglia, and Igor Bryskin for useful discussions and motivation for this work. 11. References 11.1. Normative References [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-11 (work in - progress), March 2020. + Lee, Y., Lee, K., Zheng, H., Dios, O., and D. Ceccarelli, + "A YANG Data Model for L1 Connectivity Service Model + (L1CSM)", draft-ietf-ccamp-l1csm-yang-12 (work in + progress), September 2020. [I-D.ietf-opsawg-l2nm] - Barguil, S., Dios, O., Boucadair, M., Munoz, L., Jalil, + barguil, s., Dios, O., Boucadair, M., Munoz, L., Jalil, L., and J. Ma, "A Layer 2 VPN Network YANG Model", draft- ietf-opsawg-l2nm-00 (work in progress), July 2020. [I-D.ietf-opsawg-l3sm-l3nm] - Barguil, S., Dios, O., Boucadair, M., Munoz, L., and A. + barguil, s., Dios, O., Boucadair, M., Munoz, L., and A. Aguado, "A Layer 3 VPN Network YANG Model", draft-ietf- - opsawg-l3sm-l3nm-03 (work in progress), April 2020. + opsawg-l3sm-l3nm-05 (work in progress), October 2020. + + [I-D.ietf-spring-sr-policy-yang] + Raza, K., Sawaya, R., Shunwan, Z., Voyer, D., Durrani, M., + Matsushima, S., and V. Beeram, "YANG Data Model for + Segment Routing Policy", draft-ietf-spring-sr-policy- + yang-00 (work in progress), September 2020. [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-08 (work in progress), March 2020. + Yoon, "A YANG Data Model for VN Operation", draft-ietf- + teas-actn-vn-yang-09 (work in progress), July 2020. [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-23 (work in - progress), March 2020. - - [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.raza-spring-sr-policy-yang] - Raza, K., Sawaya, R., Shunwan, Z., Voyer, D., Durrani, M., - Matsushima, S., and V. Beeram, "YANG Data Model for - Segment Routing Policy", draft-raza-spring-sr-policy- - yang-02 (work in progress), November 2019. + "A YANG Data Model for Traffic Engineering Tunnels, Label + Switched Paths and Interfaces", draft-ietf-teas-yang-te-25 + (work in progress), July 2020. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, . @@ -2035,28 +2021,34 @@ [RFC8466] Wen, B., Fioccola, G., Ed., Xie, C., and L. Jalil, "A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery", RFC 8466, DOI 10.17487/RFC8466, October 2018, . [RFC8776] Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, "Common YANG Data Types for Traffic Engineering", RFC 8776, DOI 10.17487/RFC8776, June 2020, . + [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.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-05 (work in - progress), February 2020. + Networks", draft-ietf-teas-actn-yang-06 (work in + progress), August 2020. [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, . @@ -2099,28 +2091,35 @@ Oscar Gonzalez de Dios Telefonica EMail: oscar.gonzalezdedios@telefonica.com Carlo Perocchio Ericsson EMail: carlo.perocchio@ericsson.com + Kenichi Ogaki + KDDI + Email: ke-oogaki@kddi.com + Authors' Addresses Young Lee (editor) Samsung Electronics Email: younglee.tx@gmail.com Dhruv Dhody (editor) Huawei Technologies + Divyashree Techno Park, Whitefield + Bangalore, Karnataka 560066 + India Email: dhruv.ietf@gmail.com Giuseppe Fioccola Huawei Technologies Email: giuseppe.fioccola@huawei.com Qin Wu (editor) Huawei Technologies