draft-ietf-teas-te-service-mapping-yang-02.txt		draft-ietf-teas-te-service-mapping-yang-03.txt
	TEAS Working Group Y. Lee, Ed.		TEAS Working Group Y. Lee, Ed.
	Internet-Draft SKKU		Internet-Draft Samsung Electronics
	Intended status: Standards Track D. Dhody, Ed.		Intended status: Standards Track D. Dhody, Ed.
	Expires: March 12, 2020 G. Fioccola		Expires: September 9, 2020 G. Fioccola
	Q. Wu, Ed.		Q. Wu, Ed.
	Huawei Technologies		Huawei Technologies
	D. Ceccarelli		D. Ceccarelli
	Ericsson		Ericsson
	J. Tantsura		J. Tantsura
	Apstra		Apstra
	September 9, 2019		March 8, 2020
	Traffic Engineering (TE) and Service Mapping Yang Model		Traffic Engineering (TE) and Service Mapping Yang Model
	draft-ietf-teas-te-service-mapping-yang-02		draft-ietf-teas-te-service-mapping-yang-03
	Abstract		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 March 12, 2020.		This Internet-Draft will expire on September 9, 2020.
	Copyright Notice		Copyright Notice
	Copyright (c) 2019 IETF Trust and the persons identified as the		Copyright (c) 2020 IETF Trust and the persons identified as the
	document authors. All rights reserved.		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
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4		1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
	1.2. Tree diagram . . . . . . . . . . . . . . . . . . . . . . 4		1.2. Tree diagram . . . . . . . . . . . . . . . . . . . . . . 5
	1.3. Prefixes in Data Node Names . . . . . . . . . . . . . . . 4		1.3. Prefixes in Data Node Names . . . . . . . . . . . . . . . 5
	2. TE and Service Related Parameters . . . . . . . . . . . . . . 5		2. TE and Service Related Parameters . . . . . . . . . . . . . . 6
	2.1. VN/Tunnel Selection Requirements . . . . . . . . . . . . 5		2.1. VN/Tunnel Selection Requirements . . . . . . . . . . . . 6
	2.2. Availability Requirement . . . . . . . . . . . . . . . . 6		2.2. Availability Requirement . . . . . . . . . . . . . . . . 7
	3. YANG Modeling Approach . . . . . . . . . . . . . . . . . . . 7		3. YANG Modeling Approach . . . . . . . . . . . . . . . . . . . 7
	3.1. Forward Compatibility . . . . . . . . . . . . . . . . . . 8		3.1. Forward Compatibility . . . . . . . . . . . . . . . . . . 8
	4. L3VPN Architecture in the ACTN Context . . . . . . . . . . . 8		3.2. TE and Network Models . . . . . . . . . . . . . . . . . . 8
	4.1. Service Mapping . . . . . . . . . . . . . . . . . . . . . 11		4. L3VPN Architecture in the ACTN Context . . . . . . . . . . . 9
	4.2. Site Mapping . . . . . . . . . . . . . . . . . . . . . . 11		4.1. Service Mapping . . . . . . . . . . . . . . . . . . . . . 12
	5. Applicability of TE-Service Mapping in Generic context . . . 12		4.2. Site Mapping . . . . . . . . . . . . . . . . . . . . . . 12
	6. YANG Data Trees . . . . . . . . . . . . . . . . . . . . . . . 12		5. Applicability of TE-Service Mapping in Generic context . . . 13
	6.1. L3SM . . . . . . . . . . . . . . . . . . . . . . . . . . 12		6. YANG Data Trees . . . . . . . . . . . . . . . . . . . . . . . 13
	6.2. L2SM . . . . . . . . . . . . . . . . . . . . . . . . . . 13		6.1. Service Models . . . . . . . . . . . . . . . . . . . . . 13
	6.3. L1CSM . . . . . . . . . . . . . . . . . . . . . . . . . . 14		6.1.1. L3SM . . . . . . . . . . . . . . . . . . . . . . . . 13
	7. YANG Data Models . . . . . . . . . . . . . . . . . . . . . . 15		6.1.2. L2SM . . . . . . . . . . . . . . . . . . . . . . . . 14
	7.1. ietf-te-service-mapping-types . . . . . . . . . . . . . . 15		6.1.3. L1CSM . . . . . . . . . . . . . . . . . . . . . . . . 15
	7.2. ietf-l3sm-te-service-mapping . . . . . . . . . . . . . . 21		6.2. Network Models . . . . . . . . . . . . . . . . . . . . . 16
	7.3. ietf-l2sm-te-service-mapping . . . . . . . . . . . . . . 23		6.2.1. L3NM . . . . . . . . . . . . . . . . . . . . . . . . 16
	7.4. ietf-l1csm-te-service-mapping . . . . . . . . . . . . . . 25		6.2.2. L2NM . . . . . . . . . . . . . . . . . . . . . . . . 17
	8. Security Considerations . . . . . . . . . . . . . . . . . . . 27		7. YANG Data Models . . . . . . . . . . . . . . . . . . . . . . 18
	9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28		7.1. ietf-te-service-mapping-types . . . . . . . . . . . . . . 18
	10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 29		7.2. Service Models . . . . . . . . . . . . . . . . . . . . . 24
	11. References . . . . . . . . . . . . . . . . . . . . . . . . . 29		7.2.1. ietf-l3sm-te-service-mapping . . . . . . . . . . . . 24
	11.1. Normative References . . . . . . . . . . . . . . . . . . 29		7.2.2. ietf-l2sm-te-service-mapping . . . . . . . . . . . . 26
	11.2. Informative References . . . . . . . . . . . . . . . . . 31		7.2.3. ietf-l1csm-te-service-mapping . . . . . . . . . . . . 28
	Appendix A. Contributor Addresses . . . . . . . . . . . . . . . 32		7.3. Network Models . . . . . . . . . . . . . . . . . . . . . 30
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 32		7.3.1. ietf-l3nm-te-service-mapping . . . . . . . . . . . . 30
			7.3.2. ietf-l2nm-te-service-mapping . . . . . . . . . . . . 32
			8. Security Considerations . . . . . . . . . . . . . . . . . . . 34
			9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36
			10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 37
			11. References . . . . . . . . . . . . . . . . . . . . . . . . . 37
			11.1. Normative References . . . . . . . . . . . . . . . . . . 37
			11.2. Informative References . . . . . . . . . . . . . . . . . 39
			Appendix A. Contributor Addresses . . . . . . . . . . . . . . . 40
			Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40
	1. Introduction		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 modelling of a variety of		been produced to allow configuration or modelling 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 4, line 26 ¶		skipping to change at page 4, line 36 ¶
	service orchestration functions such as multi-destination load		service orchestration functions such as multi-destination load
	balancing, guarantees of service quality, bandwidth and		balancing, guarantees of service quality, bandwidth and
	throughput. It also includes notifications for service fault and		throughput. It also includes notifications for service fault and
	performance degradation and so forth.		performance degradation and so forth.
	Section 2 describes a set of TE and service related parameters that		Section 2 describes a set of TE and service related parameters that
	this document addresses as "new and advanced parameters" that are not		this document addresses as "new and advanced parameters" that are not
	included in generic service models. Section 3 discusses YANG		included in generic service models. Section 3 discusses YANG
	modelling approach.		modelling approach.
			Apart from the service model, the TE mapping is equally applicable to
			the Network Models (L3 VPN Service Network Model (L3NM)
			[I-D.ietf-opsawg-l3sm-l3nm], L2 VPN Service Network Model (L2NM)
			[I-D.barguil-opsawg-l2sm-l2nm] etc.). See Section 3.2 for details.
	1.1. Terminology		1.1. Terminology
	Refer to [RFC8453], [RFC7926], and [RFC8309] for the key terms used		Refer to [RFC8453], [RFC7926], and [RFC8309] for the key terms used
	in this document.		in this document.
	The terminology for describing YANG data models is found in		The terminology for describing YANG data models is found in
	[RFC7950].		[RFC7950].
	1.2. Tree diagram		1.2. Tree diagram
	skipping to change at page 5, line 28 ¶		skipping to change at page 5, line 40 ¶
	| l2-tsm | ietf-l2sm-te-service- | [RFCXXXX] |		| l2-tsm | ietf-l2sm-te-service- | [RFCXXXX] |
	| | mapping | |		| | mapping | |
	| l3-tsm | ietf-l3sm-te-service- | [RFCXXXX] |		| l3-tsm | ietf-l3sm-te-service- | [RFCXXXX] |
	| | mapping | |		| | mapping | |
	| vn | ietf-vn | [I-D.ietf-teas-actn-vn-yan |		| vn | ietf-vn | [I-D.ietf-teas-actn-vn-yan |
	| | | g] |		| | | g] |
	| nw | ietf-network | [RFC8345] |		| nw | ietf-network | [RFC8345] |
	| te- | ietf-te-types | [I-D.ietf-teas-yang-te-typ |		| te- | ietf-te-types | [I-D.ietf-teas-yang-te-typ |
	| types | | es] |		| types | | es] |
	| te | ietf-te | [I-D.ietf-teas-yang-te] |		| te | ietf-te | [I-D.ietf-teas-yang-te] |
			| l1csm | ietf-l1csm | [I-D.ietf-ccamp-l1csm-yang |
			| | | ] |
			| l2vpn- | ietf-l2vpn-ntw | [I-D.barguil-opsawg-l2sm-l |
			| ntw | | 2nm] |
			| l3vpn- | ietf-l3vpn-ntw | [I-D.ietf-opsawg-l3sm-l3nm |
			| ntw | | ] |
	+---------+----------------------------+----------------------------+		+---------+----------------------------+----------------------------+
	Table 1: Prefixes and corresponding YANG modules		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
	While L1/L2/L3 service models (L1CSM, L2SM, L3SM) are intended to		While L1/L2/L3 service models (L1CSM, L2SM, L3SM) are intended to
	skipping to change at page 8, line 23 ¶		skipping to change at page 8, line 42 ¶
	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.
			3.2. TE and Network Models
			The L2/L3 network models (L2NM, L3NM) are intended to describe a VPN
			Service in the Service Provider Network. It containts information of
			the Service Provider network and might include allocated resources.
			It can be used by network controllers to manage and control the VPN
			Service configuration in the Service Provider network.
			Similar to service model, the existing network models (i.e.,
			[I-D.ietf-opsawg-l3sm-l3nm], and [I-D.barguil-opsawg-l2sm-l2nm]) are
			augmented to include the TE and Service mapping parameters. Figure 2
			shows the scope of the Augmented LxNM Model.
			+--------------+ +----------------------+ +----------+
			| LxNM |o-------| | . . . . | ACTN VN |
			+--------------+ augment| | +----------+
			| | +----------+
			+--------------+ | Augmented LxNM Model | . . . . | TE-topo |
			| TE & Service |------->| | +----------+
			| Mapping Types| import | | +----------+
			+--------------+ | | . . . . | TE-tunnel|
			+----------------------+ +----------+
			reference
			Figure 2: Augmented LxNM Model
			The Augmented LxNM model (where x=2,3) augments the basic LxNM model
			while importing the common TE mapping related parameters (defined in
			Section 2) grouping information from TE and Service Mapping Types.
			The role of the augmented LxNM network model is to expose the mapping
			relationship between network models and TE models.
	4. L3VPN Architecture in the ACTN Context		4. L3VPN Architecture in the ACTN Context
	Figure 2 shows the architectural context of this document referencing		Figure 3 shows the architectural context of this document referencing
	the ACTN components and interfaces.		the ACTN components and interfaces.
	+----------------------------+		+----------------------------+
	| Customer Service Manager |		| Customer Service Manager |
	| +-----------------------+ |		| +-----------------------+ |
	| | CNC + |		| | CNC + |
	| +-+-------------------+-+ |		| +-+-------------------+-+ |
	+----|-------------------|---+		+----|-------------------|---+
	| |		| |
	|CMI(Augmented L3SM)|CMI(VN)		|CMI(Augmented L3SM)|CMI(VN)
	skipping to change at page 9, line 28 ¶		skipping to change at page 10, line 31 ¶
	| |		| |
	V | SBI		V | SBI
	+---------------------+ |		+---------------------+ |
	/ IP/MPLS Network \ |		/ IP/MPLS Network \ |
	+-------------------------+ |		+-------------------------+ |
	V		V
	+---------------------+		+---------------------+
	/ Optical Network \		/ Optical Network \
	+-------------------------+		+-------------------------+
	Figure 2: L3VPN Architecture from the IP+Optical Network Perspective		Figure 3: L3VPN Architecture from the IP+Optical Network Perspective
	There are three main entities in the ACTN architecture and shown in		There are three main entities in the ACTN architecture and shown in
	Figure 2.		Figure 3.
	o CNC: The Customer Network Controller is responsible for generating		o CNC: The Customer Network Controller is responsible for generating
	service requests. In the context of an L3VPN, the CNC uses the		service requests. In the context of an L3VPN, the CNC uses the
	Augmented L3SM to express the service request and communicate it		Augmented L3SM to express the service request and communicate it
	to the network operator.		to the network operator.
	o MDSC: This entity is responsible for coordinating a L3VPN service		o MDSC: This entity is responsible for coordinating a L3VPN service
	request (expressed via the Augmented L3SM) with the IP/MPLS PNC		request (expressed via the Augmented L3SM) with the IP/MPLS PNC
	and the Transport PNC. For TE services, one of the key		and the Transport PNC. For TE services, one of the key
	responsibilities of the MDSC is to coordinate with both the IP PNC		responsibilities of the MDSC is to coordinate with both the IP PNC
	skipping to change at page 12, line 40 ¶		skipping to change at page 13, line 40 ¶
	As discussed in the Introduction Section, the models presented in		As discussed in the Introduction Section, the models presented in
	this document are also applicable generically outside of the ACTN		this document are also applicable generically outside of the ACTN
	architecture. [RFC8309] defines Customer Service Model between		architecture. [RFC8309] defines Customer Service Model between
	Customer and Service Orchestrator and Service Delivery Model between		Customer and Service Orchestrator and Service Delivery Model between
	Service Orchestrator and Network Orchestrator(s). TE-Service mapping		Service Orchestrator and Network Orchestrator(s). TE-Service mapping
	models defined in this document can be regarded primarily as Customer		models defined in this document can be regarded primarily as Customer
	Service Model and secondarily as Service Deliver Model.		Service Model and secondarily as Service Deliver Model.
	6. YANG Data Trees		6. YANG Data Trees
	6.1. L3SM		6.1. Service Models
			6.1.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? -> /vn:vn/vn-list/vn-id		| +--rw vn-ref? -> /vn:vn/vn-list/vn-id
	skipping to change at page 13, line 30 ¶		skipping to change at page 14, line 30 ¶
	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 vn-ref?
	| -> /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. L2SM		6.1.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? -> /vn:vn/vn-list/vn-id		| +--rw vn-ref? -> /vn:vn/vn-list/vn-id
	skipping to change at page 14, line 30 ¶		skipping to change at page 15, line 30 ¶
	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 vn-ref?
	| -> /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. L1CSM		6.1.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? -> /vn:vn/vn-list/vn-id		| +--rw vn-ref? -> /vn:vn/vn-list/vn-id
	+--:(te-topo)		+--:(te-topo)
	skipping to change at page 15, line 27 ¶		skipping to change at page 16, line 27 ¶
	+--:(te-tunnel)		+--:(te-tunnel)
	+--rw te-tunnel-list* te:tunnel-ref		+--rw te-tunnel-list* te:tunnel-ref
	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 vn-ref?
	| -> /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		6.2. Network Models
	The YANG codes are as follows:		6.2.1. L3NM
			module: ietf-l3nm-te-service-mapping
			augment /l3vpn-ntw:l3vpn-ntw/l3vpn-ntw:vpn-services
			/l3vpn-ntw:vpn-service:
			+--rw te-service-mapping!
			+--rw te-mapping
			+--rw map-type? identityref
			+--rw availability-type? identityref
			+--rw (te)?
			+--:(vn)
			| +--rw vn-ref? -> /vn:vn/vn-list/vn-id
			+--:(te-topo)
			| +--rw vn-topology-id? te-types:te-topology-id
			| +--rw abstract-node?
			| -> /nw:networks/network/node/node-id
			+--:(te-tunnel)
			+--rw te-tunnel-list* te:tunnel-ref
			augment /l3vpn-ntw:l3vpn-ntw/l3vpn-ntw:vpn-services
			/l3vpn-ntw:vpn-service/l3vpn-ntw:vpn-nodes
			/l3vpn-ntw:vpn-node/l3vpn-ntw:vpn-network-accesses
			/l3vpn-ntw:vpn-network-access:
			+--rw (te)?
			+--:(vn)
			| +--rw vn-ref?
			| -> /vn:ap/access-point-list/access-point-id
			+--:(te)
			+--rw ltp? te-types:te-tp-id
	7.1. ietf-te-service-mapping-types		6.2.2. L2NM
			module: ietf-l2nm-te-service-mapping
			augment /l2vpn-ntw:l2vpn-ntw/l2vpn-ntw:vpn-services
			/l2vpn-ntw:vpn-svc:
			+--rw te-service-mapping!
			+--rw te-mapping
			+--rw map-type? identityref
			+--rw availability-type? identityref
			+--rw (te)?
			+--:(vn)
			| +--rw vn-ref? -> /vn:vn/vn-list/vn-id
			+--:(te-topo)
			| +--rw vn-topology-id? te-types:te-topology-id
			| +--rw abstract-node?
			| -> /nw:networks/network/node/node-id
			+--:(te-tunnel)
			+--rw te-tunnel-list* te:tunnel-ref
			augment /l2vpn-ntw:l2vpn-ntw/l2vpn-ntw:vpn-services
			/l2vpn-ntw:vpn-svc/l2vpn-ntw:vpn-nodes
			/l2vpn-ntw:vpn-node/l2vpn-ntw:vpn-network-accesses
			/l2vpn-ntw:vpn-network-access:
			+--rw (te)?
			+--:(vn)
			| +--rw vn-ref?
			| -> /vn:ap/access-point-list/access-point-id
			+--:(te)
			+--rw ltp? te-types:te-tp-id
	<CODE BEGINS> file "ietf-te-service-mapping-types@2019-09-09.yang"		7. YANG Data Models
	module ietf-te-service-mapping-types {		The YANG codes are as follows:
	yang-version 1.1;		7.1. ietf-te-service-mapping-types
	namespace "urn:ietf:params:xml:ns:yang:ietf-te-service-mapping-types";		<CODE BEGINS> file "ietf-te-service-mapping-types@2020-03-08.yang"
			module ietf-te-service-mapping-types {
			yang-version 1.1;
			namespace
			"urn:ietf:params:xml:ns:yang:ietf-te-service-mapping-types";
			prefix tsm;
	prefix tsm;		import ietf-te-types {
			prefix te-types;
			reference
			"I-D.ietf-teas-yang-te-types: Traffic Engineering Common YANG
			Types";
			}
			import ietf-network {
			prefix nw;
			reference
			"RFC 8345: A YANG Data Model for Network Topologies";
			}
			import ietf-te {
			prefix te;
			reference
			"I-D.ietf-teas-yang-te: A YANG Data Model for Traffic
			Engineering Tunnels and Interfaces";
			}
			import ietf-vn {
			prefix vn;
			reference
			"I-D.ietf-teas-actn-vn-yang: A Yang Data Model for VN Operation";
			}
	import ietf-te-types {		organization
	prefix te-types;		"IETF Traffic Engineering Architecture and Signaling (TEAS)
	reference		Working Group";
	"I-D.ietf-teas-yang-te-types: Traffic Engineering Common YANG		contact
	Types";		"WG Web: <http://tools.ietf.org/wg/teas/>
	}		WG List: <mailto:teas@ietf.org>
	import ietf-network {		Editor: Young Lee
	prefix nw;		<mailto:younglee.tx@gmail.com>
	reference		Editor: Dhruv Dhody
	"RFC 8345: A YANG Data Model for Network Topologies";		<mailto:dhruv.ietf@gmail.com>
	}		Editor: Qin Wu
			<mailto:bill.wu@huawei.com>";
			description
			"This module contains a YANG module for TE & Service mapping
			parameters and policies as a common grouping applicable to
			variuous service models (e.g., L1CSM, L2SM, L3SM, etc.)
	import ietf-te {		Copyright (c) 2020 IETF Trust and the persons identified as
	prefix te;		authors of the code. All rights reserved.
	reference
	"I-D.ietf-teas-yang-te: A YANG Data Model for Traffic
	Engineering Tunnels and Interfaces";
	}
	import ietf-vn {		Redistribution and use in source and binary forms, with or
	prefix vn;		without modification, is permitted pursuant to, and subject to
	reference		the license terms contained in, the Simplified BSD License set
	"I-D.ietf-teas-actn-vn-yang: A Yang Data Model for VN Operation";		forth in Section 4.c of the IETF Trust's Legal Provisions
	}		Relating to IETF Documents
			(https://trustee.ietf.org/license-info).
	organization		This version of this YANG module is part of RFC XXXX; see the
	"IETF Traffic Engineering Architecture and Signaling (TEAS)		RFC itself for full legal notices.
	Working Group";
	contact		The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
	"WG Web: <http://tools.ietf.org/wg/teas/>		NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
	WG List: <mailto:teas@ietf.org>		'MAY', and 'OPTIONAL' in this document are to be interpreted as
			described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
			they appear in all capitals, as shown here.";
	Editor: Young Lee		revision 2020-03-08 {
	<mailto:younglee.tx@gmail.com>		description
	Editor: Dhruv Dhody		"Initial revision.";
	<mailto:dhruv.ietf@gmail.com>		reference
	Editor: Qin Wu		"RFC XXXX: Traffic Engineering and Service Mapping Yang Model";
	<mailto:bill.wu@huawei.com>";		}
	description		/*
	"This module contains a YANG module for TE & Service mapping		* Identity for map-type
	parameters and policies as a common grouping applicable to		*/
	variuous service models (e.g., L1CSM, L2SM, L3SM, etc.)
	Copyright (c) 2019 IETF Trust and the persons identified as		identity map-type {
	authors of the code. All rights reserved.		description
			"Base identity from which specific map types are derived.";
			}
	Redistribution and use in source and binary forms, with or		identity new {
	without modification, is permitted pursuant to, and subject		base map-type;
	to the license terms contained in, the Simplified BSD License		description
	set forth in Section 4.c of the IETF Trust's Legal Provisions		"The new VN/tunnels are binded to the service.";
	Relating to IETF Documents		}
	(https://trustee.ietf.org/license-info).
	This version of this YANG module is part of RFC XXXX; see the		identity hard-isolation {
	RFC itself for full legal notices.";		base new;
			description
			"Hard isolation.";
			}
	revision 2019-09-09 {		identity detnet-hard-isolation {
	description		base hard-isolation;
	"Initial revision.";		description
	reference		"Hard isolation with deterministic characteristics.";
	"RFC XXXX: Traffic Engineering and Service Mapping Yang Model";		}
	}
	/*		identity soft-isolation {
	* Identity for map-type		base new;
	*/		description
			"Soft-isolation.";
			}
	identity map-type {		identity select {
	description		base map-type;
	"Base identity from which specific map types are derived.";		description
	}		"The VPN service selects an existing tunnel with no
			modification.";
			}
	identity new {		identity modify {
	base map-type;		base map-type;
	description		description
	"The new VN/tunnels are binded to the service.";		"The VPN service selects an existing tunnel and allows to modify
	}		the properties of the tunnel (e.g., b/w)";
			}
	identity hard-isolation {		/*
	base new;		* Identity for availability-type
	description		*/
	"Hard isolation.";
	}
	identity detnet-hard-isolation {		identity availability-type {
	base hard-isolation;		description
	description		"Base identity from which specific map types are derived.";
	"Hard isolation with deterministic characteristics.";		}
	}
	identity soft-isolation {		identity level-1 {
	base new;		base availability-type;
	description		description
	"Soft-isolation.";		"level 1: 99.9999%";
	}		}
	identity select {		identity level-2 {
	base map-type;		base availability-type;
	description		description
	"The VPN service selects an existing tunnel with no		"level 2: 99.999%";
	modification.";		}
	}
	identity modify {
	base map-type;
	description
	"The VPN service selects an existing tunnel and allows to modify
	the properties of the tunnel (e.g., b/w)";
	}
	/*		identity level-3 {
	* Identity for availability-type		base availability-type;
	*/		description
			"level 3: 99.99%";
			}
	identity availability-type {		identity level-4 {
	description		base availability-type;
	"Base identity from which specific map types are derived.";		description
	}		"level 4: 99.9%";
			}
	identity level-1 {		identity level-5 {
	base availability-type;		base availability-type;
	description		description
	"level 1: 99.9999%";		"level 5: 99%";
	}		}
	identity level-2 {		/*
	base availability-type;		* Groupings
	description		*/
	"level 2: 99.999%";
	}
	identity level-3 {		grouping te-ref {
	base availability-type;		description
	description		"The reference to TE.";
	"level 3: 99.99%";		choice te {
	}		description
			"The TE";
			case vn {
			leaf vn-ref {
			type leafref {
			path "/vn:vn/vn:vn-list/vn:vn-id";
			}
			description
			"The reference to VN";
			reference
			"RFC 8453: Framework for Abstraction and Control of TE
			Networks (ACTN)";
			}
			}
			case te-topo {
			leaf vn-topology-id {
			type te-types:te-topology-id;
			description
			"An identifier to the TE Topology Model where the abstract
			nodes and links of the Topology can be found for Type 2
			VNS";
			reference
			"I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic
			Engineering (TE) Topologies";
			}
			leaf abstract-node {
			type leafref {
			path "/nw:networks/nw:network/nw:node/nw:node-id";
			}
			description
			"A reference to the abstract node in TE Topology";
			reference
			"I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic
			Engineering (TE) Topologies";
			}
			}
			case te-tunnel {
			leaf-list te-tunnel-list {
			type te:tunnel-ref;
			description
			"Reference to TE Tunnels";
			reference
			"I-D.ietf-teas-yang-te: A YANG Data Model for Traffic
			Engineering Tunnels and Interfaces";
			}
			}
			}
			}
	identity level-4 {		//grouping
	base availability-type;
	description
	"level 4: 99.9%";
	}
	identity level-5 {		grouping te-endpoint-ref {
	base availability-type;		description
	description		"The reference to TE endpoints.";
	"level 5: 99%";		choice te {
	}		description
			"The TE";
			case vn {
			leaf vn-ref {
			type leafref {
			path "/vn:ap/vn:access-point-list/vn:access-point-id";
			}
			description
			"The reference to VN AP";
			reference
			"RFC 8453: Framework for Abstraction and Control of TE
			Networks (ACTN)";
			}
			}
			case te {
			leaf ltp {
			type te-types:te-tp-id;
			description
			"Reference LTP in the TE-topology";
			reference
			"I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic
			Engineering (TE) Topologies";
			}
			}
			}
			}
	/*		//grouping
	* Groupings
	*/
	grouping te-ref {		grouping te-mapping {
	description		description
	"The reference to TE.";		"Mapping between Services and TE";
	choice te {		container te-mapping {
	description		description
	"The TE";		"Mapping between Services and TE";
	case vn {		leaf map-type {
	leaf vn-ref {		type identityref {
	type leafref {		base map-type;
	path "/vn:vn/vn:vn-list/vn:vn-id";		}
	}		description
	description		"Isolation Requirements, Tunnel Bind or
	"The reference to VN";		Tunnel Selection";
	reference		}
	"RFC 8453: Framework for Abstraction and Control of TE		leaf availability-type {
	Networks (ACTN)";		type identityref {
	}		base availability-type;
	}		}
	case te-topo {		description
	leaf vn-topology-id{		"Availability Requirement for the Service";
	type te-types:te-topology-id;		}
	description		uses te-ref;
	"An identifier to the TE Topology Model where the abstract		}
	nodes and links of the Topology can be found for Type 2		}
	VNS";
	reference
	"I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic
	Engineering (TE) Topologies";
	}
	leaf abstract-node {
	type leafref {
	path "/nw:networks/nw:network/nw:node/nw:node-id";
	}
	description
	"A reference to the abstract node in TE Topology";
	reference
	"I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic
	Engineering (TE) Topologies";
	}
	}
	case te-tunnel {
	leaf-list te-tunnel-list {
	type te:tunnel-ref;
	description
	"Reference to TE Tunnels";
	reference
	"I-D.ietf-teas-yang-te: A YANG Data Model for Traffic
	Engineering Tunnels and Interfaces";
	}
	}
	}
	}//grouping
	grouping te-endpoint-ref {		//grouping
	description		}
	"The reference to TE endpoints.";
	choice te {
	description
	"The TE";
	case vn {
	leaf vn-ref {
	type leafref {
	path "/vn:ap/vn:access-point-list/vn:access-point-id";
	}
	description
	"The reference to VN AP";
	reference
	"RFC 8453: Framework for Abstraction and Control of TE
	Networks (ACTN)";
	}
	}
	case te {
	leaf ltp {
	type te-types:te-tp-id;
	description
	"Reference LTP in the TE-topology";
	reference
	"I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic
	Engineering (TE) Topologies";
	}
	}
	}
	}//grouping
	grouping te-mapping {		<CODE ENDS>
	description
	"Mapping between Services and TE";
	container te-mapping {
	description
	"Mapping between Services and TE";
	leaf map-type {
	type identityref {
	base map-type;
	}
	description
	"Isolation Requirements, Tunnel Bind or
	Tunnel Selection";
	}
	leaf availability-type {
	type identityref {
	base availability-type;
	}
	description
	"Availability Requirement for the Service";
	}
	uses te-ref;
	}
	}//grouping
	}//module
	<CODE ENDS>		7.2. Service Models
	7.2. ietf-l3sm-te-service-mapping		7.2.1. ietf-l3sm-te-service-mapping
	<CODE BEGINS> file "ietf-l3sm-te-service-mapping@2019-09-09.yang"		<CODE BEGINS> file "ietf-l3sm-te-service-mapping@2020-03-08.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";
	}		}
	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>
	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.
	skipping to change at page 22, line 14 ¶		skipping to change at page 25, line 24 ¶
	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) 2019 IETF Trust and the persons identified as		Copyright (c) 2020 IETF Trust and the persons identified as
	authors of the code. All rights reserved.		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		without modification, is permitted pursuant to, and subject to
	to the license terms contained in, the Simplified BSD License		the license terms contained in, the Simplified BSD License set
	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 2019-09-09 {		The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
			NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
			'MAY', and 'OPTIONAL' in this document are to be interpreted as
			described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
			they appear in all capitals, as shown here.";
			revision 2020-03-08 {
	description		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		presence "Indicates L3 service to TE mapping";
	"Indicates L3 service to TE mapping";		description
	description		"Container to augment l3sm to TE parameters and mapping";
	"Container to augment l3sm to TE parameters and mapping";		uses tsm-types:te-mapping;
	uses tsm-types:te-mapping;		}
	}		}
	}//augment
			//augment
	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" {
	description		description
	"This augment is only valid for TE mapping of L3SM network-access		"This augment is only valid for TE mapping of L3SM network-access
	to TE endpoints";		to TE endpoints";
	uses tsm-types:te-endpoint-ref;		uses tsm-types:te-endpoint-ref;
	}//augment		}
	}//module
			//augment
			}
	<CODE ENDS>		<CODE ENDS>
	7.3. ietf-l2sm-te-service-mapping		7.2.2. ietf-l2sm-te-service-mapping
	<CODE BEGINS> file "ietf-l2sm-te-service-mapping@2019-09-09.yang"		<CODE BEGINS> file "ietf-l2sm-te-service-mapping@2020-03-08.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";
	}		}
	import ietf-l2vpn-svc {		import ietf-l2vpn-svc {
	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";
	skipping to change at page 24, line 5 ¶		skipping to change at page 27, line 20 ¶
	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>
	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) 2019 IETF Trust and the persons identified as		Copyright (c) 2020 IETF Trust and the persons identified as
	authors of the code. All rights reserved.		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		without modification, is permitted pursuant to, and subject to
	to the license terms contained in, the Simplified BSD License		the license terms contained in, the Simplified BSD License set
	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 2019-09-09 {		The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
			NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
			'MAY', and 'OPTIONAL' in this document are to be interpreted as
			described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
			they appear in all capitals, as shown here.";
			revision 2020-03-08 {
	description		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 "/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" {
	description		description
	"L2SM augmented to include TE parameters and mapping";		"L2SM augmented to include TE parameters and mapping";
	container te-service-mapping {		container te-service-mapping {
	presence		presence "indicates L2 service to te mapping";
	"indicates L2 service to te mapping";
	description		description
	"Container to augment L2SM to TE parameters and mapping";		"Container to augment L2SM to TE parameters and mapping";
	uses tsm-types:te-mapping;		uses tsm-types:te-mapping;
	}		}
	}//augment		}
			//augment
	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" {
	description		description
	"This augment is only valid for TE mapping of L2SM network-access		"This augment is only valid for TE mapping of L2SM network-access
	to TE endpoints";		to TE endpoints";
			uses tsm-types:te-endpoint-ref;
			}
			//augment
			}
			<CODE ENDS>
			7.2.3. ietf-l1csm-te-service-mapping
			<CODE BEGINS> file "ietf-l1csm-te-service-mapping@2020-03-08.yang"
			module ietf-l1csm-te-service-mapping {
			yang-version 1.1;
			namespace
			"urn:ietf:params:xml:ns:yang:ietf-l1csm-te-service-mapping";
			prefix l1-tsm;
			import ietf-te-service-mapping-types {
			prefix tsm-types;
			reference
			"RFC XXXX: Traffic Engineering and Service Mapping Yang Model";
			}
			import ietf-l1csm {
			prefix l1csm;
			reference
			"I-D.ietf-ccamp-l1csm-yang: A YANG Data Model for L1 Connectivity
			Service Model (L1CSM)";
			}
			organization
			"IETF Traffic Engineering Architecture and Signaling (TEAS)
			Working Group";
			contact
			"WG Web: <http://tools.ietf.org/wg/teas/>
			WG List: <mailto:teas@ietf.org>
			Editor: Young Lee
			<mailto:younglee.tx@gmail.com>
			Editor: Dhruv Dhody
			<mailto:dhruv.ietf@gmail.com>
			Editor: Qin Wu
			<mailto:bill.wu@huawei.com>";
			description
			"This module contains a YANG module for the mapping of
			Layer 1 Connectivity Service Module (L1CSM) to the TE and VN
			Copyright (c) 2020 IETF Trust and the persons identified as
			authors of the code. All rights reserved.
			Redistribution and use in source and binary forms, with or
			without modification, is permitted pursuant to, and subject to
			the license terms contained in, the Simplified BSD License set
			forth in Section 4.c of the IETF Trust's Legal Provisions
			Relating to IETF Documents
			(https://trustee.ietf.org/license-info).
			This version of this YANG module is part of RFC XXXX; see the
			RFC itself for full legal notices.
			The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
			NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
			'MAY', and 'OPTIONAL' in this document are to be interpreted as
			described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
			they appear in all capitals, as shown here.";
			revision 2020-03-08 {
			description
			"Initial revision.";
			reference
			"RFC XXXX: Traffic Engineering and Service Mapping Yang Model";
			}
			/*
			* Augmentation to L1CSM
			*/
			augment "/l1csm:l1-connectivity/l1csm:services/l1csm:service" {
			description
			"L1CSM augmented to include TE parameters and mapping";
			container te-service-mapping {
			presence "Indicates L1 service to TE mapping";
			description
			"Container to augment L1CSM to TE parameters and mapping";
			uses tsm-types:te-mapping;
			}
			}
			//augment
			augment "/l1csm:l1-connectivity/l1csm:access/l1csm:unis/"
			+ "l1csm:uni" {
			description
			"This augment is only valid for TE mapping of L1CSM UNI to TE
			endpoints";
	uses tsm-types:te-endpoint-ref;		uses tsm-types:te-endpoint-ref;
	}//augment		}
	}//module
			//augment
			}
	<CODE ENDS>		<CODE ENDS>
	7.4. ietf-l1csm-te-service-mapping		7.3. Network Models
	<CODE BEGINS> file "ietf-l1csm-te-service-mapping@2019-09-09.yang"		7.3.1. ietf-l3nm-te-service-mapping
	module ietf-l1csm-te-service-mapping {
	yang-version 1.1;		<CODE BEGINS> file "ietf-l3nm-te-service-mapping@2020-03-08.yang"
			module ietf-l3nm-te-service-mapping {
			yang-version 1.1;
			namespace
			"urn:ietf:params:xml:ns:yang:ietf-l3nm-te-service-mapping";
			prefix l3nm-tsm;
	namespace "urn:ietf:params:xml:ns:yang:ietf-l1csm-te-service-mapping";		import ietf-te-service-mapping-types {
			prefix tsm-types;
			reference
			"RFC XXXX: Traffic Engineering and Service Mapping Yang Model";
			}
			import ietf-l3vpn-ntw {
			prefix l3vpn-ntw;
			reference
			"I-D.ietf-opsawg-l3sm-l3nm: A Layer 3 VPN Network YANG Model";
	prefix l1-tsm;		}
			organization
			"IETF Traffic Engineering Architecture and Signaling (TEAS)
			Working Group";
			contact
			"WG Web: <http://tools.ietf.org/wg/teas/>
			WG List: <mailto:teas@ietf.org>
			Editor: Young Lee
			<mailto:younglee.tx@gmail.com>
			Editor: Dhruv Dhody
			<mailto:dhruv.ietf@gmail.com>
			Editor: Qin Wu
			<mailto:bill.wu@huawei.com>";
			description
			"This module contains a YANG module for the mapping of Layer 3
			Network Model (L3NM) to the TE and VN.
			Copyright (c) 2020 IETF Trust and the persons identified as
			authors of the code. All rights reserved.
			Redistribution and use in source and binary forms, with or
			without modification, is permitted pursuant to, and subject to
			the license terms contained in, the Simplified BSD License set
			forth in Section 4.c of the IETF Trust's Legal Provisions
			Relating to IETF Documents
			(https://trustee.ietf.org/license-info).
			This version of this YANG module is part of RFC XXXX; see the
			RFC itself for full legal notices.
			The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
			NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
			'MAY', and 'OPTIONAL' in this document are to be interpreted as
			described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
			they appear in all capitals, as shown here.";
			revision 2020-03-08 {
			description
			"Initial revision.";
			reference
			"RFC XXXX: Traffic Engineering and Service Mapping Yang Model";
			}
			/*
			* Augmentation to L3NM
			*/
			augment "/l3vpn-ntw:l3vpn-ntw/l3vpn-ntw:vpn-services"
			+ "/l3vpn-ntw:vpn-service" {
			description
			"L3SM augmented to include TE parameters and mapping";
			container te-service-mapping {
			presence "Indicates L3 network to TE mapping";
			description
			"Container to augment l3nm to TE parameters and mapping";
			uses tsm-types:te-mapping;
			}
			}
			//augment
			augment "/l3vpn-ntw:l3vpn-ntw/l3vpn-ntw:vpn-services"
			+ "/l3vpn-ntw:vpn-service"
			+ "/l3vpn-ntw:vpn-nodes/l3vpn-ntw:vpn-node"
			+ "/l3vpn-ntw:vpn-network-accesses"
			+ "/l3vpn-ntw:vpn-network-access" {
			description
			"This augment is only valid for TE mapping of L3NM network-access
			to TE endpoints";
			uses tsm-types:te-endpoint-ref;
			}
			//augment
			}
			<CODE ENDS>
			7.3.2. ietf-l2nm-te-service-mapping
			<CODE BEGINS> file "ietf-l2nm-te-service-mapping@2020-03-08.yang"
			module ietf-l2nm-te-service-mapping {
			yang-version 1.1;
			namespace
			"urn:ietf:params:xml:ns:yang:ietf-l2nm-te-service-mapping";
			prefix l2nm-tsm;
	import ietf-te-service-mapping-types {		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-l1csm {		prefix l2vpn-ntw;
	prefix l1csm;
	reference		reference
	"I-D.ietf-ccamp-l1csm-yang: A YANG Data Model for L1 Connectivity		"I-D.-barguil-opsawg-l2sm-l2nm: A Layer 2 VPN Network YANG Model";
	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: <http://tools.ietf.org/wg/teas/>
	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>";
	skipping to change at page 25, line 48 ¶		skipping to change at page 33, line 20 ¶
	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>
	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 2
	Layer 1 Connectivity Service Module (L1CSM) to the TE and VN		Network Model (L2NM) to the TE and VN.
	Copyright (c) 2019 IETF Trust and the persons identified as
			Copyright (c) 2020 IETF Trust and the persons identified as
	authors of the code. All rights reserved.		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		without modification, is permitted pursuant to, and subject to
	to the license terms contained in, the Simplified BSD License		the license terms contained in, the Simplified BSD License set
	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 2019-09-09 {		The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
			NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
			'MAY', and 'OPTIONAL' in this document are to be interpreted as
			described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
			they appear in all capitals, as shown here.";
			revision 2020-03-08 {
	description		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 L2NM
	*/		*/
	augment "/l1csm:l1-connectivity/l1csm:services/l1csm:service" {
			augment "/l2vpn-ntw:l2vpn-ntw/l2vpn-ntw:vpn-services"
			+ "/l2vpn-ntw:vpn-svc" {
	description		description
	"L1CSM augmented to include TE parameters and mapping";		"L2SM augmented to include TE parameters and mapping";
	container te-service-mapping {		container te-service-mapping {
	presence		presence "Indicates L2 network to TE mapping";
	"Indicates L1 service to TE mapping";
	description		description
	"Container to augment L1CSM to TE parameters and mapping";		"Container to augment l2nm to TE parameters and mapping";
	uses tsm-types:te-mapping;		uses tsm-types:te-mapping;
	}		}
	}//augment		}
	augment "/l1csm:l1-connectivity/l1csm:access/l1csm:unis/"		//augment
	+ "l1csm:uni" {
			augment "/l2vpn-ntw:l2vpn-ntw/l2vpn-ntw:vpn-services"
			+ "/l2vpn-ntw:vpn-svc"
			+ "/l2vpn-ntw:vpn-nodes/l2vpn-ntw:vpn-node"
			+ "/l2vpn-ntw:vpn-network-accesses"
			+ "/l2vpn-ntw:vpn-network-access" {
	description		description
	"This augment is only valid for TE mapping of L1CSM UNI to TE		"This augment is only valid for TE mapping of L2NM network-access
	endpoints";		to TE endpoints";
	uses tsm-types:te-endpoint-ref;		uses tsm-types:te-endpoint-ref;
	}//augment		}
	}//module
			//augment
			}
			<CODE ENDS>
	<CODE ENDS>
	8. Security Considerations		8. Security Considerations
	The YANG modules defined in this document is designed to be accessed		The YANG modules defined in this document is designed to be accessed
	via network management protocol such as NETCONF [RFC6241] or RESTCONF		via network management protocol such as NETCONF [RFC6241] or RESTCONF
	[RFC8040]. The lowest NETCONF layer is the secure transport layer		[RFC8040]. The lowest NETCONF layer is the secure transport layer
	and the mandatory-to-implement secure transport is SSH [RFC6242].		and the mandatory-to-implement secure transport is SSH [RFC6242].
	The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement		The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement
	secure transport is TLS [RFC8446]		secure transport is TLS [RFC8446]
	The NETCONF access control model [RFC8341] provides the means to		The NETCONF access control model [RFC8341] provides the means to
	skipping to change at page 27, line 44 ¶		skipping to change at page 35, line 26 ¶
	o /l2vpn-svc/sites/site/site-network-accesses/site-network-access/		o /l2vpn-svc/sites/site/site-network-accesses/site-network-access/
	te/ - configure TE Endpoint mapping.		te/ - configure TE Endpoint mapping.
	o /l1-connectivity/services/service/te-service-mapping/te-mapping/ -		o /l1-connectivity/services/service/te-service-mapping/te-mapping/ -
	configure TE Service mapping.		configure TE Service mapping.
	o /l1-connectivity/access/unis/uni/te/ - configure TE Endpoint		o /l1-connectivity/access/unis/uni/te/ - configure TE Endpoint
	mapping.		mapping.
			o /l3vpn-ntw/vpn-services/vpn-service/te-service-mapping/te-mapping/
			- configure TE Network mapping.
			o /l3vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/vpn-
			network-accesses/vpn-network-access/te/ - configure TE Endpoint
			mapping.
			o /l2vpn-ntw/vpn-services/vpn-service/te-service-mapping/te-mapping/
			- configure TE Network mapping.
			o /l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/vpn-
			network-accesses/vpn-network-access/te/ - configure TE Endpoint
			mapping.
	Unauthorized access to above list can adversely affect the VPN		Unauthorized access to above list can adversely affect the VPN
	service.		service.
	Some of the readable data nodes in the YANG module may be considered		Some of the readable data nodes in the YANG module may be considered
	sensitive or vulnerable in some network environments. It is thus		sensitive or vulnerable in some network environments. It is thus
	important to control read access (e.g., via get, get-config, or		important to control read access (e.g., via get, get-config, or
	notification) to these data nodes. The TE related parameters		notification) to these data nodes. The TE related parameters
	attached to the VPN service can leak sensitive information about the		attached to the VPN service can leak sensitive information about the
	network. This is apploicable to all elements in the yang models		network. This is apploicable to all elements in the yang models
	defined in this document.		defined in this document.
	skipping to change at page 28, line 31 ¶		skipping to change at page 36, line 27 ¶
	XML: N/A, the requested URI is an XML namespace.		XML: N/A, the requested URI is an XML namespace.
	URI: urn:ietf:params:xml:ns:yang:ietf-l2sm-te-service-mapping		URI: urn:ietf:params:xml:ns:yang:ietf-l2sm-te-service-mapping
	Registrant Contact: The IESG.		Registrant Contact: The IESG.
	XML: N/A, the requested URI is an XML namespace.		XML: N/A, the requested URI is an XML namespace.
	URI: urn:ietf:params:xml:ns:yang:ietf-l1csm-te-service-mapping		URI: urn:ietf:params:xml:ns:yang:ietf-l1csm-te-service-mapping
	Registrant Contact: The IESG.		Registrant Contact: The IESG.
	XML: N/A, the requested URI is an XML namespace.		XML: N/A, the requested URI is an XML namespace.
			URI: urn:ietf:params:xml:ns:yang:ietf-l3nm-te-service-mapping
			Registrant Contact: The IESG.
			XML: N/A, the requested URI is an XML namespace.
			URI: urn:ietf:params:xml:ns:yang:ietf-l2nm-te-service-mapping
			Registrant Contact: The IESG.
			XML: N/A, the requested URI is an XML namespace.
	This document request the IANA to register four YANG modules in the		This document request the IANA to register four YANG modules in the
	"YANG Module Names" registry [RFC6020], as follows -		"YANG Module Names" registry [RFC6020], as follows -
	Name: ietf-te-service-mapping-types		Name: ietf-te-service-mapping-types
	Namespace: urn:ietf:params:xml:ns:yang:ietf-te-service-mapping-types		Namespace: urn:ietf:params:xml:ns:yang:ietf-te-service-mapping-types
	Prefix: tsm		Prefix: tsm
	Reference: [This.I-D]		Reference: [This.I-D]
	Name: ietf-l3sm-te-service-mapping		Name: ietf-l3sm-te-service-mapping
	Namespace: urn:ietf:params:xml:ns:yang:ietf-l3sm-te-service-mapping		Namespace: urn:ietf:params:xml:ns:yang:ietf-l3sm-te-service-mapping
	Prefix: l3-tsm		Prefix: l3-tsm
	skipping to change at page 29, line 24 ¶		skipping to change at page 37, line 24 ¶
	Name: ietf-l2sm-te-service-mapping		Name: ietf-l2sm-te-service-mapping
	Namespace: urn:ietf:params:xml:ns:yang:ietf-l2sm-te-service-mapping		Namespace: urn:ietf:params:xml:ns:yang:ietf-l2sm-te-service-mapping
	Prefix: l2-tsm		Prefix: l2-tsm
	Reference: [This.I-D]		Reference: [This.I-D]
	Name: ietf-l1csm-te-service-mapping		Name: ietf-l1csm-te-service-mapping
	Namespace: urn:ietf:params:xml:ns:yang:ietf-l1csm-te-service-mapping		Namespace: urn:ietf:params:xml:ns:yang:ietf-l1csm-te-service-mapping
	Prefix: l1-tsm		Prefix: l1-tsm
	Reference: [This.I-D]		Reference: [This.I-D]
			Name: ietf-l3nm-te-service-mapping
			Namespace: urn:ietf:params:xml:ns:yang:ietf-l3nm-te-service-mapping
			Prefix: l3nm-tsm
			Reference: [This.I-D]
			Name: ietf-l2nm-te-service-mapping
			Namespace: urn:ietf:params:xml:ns:yang:ietf-l2nm-te-service-mapping
			Prefix: l2nm-tsm
			Reference: [This.I-D]
	10. Acknowledgements		10. Acknowledgements
	We thank Diego Caviglia and Igor Bryskin for useful discussions and		We thank Diego Caviglia, Igor Bryskin, Oscar Gonzalez de Dios, and
	motivation for this work.		Samier Barguil Giraldo for useful discussions and motivation for this
			work.
	11. References		11. References
	11.1. Normative References		11.1. Normative References
	[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>.
	[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure		[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
	skipping to change at page 30, line 46 ¶		skipping to change at page 39, line 8 ¶
	[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., Dhody, D., Dios, O., and D.
	Ceccarelli, "A YANG Data Model for L1 Connectivity Service		Ceccarelli, "A YANG Data Model for L1 Connectivity Service
	Model (L1CSM)", draft-ietf-ccamp-l1csm-yang-10 (work in		Model (L1CSM)", draft-ietf-ccamp-l1csm-yang-10 (work in
	progress), September 2019.		progress), September 2019.
	[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-06 (work in progress), July 2019.		teas-actn-vn-yang-07 (work in progress), October 2019.
	[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 and
	Interfaces", draft-ietf-teas-yang-te-21 (work in		Interfaces", draft-ietf-teas-yang-te-22 (work in
	progress), April 2019.		progress), November 2019.
	[I-D.ietf-teas-yang-te-types]		[I-D.ietf-teas-yang-te-types]
	Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,		Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,
	"Traffic Engineering Common YANG Types", draft-ietf-teas-		"Traffic Engineering Common YANG Types", draft-ietf-teas-
	yang-te-types-10 (work in progress), July 2019.		yang-te-types-13 (work in progress), November 2019.
			[I-D.ietf-opsawg-l3sm-l3nm]
			Aguado, A., Dios, O., Lopezalvarez, V., Voyer, D., and L.
			Munoz, "A Layer 3 VPN Network YANG Model", draft-ietf-
			opsawg-l3sm-l3nm-01 (work in progress), November 2019.
			[I-D.barguil-opsawg-l2sm-l2nm]
			Barguil, S., Dios, O., Lopezalvarez, V., Munoz, L., and L.
			Jalil, "A Layer 2 VPN Network Yang Model", draft-barguil-
			opsawg-l2sm-l2nm-00 (work in progress), December 2019.
	11.2. Informative References		11.2. Informative References
	[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>.
	[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
	skipping to change at page 31, line 50 ¶		skipping to change at page 40, line 25 ¶
	[I-D.ietf-teas-yang-te-topo]		[I-D.ietf-teas-yang-te-topo]
	Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and		Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and
	O. Dios, "YANG Data Model for Traffic Engineering (TE)		O. Dios, "YANG Data Model for Traffic Engineering (TE)
	Topologies", draft-ietf-teas-yang-te-topo-22 (work in		Topologies", draft-ietf-teas-yang-te-topo-22 (work in
	progress), June 2019.		progress), June 2019.
	[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-04 (work in		Networks", draft-ietf-teas-actn-yang-05 (work in
	progress), August 2019.		progress), February 2020.
	Appendix A. Contributor Addresses		Appendix A. 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
	skipping to change at page 32, line 25 ¶		skipping to change at page 40, line 48 ¶
	EMail: Italo.Busi@huawei.com		EMail: Italo.Busi@huawei.com
	Haomian Zheng		Haomian Zheng
	Huawei Technologies		Huawei Technologies
	EMail: zhenghaomian@huawei.com		EMail: zhenghaomian@huawei.com
	Authors' Addresses		Authors' Addresses
	Young Lee (editor)		Young Lee (editor)
	SKKU		Samsung Electronics
	Email: younglee.tx@gmail.com		Email: younglee.tx@gmail.com
	Dhruv Dhody (editor)		Dhruv Dhody (editor)
	Huawei Technologies		Huawei Technologies
	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
End of changes. 120 change blocks.
	372 lines changed or deleted		752 lines changed or added
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/