< draft-contreras-teas-slice-nbi-03.txt		draft-contreras-teas-slice-nbi-04.txt >
	TEAS Working Group LM. Contreras		TEAS Working Group LM. Contreras
	Internet-Draft Telefonica		Internet-Draft Telefonica
	Intended status: Informational S. Homma		Intended status: Informational S. Homma
	Expires: May 3, 2021 NTT		Expires: August 26, 2021 NTT
	J. Ordonez-Lucena		J. Ordonez-Lucena
	Telefonica		Telefonica
	October 30, 2020		February 22, 2021
	IETF Network Slice use cases and attributes for Northbound Interface of		IETF Network Slice Use Cases and Attributes for Northbound Interface of
	controller		IETF Network Slice Controllers
	draft-contreras-teas-slice-nbi-03		draft-contreras-teas-slice-nbi-04
	Abstract		Abstract
	The transport network is an essential component in the end-to-end		This document analyses the needs of potential customers of network
	delivery of services and, consequently, with the advent of network		slices realized with IETF techniques in several use cases, identifies
	slicing it is necessary to understand what could be the way in which		the functionalities for the North Bound Interface (NBI) of an IETF
	the transport network is consumed as a slice. This document analyses		Network Slice Controller to satisfy such requests.
	the needs of potential IETF network slice customers (i.e., use cases)
	in order to identify the functionality required on the North Bound
	Interface (NBI) of a IETF network slice controller for satisfying
	such IETF network slice requests.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	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 3, 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. Conventions used in this document . . . . . . . . . . . . . . 3		2. Conventions used in this document and terminology . . . . . . 3
	3. Northbound interface for IETF network slices . . . . . . . . 3		3. Northbound Interface for IETF Network Slices . . . . . . . . 3
	4. IETF network slice use cases . . . . . . . . . . . . . . . . 4		4. IETF Network Slice Use Cases . . . . . . . . . . . . . . . . 4
	4.1. 5G Services . . . . . . . . . . . . . . . . . . . . . . . 4		4.1. 5G Services . . . . . . . . . . . . . . . . . . . . . . . 4
	4.1.1. Generic network Slice Template . . . . . . . . . . . 6		4.1.1. Generic network Slice Template . . . . . . . . . . . 5
	4.1.2. Categorization of GST attributes . . . . . . . . . . 6		4.1.2. Categorization of GST attributes . . . . . . . . . . 6
	4.1.2.1. Attributes with direct impact on the IETF network		4.1.2.1. Attributes with direct impact on the IETF network
	slice definition . . . . . . . . . . . . . . . . 7		slice definition . . . . . . . . . . . . . . . . 7
	4.1.2.2. Attributes with indirect impact on the IETF		4.1.2.2. Attributes with indirect impact on the IETF
	network slice definition . . . . . . . . . . . . 8		network slice definition . . . . . . . . . . . . 7
	4.1.2.3. Attributes with no impact on the IETF network		4.1.2.3. Attributes with no impact on the IETF network
	slice definition . . . . . . . . . . . . . . . . 8		slice definition . . . . . . . . . . . . . . . . 8
	4.1.3. Provisioning procedures . . . . . . . . . . . . . . . 9		4.1.3. Provisioning procedures . . . . . . . . . . . . . . . 9
	4.2. NFV-based services . . . . . . . . . . . . . . . . . . . 9		4.2. NFV-based services . . . . . . . . . . . . . . . . . . . 9
	4.2.1. Connectivity attributes . . . . . . . . . . . . . . . 10		4.2.1. Connectivity attributes . . . . . . . . . . . . . . . 10
	4.2.2. Provisioning procedures . . . . . . . . . . . . . . . 10		4.2.2. Provisioning procedures . . . . . . . . . . . . . . . 10
	4.3. RAN sharing . . . . . . . . . . . . . . . . . . . . . . . 11		4.3. Network sharing . . . . . . . . . . . . . . . . . . . . . 11
	4.3.1. Connectivity attributes . . . . . . . . . . . . . . . 12		4.3.1. Connectivity attributes . . . . . . . . . . . . . . . 12
	4.3.2. Provisioning procedures . . . . . . . . . . . . . . . 12		4.3.2. Provisioning procedures . . . . . . . . . . . . . . . 12
	4.4. Additional use cases . . . . . . . . . . . . . . . . . . 12		4.4. Additional use cases . . . . . . . . . . . . . . . . . . 12
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 13		5. Security Considerations . . . . . . . . . . . . . . . . . . . 12
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . 13		7. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
	7.1. Normative References . . . . . . . . . . . . . . . . . . 13		7.1. Normative References . . . . . . . . . . . . . . . . . . 13
	7.2. Informative References . . . . . . . . . . . . . . . . . 13		7.2. Informative References . . . . . . . . . . . . . . . . . 13
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
	1. Introduction		1. Introduction
	Editor's Note: the terminology in this draft will be aligned in
	forthcoming versions with the final terminology selected for
	describing the notion of IETF network slice when applied to IETF
	technologies, which is currently under discussion. By now same
	terminology as used in [I-D.nsdt-teas-ietf-network-slice-definition]
	and [I-D.nsdt-teas-ns-framework] is primarily used here.
	Editor's Note: the term "transport network" in the context of this
	draft refers in broad sense to WAN, MBH, IP backbone and other
	network segments implemented by IETF technologies.
	A number of new technologies, such as 5G, NFV and SDN are not only		A number of new technologies, such as 5G, NFV and SDN are not only
	evolving the network from a pure technological perspective but also		evolving the network from a pure technological perspective but also
	are changing the concept in which new services are offered to the		are changing the concept in which new services are offered to the
	customers [I-D.homma-slice-provision-models] by introducing the		customers [I-D.homma-slice-provision-models] by introducing the
	concept of network slicing.		concept of network slicing.
	The transport network is an essential component in the end-to-end		The transport network is an essential component in the end-to-end
	delivery of services and, consequently, it is necessary to understand		delivery of services and, consequently, it is necessary to understand
	what could be the way in which the transport network is consumed as a		what could be the way in which the transport network is consumed as a
	slice. For a definition of IETF network slice refer to		slice. For a definition of IETF network slice refer to
	[I-D.nsdt-teas-ietf-network-slice-definition].		[I-D.ietf-teas-ietf-network-slice-definition].
	In this document it is assumed that there exists a (logically)		In this document it is assumed that there exists a (logically)
	centralized component in the transport network, namely IETF Network		centralized component in the transport network, namely IETF Network
	Slice Controller (NSC) with the responsibilities on the control and		Slice Controller (NSC) with the responsibilities on the control and
	management of the IETF network slices invoked for a given service, as		management of the IETF network slices invoked for a given service, as
	requested by IETF network slice customers.		requested by IETF network slice customers.
	This document analyses different use cases deriving the needs of		This document analyses different use cases deriving the needs of
	potential IETF network slice customers in order to identify the		potential IETF network slice customers in order to identify the
	functionality required on the North Bound Interface (NBI) of the NSC		functionality required on the North Bound Interface (NBI) of the NSC
	to be exposed towards such IETF network slice customers. Solutions		to be exposed towards such IETF network slice customers. Solutions
	to construct the requested IETF network slices are out of scope of		to construct the requested IETF network slices are out of scope of
	this document.		this document.
	This document addresses some of the discussions of the TEAS Slice		This document addresses some of the discussions of the TEAS Slice
	Design Team. However, it is not at this stage an official outcome of		Design Team. However, it is not at this stage an official outcome of
	the Design Team.		the Design Team.
	2. Conventions used in this document		2. Conventions used in this document and terminology
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in RFC2119 [RFC2119].		document are to be interpreted as described in RFC2119 [RFC2119].
	3. Northbound interface for IETF network slices		The terminology in this draft will be aligned in forthcoming versions
			with the final terminology selected for describing the notion of IETF
			network slice when applied to IETF technologies, which is currently
			under discussion. By now same terminology as used in
			[I-D.ietf-teas-ietf-network-slice-definition] and
			[I-D.nsdt-teas-ns-framework] is primarily used here.
			The term "transport network" in the context of this draft refers in
			broad sense to WAN, MBH, IP backbone and other network segments
			implemented by IETF technologies.
			3. Northbound Interface for IETF Network Slices
	In a general manner, the transport network supports different kinds		In a general manner, the transport network supports different kinds
	of services. These services consume capabilities provided by the		of services. These services consume capabilities provided by the
	transport network for deploying end-to-end services, interconnecting		transport network for deploying end-to-end services, interconnecting
	network functions or applications spread across the network and		network functions or applications spread across the network and
	providing connectivity toward the final users of these services.		providing connectivity toward the final users of these services.
	Under the slicing approach, a IETF network slice customer requests to		Under the slicing approach, a IETF network slice customer requests to
	a IETF network slice controller a slice with certain characteristics		a IETF network slice controller a slice with certain characteristics
	and parametrization. Such request it is assumed here to be done		and parametrization. Such request it is assumed here to be done
	skipping to change at page 4, line 38 ¶		skipping to change at page 4, line 32 ¶
	| |		| |
	+--------------------+		+--------------------+
	Figure 1: IETF network slice NBI concept		Figure 1: IETF network slice NBI concept
	The functionality supported by the NBI depends on the requirements		The functionality supported by the NBI depends on the requirements
	that the slice customer has to satisfy. It is then important to		that the slice customer has to satisfy. It is then important to
	understand the needs of the slice customers as well as the way of		understand the needs of the slice customers as well as the way of
	expressing them.		expressing them.
	4. IETF network slice use cases		4. IETF Network Slice Use Cases
	Different use cases for slice customers can be identified, as		Different use cases for slice customers can be identified, as
	described in the following sections.		described in the following sections.
	4.1. 5G Services		4.1. 5G Services
	5G services natively rely on the concept of network slicing. 5G is		5G services natively rely on the concept of network slicing. 5G is
	expected to allow vertical customers to request slices in such a		expected to allow vertical customers to request slices in such a
	manner that the allocated resources and capabilities in the network		manner that the allocated resources and capabilities in the network
	appear as dedicated for them.		appear as dedicated for them.
	skipping to change at page 7, line 10 ¶		skipping to change at page 6, line 48 ¶
	or the mobile core part.		or the mobile core part.
	In the analysis performed in this document, the attributes have been		In the analysis performed in this document, the attributes have been
	categorized as:		categorized as:
	o Directly impactive attributes, which are those that have direct		o Directly impactive attributes, which are those that have direct
	impact on the definition of the IETF network slice, i.e.,		impact on the definition of the IETF network slice, i.e.,
	attributes that can be directly translated into requirements		attributes that can be directly translated into requirements
	required to be satisfied by a IETF network slice.		required to be satisfied by a IETF network slice.
	o Indirectly impactive attributes, which are thise that impact in an		o Indirectly impactive attributes, which are those that impact in an
	indirect manner on the definition of the IETF network slice, i.e.,		indirect manner on the definition of the IETF network slice, i.e.,
	attributes that indirectly impose some requirements to a IETF		attributes that indirectly impose some requirements to a IETF
	network slice.		network slice.
	o Non-impactive attributes, that are those which do not have impact		o Non-impactive attributes, that are those which do not have impact
	on the IETF network slice at all.		on the IETF network slice at all.
	The following sections describe the attributes falling into the three		The following sections describe the attributes falling into the three
	categories.		categories.
	skipping to change at page 11, line 20 ¶		skipping to change at page 11, line 14 ¶
	the connectivity service, as well as about information of consumed		the connectivity service, as well as about information of consumed
	and available capacity on the underlying network resources.		and available capacity on the underlying network resources.
	o Fault Management: this interface serves for the provision of		o Fault Management: this interface serves for the provision of
	alarms related to the MSCSs.		alarms related to the MSCSs.
	o Performance Management: this interface assists on the retrieval of		o Performance Management: this interface assists on the retrieval of
	performance information (measurement results collection and		performance information (measurement results collection and
	notifications) related to MSCSs.		notifications) related to MSCSs.
	4.3. RAN sharing		4.3. Network sharing
	Network sharing is one of the means network operators exploit for		Network sharing is one of the means network operators exploit for
	increasing efficiencies. There are different scenarios of network		increasing efficiencies. There are different scenarios of network
	sharing, being especially popular in the deployment of mobile		sharing, being especially popular in the deployment of mobile
	networks, typically referred to as Radio Access Network (RAN)		networks, typically referred to as Radio Access Network (RAN)
	sharing. From an operational perspective, in RAN sharing we have two		sharing. From an operational perspective, in RAN sharing we have two
	roles: master operator, being the actor (e.g. infrastructure		roles: master operator, being the actor (e.g. infrastructure
	provider, network operator) to which the deployment and daily		provider, network operator) to which the deployment and daily
	operation of shared RAN elements are entrusted to; and the		operation of shared RAN elements are entrusted to; and the
	participant operators, who are the mobile operators who share the RAN		participant operators, who are the mobile operators who share the RAN
	skipping to change at page 12, line 38 ¶		skipping to change at page 12, line 32 ¶
	o Recovery time (on the event of failures).		o Recovery time (on the event of failures).
	o Secure connection (e.g., encryption support).		o Secure connection (e.g., encryption support).
	4.3.2. Provisioning procedures		4.3.2. Provisioning procedures
	The expected provisioning procedures are:		The expected provisioning procedures are:
	o Connection provisioning between site and interconnection point.		o Connection provisioning between site and interconnection point.
	Those connections could evolve in time in terms of capacity		Those connections could evolve in time in terms of capacity
	depending on the capacity grow of each particular site.		depending on the capacity growth of each particular site.
	o Collection of management data, including performance measurements,		o Collection of management data, including performance measurements,
	fault alarms and trace data.		fault alarms and trace data.
	4.4. Additional use cases		4.4. Additional use cases
	This is a placeholder for describing additional use cases (e.g., data		This is a placeholder for describing additional use cases (e.g., data
	center interconnection, etc). To be completed.		center interconnection, etc). To be completed.
	5. Security Considerations		5. Security Considerations
	skipping to change at page 13, line 34 ¶		skipping to change at page 13, line 26 ¶
	[GSMA] "Generic Network Slice Template, version 3.0", NG.116 ,		[GSMA] "Generic Network Slice Template, version 3.0", NG.116 ,
	May 2020.		May 2020.
	[I-D.homma-slice-provision-models]		[I-D.homma-slice-provision-models]
	Homma, S., Nishihara, H., Miyasaka, T., Galis, A., OV, V.,		Homma, S., Nishihara, H., Miyasaka, T., Galis, A., OV, V.,
	Lopez, D., Contreras, L., Ordonez-Lucena, J., Martinez-		Lopez, D., Contreras, L., Ordonez-Lucena, J., Martinez-
	Julia, P., Qiang, L., Rokui, R., Ciavaglia, L., and X.		Julia, P., Qiang, L., Rokui, R., Ciavaglia, L., and X.
	Foy, "Network Slice Provision Models", draft-homma-slice-		Foy, "Network Slice Provision Models", draft-homma-slice-
	provision-models-02 (work in progress), November 2019.		provision-models-02 (work in progress), November 2019.
	[I-D.nsdt-teas-ietf-network-slice-definition]		[I-D.ietf-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-ietf-
	teas-ietf-network-slice-definition-00 (work in progress),		teas-ietf-network-slice-definition-00 (work in progress),
	October 2020.		January 2021.
	[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.
	[IFA032] "IFA032 Interface and Information Model Specification for		[IFA032] "IFA032 Interface and Information Model Specification for
	Multi-Site Connectivity Services V3.2.1.", ETSI GS NFV-IFA		Multi-Site Connectivity Services V3.2.1.", ETSI GS NFV-IFA
	032 V3.2.1 , April 2019.		032 V3.2.1 , April 2019.
End of changes. 22 change blocks.
	44 lines changed or deleted		40 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/