draft-ietf-teas-te-service-mapping-yang-08.txt   draft-ietf-teas-te-service-mapping-yang-09.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: 1 March 2022 G. Fioccola Expires: 27 April 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
28 August 2021 24 October 2021
Traffic Engineering (TE) and Service Mapping Yang Model Traffic Engineering (TE) and Service Mapping YANG Model
draft-ietf-teas-te-service-mapping-yang-08 draft-ietf-teas-te-service-mapping-yang-09
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 1 March 2022. This Internet-Draft will expire on 27 April 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 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
skipping to change at page 2, line 34 skipping to change at page 2, line 34
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
2.1. VN/Tunnel Selection Requirements . . . . . . . . . . . . 8 2.1. VN/Tunnel Selection Requirements . . . . . . . . . . . . 8
2.2. TE Policy . . . . . . . . . . . . . . . . . . . . . . . . 9 2.2. TE Policy . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2.1. Availability Requirement . . . . . . . . . . . . . . 9 2.2.1. Availability Requirement . . . . . . . . . . . . . . 9
3. YANG Modeling Approach . . . . . . . . . . . . . . . . . . . 9 3. YANG Modeling Approach . . . . . . . . . . . . . . . . . . . 9
3.1. Forward Compatibility . . . . . . . . . . . . . . . . . . 11 3.1. Forward Compatibility . . . . . . . . . . . . . . . . . . 11
3.2. TE and Network Models . . . . . . . . . . . . . . . . . . 11 3.2. TE and Network Models . . . . . . . . . . . . . . . . . . 11
4. L3VPN Architecture in the ACTN Context . . . . . . . . . . . 11 4. L3VPN Architecture in the ACTN Context . . . . . . . . . . . 12
4.1. Service Mapping . . . . . . . . . . . . . . . . . . . . . 15 4.1. Service Mapping . . . . . . . . . . . . . . . . . . . . . 16
4.2. Site Mapping . . . . . . . . . . . . . . . . . . . . . . 15 4.2. Site Mapping . . . . . . . . . . . . . . . . . . . . . . 16
5. Applicability of TE-Service Mapping in Generic context . . . 16 5. Applicability of TE-Service Mapping in Generic context . . . 17
6. YANG Data Trees . . . . . . . . . . . . . . . . . . . . . . . 16 6. YANG Data Trees . . . . . . . . . . . . . . . . . . . . . . . 17
6.1. Service Mapping Types . . . . . . . . . . . . . . . . . . 16 6.1. Service Mapping Types . . . . . . . . . . . . . . . . . . 17
6.2. Service Models . . . . . . . . . . . . . . . . . . . . . 17 6.2. Service Models . . . . . . . . . . . . . . . . . . . . . 18
6.2.1. L3SM . . . . . . . . . . . . . . . . . . . . . . . . 17 6.2.1. L3SM . . . . . . . . . . . . . . . . . . . . . . . . 18
6.2.2. L2SM . . . . . . . . . . . . . . . . . . . . . . . . 18 6.2.2. L2SM . . . . . . . . . . . . . . . . . . . . . . . . 19
6.2.3. L1CSM . . . . . . . . . . . . . . . . . . . . . . . . 19 6.2.3. L1CSM . . . . . . . . . . . . . . . . . . . . . . . . 20
6.3. Network Models . . . . . . . . . . . . . . . . . . . . . 20 6.3. Network Models . . . . . . . . . . . . . . . . . . . . . 21
6.3.1. L3NM . . . . . . . . . . . . . . . . . . . . . . . . 20 6.3.1. L3NM . . . . . . . . . . . . . . . . . . . . . . . . 21
6.3.2. L2NM . . . . . . . . . . . . . . . . . . . . . . . . 21 6.3.2. L2NM . . . . . . . . . . . . . . . . . . . . . . . . 22
7. YANG Data Models . . . . . . . . . . . . . . . . . . . . . . 22 7. YANG Data Models . . . . . . . . . . . . . . . . . . . . . . 23
7.1. ietf-te-service-mapping-types . . . . . . . . . . . . . . 22 7.1. ietf-te-service-mapping-types . . . . . . . . . . . . . . 23
7.2. Service Models . . . . . . . . . . . . . . . . . . . . . 31 7.2. Service Models . . . . . . . . . . . . . . . . . . . . . 32
7.2.1. ietf-l3sm-te-service-mapping . . . . . . . . . . . . 32 7.2.1. ietf-l3sm-te-service-mapping . . . . . . . . . . . . 33
7.2.2. ietf-l2sm-te-service-mapping . . . . . . . . . . . . 34 7.2.2. ietf-l2sm-te-service-mapping . . . . . . . . . . . . 35
7.2.3. ietf-l1csm-te-service-mapping . . . . . . . . . . . . 36 7.2.3. ietf-l1csm-te-service-mapping . . . . . . . . . . . . 37
7.3. Network Models . . . . . . . . . . . . . . . . . . . . . 38 7.3. Network Models . . . . . . . . . . . . . . . . . . . . . 39
7.3.1. ietf-l3nm-te-service-mapping . . . . . . . . . . . . 38 7.3.1. ietf-l3nm-te-service-mapping . . . . . . . . . . . . 39
7.3.2. ietf-l2nm-te-service-mapping . . . . . . . . . . . . 40 7.3.2. ietf-l2nm-te-service-mapping . . . . . . . . . . . . 41
8. Security Considerations . . . . . . . . . . . . . . . . . . . 42 8. Security Considerations . . . . . . . . . . . . . . . . . . . 43
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 43 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 44
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 45 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 46
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 45 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 46
11.1. Normative References . . . . . . . . . . . . . . . . . . 45 11.1. Normative References . . . . . . . . . . . . . . . . . . 46
11.2. Informative References . . . . . . . . . . . . . . . . . 48 11.2. Informative References . . . . . . . . . . . . . . . . . 49
Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 49 Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 50
Appendix B. Discussion . . . . . . . . . . . . . . . . . . . . . 51 Appendix B. Contributor Addresses . . . . . . . . . . . . . . . 52
Appendix C. Contributor Addresses . . . . . . . . . . . . . . . 51
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 52 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 52
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
their own scheduling mechanism on top of this YANG model. In future
augmentations to this model might also be designed to integrate
scheduling and calendering.
Note that the mechanism to map traffic (for example the enterprise
customer can tell, the traffic from source X on port Y should go on a
path with delay less than Z) can be via local configuration or
through a YANG model developed in the future (See one such attempt at
[I-D.dhody-teas-te-traffic-yang]).
3.2. TE and Network Models 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.,
[I-D.ietf-opsawg-l3sm-l3nm], and [I-D.ietf-opsawg-l2nm]) are [I-D.ietf-opsawg-l3sm-l3nm], and [I-D.ietf-opsawg-l2nm]) are
skipping to change at page 23, 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-08-28.yang" <CODE BEGINS> file "ietf-te-service-mapping-types@2021-10-24.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 24, line 44 skipping to change at page 25, line 44
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 Simplified 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-08-28 { revision 2021-10-24 {
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 32, line 6 skipping to change at page 33, line 6
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-08-28.yang" <CODE BEGINS> file "ietf-l3sm-te-service-mapping@2021-10-24.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";
skipping to change at page 33, line 5 skipping to change at page 34, line 5
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 Simplified 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-08-28 { revision 2021-10-24 {
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
*/ */
skipping to change at page 34, line 20 skipping to change at page 35, line 20
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-08-28.yang" <CODE BEGINS> file "ietf-l2sm-te-service-mapping@2021-10-24.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 20 skipping to change at page 36, line 20
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 Simplified 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-08-28 { revision 2021-10-24 {
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 36, line 40 skipping to change at page 37, line 40
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-08-28.yang" <CODE BEGINS> file "ietf-l1csm-te-service-mapping@2021-10-24.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 37, line 40 skipping to change at page 38, line 40
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 Simplified 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-08-28 { revision 2021-10-24 {
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 38, line 32 skipping to change at page 39, line 32
} }
//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-08-28.yang" <CODE BEGINS> file "ietf-l3nm-te-service-mapping@2021-10-24.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 39, line 31 skipping to change at page 40, line 31
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 Simplified 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-08-28 { revision 2021-10-24 {
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 40, line 26 skipping to change at page 41, line 26
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-08-28.yang" <CODE BEGINS> file "ietf-l2nm-te-service-mapping@2021-10-24.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 26 skipping to change at page 42, line 26
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 Simplified 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-08-28 { revision 2021-10-24 {
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 45, 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-14, 20 February 2021, ietf-ccamp-l1csm-yang-15, 8 September 2021,
<https://datatracker.ietf.org/doc/html/draft-ietf-ccamp- <https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-
l1csm-yang-14>. l1csm-yang-15>.
[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-04, 28 Progress, Internet-Draft, draft-ietf-opsawg-l2nm-09, 20
July 2021, <https://datatracker.ietf.org/doc/html/draft- October 2021, <https://datatracker.ietf.org/doc/html/
ietf-opsawg-l2nm-04>. draft-ietf-opsawg-l2nm-09>.
[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 Layer 3 VPN Network YANG Model", Work in
Progress, Internet-Draft, draft-ietf-opsawg-l3sm-l3nm-10, Progress, Internet-Draft, draft-ietf-opsawg-l3sm-l3nm-18,
15 July 2021, <https://datatracker.ietf.org/doc/html/ 8 October 2021, <https://datatracker.ietf.org/doc/html/
draft-ietf-opsawg-l3sm-l3nm-10>. 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-12, Progress, Internet-Draft, draft-ietf-teas-actn-vn-yang-13,
25 August 2021, <https://datatracker.ietf.org/doc/html/ 23 October 2021, <https://datatracker.ietf.org/doc/html/
draft-ietf-teas-actn-vn-yang-12>. draft-ietf-teas-actn-vn-yang-13>.
[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/ 27, 8 July 2021, <https://datatracker.ietf.org/doc/html/
draft-ietf-teas-yang-te-27>. draft-ietf-teas-yang-te-27>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
skipping to change at page 48, line 27 skipping to change at page 49, line 27
<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 [RFC8795] Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and
O. Gonzalez de Dios, "YANG Data Model for Traffic O. Gonzalez de Dios, "YANG Data Model for Traffic
Engineering (TE) Topologies", RFC 8795, Engineering (TE) Topologies", RFC 8795,
DOI 10.17487/RFC8795, August 2020, DOI 10.17487/RFC8795, August 2020,
<https://www.rfc-editor.org/info/rfc8795>. <https://www.rfc-editor.org/info/rfc8795>.
11.2. Informative References 11.2. Informative References
[I-D.dhody-teas-te-traffic-yang]
Dhody, D., "Traffic Mapping YANG model for Traffic
Engineering (TE)", Work in Progress, Internet-Draft,
draft-dhody-teas-te-traffic-yang-00, 24 October 2021,
<https://datatracker.ietf.org/doc/html/draft-dhody-teas-
te-traffic-yang-00>.
[I-D.ietf-teas-actn-yang] [I-D.ietf-teas-actn-yang]
Lee, Y., Zheng, H., Ceccarelli, D., Yoon, B. Y., and S. Lee, Y., Zheng, H., Ceccarelli, D., Yoon, B. Y., and S.
Belotti, "Applicability of YANG models for Abstraction and Belotti, "Applicability of YANG models for Abstraction and
Control of Traffic Engineered Networks", Work in Progress, Control of Traffic Engineered Networks", Work in Progress,
Internet-Draft, draft-ietf-teas-actn-yang-07, 21 February Internet-Draft, draft-ietf-teas-actn-yang-08, 8 September
2021, <https://datatracker.ietf.org/doc/html/draft-ietf- 2021, <https://datatracker.ietf.org/doc/html/draft-ietf-
teas-actn-yang-07>. teas-actn-yang-08>.
[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 51, 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. Discussion Appendix B. Contributor Addresses
* While the support to bind a tunnel to the VPN is supported. We do
not have a mechanism to map traffic to a path. The input can come
from the user. E.g. the enterprise customer can tell, the traffic
from source X on port Y should go with delay less than Z. Further
discussion is required on how and where to model these.
* Support for Calendaring and scheduling TE resources.
Appendix 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. 29 change blocks. 
71 lines changed or deleted 79 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/