< draft-contreras-teas-slice-controller-models-00.txt		draft-contreras-teas-slice-controller-models-01.txt >
	TEAS LM. Contreras		TEAS LM. Contreras
	Internet-Draft Telefonica		Internet-Draft Telefonica
	Intended status: Informational R. Rokui		Intended status: Informational R. Rokui
	Expires: May 6, 2021 Nokia		Expires: August 26, 2021 Nokia
	J. Tantsura		J. Tantsura
	Apstra		Apstra
	B. Wu		B. Wu
	Huawei		Huawei
	X. Liu		X. Liu
	Volta		Volta
	D. Dhody		D. Dhody
	Huawei		Huawei
	S. Belloti		S. Belloti
	Nokia		Nokia
	November 2, 2020		February 22, 2021
	IETF Network Slice Controller and its associated data models		IETF Network Slice Controller and its associated data models
	draft-contreras-teas-slice-controller-models-00		draft-contreras-teas-slice-controller-models-01
	Abstract		Abstract
	This document describes the major functional components of an IETF		This document describes the major functional components of an IETF
	Network Slice Controller (NSC) as well as references the data models		Network Slice Controller (NSC) as well as references the data models
	required for supporting the requests of IETF network slices and their		required for supporting the requests of IETF network slices and their
	realization.		realization.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 44 ¶		skipping to change at page 1, line 44 ¶
	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 May 6, 2021.		This Internet-Draft will expire on August 26, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 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		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 . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. IETF Network Slice data models . . . . . . . . . . . . . . . 3		2. IETF Network Slice data models . . . . . . . . . . . . . . . 3
	3. Structure of the IETF Network Slice Controller (NSC) . . . . 4		3. Structure of the IETF Network Slice Controller (NSC) . . . . 4
	4. Security Considerations . . . . . . . . . . . . . . . . . . . 7		3.1. NS Mapper . . . . . . . . . . . . . . . . . . . . . . . . 7
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7		3.2. NS Realizer . . . . . . . . . . . . . . . . . . . . . . . 7
	6. References . . . . . . . . . . . . . . . . . . . . . . . . . 7		4. Model types in IETF Network Slice Controller interfaces . . . 7
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8		5. Security Considerations . . . . . . . . . . . . . . . . . . . 8
			6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
			7. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
			Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
	1. Introduction		1. Introduction
	Editor's Note: the terminology in this draft will be aligned with the		Editor's Note: the terminology in this draft will be aligned with the
	final terminology selected for describing the notion of IETF Network		final terminology selected for describing the notion of IETF Network
	Slice when applied to IETF technologies, which is currently under		Slice when applied to IETF technologies, which is currently under
	discussion. By now same terminology as used in		discussion. By now same terminology as used in
	[I-D.nsdt-teas-ietf-network-slice-definition] and		[I-D.nsdt-teas-ietf-network-slice-definition] and
	[I-D.nsdt-teas-ns-framework] is primarily used here. Consensus to		[I-D.nsdt-teas-ns-framework] is primarily used here. Consensus to
	use "IETF Network Slice" term has been reached.		use "IETF Network Slice" term has been reached.
	skipping to change at page 6, line 31 ¶		skipping to change at page 6, line 31 ¶
	| ------------------- |		| ------------------- |
	| | (c) |		| | (c) |
	---------------------------		---------------------------
	|		|
	v		v
	Network Controllers		Network Controllers
	Figure 2: IETF Network Slice Controller structure and asspociated		Figure 2: IETF Network Slice Controller structure and asspociated
	data models		data models
	TODO item #1 - Breakdown "NS mapper" and "NS Realizer" to their		IETF Network Slices with different level of detail could be
	logical components.		requested:
	TODO item #2- Add complementarity of the models for satisfying Type 1
	and Type 2 Services as per [RFC8453]. Discussion: equivalent to the
	Virtual Network (VN) described in [RFC8453], there are two views of
	an IETF network slices as well:
	o The IETF network slice can be abstracted as a set of edge-to-edge		o The IETF network slice can be abstracted as a set of edge-to-edge
	links (Type 1).		links (Type 1).
	o The IETF network slice can be abstracted as a topology of virtual		o The IETF network slice can be abstracted as a topology of virtual
	nodes and virtual links (Type 2) which represent the partitioning		nodes and virtual links (Type 2) which represent the partitioning
	of underlay network resources for use by network slice		of underlay network resources for use by network slice
	connectivity.		connectivity.
	The use cases of these two types of networks are further described by		The use cases of these two types of networks are further described by
	[RFC8453]. [I-D.wd-teas-ietf-network-slice-nbi-yang] models the Type		[RFC8453]. [I-D.wd-teas-ietf-network-slice-nbi-yang] models the Type
	1 service, while [I-D.liu-teas-transport-network-slice-yang] models		1 service, while [I-D.liu-teas-transport-network-slice-yang] models
	the Type 2 service. When a customer intends to request a Type 2		the Type 2 service. When a customer intends to request a Type 2
	service, [I-D.liu-teas-transport-network-slice-yang] can also be used		service, [I-D.liu-teas-transport-network-slice-yang] can also be used
	at the point (a) in Figure 2. As an example, when ACTN is used to		at the point (a) in Figure 2. As an example, when ACTN is used to
	realize an IETF network slice, model mappings are described in more		realize an IETF network slice, model mappings are described in more
	details in [I-D.ietf-teas-actn-yang].		details in [I-D.ietf-teas-actn-yang].
	4. Security Considerations		3.1. NS Mapper
			The Mapper will receive the IETF Network Slice request from the
			customer. It will process it obtaining an overall view of how this
			new request complements or fits with the rest of IETF Network Slices,
			if any, as provisioned in the network. As part of that processing, a
			single customer IETF Network Slice request could result in the need
			of actually provisioning different IETF Network Slices in the
			network. The Mapper will maintain the relationship among customer
			IETF Network Slice request and provisioned IETF Network Slices.
			3.2. NS Realizer
			The Realizer will receive from the Mapper one or more requests for
			provision of IETF Network Slices, potentially including some
			technology-specific information. With that information, the Realizer
			will determine the realization of each particular IETF Network Slice
			interacting with technology-specific Network Controllers.
			4. Model types in IETF Network Slice Controller interfaces
			Both [RFC8309] and [RFC8969] offer a complete view of customer,
			service and network model types. In this sense a potential mapping
			of models to IETF Network Slcie Controller interfaces is as follows:
			o NBI of the IETF NSC (interface (a) in Figure 2) -> Customer
			service model. According to [RFC8309] "a customer's service
			request is (or should be) technology agnostic. That is, a
			customer is unaware of the technology that the network operator
			has available to deliver the service, so the customer does not
			make requests specific to the underlying technology but is limited
			to making requests specific to the service that is to be
			delivered". This definition matches the expected behavior of the
			IETF NSC NBI as considered in in
			[I-D.nsdt-teas-ietf-network-slice-definition] and
			[I-D.nsdt-teas-ns-framework].
			o Interface between NS Mapper and NS Realizer (interface (b) in
			Figure 2) -> Service Delivery model. According to [RFC8309] "a
			service delivery module is expressed as a core set of parameters
			that are common across a network type and technology [...] Service
			delivery modules include technology-specific modules.".
			Furthermore, [RFC8969] (in its Figures 3 and 5) considers L3SM or
			VN Service models to be later on fed into a controller.
			o SBI of the IETF NSC (interface (c) in Figure 2) -> Network
			Configuration model. According to [RFC8309] "the orchestrator
			must map the service request to its view, and this mapping may
			include a choice of which networks and technologies to use
			depending on which service features have been requested". This is
			coincideent with the expected behavior of the IETF NSC SBI as
			considered in in [I-D.nsdt-teas-ietf-network-slice-definition] and
			[I-D.nsdt-teas-ns-framework].
			5. Security Considerations
	To be done.		To be done.
	5. IANA Considerations		6. IANA Considerations
	This draft does not include any IANA considerations		This draft does not include any IANA considerations
	6. References		7. References
	[I-D.ietf-teas-actn-yang]		[I-D.ietf-teas-actn-yang]
	Lee, Y., Zheng, H., Ceccarelli, D., Yoon, B., Dios, O.,		Lee, Y., Zheng, H., Ceccarelli, D., Yoon, B., Dios, O.,
	Shin, J., and S. Belotti, "Applicability of YANG models		Shin, J., and S. Belotti, "Applicability of YANG models
	for Abstraction and Control of Traffic Engineered		for Abstraction and Control of Traffic Engineered
	Networks", draft-ietf-teas-actn-yang-06 (work in		Networks", draft-ietf-teas-actn-yang-06 (work in
	progress), August 2020.		progress), August 2020.
	[I-D.liu-teas-transport-network-slice-yang]		[I-D.liu-teas-transport-network-slice-yang]
	Liu, X., Tantsura, J., Bryskin, I., Contreras, L., WU, Q.,		Liu, X., Tantsura, J., Bryskin, I., Contreras, L., WU, Q.,
	Belotti, S., and R. Rokui, "Transport Network Slice YANG		Belotti, S., and R. Rokui, "IETF Network Slice YANG Data
	Data Model", draft-liu-teas-transport-network-slice-		Model", draft-liu-teas-transport-network-slice-yang-02
	yang-01 (work in progress), July 2020.		(work in progress), November 2020.
	[I-D.nsdt-teas-ietf-network-slice-definition]		[I-D.nsdt-teas-ietf-network-slice-definition]
	Rokui, R., Homma, S., Makhijani, K., Contreras, L., and J.		Rokui, R., Homma, S., Makhijani, K., Contreras, L., and J.
	Tantsura, "Definition of IETF Network Slices", draft-nsdt-		Tantsura, "Definition of IETF Network Slices", draft-nsdt-
	teas-ietf-network-slice-definition-00 (work in progress),		teas-ietf-network-slice-definition-02 (work in progress),
	October 2020.		December 2020.
	[I-D.nsdt-teas-ns-framework]		[I-D.nsdt-teas-ns-framework]
	Gray, E. and J. Drake, "Framework for Transport Network		Gray, E. and J. Drake, "Framework for Transport Network
	Slices", draft-nsdt-teas-ns-framework-04 (work in		Slices", draft-nsdt-teas-ns-framework-04 (work in
	progress), July 2020.		progress), July 2020.
	[I-D.wd-teas-ietf-network-slice-nbi-yang]		[I-D.wd-teas-ietf-network-slice-nbi-yang]
	Bo, W., Dhody, D., Han, L., and R. Rokui, "A Yang Data		Bo, W., Dhody, D., Han, L., and R. Rokui, "A Yang Data
	Model for IETF Network Slice NBI", draft-wd-teas-ietf-		Model for IETF Network Slice NBI", draft-wd-teas-ietf-
	network-slice-nbi-yang-00 (work in progress), October		network-slice-nbi-yang-01 (work in progress), November
	2020.		2020.
			[RFC8309] Wu, Q., Liu, W., and A. Farrel, "Service Models
			Explained", RFC 8309, DOI 10.17487/RFC8309, January 2018,
			<https://www.rfc-editor.org/info/rfc8309>.
	[RFC8453] Ceccarelli, D., Ed. and Y. Lee, Ed., "Framework for		[RFC8453] Ceccarelli, D., Ed. and Y. Lee, Ed., "Framework for
	Abstraction and Control of TE Networks (ACTN)", RFC 8453,		Abstraction and Control of TE Networks (ACTN)", RFC 8453,
	DOI 10.17487/RFC8453, August 2018,		DOI 10.17487/RFC8453, August 2018,
	<https://www.rfc-editor.org/info/rfc8453>.		<https://www.rfc-editor.org/info/rfc8453>.
			[RFC8969] Wu, Q., Ed., Boucadair, M., Ed., Lopez, D., Xie, C., and
			L. Geng, "A Framework for Automating Service and Network
			Management with YANG", RFC 8969, DOI 10.17487/RFC8969,
			January 2021, <https://www.rfc-editor.org/info/rfc8969>.
	Authors' Addresses		Authors' Addresses
	Luis M. Contreras		Luis M. Contreras
	Telefonica		Telefonica
	Ronda de la Comunicacion, s/n		Ronda de la Comunicacion, s/n
	Sur-3 building, 3rd floor		Sur-3 building, 3rd floor
	Madrid 28050		Madrid 28050
	Spain		Spain
	Email: luismiguel.contrerasmurillo@telefonica.com		Email: luismiguel.contrerasmurillo@telefonica.com
End of changes. 15 change blocks.
	25 lines changed or deleted		86 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/