draft-ietf-teas-te-service-mapping-yang-09.txt   draft-ietf-teas-te-service-mapping-yang-10.txt 
TEAS Working Group Y. Lee, Ed. TEAS Working Group Y. Lee, Ed.
Internet-Draft Samsung Electronics Internet-Draft Samsung Electronics
Intended status: Standards Track D. Dhody, Ed. Intended status: Standards Track D. Dhody, Ed.
Expires: 27 April 2022 G. Fioccola Expires: 8 September 2022 G. Fioccola
Q. Wu, Ed. Q. Wu, Ed.
Huawei Technologies Huawei Technologies
D. Ceccarelli D. Ceccarelli
Ericsson Ericsson
J. Tantsura J. Tantsura
Microsoft Microsoft
24 October 2021 7 March 2022
Traffic Engineering (TE) and Service Mapping YANG Model Traffic Engineering (TE) and Service Mapping YANG Model
draft-ietf-teas-te-service-mapping-yang-09 draft-ietf-teas-te-service-mapping-yang-10
Abstract Abstract
This document provides a YANG data model to map customer service This document provides a YANG data model to map customer service
models (e.g., the L3VPN Service Model (L3SM)) to Traffic Engineering models (e.g., the L3VPN Service Model (L3SM)) to Traffic Engineering
(TE) models (e.g., the TE Tunnel or the Virtual Network (VN) model). (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 These models are referred to as TE Service Mapping Model and are
applicable generically to the operator's need for seamless control applicable generically to the operator's need for seamless control
and management of their VPN services with underlying TE support. and management of their VPN services with underlying TE support.
skipping to change at page 1, line 46 skipping to change at page 1, line 46
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on 27 April 2022. This Internet-Draft will expire on 8 September 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2022 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text extracted from this document must include Revised BSD License text as
as described in Section 4.e of the Trust Legal Provisions and are described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License. provided without warranty as described in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Purpose of TE Service Mapping for Service Model . . . . . 4 1.1. Purpose of TE Service Mapping for Service Model . . . . . 4
1.2. Purpose of TE Service Mapping for Network Model . . . . . 5 1.2. Purpose of TE Service Mapping for Network Model . . . . . 5
1.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 6 1.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 6
1.4. Tree diagram . . . . . . . . . . . . . . . . . . . . . . 6 1.4. Tree diagram . . . . . . . . . . . . . . . . . . . . . . 6
1.5. Prefixes in Data Node Names . . . . . . . . . . . . . . . 6 1.5. Prefixes in Data Node Names . . . . . . . . . . . . . . . 6
2. TE and Service Related Parameters . . . . . . . . . . . . . . 8 2. TE and Service Related Parameters . . . . . . . . . . . . . . 8
skipping to change at page 2, line 43 skipping to change at page 2, line 43
3.2. TE and Network Models . . . . . . . . . . . . . . . . . . 11 3.2. TE and Network Models . . . . . . . . . . . . . . . . . . 11
4. L3VPN Architecture in the ACTN Context . . . . . . . . . . . 12 4. L3VPN Architecture in the ACTN Context . . . . . . . . . . . 12
4.1. Service Mapping . . . . . . . . . . . . . . . . . . . . . 16 4.1. Service Mapping . . . . . . . . . . . . . . . . . . . . . 16
4.2. Site Mapping . . . . . . . . . . . . . . . . . . . . . . 16 4.2. Site Mapping . . . . . . . . . . . . . . . . . . . . . . 16
5. Applicability of TE-Service Mapping in Generic context . . . 17 5. Applicability of TE-Service Mapping in Generic context . . . 17
6. YANG Data Trees . . . . . . . . . . . . . . . . . . . . . . . 17 6. YANG Data Trees . . . . . . . . . . . . . . . . . . . . . . . 17
6.1. Service Mapping Types . . . . . . . . . . . . . . . . . . 17 6.1. Service Mapping Types . . . . . . . . . . . . . . . . . . 17
6.2. Service Models . . . . . . . . . . . . . . . . . . . . . 18 6.2. Service Models . . . . . . . . . . . . . . . . . . . . . 18
6.2.1. L3SM . . . . . . . . . . . . . . . . . . . . . . . . 18 6.2.1. L3SM . . . . . . . . . . . . . . . . . . . . . . . . 18
6.2.2. L2SM . . . . . . . . . . . . . . . . . . . . . . . . 19 6.2.2. L2SM . . . . . . . . . . . . . . . . . . . . . . . . 19
6.2.3. L1CSM . . . . . . . . . . . . . . . . . . . . . . . . 20 6.2.3. L1CSM . . . . . . . . . . . . . . . . . . . . . . . . 21
6.3. Network Models . . . . . . . . . . . . . . . . . . . . . 21 6.3. Network Models . . . . . . . . . . . . . . . . . . . . . 21
6.3.1. L3NM . . . . . . . . . . . . . . . . . . . . . . . . 21 6.3.1. L3NM . . . . . . . . . . . . . . . . . . . . . . . . 22
6.3.2. L2NM . . . . . . . . . . . . . . . . . . . . . . . . 22 6.3.2. L2NM . . . . . . . . . . . . . . . . . . . . . . . . 22
7. YANG Data Models . . . . . . . . . . . . . . . . . . . . . . 23 7. YANG Data Models . . . . . . . . . . . . . . . . . . . . . . 23
7.1. ietf-te-service-mapping-types . . . . . . . . . . . . . . 23 7.1. ietf-te-service-mapping-types . . . . . . . . . . . . . . 23
7.2. Service Models . . . . . . . . . . . . . . . . . . . . . 32 7.2. Service Models . . . . . . . . . . . . . . . . . . . . . 32
7.2.1. ietf-l3sm-te-service-mapping . . . . . . . . . . . . 33 7.2.1. ietf-l3sm-te-service-mapping . . . . . . . . . . . . 32
7.2.2. ietf-l2sm-te-service-mapping . . . . . . . . . . . . 35 7.2.2. ietf-l2sm-te-service-mapping . . . . . . . . . . . . 35
7.2.3. ietf-l1csm-te-service-mapping . . . . . . . . . . . . 37 7.2.3. ietf-l1csm-te-service-mapping . . . . . . . . . . . . 37
7.3. Network Models . . . . . . . . . . . . . . . . . . . . . 39 7.3. Network Models . . . . . . . . . . . . . . . . . . . . . 39
7.3.1. ietf-l3nm-te-service-mapping . . . . . . . . . . . . 39 7.3.1. ietf-l3nm-te-service-mapping . . . . . . . . . . . . 39
7.3.2. ietf-l2nm-te-service-mapping . . . . . . . . . . . . 41 7.3.2. ietf-l2nm-te-service-mapping . . . . . . . . . . . . 41
8. Security Considerations . . . . . . . . . . . . . . . . . . . 43 8. Security Considerations . . . . . . . . . . . . . . . . . . . 43
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 44 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 44
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 46 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 46
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 46 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 46
11.1. Normative References . . . . . . . . . . . . . . . . . . 46 11.1. Normative References . . . . . . . . . . . . . . . . . . 46
11.2. Informative References . . . . . . . . . . . . . . . . . 49 11.2. Informative References . . . . . . . . . . . . . . . . . 49
Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 50 Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 50
Appendix B. Contributor Addresses . . . . . . . . . . . . . . . 52 Appendix B. Out of Scope . . . . . . . . . . . . . . . . . . . . 52
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 52 Appendix C. Contributor Addresses . . . . . . . . . . . . . . . 52
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 53
1. Introduction 1. Introduction
Data models are a representation of objects that can be configured or Data models are a representation of objects that can be configured or
monitored within a system. Within the IETF, YANG [RFC7950] is the monitored within a system. Within the IETF, YANG [RFC7950] is the
language of choice for documenting data models, and YANG models have language of choice for documenting data models, and YANG models have
been produced to allow configuration or modeling of a variety of been produced to allow configuration or modeling of a variety of
network devices, protocol instances, and network services. YANG data network devices, protocol instances, and network services. YANG data
models have been classified in [RFC8199] and [RFC8309]. models have been classified in [RFC8199] and [RFC8309].
skipping to change at page 11, line 16 skipping to change at page 11, line 16
The YANG module defined in this document supports three existing The YANG module defined in this document supports three existing
service models via augmenting while sharing the common TE and Service service models via augmenting while sharing the common TE and Service
Mapping Types. Mapping Types.
It is possible that new service models will be defined at some future 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 time and that it will be desirable to map them to underlying TE
constructs in the same way as the three existing models are constructs in the same way as the three existing models are
augmented. augmented.
Scheduling is currently out of scope, although an operator could use Appendix B higlights some some features that are deemed out of scope
their own scheduling mechanism on top of this YANG model. In future of this document.
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 3.2. TE and Network Models
The L2/L3 network models (L2NM, L3NM) are intended to describe a VPN The L2/L3 network models (L2NM, L3NM) are intended to describe a VPN
Service in the Service Provider Network. It contains information of Service in the Service Provider Network. It contains information of
the Service Provider network and might include allocated resources. the Service Provider network and might include allocated resources.
It can be used by network controllers to manage and control the VPN It can be used by network controllers to manage and control the VPN
Service configuration in the Service Provider network. Service configuration in the Service Provider network.
Similar to service model, the existing network models (i.e., Similar to service model, the existing network models (i.e.,
skipping to change at page 18, line 31 skipping to change at page 18, line 31
+--:(objective-function) +--:(objective-function)
{path-optimization-objective-function}? {path-optimization-objective-function}?
+--rw objective-function +--rw objective-function
+--rw objective-function-type? identityref +--rw objective-function-type? identityref
6.2. Service Models 6.2. Service Models
6.2.1. L3SM 6.2.1. L3SM
module: ietf-l3sm-te-service-mapping module: ietf-l3sm-te-service-mapping
augment /l3vpn-svc:l3vpn-svc/l3vpn-svc:vpn-services augment /l3vpn-svc:l3vpn-svc/l3vpn-svc:vpn-services
/l3vpn-svc:vpn-service: /l3vpn-svc:vpn-service:
+--rw te-service-mapping! +--rw te-service-mapping!
+--rw te-mapping +--rw te-mapping
+--rw map-type? identityref +--rw map-type? identityref
+--rw te-policy +--rw te-policy
| +--rw color? uint32 | +--rw color? uint32
| +--rw protection-type? identityref | +--rw protection-type? identityref
| +--rw availability-type? identityref | +--rw availability-type? identityref
+--rw (te)? +--rw (te)?
| +--:(vn) | +--:(vn)
| | +--rw vn* | | +--rw vn*
| | -> /vn:virtual-network/vn/vn-id | | -> /vn:virtual-network/vn/vn-id
| +--:(te-topo) | +--:(te-topo)
| | +--rw vn-topology-id? te-types:te-topology-id | | +--rw te-topology-identifier
| | | +--rw provider-id? te-global-id
| | | +--rw client-id? te-global-id
| | | +--rw topology-id? te-topology-id
| | +--rw abstract-node? | | +--rw abstract-node?
| | -> /nw:networks/network/node/node-id | | -> /nw:networks/network/node/node-id
| +--:(te-tunnel) | +--:(te-tunnel)
| +--rw te-tunnel* te:tunnel-ref | +--rw te-tunnel* te:tunnel-ref
| +--rw sr-policy* | +--rw sr-policy*
| [policy-color-ref policy-endpoint-ref] | [policy-color-ref policy-endpoint-ref]
| {sr-policy}? | {sr-policy}?
| +--rw policy-color-ref leafref | +--rw policy-color-ref leafref
| +--rw policy-endpoint-ref leafref | +--rw policy-endpoint-ref leafref
+--rw te-mapping-template-ref? +--rw te-mapping-template-ref?
-> /tsmt:te-mapping-templates/te-mapping-template/id -> /tsmt:te-mapping-templates/te-mapping-template/id
{template}? {template}?
augment /l3vpn-svc:l3vpn-svc/l3vpn-svc:sites/l3vpn-svc:site augment /l3vpn-svc:l3vpn-svc/l3vpn-svc:sites/l3vpn-svc:site
/l3vpn-svc:site-network-accesses /l3vpn-svc:site-network-accesses
skipping to change at page 19, line 42 skipping to change at page 19, line 46
/l3vpn-svc:class: /l3vpn-svc:class:
+--rw (te)? +--rw (te)?
+--:(vn) +--:(vn)
| +--rw vn-ap* -> /vn:access-point/ap/vn-ap/vn-ap-id | +--rw vn-ap* -> /vn:access-point/ap/vn-ap/vn-ap-id
+--:(te) +--:(te)
+--rw ltp? te-types:te-tp-id +--rw ltp? te-types:te-tp-id
6.2.2. L2SM 6.2.2. L2SM
module: ietf-l2sm-te-service-mapping module: ietf-l2sm-te-service-mapping
augment /l2vpn-svc:l2vpn-svc/l2vpn-svc:vpn-services augment /l2vpn-svc:l2vpn-svc/l2vpn-svc:vpn-services
/l2vpn-svc:vpn-service: /l2vpn-svc:vpn-service:
+--rw te-service-mapping! +--rw te-service-mapping!
+--rw te-mapping +--rw te-mapping
+--rw map-type? identityref +--rw map-type? identityref
+--rw te-policy +--rw te-policy
| +--rw color? uint32 | +--rw color? uint32
| +--rw protection-type? identityref | +--rw protection-type? identityref
| +--rw availability-type? identityref | +--rw availability-type? identityref
+--rw (te)? +--rw (te)?
| +--:(vn) | +--:(vn)
| | +--rw vn* | | +--rw vn*
| | -> /vn:virtual-network/vn/vn-id | | -> /vn:virtual-network/vn/vn-id
| +--:(te-topo) | +--:(te-topo)
| | +--rw vn-topology-id? te-types:te-topology-id | | +--rw te-topology-identifier
| | | +--rw provider-id? te-global-id
| | | +--rw client-id? te-global-id
| | | +--rw topology-id? te-topology-id
| | +--rw abstract-node? | | +--rw abstract-node?
| | -> /nw:networks/network/node/node-id | | -> /nw:networks/network/node/node-id
| +--:(te-tunnel) | +--:(te-tunnel)
| +--rw te-tunnel* te:tunnel-ref | +--rw te-tunnel* te:tunnel-ref
| +--rw sr-policy* | +--rw sr-policy*
| [policy-color-ref policy-endpoint-ref] | [policy-color-ref policy-endpoint-ref]
| {sr-policy}? | {sr-policy}?
| +--rw policy-color-ref leafref | +--rw policy-color-ref leafref
| +--rw policy-endpoint-ref leafref | +--rw policy-endpoint-ref leafref
+--rw te-mapping-template-ref? +--rw te-mapping-template-ref?
-> /tsmt:te-mapping-templates/te-mapping-template/id -> /tsmt:te-mapping-templates/te-mapping-template/id
{template}? {template}?
augment /l2vpn-svc:l2vpn-svc/l2vpn-svc:sites/l2vpn-svc:site augment /l2vpn-svc:l2vpn-svc/l2vpn-svc:sites/l2vpn-svc:site
/l2vpn-svc:site-network-accesses /l2vpn-svc:site-network-accesses
skipping to change at page 20, line 44 skipping to change at page 21, line 4
+--:(vn) +--:(vn)
| +--rw vn-ap* -> /vn:access-point/ap/vn-ap/vn-ap-id | +--rw vn-ap* -> /vn:access-point/ap/vn-ap/vn-ap-id
+--:(te) +--:(te)
+--rw ltp? te-types:te-tp-id +--rw ltp? te-types:te-tp-id
augment /l2vpn-svc:l2vpn-svc/l2vpn-svc:sites/l2vpn-svc:site augment /l2vpn-svc:l2vpn-svc/l2vpn-svc:sites/l2vpn-svc:site
/l2vpn-svc:site-network-accesses /l2vpn-svc:site-network-accesses
/l2vpn-svc:site-network-access/l2vpn-svc:service /l2vpn-svc:site-network-access/l2vpn-svc:service
/l2vpn-svc:qos/l2vpn-svc:qos-profile /l2vpn-svc:qos/l2vpn-svc:qos-profile
/l2vpn-svc:qos-profile/l2vpn-svc:custom/l2vpn-svc:classes /l2vpn-svc:qos-profile/l2vpn-svc:custom/l2vpn-svc:classes
/l2vpn-svc:class: /l2vpn-svc:class:
+--rw (te)? +--rw (te)?
+--:(vn) +--:(vn)
| +--rw vn-ap* -> /vn:access-point/ap/vn-ap/vn-ap-id | +--rw vn-ap* -> /vn:access-point/ap/vn-ap/vn-ap-id
+--:(te) +--:(te)
+--rw ltp? te-types:te-tp-id +--rw ltp? te-types:te-tp-id
6.2.3. L1CSM 6.2.3. L1CSM
module: ietf-l1csm-te-service-mapping module: ietf-l1csm-te-service-mapping
augment /l1csm:l1-connectivity/l1csm:services/l1csm:service: augment /l1csm:l1-connectivity/l1csm:services/l1csm:service:
+--rw te-service-mapping! +--rw te-service-mapping!
+--rw te-mapping +--rw te-mapping
+--rw map-type? identityref +--rw map-type? identityref
+--rw te-policy +--rw te-policy
| +--rw color? uint32 | +--rw color? uint32
| +--rw protection-type? identityref | +--rw protection-type? identityref
| +--rw availability-type? identityref | +--rw availability-type? identityref
+--rw (te)? +--rw (te)?
| +--:(vn) | +--:(vn)
| | +--rw vn* | | +--rw vn*
| | -> /vn:virtual-network/vn/vn-id | | -> /vn:virtual-network/vn/vn-id
| +--:(te-topo) | +--:(te-topo)
| | +--rw vn-topology-id? te-types:te-topology-id | | +--rw te-topology-identifier
| | | +--rw provider-id? te-global-id
| | | +--rw client-id? te-global-id
| | | +--rw topology-id? te-topology-id
| | +--rw abstract-node? | | +--rw abstract-node?
| | -> /nw:networks/network/node/node-id | | -> /nw:networks/network/node/node-id
| +--:(te-tunnel) | +--:(te-tunnel)
| +--rw te-tunnel* te:tunnel-ref | +--rw te-tunnel* te:tunnel-ref
| +--rw sr-policy* | +--rw sr-policy*
| [policy-color-ref policy-endpoint-ref] | [policy-color-ref policy-endpoint-ref]
| {sr-policy}? | {sr-policy}?
| +--rw policy-color-ref leafref | +--rw policy-color-ref leafref
| +--rw policy-endpoint-ref leafref | +--rw policy-endpoint-ref leafref
+--rw te-mapping-template-ref? +--rw te-mapping-template-ref?
-> /tsmt:te-mapping-templates/te-mapping-template/id -> /tsmt:te-mapping-templates/te-mapping-template/id
{template}? {template}?
augment /l1csm:l1-connectivity/l1csm:access/l1csm:unis/l1csm:uni: augment /l1csm:l1-connectivity/l1csm:access/l1csm:unis/l1csm:uni:
+--rw (te)? +--rw (te)?
skipping to change at page 21, line 39 skipping to change at page 22, line 4
-> /tsmt:te-mapping-templates/te-mapping-template/id -> /tsmt:te-mapping-templates/te-mapping-template/id
{template}? {template}?
augment /l1csm:l1-connectivity/l1csm:access/l1csm:unis/l1csm:uni: augment /l1csm:l1-connectivity/l1csm:access/l1csm:unis/l1csm:uni:
+--rw (te)? +--rw (te)?
+--:(vn) +--:(vn)
| +--rw vn-ap* -> /vn:access-point/ap/vn-ap/vn-ap-id | +--rw vn-ap* -> /vn:access-point/ap/vn-ap/vn-ap-id
+--:(te) +--:(te)
+--rw ltp? te-types:te-tp-id +--rw ltp? te-types:te-tp-id
6.3. Network Models 6.3. Network Models
6.3.1. L3NM 6.3.1. L3NM
module: ietf-l3nm-te-service-mapping module: ietf-l3nm-te-service-mapping
augment /l3vpn-ntw:l3vpn-ntw/l3vpn-ntw:vpn-services augment /l3vpn-ntw:l3vpn-ntw/l3vpn-ntw:vpn-services
/l3vpn-ntw:vpn-service: /l3vpn-ntw:vpn-service:
+--rw te-service-mapping! +--rw te-service-mapping!
+--rw te-mapping +--rw te-mapping
+--rw map-type? identityref +--rw map-type? identityref
+--rw te-policy +--rw te-policy
| +--rw color? uint32 | +--rw color? uint32
| +--rw protection-type? identityref | +--rw protection-type? identityref
| +--rw availability-type? identityref | +--rw availability-type? identityref
+--rw (te)? +--rw (te)?
| +--:(vn) | +--:(vn)
| | +--rw vn* | | +--rw vn*
| | -> /vn:virtual-network/vn/vn-id | | -> /vn:virtual-network/vn/vn-id
| +--:(te-topo) | +--:(te-topo)
| | +--rw vn-topology-id? te-types:te-topology-id | | +--rw te-topology-identifier
| | | +--rw provider-id? te-global-id
| | | +--rw client-id? te-global-id
| | | +--rw topology-id? te-topology-id
| | +--rw abstract-node? | | +--rw abstract-node?
| | -> /nw:networks/network/node/node-id | | -> /nw:networks/network/node/node-id
| +--:(te-tunnel) | +--:(te-tunnel)
| +--rw te-tunnel* te:tunnel-ref | +--rw te-tunnel* te:tunnel-ref
| +--rw sr-policy* | +--rw sr-policy*
| [policy-color-ref policy-endpoint-ref] | [policy-color-ref policy-endpoint-ref]
| {sr-policy}? | {sr-policy}?
| +--rw policy-color-ref leafref | +--rw policy-color-ref leafref
| +--rw policy-endpoint-ref leafref | +--rw policy-endpoint-ref leafref
+--rw te-mapping-template-ref? +--rw te-mapping-template-ref?
-> /tsmt:te-mapping-templates/te-mapping-template/id -> /tsmt:te-mapping-templates/te-mapping-template/id
{template}? {template}?
augment /l3vpn-ntw:l3vpn-ntw/l3vpn-ntw:vpn-services augment /l3vpn-ntw:l3vpn-ntw/l3vpn-ntw:vpn-services
/l3vpn-ntw:vpn-service/l3vpn-ntw:vpn-nodes /l3vpn-ntw:vpn-service/l3vpn-ntw:vpn-nodes
skipping to change at page 23, line 5 skipping to change at page 23, line 5
/l3vpn-ntw:vpn-node/l3vpn-ntw:vpn-network-accesses /l3vpn-ntw:vpn-node/l3vpn-ntw:vpn-network-accesses
/l3vpn-ntw:vpn-network-access: /l3vpn-ntw:vpn-network-access:
+--rw (te)? +--rw (te)?
+--:(vn) +--:(vn)
| +--rw vn-ap* -> /vn:access-point/ap/vn-ap/vn-ap-id | +--rw vn-ap* -> /vn:access-point/ap/vn-ap/vn-ap-id
+--:(te) +--:(te)
+--rw ltp? te-types:te-tp-id +--rw ltp? te-types:te-tp-id
6.3.2. L2NM 6.3.2. L2NM
module: ietf-l2nm-te-service-mapping module: ietf-l2nm-te-service-mapping
augment /l2vpn-ntw:l2vpn-ntw/l2vpn-ntw:vpn-services augment /l2vpn-ntw:l2vpn-ntw/l2vpn-ntw:vpn-services
/l2vpn-ntw:vpn-service: /l2vpn-ntw:vpn-service:
+--rw te-service-mapping! +--rw te-service-mapping!
+--rw te-mapping +--rw te-mapping
+--rw map-type? identityref +--rw map-type? identityref
+--rw te-policy +--rw te-policy
| +--rw color? uint32 | +--rw color? uint32
| +--rw protection-type? identityref | +--rw protection-type? identityref
| +--rw availability-type? identityref | +--rw availability-type? identityref
+--rw (te)? +--rw (te)?
| +--:(vn) | +--:(vn)
| | +--rw vn* | | +--rw vn*
| | -> /vn:virtual-network/vn/vn-id | | -> /vn:virtual-network/vn/vn-id
| +--:(te-topo) | +--:(te-topo)
| | +--rw vn-topology-id? te-types:te-topology-id | | +--rw te-topology-identifier
| | | +--rw provider-id? te-global-id
| | | +--rw client-id? te-global-id
| | | +--rw topology-id? te-topology-id
| | +--rw abstract-node? | | +--rw abstract-node?
| | -> /nw:networks/network/node/node-id | | -> /nw:networks/network/node/node-id
| +--:(te-tunnel) | +--:(te-tunnel)
| +--rw te-tunnel* te:tunnel-ref | +--rw te-tunnel* te:tunnel-ref
| +--rw sr-policy* | +--rw sr-policy*
| [policy-color-ref policy-endpoint-ref] | [policy-color-ref policy-endpoint-ref]
| {sr-policy}? | {sr-policy}?
| +--rw policy-color-ref leafref | +--rw policy-color-ref leafref
| +--rw policy-endpoint-ref leafref | +--rw policy-endpoint-ref leafref
+--rw te-mapping-template-ref? +--rw te-mapping-template-ref?
-> /tsmt:te-mapping-templates/te-mapping-template/id -> /tsmt:te-mapping-templates/te-mapping-template/id
{template}? {template}?
augment /l2vpn-ntw:l2vpn-ntw/l2vpn-ntw:vpn-services augment /l2vpn-ntw:l2vpn-ntw/l2vpn-ntw:vpn-services
/l2vpn-ntw:vpn-service/l2vpn-ntw:vpn-nodes /l2vpn-ntw:vpn-service/l2vpn-ntw:vpn-nodes
skipping to change at page 24, line 4 skipping to change at page 24, line 4
+--:(vn) +--:(vn)
| +--rw vn-ap* -> /vn:access-point/ap/vn-ap/vn-ap-id | +--rw vn-ap* -> /vn:access-point/ap/vn-ap/vn-ap-id
+--:(te) +--:(te)
+--rw ltp? te-types:te-tp-id +--rw ltp? te-types:te-tp-id
7. YANG Data Models 7. YANG Data Models
The YANG codes are as follows: The YANG codes are as follows:
7.1. ietf-te-service-mapping-types 7.1. ietf-te-service-mapping-types
<CODE BEGINS> file "ietf-te-service-mapping-types@2021-10-24.yang" <CODE BEGINS> file "ietf-te-service-mapping-types@2022-03-07.yang"
module ietf-te-service-mapping-types { module ietf-te-service-mapping-types {
yang-version 1.1; yang-version 1.1;
namespace namespace
"urn:ietf:params:xml:ns:yang:ietf-te-service-mapping-types"; "urn:ietf:params:xml:ns:yang:ietf-te-service-mapping-types";
prefix tsmt; prefix tsmt;
/* Import te-types */ /* Import te-types */
import ietf-te-types { import ietf-te-types {
prefix te-types; prefix te-types;
skipping to change at page 25, line 17 skipping to change at page 25, line 17
prefix sr-policy; prefix sr-policy;
reference reference
"I-D.ietf-spring-sr-policy-yang: YANG Data Model for Segment "I-D.ietf-spring-sr-policy-yang: YANG Data Model for Segment
Routing Policy"; Routing Policy";
} }
organization organization
"IETF Traffic Engineering Architecture and Signaling (TEAS) "IETF Traffic Engineering Architecture and Signaling (TEAS)
Working Group"; Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/teas/> "WG Web: <https://datatracker.ietf.org/wg/teas/about/>
WG List: <mailto:teas@ietf.org> WG List: <mailto:teas@ietf.org>
Editor: Young Lee Editor: Young Lee
<mailto:younglee.tx@gmail.com> <mailto:younglee.tx@gmail.com>
Editor: Dhruv Dhody Editor: Dhruv Dhody
<mailto:dhruv.ietf@gmail.com> <mailto:dhruv.ietf@gmail.com>
Editor: Qin Wu Editor: Qin Wu
<mailto:bill.wu@huawei.com>"; <mailto:bill.wu@huawei.com>";
description description
"This module contains a YANG module for TE & Service mapping "This module contains a YANG module for TE & Service mapping
parameters and policies as a common grouping applicable to parameters and policies as a common grouping applicable to
variuous service models (e.g., L1CSM, L2SM, L3SM, etc.) variuous service models (e.g., L1CSM, L2SM, L3SM, etc.)
Copyright (c) 2021 IETF Trust and the persons identified as Copyright (c) 2022 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Revised BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the 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 2021-10-24 { revision 2022-03-07 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; "RFC XXXX: Traffic Engineering and Service Mapping Yang Model";
} }
/* /*
* Features * Features
*/ */
skipping to change at page 28, line 47 skipping to change at page 28, line 47
path "/vn:virtual-network/vn:vn/vn:vn-id"; path "/vn:virtual-network/vn:vn/vn:vn-id";
} }
description description
"The reference to VN"; "The reference to VN";
reference reference
"RFC 8453: Framework for Abstraction and Control of TE "RFC 8453: Framework for Abstraction and Control of TE
Networks (ACTN)"; Networks (ACTN)";
} }
} }
case te-topo { case te-topo {
leaf vn-topology-id { /*An identifier to the TE Topology Model where the abstract
type te-types:te-topology-id; nodes and links of the Topology can be found for Type 2
description VNs as defined in RFC 8453*/
"An identifier to the TE Topology Model where the abstract uses te-types:te-topology-identifier;
nodes and links of the Topology can be found for Type 2
VNs as defined in RFC 8453";
reference
"RFC 8795: YANG Data Model for Traffic Engineering (TE)
Topologies
RFC 8453: Framework for Abstraction and Control of TE
Networks (ACTN)";
}
leaf abstract-node { leaf abstract-node {
type leafref { type leafref {
path "/nw:networks/nw:network/nw:node/nw:node-id"; path "/nw:networks/nw:network/nw:node/nw:node-id";
} }
description description
"A reference to the abstract node in TE Topology"; "A reference to the abstract node in TE Topology";
reference reference
"RFC 8795: YANG Data Model for Traffic Engineering (TE) "RFC 8795: YANG Data Model for Traffic Engineering (TE)
Topologies"; Topologies";
} }
skipping to change at page 29, line 33 skipping to change at page 29, line 25
leaf-list te-tunnel { leaf-list te-tunnel {
type te:tunnel-ref; type te:tunnel-ref;
description description
"Reference to TE Tunnels"; "Reference to TE Tunnels";
reference reference
"I-D.ietf-teas-yang-te: A YANG Data Model for Traffic "I-D.ietf-teas-yang-te: A YANG Data Model for Traffic
Engineering Tunnels and Interfaces"; Engineering Tunnels and Interfaces";
} }
list sr-policy { list sr-policy {
if-feature "sr-policy"; if-feature "sr-policy";
/*Headend should also be there!*/
key "policy-color-ref policy-endpoint-ref"; key "policy-color-ref policy-endpoint-ref";
description description
"SR Policy"; "SR Policy";
leaf policy-color-ref { leaf policy-color-ref {
type leafref { type leafref {
path path
"/rt:routing/sr-policy:segment-routing" "/rt:routing/sr-policy:segment-routing"
+ "/sr-policy:traffic-engineering/sr-policy:policies" + "/sr-policy:traffic-engineering/sr-policy:policies"
+ "/sr-policy:policy/sr-policy:color"; + "/sr-policy:policy/sr-policy:color";
} }
skipping to change at page 33, line 4 skipping to change at page 32, line 43
uses te-types:generic-path-constraints; uses te-types:generic-path-constraints;
uses te-types:generic-path-optimization; uses te-types:generic-path-optimization;
description description
"List for templates."; "List for templates.";
} }
} }
} }
<CODE ENDS> <CODE ENDS>
7.2. Service Models 7.2. Service Models
7.2.1. ietf-l3sm-te-service-mapping 7.2.1. ietf-l3sm-te-service-mapping
<CODE BEGINS> file "ietf-l3sm-te-service-mapping@2021-10-24.yang" <CODE BEGINS> file "ietf-l3sm-te-service-mapping@2022-03-07.yang"
module ietf-l3sm-te-service-mapping { module ietf-l3sm-te-service-mapping {
yang-version 1.1; yang-version 1.1;
namespace namespace
"urn:ietf:params:xml:ns:yang:ietf-l3sm-te-service-mapping"; "urn:ietf:params:xml:ns:yang:ietf-l3sm-te-service-mapping";
prefix l3-tsm; prefix l3-tsm;
import ietf-te-service-mapping-types { import ietf-te-service-mapping-types {
prefix tsmt; prefix tsmt;
reference reference
"RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; "RFC XXXX: Traffic Engineering and Service Mapping Yang Model";
} }
import ietf-l3vpn-svc { import ietf-l3vpn-svc {
prefix l3vpn-svc; prefix l3vpn-svc;
reference reference
"RFC 8299: YANG Data Model for L3VPN Service Delivery"; "RFC 8299: YANG Data Model for L3VPN Service Delivery";
} }
skipping to change at page 33, line 28 skipping to change at page 33, line 19
import ietf-l3vpn-svc { import ietf-l3vpn-svc {
prefix l3vpn-svc; prefix l3vpn-svc;
reference reference
"RFC 8299: YANG Data Model for L3VPN Service Delivery"; "RFC 8299: YANG Data Model for L3VPN Service Delivery";
} }
organization organization
"IETF Traffic Engineering Architecture and Signaling (TEAS) "IETF Traffic Engineering Architecture and Signaling (TEAS)
Working Group"; Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/teas/> "WG Web: <https://datatracker.ietf.org/wg/teas/about/>
WG List: <mailto:teas@ietf.org> WG List: <mailto:teas@ietf.org>
Editor: Young Lee Editor: Young Lee
<mailto:younglee.tx@gmail.com> <mailto:younglee.tx@gmail.com>
Editor: Dhruv Dhody Editor: Dhruv Dhody
<mailto:dhruv.ietf@gmail.com> <mailto:dhruv.ietf@gmail.com>
Editor: Qin Wu Editor: Qin Wu
<mailto:bill.wu@huawei.com>"; <mailto:bill.wu@huawei.com>";
description description
"This module contains a YANG module for the mapping of Layer 3 "This module contains a YANG module for the mapping of Layer 3
Service Model (L3SM) to the TE and VN. Service Model (L3SM) to the TE and VN.
Copyright (c) 2021 IETF Trust and the persons identified as Copyright (c) 2022 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Revised BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the 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 2021-10-24 { revision 2022-03-07 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; "RFC XXXX: Traffic Engineering and Service Mapping Yang Model";
} }
/* /*
* Augmentation to L3SM * Augmentation to L3SM
*/ */
augment "/l3vpn-svc:l3vpn-svc/l3vpn-svc:vpn-services" augment "/l3vpn-svc:l3vpn-svc/l3vpn-svc:vpn-services"
+ "/l3vpn-svc:vpn-service" { + "/l3vpn-svc:vpn-service" {
description description
"L3SM augmented to include TE parameters and mapping"; "L3SM augmented to include TE parameters and mapping";
container te-service-mapping { container te-service-mapping {
presence "Indicates L3 service to TE mapping"; presence "Indicates L3 service to TE mapping";
skipping to change at page 35, line 20 skipping to change at page 35, line 12
description description
"This augment is for per-class in site-network-access for custom "This augment is for per-class in site-network-access for custom
QoS profile"; QoS profile";
uses tsmt:te-endpoint-ref; uses tsmt:te-endpoint-ref;
} }
} }
<CODE ENDS> <CODE ENDS>
7.2.2. ietf-l2sm-te-service-mapping 7.2.2. ietf-l2sm-te-service-mapping
<CODE BEGINS> file "ietf-l2sm-te-service-mapping@2021-10-24.yang" <CODE BEGINS> file "ietf-l2sm-te-service-mapping@2022-03-07.yang"
module ietf-l2sm-te-service-mapping { module ietf-l2sm-te-service-mapping {
yang-version 1.1; yang-version 1.1;
namespace namespace
"urn:ietf:params:xml:ns:yang:ietf-l2sm-te-service-mapping"; "urn:ietf:params:xml:ns:yang:ietf-l2sm-te-service-mapping";
prefix l2-tsm; prefix l2-tsm;
import ietf-te-service-mapping-types { import ietf-te-service-mapping-types {
prefix tsmt; prefix tsmt;
reference reference
"RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; "RFC XXXX: Traffic Engineering and Service Mapping Yang Model";
skipping to change at page 35, line 43 skipping to change at page 35, line 35
prefix l2vpn-svc; prefix l2vpn-svc;
reference reference
"RFC 8466: A YANG Data Model for Layer 2 Virtual Private Network "RFC 8466: A YANG Data Model for Layer 2 Virtual Private Network
(L2VPN) Service Delivery"; (L2VPN) Service Delivery";
} }
organization organization
"IETF Traffic Engineering Architecture and Signaling (TEAS) "IETF Traffic Engineering Architecture and Signaling (TEAS)
Working Group"; Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/teas/> "WG Web: <https://datatracker.ietf.org/wg/teas/about/>
WG List: <mailto:teas@ietf.org> WG List: <mailto:teas@ietf.org>
Editor: Young Lee Editor: Young Lee
<mailto:younglee.tx@gmail.com> <mailto:younglee.tx@gmail.com>
Editor: Dhruv Dhody Editor: Dhruv Dhody
<mailto:dhruv.ietf@gmail.com> <mailto:dhruv.ietf@gmail.com>
Editor: Qin Wu Editor: Qin Wu
<mailto:bill.wu@huawei.com>"; <mailto:bill.wu@huawei.com>";
description description
"This module contains a YANG module for the mapping of Layer 2 "This module contains a YANG module for the mapping of Layer 2
Service Model (L2SM) to the TE and VN. Service Model (L2SM) to the TE and VN.
Copyright (c) 2021 IETF Trust and the persons identified as Copyright (c) 2022 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Revised BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the 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 2021-10-24 { revision 2022-03-07 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; "RFC XXXX: Traffic Engineering and Service Mapping Yang Model";
} }
/* /*
* Augmentation to L2SM * Augmentation to L2SM
*/ */
skipping to change at page 37, line 40 skipping to change at page 37, line 32
description description
"This augment is for per-class in site-network-access for custom "This augment is for per-class in site-network-access for custom
QoS profile"; QoS profile";
uses tsmt:te-endpoint-ref; uses tsmt:te-endpoint-ref;
} }
} }
<CODE ENDS> <CODE ENDS>
7.2.3. ietf-l1csm-te-service-mapping 7.2.3. ietf-l1csm-te-service-mapping
<CODE BEGINS> file "ietf-l1csm-te-service-mapping@2021-10-24.yang" <CODE BEGINS> file "ietf-l1csm-te-service-mapping@2022-03-07.yang"
module ietf-l1csm-te-service-mapping { module ietf-l1csm-te-service-mapping {
yang-version 1.1; yang-version 1.1;
namespace namespace
"urn:ietf:params:xml:ns:yang:ietf-l1csm-te-service-mapping"; "urn:ietf:params:xml:ns:yang:ietf-l1csm-te-service-mapping";
prefix l1-tsm; prefix l1-tsm;
import ietf-te-service-mapping-types { import ietf-te-service-mapping-types {
prefix tsmt; prefix tsmt;
reference reference
"RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; "RFC XXXX: Traffic Engineering and Service Mapping Yang Model";
skipping to change at page 38, line 14 skipping to change at page 38, line 7
prefix l1csm; prefix l1csm;
reference reference
"I-D.ietf-ccamp-l1csm-yang: A YANG Data Model for L1 Connectivity "I-D.ietf-ccamp-l1csm-yang: A YANG Data Model for L1 Connectivity
Service Model (L1CSM)"; Service Model (L1CSM)";
} }
organization organization
"IETF Traffic Engineering Architecture and Signaling (TEAS) "IETF Traffic Engineering Architecture and Signaling (TEAS)
Working Group"; Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/teas/> "WG Web: <https://datatracker.ietf.org/wg/teas/about/>
WG List: <mailto:teas@ietf.org> WG List: <mailto:teas@ietf.org>
Editor: Young Lee Editor: Young Lee
<mailto:younglee.tx@gmail.com> <mailto:younglee.tx@gmail.com>
Editor: Dhruv Dhody Editor: Dhruv Dhody
<mailto:dhruv.ietf@gmail.com> <mailto:dhruv.ietf@gmail.com>
Editor: Qin Wu Editor: Qin Wu
<mailto:bill.wu@huawei.com>"; <mailto:bill.wu@huawei.com>";
description description
"This module contains a YANG module for the mapping of "This module contains a YANG module for the mapping of
Layer 1 Connectivity Service Module (L1CSM) to the TE and VN Layer 1 Connectivity Service Module (L1CSM) to the TE and VN
Copyright (c) 2021 IETF Trust and the persons identified as Copyright (c) 2022 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Revised BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the 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 2021-10-24 { revision 2022-03-07 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; "RFC XXXX: Traffic Engineering and Service Mapping Yang Model";
} }
/* /*
* Augmentation to L1CSM * Augmentation to L1CSM
*/ */
skipping to change at page 39, line 32 skipping to change at page 39, line 26
} }
//augment //augment
} }
<CODE ENDS> <CODE ENDS>
7.3. Network Models 7.3. Network Models
7.3.1. ietf-l3nm-te-service-mapping 7.3.1. ietf-l3nm-te-service-mapping
<CODE BEGINS> file "ietf-l3nm-te-service-mapping@2021-10-24.yang" <CODE BEGINS> file "ietf-l3nm-te-service-mapping@2022-03-07.yang"
module ietf-l3nm-te-service-mapping { module ietf-l3nm-te-service-mapping {
yang-version 1.1; yang-version 1.1;
namespace namespace
"urn:ietf:params:xml:ns:yang:ietf-l3nm-te-service-mapping"; "urn:ietf:params:xml:ns:yang:ietf-l3nm-te-service-mapping";
prefix l3nm-tsm; prefix l3nm-tsm;
import ietf-te-service-mapping-types { import ietf-te-service-mapping-types {
prefix tsmt; prefix tsmt;
reference reference
"RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; "RFC XXXX: Traffic Engineering and Service Mapping Yang Model";
skipping to change at page 40, line 6 skipping to change at page 39, line 48
import ietf-l3vpn-ntw { import ietf-l3vpn-ntw {
prefix l3vpn-ntw; prefix l3vpn-ntw;
reference reference
"I-D.ietf-opsawg-l3sm-l3nm: A Layer 3 VPN Network YANG Model"; "I-D.ietf-opsawg-l3sm-l3nm: A Layer 3 VPN Network YANG Model";
} }
organization organization
"IETF Traffic Engineering Architecture and Signaling (TEAS) "IETF Traffic Engineering Architecture and Signaling (TEAS)
Working Group"; Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/teas/> "WG Web: <https://datatracker.ietf.org/wg/teas/about/>
WG List: <mailto:teas@ietf.org> WG List: <mailto:teas@ietf.org>
Editor: Young Lee Editor: Young Lee
<mailto:younglee.tx@gmail.com> <mailto:younglee.tx@gmail.com>
Editor: Dhruv Dhody Editor: Dhruv Dhody
<mailto:dhruv.ietf@gmail.com> <mailto:dhruv.ietf@gmail.com>
Editor: Qin Wu Editor: Qin Wu
<mailto:bill.wu@huawei.com>"; <mailto:bill.wu@huawei.com>";
description description
"This module contains a YANG module for the mapping of Layer 3 "This module contains a YANG module for the mapping of Layer 3
Network Model (L3NM) to the TE and VN. Network Model (L3NM) to the TE and VN.
Copyright (c) 2021 IETF Trust and the persons identified as Copyright (c) 2022 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Revised BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the 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 2021-10-24 { revision 2022-03-07 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; "RFC XXXX: Traffic Engineering and Service Mapping Yang Model";
} }
/* /*
* Augmentation to L3NM * Augmentation to L3NM
*/ */
skipping to change at page 41, line 26 skipping to change at page 41, line 19
to TE endpoints when underlying TE is used"; to TE endpoints when underlying TE is used";
uses tsmt:te-endpoint-ref; uses tsmt:te-endpoint-ref;
} }
//augment //augment
} }
<CODE ENDS> <CODE ENDS>
7.3.2. ietf-l2nm-te-service-mapping 7.3.2. ietf-l2nm-te-service-mapping
<CODE BEGINS> file "ietf-l2nm-te-service-mapping@2021-10-24.yang" <CODE BEGINS> file "ietf-l2nm-te-service-mapping@2022-03-07.yang"
module ietf-l2nm-te-service-mapping { module ietf-l2nm-te-service-mapping {
yang-version 1.1; yang-version 1.1;
namespace namespace
"urn:ietf:params:xml:ns:yang:ietf-l2nm-te-service-mapping"; "urn:ietf:params:xml:ns:yang:ietf-l2nm-te-service-mapping";
prefix l2nm-tsm; prefix l2nm-tsm;
import ietf-te-service-mapping-types { import ietf-te-service-mapping-types {
prefix tsmt; prefix tsmt;
reference reference
"RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; "RFC XXXX: Traffic Engineering and Service Mapping Yang Model";
skipping to change at page 41, line 48 skipping to change at page 41, line 41
import ietf-l2vpn-ntw { import ietf-l2vpn-ntw {
prefix l2vpn-ntw; prefix l2vpn-ntw;
reference reference
"I-D.ietf-opsawg-l2nm: A Layer 2 VPN Network YANG Model"; "I-D.ietf-opsawg-l2nm: A Layer 2 VPN Network YANG Model";
} }
organization organization
"IETF Traffic Engineering Architecture and Signaling (TEAS) "IETF Traffic Engineering Architecture and Signaling (TEAS)
Working Group"; Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/teas/> "WG Web: <https://datatracker.ietf.org/wg/teas/about/>
WG List: <mailto:teas@ietf.org> WG List: <mailto:teas@ietf.org>
Editor: Young Lee Editor: Young Lee
<mailto:younglee.tx@gmail.com> <mailto:younglee.tx@gmail.com>
Editor: Dhruv Dhody Editor: Dhruv Dhody
<mailto:dhruv.ietf@gmail.com> <mailto:dhruv.ietf@gmail.com>
Editor: Qin Wu Editor: Qin Wu
<mailto:bill.wu@huawei.com>"; <mailto:bill.wu@huawei.com>";
description description
"This module contains a YANG module for the mapping of Layer 2 "This module contains a YANG module for the mapping of Layer 2
Network Model (L2NM) to the TE and VN. Network Model (L2NM) to the TE and VN.
Copyright (c) 2021 IETF Trust and the persons identified as Copyright (c) 2022 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Revised BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the 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 2021-10-24 { revision 2022-03-07 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; "RFC XXXX: Traffic Engineering and Service Mapping Yang Model";
} }
/* /*
* Augmentation to L2NM * Augmentation to L2NM
*/ */
skipping to change at page 46, line 47 skipping to change at page 46, line 47
motivation for this work. motivation for this work.
11. References 11. References
11.1. Normative References 11.1. Normative References
[I-D.ietf-ccamp-l1csm-yang] [I-D.ietf-ccamp-l1csm-yang]
Lee, Y., Lee, K., Zheng, H., Dios, O. G. D., and D. Lee, Y., Lee, K., Zheng, H., Dios, O. G. D., and D.
Ceccarelli, "A YANG Data Model for L1 Connectivity Service Ceccarelli, "A YANG Data Model for L1 Connectivity Service
Model (L1CSM)", Work in Progress, Internet-Draft, draft- Model (L1CSM)", Work in Progress, Internet-Draft, draft-
ietf-ccamp-l1csm-yang-15, 8 September 2021, ietf-ccamp-l1csm-yang-16, 13 December 2021,
<https://datatracker.ietf.org/doc/html/draft-ietf-ccamp- <https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-
l1csm-yang-15>. l1csm-yang-16>.
[I-D.ietf-opsawg-l2nm] [I-D.ietf-opsawg-l2nm]
Barguil, S., Dios, O. G. D., Boucadair, M., and L. A. Barguil, S., Dios, O. G. D., Boucadair, M., and L. A.
Munoz, "A Layer 2 VPN Network YANG Model", Work in Munoz, "A Layer 2 VPN Network YANG Model", Work in
Progress, Internet-Draft, draft-ietf-opsawg-l2nm-09, 20 Progress, Internet-Draft, draft-ietf-opsawg-l2nm-12, 22
October 2021, <https://datatracker.ietf.org/doc/html/ November 2021, <https://datatracker.ietf.org/doc/html/
draft-ietf-opsawg-l2nm-09>. draft-ietf-opsawg-l2nm-12>.
[I-D.ietf-opsawg-l3sm-l3nm] [I-D.ietf-opsawg-l3sm-l3nm]
Barguil, S., Dios, O. G. D., Boucadair, M., Munoz, L. A., Barguil, S., Dios, O. G. D., Boucadair, M., Munoz, L. A.,
and A. Aguado, "A Layer 3 VPN Network YANG Model", Work in and A. Aguado, "A YANG Network Data Model for Layer 3
Progress, Internet-Draft, draft-ietf-opsawg-l3sm-l3nm-18, VPNs", Work in Progress, Internet-Draft, draft-ietf-
8 October 2021, <https://datatracker.ietf.org/doc/html/ opsawg-l3sm-l3nm-18, 8 October 2021,
draft-ietf-opsawg-l3sm-l3nm-18>. <https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-
l3sm-l3nm-18>.
[I-D.ietf-spring-sr-policy-yang] [I-D.ietf-spring-sr-policy-yang]
Raza, K., Sawaya, R., Shunwan, Z., Voyer, D., Durrani, M., Raza, K., Sawaya, R., Shunwan, Z., Voyer, D., Durrani, M.,
Matsushima, S., and V. P. Beeram, "YANG Data Model for Matsushima, S., and V. P. Beeram, "YANG Data Model for
Segment Routing Policy", Work in Progress, Internet-Draft, Segment Routing Policy", Work in Progress, Internet-Draft,
draft-ietf-spring-sr-policy-yang-01, 7 April 2021, draft-ietf-spring-sr-policy-yang-01, 7 April 2021,
<https://datatracker.ietf.org/doc/html/draft-ietf-spring- <https://datatracker.ietf.org/doc/html/draft-ietf-spring-
sr-policy-yang-01>. sr-policy-yang-01>.
[I-D.ietf-teas-actn-vn-yang] [I-D.ietf-teas-actn-vn-yang]
Lee, Y., Dhody, D., Ceccarelli, D., Bryskin, I., and B. Y. Lee, Y., Dhody, D., Ceccarelli, D., Bryskin, I., and B. Y.
Yoon, "A YANG Data Model for VN Operation", Work in Yoon, "A YANG Data Model for VN Operation", Work in
Progress, Internet-Draft, draft-ietf-teas-actn-vn-yang-13, Progress, Internet-Draft, draft-ietf-teas-actn-vn-yang-14,
23 October 2021, <https://datatracker.ietf.org/doc/html/ 7 March 2022, <https://datatracker.ietf.org/doc/html/
draft-ietf-teas-actn-vn-yang-13>. draft-ietf-teas-actn-vn-yang-14>.
[I-D.ietf-teas-yang-te] [I-D.ietf-teas-yang-te]
Saad, T., Gandhi, R., Liu, X., Beeram, V. P., Bryskin, I., Saad, T., Gandhi, R., Liu, X., Beeram, V. P., Bryskin, I.,
and O. G. D. Dios, "A YANG Data Model for Traffic and O. G. D. Dios, "A YANG Data Model for Traffic
Engineering Tunnels, Label Switched Paths and Interfaces", Engineering Tunnels, Label Switched Paths and Interfaces",
Work in Progress, Internet-Draft, draft-ietf-teas-yang-te- Work in Progress, Internet-Draft, draft-ietf-teas-yang-te-
27, 8 July 2021, <https://datatracker.ietf.org/doc/html/ 29, 7 February 2022,
draft-ietf-teas-yang-te-27>. <https://datatracker.ietf.org/doc/html/draft-ietf-teas-
yang-te-29>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/info/rfc6020>. <https://www.rfc-editor.org/info/rfc6020>.
skipping to change at page 52, line 5 skipping to change at page 52, line 5
</te-service-mapping> </te-service-mapping>
</vpn-service> </vpn-service>
</vpn-services> </vpn-services>
</l2vpn-svc> </l2vpn-svc>
Example 4: A VPN service may want different optimization criteria for 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 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 it can be achieved by creating the TE resources separately and then
mapping them to the service. mapping them to the service.
Appendix B. Contributor Addresses Appendix B. Out of Scope
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]).
Appendix C. Contributor Addresses
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
EMail: adrian@olddog.co.uk EMail: adrian@olddog.co.uk
Italo Busi Italo Busi
Huawei Technologies Huawei Technologies
EMail: Italo.Busi@huawei.com EMail: Italo.Busi@huawei.com
 End of changes. 82 change blocks. 
99 lines changed or deleted 122 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/