draft-ietf-teas-te-service-mapping-yang-04.txt   draft-ietf-teas-te-service-mapping-yang-05.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: January 14, 2021 G. Fioccola Expires: May 6, 2021 G. Fioccola
Q. Wu, Ed. Q. Wu, Ed.
Huawei Technologies Huawei Technologies
D. Ceccarelli D. Ceccarelli
Ericsson Ericsson
J. Tantsura J. Tantsura
Apstra Apstra
July 13, 2020 November 2, 2020
Traffic Engineering (TE) and Service Mapping Yang Model 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 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).
This model is referred to as TE Service Mapping Model and is This model is referred to as TE Service Mapping Model and is
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 TE tunnel support. and management of their VPN services with TE tunnel 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 January 14, 2021. This Internet-Draft will expire on May 6, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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 Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 41 skipping to change at page 2, line 41
3.1. Forward Compatibility . . . . . . . . . . . . . . . . . . 9 3.1. Forward Compatibility . . . . . . . . . . . . . . . . . . 9
3.2. TE and Network Models . . . . . . . . . . . . . . . . . . 9 3.2. TE and Network Models . . . . . . . . . . . . . . . . . . 9
4. L3VPN Architecture in the ACTN Context . . . . . . . . . . . 10 4. L3VPN Architecture in the ACTN Context . . . . . . . . . . . 10
4.1. Service Mapping . . . . . . . . . . . . . . . . . . . . . 13 4.1. Service Mapping . . . . . . . . . . . . . . . . . . . . . 13
4.2. Site Mapping . . . . . . . . . . . . . . . . . . . . . . 13 4.2. Site Mapping . . . . . . . . . . . . . . . . . . . . . . 13
5. Applicability of TE-Service Mapping in Generic context . . . 14 5. Applicability of TE-Service Mapping in Generic context . . . 14
6. YANG Data Trees . . . . . . . . . . . . . . . . . . . . . . . 14 6. YANG Data Trees . . . . . . . . . . . . . . . . . . . . . . . 14
6.1. Service Mapping Types . . . . . . . . . . . . . . . . . . 14 6.1. Service Mapping Types . . . . . . . . . . . . . . . . . . 14
6.2. Service Models . . . . . . . . . . . . . . . . . . . . . 16 6.2. Service Models . . . . . . . . . . . . . . . . . . . . . 16
6.2.1. L3SM . . . . . . . . . . . . . . . . . . . . . . . . 16 6.2.1. L3SM . . . . . . . . . . . . . . . . . . . . . . . . 16
6.2.2. L2SM . . . . . . . . . . . . . . . . . . . . . . . . 16 6.2.2. L2SM . . . . . . . . . . . . . . . . . . . . . . . . 17
6.2.3. L1CSM . . . . . . . . . . . . . . . . . . . . . . . . 17 6.2.3. L1CSM . . . . . . . . . . . . . . . . . . . . . . . . 17
6.3. Network Models . . . . . . . . . . . . . . . . . . . . . 18 6.3. Network Models . . . . . . . . . . . . . . . . . . . . . 18
6.3.1. L3NM . . . . . . . . . . . . . . . . . . . . . . . . 18 6.3.1. L3NM . . . . . . . . . . . . . . . . . . . . . . . . 18
6.3.2. L2NM . . . . . . . . . . . . . . . . . . . . . . . . 19 6.3.2. L2NM . . . . . . . . . . . . . . . . . . . . . . . . 19
7. YANG Data Models . . . . . . . . . . . . . . . . . . . . . . 20 7. YANG Data Models . . . . . . . . . . . . . . . . . . . . . . 20
7.1. ietf-te-service-mapping-types . . . . . . . . . . . . . . 20 7.1. ietf-te-service-mapping-types . . . . . . . . . . . . . . 20
7.2. Service Models . . . . . . . . . . . . . . . . . . . . . 29 7.2. Service Models . . . . . . . . . . . . . . . . . . . . . 29
7.2.1. ietf-l3sm-te-service-mapping . . . . . . . . . . . . 29 7.2.1. ietf-l3sm-te-service-mapping . . . . . . . . . . . . 29
7.2.2. ietf-l2sm-te-service-mapping . . . . . . . . . . . . 31 7.2.2. ietf-l2sm-te-service-mapping . . . . . . . . . . . . 31
7.2.3. ietf-l1csm-te-service-mapping . . . . . . . . . . . . 33 7.2.3. ietf-l1csm-te-service-mapping . . . . . . . . . . . . 33
skipping to change at page 6, line 33 skipping to change at page 6, line 33
| | | ] | | | | ] |
| nw | ietf-network | [RFC8345] | | nw | ietf-network | [RFC8345] |
| te- | ietf-te-types | [RFC8776] | | te- | ietf-te-types | [RFC8776] |
| types | | | | types | | |
| te | ietf-te | [I-D.ietf-teas-yang-te] | | te | ietf-te | [I-D.ietf-teas-yang-te] |
| l2vpn- | ietf-l2vpn-ntw | [I-D.ietf-opsawg-l2nm] | | l2vpn- | ietf-l2vpn-ntw | [I-D.ietf-opsawg-l2nm] |
| ntw | | | | ntw | | |
| l3vpn- | ietf-l3vpn-ntw | [I-D.ietf-opsawg-l3sm-l3nm] | | l3vpn- | ietf-l3vpn-ntw | [I-D.ietf-opsawg-l3sm-l3nm] |
| ntw | | | | ntw | | |
| rt | ietf-routing | [RFC8349] | | 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] | | policy | | yang] |
+---------+---------------------------+-----------------------------+ +---------+---------------------------+-----------------------------+
Table 1: Prefixes and corresponding YANG modules Table 1: Prefixes and corresponding YANG modules
Note: The RFC Editor should replace XXXX with the number assigned to Note: The RFC Editor should replace XXXX with the number assigned to
the RFC once this draft becomes an RFC. the RFC once this draft becomes an RFC.
2. TE and Service Related Parameters 2. TE and Service Related Parameters
skipping to change at page 9, line 20 skipping to change at page 9, line 20
customers to access operational state information about how their customers to access operational state information about how their
services are instantiated with the underlying VN, TE topology or TE services are instantiated with the underlying VN, TE topology or TE
tunnels provided that the MDSC operator is willing to share that tunnels provided that the MDSC operator is willing to share that
information. This mapping will facilitate a seamless service information. This mapping will facilitate a seamless service
management operation with underlay-TE network visibility. management operation with underlay-TE network visibility.
As seen in Figure 1, the augmented LxSM service model records a As seen in Figure 1, the augmented LxSM service model records a
mapping between the customer service models and the ACTN VN YANG mapping between the customer service models and the ACTN VN YANG
model. Thus, when the MDSC receives a service request it creates a model. Thus, when the MDSC receives a service request it creates a
VN that meets the customer's service objectives with various VN that meets the customer's service objectives with various
constraints via TE-topology model [I-D.ietf-teas-yang-te-topo], and constraints via TE-topology model [RFC8795], and this relationship is
this relationship is recorded by the Augmented LxSM Model. The model recorded by the Augmented LxSM Model. The model also supports a
also supports a mapping between a service model and TE-topology or a mapping between a service model and TE-topology or a TE-tunnel.
TE-tunnel.
The YANG models defined in this document conforms to the Network The YANG models defined in this document conforms to the Network
Management Datastore Architecture (NMDA) [RFC8342]. Management Datastore Architecture (NMDA) [RFC8342].
3.1. Forward Compatibility 3.1. Forward Compatibility
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.
skipping to change at page 15, line 39 skipping to change at page 15, line 39
| | +--rw names* string | | +--rw names* string
| +--rw disjointness? te-path-disjointness | +--rw disjointness? te-path-disjointness
+--rw optimizations +--rw optimizations
+--rw (algorithm)? +--rw (algorithm)?
+--:(metric) {path-optimization-metric}? +--:(metric) {path-optimization-metric}?
| +--rw optimization-metric* [metric-type] | +--rw optimization-metric* [metric-type]
| | +--rw metric-type | | +--rw metric-type
| | | identityref | | | identityref
| | +--rw weight? uint8 | | +--rw weight? uint8
| | +--rw explicit-route-exclude-objects | | +--rw explicit-route-exclude-objects
| | | +--rw route-object-exclude-object* [index] | | | ...
| | | ...
| | +--rw explicit-route-include-objects | | +--rw explicit-route-include-objects
| | +--rw route-object-include-object* [index] | | ...
| | ...
| +--rw tiebreakers | +--rw tiebreakers
| +--rw tiebreaker* [tiebreaker-type] | +--rw tiebreaker* [tiebreaker-type]
| +--rw tiebreaker-type identityref | ...
+--:(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 availability-type? identityref +--rw availability-type? identityref
+--rw (te)? +--rw (te)?
+--:(vn) +--:(vn)
| +--rw vn-ref? | +--rw vn-list*
| -> /vn:vn/vn-list/vn-id | -> /vn:vn/vn-list/vn-id
+--:(te-topo) +--:(te-topo)
| +--rw vn-topology-id? | +--rw vn-topology-id?
| | te-types:te-topology-id | | te-types: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-list* te:tunnel-ref | +--rw te-tunnel-list* 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
+--:(te-mapping-template) {template}? +--:(te-mapping-template) {template}?
+--rw te-mapping-template-ref? leafref +--rw te-mapping-template-ref? leafref
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
/l3vpn-svc:site-network-access: /l3vpn-svc:site-network-access:
+--rw (te)? +--rw (te)?
+--:(vn) +--:(vn)
| +--rw vn-ref? | +--rw ap-list*
| -> /vn:ap/access-point-list/access-point-id | -> /vn:ap/access-point-list/access-point-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 availability-type? identityref +--rw availability-type? identityref
+--rw (te)? +--rw (te)?
+--:(vn) +--:(vn)
| +--rw vn-ref? | +--rw vn-list*
| -> /vn:vn/vn-list/vn-id | -> /vn:vn/vn-list/vn-id
+--:(te-topo) +--:(te-topo)
| +--rw vn-topology-id? | +--rw vn-topology-id?
| | te-types:te-topology-id | | te-types: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-list* te:tunnel-ref | +--rw te-tunnel-list* 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
+--:(te-mapping-template) {template}? +--:(te-mapping-template) {template}?
+--rw te-mapping-template-ref? leafref +--rw te-mapping-template-ref? leafref
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:site-network-access:
+--rw (te)? +--rw (te)?
+--:(vn) +--:(vn)
| +--rw vn-ref? | +--rw ap-list*
| -> /vn:ap/access-point-list/access-point-id | -> /vn:ap/access-point-list/access-point-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 availability-type? identityref +--rw availability-type? identityref
+--rw (te)? +--rw (te)?
+--:(vn) +--:(vn)
| +--rw vn-ref? | +--rw vn-list*
| -> /vn:vn/vn-list/vn-id | -> /vn:vn/vn-list/vn-id
+--:(te-topo) +--:(te-topo)
| +--rw vn-topology-id? | +--rw vn-topology-id?
| | te-types:te-topology-id | | te-types: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-list* te:tunnel-ref | +--rw te-tunnel-list* 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
+--:(te-mapping-template) {template}? +--:(te-mapping-template) {template}?
+--rw te-mapping-template-ref? leafref +--rw te-mapping-template-ref? leafref
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-ref? | +--rw ap-list*
| -> /vn:ap/access-point-list/access-point-id | -> /vn:ap/access-point-list/access-point-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 availability-type? identityref +--rw availability-type? identityref
+--rw (te)? +--rw (te)?
+--:(vn) +--:(vn)
| +--rw vn-ref? | +--rw vn-list*
| -> /vn:vn/vn-list/vn-id | -> /vn:vn/vn-list/vn-id
+--:(te-topo) +--:(te-topo)
| +--rw vn-topology-id? | +--rw vn-topology-id?
| | te-types:te-topology-id | | te-types: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-list* te:tunnel-ref | +--rw te-tunnel-list* te:tunnel-ref
| +--rw sr-policy* | +--rw sr-policy*
| [policy-color-ref policy-endpoint-ref] | [policy-color-ref policy-endpoint-ref]
skipping to change at page 19, line 35 skipping to change at page 19, line 35
| +--rw policy-color-ref leafref | +--rw policy-color-ref leafref
| +--rw policy-endpoint-ref leafref | +--rw policy-endpoint-ref leafref
+--:(te-mapping-template) {template}? +--:(te-mapping-template) {template}?
+--rw te-mapping-template-ref? leafref +--rw te-mapping-template-ref? leafref
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
/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-ref? | +--rw ap-list*
| -> /vn:ap/access-point-list/access-point-id | -> /vn:ap/access-point-list/access-point-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 availability-type? identityref +--rw availability-type? identityref
+--rw (te)? +--rw (te)?
+--:(vn) +--:(vn)
| +--rw vn-ref? | +--rw vn-list*
| -> /vn:vn/vn-list/vn-id | -> /vn:vn/vn-list/vn-id
+--:(te-topo) +--:(te-topo)
| +--rw vn-topology-id? | +--rw vn-topology-id?
| | te-types:te-topology-id | | te-types: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-list* te:tunnel-ref | +--rw te-tunnel-list* te:tunnel-ref
| +--rw sr-policy* | +--rw sr-policy*
| [policy-color-ref policy-endpoint-ref] | [policy-color-ref policy-endpoint-ref]
skipping to change at page 20, line 35 skipping to change at page 20, line 35
| +--rw policy-color-ref leafref | +--rw policy-color-ref leafref
| +--rw policy-endpoint-ref leafref | +--rw policy-endpoint-ref leafref
+--:(te-mapping-template) {template}? +--:(te-mapping-template) {template}?
+--rw te-mapping-template-ref? leafref +--rw te-mapping-template-ref? leafref
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
/l2vpn-ntw:vpn-node/l2vpn-ntw:vpn-network-accesses /l2vpn-ntw:vpn-node/l2vpn-ntw:vpn-network-accesses
/l2vpn-ntw:vpn-network-access: /l2vpn-ntw:vpn-network-access:
+--rw (te)? +--rw (te)?
+--:(vn) +--:(vn)
| +--rw vn-ref? | +--rw ap-list*
| -> /vn:ap/access-point-list/access-point-id | -> /vn:ap/access-point-list/access-point-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@2020-07-13.yang" <CODE BEGINS> file "ietf-te-service-mapping-types@2020-11-02.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 tsm-types; prefix tsm-types;
/* Import inet-types */ /* Import inet-types */
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
reference reference
"RFC 6991: Common YANG Data Types"; "RFC 6991: Common YANG Data Types";
} }
skipping to change at page 22, line 12 skipping to change at page 22, line 13
prefix rt; prefix rt;
reference reference
"RFC 8349: A YANG Data Model for Routing Management"; "RFC 8349: A YANG Data Model for Routing Management";
} }
/* Import SR Policy */ /* Import SR Policy */
import ietf-sr-policy { import ietf-sr-policy {
prefix sr-policy; prefix sr-policy;
reference 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"; 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: <http://tools.ietf.org/wg/teas/>
WG List: <mailto:teas@ietf.org> WG List: <mailto:teas@ietf.org>
skipping to change at page 23, line 5 skipping to change at page 23, line 6
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.
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
'MAY', and 'OPTIONAL' in this document are to be interpreted as 'MAY', and 'OPTIONAL' in this document are to be interpreted as
described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
they appear in all capitals, as shown here."; they appear in all capitals, as shown here.";
revision 2020-07-13 { revision 2020-11-02 {
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 25, line 48 skipping to change at page 25, line 51
* Groupings * Groupings
*/ */
grouping te-ref { grouping te-ref {
description description
"The reference to TE."; "The reference to TE.";
choice te { choice te {
description description
"The TE"; "The TE";
case vn { case vn {
leaf vn-ref { leaf-list vn-list {
type leafref { type leafref {
path "/vn:vn/vn:vn-list/vn:vn-id"; path "/vn:vn/vn:vn-list/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 { leaf vn-topology-id {
type te-types:te-topology-id; type te-types:te-topology-id;
description description
"An identifier to the TE Topology Model where the abstract "An identifier to the TE Topology Model where the abstract
nodes and links of the Topology can be found for Type 2 nodes and links of the Topology can be found for Type 2
VNS"; VNS";
reference reference
"I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic "RFC 8795: YANG Data Model for Traffic Engineering (TE)
Engineering (TE) Topologies"; Topologies";
} }
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
"I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic "RFC 8795: YANG Data Model for Traffic Engineering (TE)
Engineering (TE) Topologies"; Topologies";
} }
} }
case te-tunnel { case te-tunnel {
leaf-list te-tunnel-list { leaf-list te-tunnel-list {
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";
skipping to change at page 27, line 25 skipping to change at page 27, line 27
} }
description description
"Reference to sr-policy endpoint"; "Reference to sr-policy endpoint";
} }
} }
} }
case te-mapping-template { case te-mapping-template {
if-feature "template"; if-feature "template";
leaf te-mapping-template-ref { leaf te-mapping-template-ref {
type leafref { 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 description
"An identifier to the TE Mapping Template where the TE "An identifier to the TE Mapping Template where the TE
constraints and optimization criteria are specified."; constraints and optimization criteria are specified.";
} }
} }
} }
} }
//grouping //grouping
grouping te-endpoint-ref { grouping te-endpoint-ref {
description description
"The reference to TE endpoints."; "The reference to TE endpoints.";
choice te { choice te {
description description
"The TE"; "The TE";
case vn { case vn {
leaf vn-ref { leaf-list ap-list {
type leafref { type leafref {
path "/vn:ap/vn:access-point-list/vn:access-point-id"; path "/vn:ap/vn:access-point-list/vn:access-point-id";
} }
description description
"The reference to VN AP"; "The reference to VN AP";
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 { case te {
leaf ltp { leaf ltp {
type te-types:te-tp-id; type te-types:te-tp-id;
description description
"Reference LTP in the TE-topology"; "Reference LTP in the TE-topology";
reference reference
"I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic "RFC 8795: YANG Data Model for Traffic Engineering (TE)
Engineering (TE) Topologies"; Topologies";
} }
} }
} }
} }
//grouping //grouping
grouping te-mapping { grouping te-mapping {
description description
"Mapping between Services and TE"; "Mapping between Services and TE";
skipping to change at page 29, line 21 skipping to change at page 29, line 23
} }
leaf description { leaf description {
type string; type string;
description description
"Description of the template."; "Description of the template.";
} }
leaf map-type { leaf map-type {
type identityref { type identityref {
base map-type; base map-type;
} }
must '(. != "template")' { must "0 = derived-from-or-self(.,'template')" {
error-message "The map-type must be other than " error-message "The map-type must be other than "
+ "TE mapping template"; + "TE mapping template";
} }
description description
"Map type for the VN/Tunnel creation/ "Map type for the VN/Tunnel creation/
selection."; selection.";
} }
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
skipping to change at page 29, line 43 skipping to change at page 29, line 45
} }
} }
} }
<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@2020-07-13.yang" <CODE BEGINS> file "ietf-l3sm-te-service-mapping@2020-11-02.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 tsm-types; prefix tsm-types;
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 30, line 49 skipping to change at page 30, line 51
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.
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
'MAY', and 'OPTIONAL' in this document are to be interpreted as 'MAY', and 'OPTIONAL' in this document are to be interpreted as
described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
they appear in all capitals, as shown here."; they appear in all capitals, as shown here.";
revision 2020-03-08 { revision 2020-11-02 {
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" {
skipping to change at page 31, line 43 skipping to change at page 31, line 44
uses tsm-types:te-endpoint-ref; uses tsm-types:te-endpoint-ref;
} }
//augment //augment
} }
<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@2020-07-13.yang" <CODE BEGINS> file "ietf-l2sm-te-service-mapping@2020-11-02.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 tsm-types; prefix tsm-types;
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 32, line 49 skipping to change at page 32, line 51
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.
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
'MAY', and 'OPTIONAL' in this document are to be interpreted as 'MAY', and 'OPTIONAL' in this document are to be interpreted as
described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
they appear in all capitals, as shown here."; they appear in all capitals, as shown here.";
revision 2020-07-13 { revision 2020-11-02 {
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
*/ */
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" {
skipping to change at page 33, line 43 skipping to change at page 33, line 44
uses tsm-types:te-endpoint-ref; uses tsm-types:te-endpoint-ref;
} }
//augment //augment
} }
<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@2020-07-13.yang" <CODE BEGINS> file "ietf-l1csm-te-service-mapping@2020-11-02.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 tsm-types; prefix tsm-types;
reference reference
"RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; "RFC XXXX: Traffic Engineering and Service Mapping Yang Model";
} }
import ietf-l1csm { import ietf-l1csm {
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)";
skipping to change at page 34, line 49 skipping to change at page 35, line 5
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.
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
'MAY', and 'OPTIONAL' in this document are to be interpreted as 'MAY', and 'OPTIONAL' in this document are to be interpreted as
described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
they appear in all capitals, as shown here."; they appear in all capitals, as shown here.";
revision 2020-07-13 { revision 2020-11-02 {
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
*/ */
augment "/l1csm:l1-connectivity/l1csm:services/l1csm:service" { augment "/l1csm:l1-connectivity/l1csm:services/l1csm:service" {
description description
skipping to change at page 35, line 43 skipping to change at page 35, line 46
//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@2020-07-13.yang" <CODE BEGINS> file "ietf-l3nm-te-service-mapping@2020-11-02.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 tsm-types; prefix tsm-types;
reference reference
"RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; "RFC XXXX: Traffic Engineering and Service Mapping Yang Model";
} }
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";
} }
skipping to change at page 36, line 48 skipping to change at page 36, line 51
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.
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
'MAY', and 'OPTIONAL' in this document are to be interpreted as 'MAY', and 'OPTIONAL' in this document are to be interpreted as
described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
they appear in all capitals, as shown here."; they appear in all capitals, as shown here.";
revision 2020-07-13 { revision 2020-11-02 {
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 37, line 43 skipping to change at page 37, line 46
uses tsm-types:te-endpoint-ref; uses tsm-types: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@2020-07-13.yang" <CODE BEGINS> file "ietf-l2nm-te-service-mapping@2020-11-02.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 tsm-types; prefix tsm-types;
reference reference
"RFC XXXX: Traffic Engineering and Service Mapping Yang Model"; "RFC XXXX: Traffic Engineering and Service Mapping Yang Model";
} }
import ietf-l2vpn-ntw { import ietf-l2vpn-ntw {
prefix l2vpn-ntw; prefix l2vpn-ntw;
reference reference
"I-D.ietf-l2nm: A Layer 2 VPN Network YANG Model"; "I-D.ietf-l2nm: A Layer 2 VPN Network YANG Model";
} }
skipping to change at page 38, line 49 skipping to change at page 38, line 51
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.
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
'MAY', and 'OPTIONAL' in this document are to be interpreted as 'MAY', and 'OPTIONAL' in this document are to be interpreted as
described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
they appear in all capitals, as shown here."; they appear in all capitals, as shown here.";
revision 2020-07-13 { revision 2020-11-02 {
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
*/ */
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" {
skipping to change at page 42, line 44 skipping to change at page 42, line 44
10. Acknowledgements 10. Acknowledgements
We thank Diego Caviglia, and Igor Bryskin for useful discussions and We thank Diego Caviglia, and Igor Bryskin for useful discussions and
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., Dhody, D., Dios, O., and D. Lee, Y., Lee, K., Zheng, H., Dios, O., and D. Ceccarelli,
Ceccarelli, "A YANG Data Model for L1 Connectivity Service "A YANG Data Model for L1 Connectivity Service Model
Model (L1CSM)", draft-ietf-ccamp-l1csm-yang-11 (work in (L1CSM)", draft-ietf-ccamp-l1csm-yang-12 (work in
progress), March 2020. progress), September 2020.
[I-D.ietf-opsawg-l2nm] [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- L., and J. Ma, "A Layer 2 VPN Network YANG Model", draft-
ietf-opsawg-l2nm-00 (work in progress), July 2020. ietf-opsawg-l2nm-00 (work in progress), July 2020.
[I-D.ietf-opsawg-l3sm-l3nm] [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- 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] [I-D.ietf-teas-actn-vn-yang]
Lee, Y., Dhody, D., Ceccarelli, D., Bryskin, I., and B. Lee, Y., Dhody, D., Ceccarelli, D., Bryskin, I., and B.
Yoon, "A Yang Data Model for VN Operation", draft-ietf- Yoon, "A YANG Data Model for VN Operation", draft-ietf-
teas-actn-vn-yang-08 (work in progress), March 2020. teas-actn-vn-yang-09 (work in progress), July 2020.
[I-D.ietf-teas-yang-te] [I-D.ietf-teas-yang-te]
Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,
"A YANG Data Model for Traffic Engineering Tunnels and "A YANG Data Model for Traffic Engineering Tunnels, Label
Interfaces", draft-ietf-teas-yang-te-23 (work in Switched Paths and Interfaces", draft-ietf-teas-yang-te-25
progress), March 2020. (work in progress), July 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.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[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>.
skipping to change at page 45, line 29 skipping to change at page 45, line 19
[RFC8466] Wen, B., Fioccola, G., Ed., Xie, C., and L. Jalil, "A YANG [RFC8466] Wen, B., Fioccola, G., Ed., Xie, C., and L. Jalil, "A YANG
Data Model for Layer 2 Virtual Private Network (L2VPN) Data Model for Layer 2 Virtual Private Network (L2VPN)
Service Delivery", RFC 8466, DOI 10.17487/RFC8466, October Service Delivery", RFC 8466, DOI 10.17487/RFC8466, October
2018, <https://www.rfc-editor.org/info/rfc8466>. 2018, <https://www.rfc-editor.org/info/rfc8466>.
[RFC8776] Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, [RFC8776] Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,
"Common YANG Data Types for Traffic Engineering", "Common YANG Data Types for Traffic Engineering",
RFC 8776, DOI 10.17487/RFC8776, June 2020, RFC 8776, DOI 10.17487/RFC8776, June 2020,
<https://www.rfc-editor.org/info/rfc8776>. <https://www.rfc-editor.org/info/rfc8776>.
[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,
<https://www.rfc-editor.org/info/rfc8795>.
11.2. Informative References 11.2. Informative References
[I-D.ietf-teas-actn-yang] [I-D.ietf-teas-actn-yang]
Lee, Y., Zheng, H., Ceccarelli, D., Yoon, B., Dios, O., Lee, Y., Zheng, H., Ceccarelli, D., Yoon, B., Dios, O.,
Shin, J., and S. Belotti, "Applicability of YANG models Shin, J., and S. Belotti, "Applicability of YANG models
for Abstraction and Control of Traffic Engineered for Abstraction and Control of Traffic Engineered
Networks", draft-ietf-teas-actn-yang-05 (work in Networks", draft-ietf-teas-actn-yang-06 (work in
progress), February 2020. progress), August 2020.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[RFC8199] Bogdanovic, D., Claise, B., and C. Moberg, "YANG Module [RFC8199] Bogdanovic, D., Claise, B., and C. Moberg, "YANG Module
Classification", RFC 8199, DOI 10.17487/RFC8199, July Classification", RFC 8199, DOI 10.17487/RFC8199, July
2017, <https://www.rfc-editor.org/info/rfc8199>. 2017, <https://www.rfc-editor.org/info/rfc8199>.
skipping to change at page 46, line 47 skipping to change at page 46, line 42
Oscar Gonzalez de Dios Oscar Gonzalez de Dios
Telefonica Telefonica
EMail: oscar.gonzalezdedios@telefonica.com EMail: oscar.gonzalezdedios@telefonica.com
Carlo Perocchio Carlo Perocchio
Ericsson Ericsson
EMail: carlo.perocchio@ericsson.com EMail: carlo.perocchio@ericsson.com
Kenichi Ogaki
KDDI
Email: ke-oogaki@kddi.com
Authors' Addresses Authors' Addresses
Young Lee (editor) Young Lee (editor)
Samsung Electronics Samsung Electronics
Email: younglee.tx@gmail.com Email: younglee.tx@gmail.com
Dhruv Dhody (editor) Dhruv Dhody (editor)
Huawei Technologies Huawei Technologies
Divyashree Techno Park, Whitefield
Bangalore, Karnataka 560066
India
Email: dhruv.ietf@gmail.com Email: dhruv.ietf@gmail.com
Giuseppe Fioccola Giuseppe Fioccola
Huawei Technologies Huawei Technologies
Email: giuseppe.fioccola@huawei.com Email: giuseppe.fioccola@huawei.com
Qin Wu (editor) Qin Wu (editor)
Huawei Technologies Huawei Technologies
 End of changes. 65 change blocks. 
88 lines changed or deleted 85 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/