< draft-contreras-nmrg-transport-slice-intent-00.txt		draft-contreras-nmrg-transport-slice-intent-01.txt >
	NMRG LM. Contreras		NMRG LM. Contreras
	Internet-Draft Telefonica		Internet-Draft Telefonica
	Intended status: Informational P. Demestichas		Intended status: Informational P. Demestichas
	Expires: September 10, 2020 WINGS		Expires: January 14, 2021 WINGS
	March 9, 2020		J. Tantsura
			Apstra, Inc.
			July 13, 2020
	Transport Slice Intent		Transport Slice Intent
	draft-contreras-nmrg-transport-slice-intent-00		draft-contreras-nmrg-transport-slice-intent-01
	Abstract		Abstract
	Slicing at the transport network is expected to be offered as part of		Slicing at the transport network is expected to be offered as part of
	end-to-end network slices, fostered by the introducion of new		end-to-end network slices, fostered by the introduction of new
	services such as 5G. This document explores the usage of intent		services such as 5G. This document explores the usage of intent
	machanisms for requesting transport slices.		technologies for requesting transport slices.
	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 September 10, 2020.		This Internet-Draft will expire on January 14, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2020 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 2, line 13 ¶		skipping to change at page 2, line 15 ¶
	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. Transport slice intent . . . . . . . . . . . . . . . . . . . 3		2. Transport slice intent . . . . . . . . . . . . . . . . . . . 3
	3. Foundation of transport slice intents . . . . . . . . . . . . 3		3. Foundation of transport slice intents . . . . . . . . . . . . 3
	4. Mechanisms for translating transport slice intents . . . . . 4		4. Mechanisms for translating transport slice intents . . . . . 4
	4.1. Translation approaches and interaction with the upper		4.1. Translation approaches and interaction with the upper
	systems . . . . . . . . . . . . . . . . . . . . . . . . . 4		systems . . . . . . . . . . . . . . . . . . . . . . . . . 4
	4.2. Intent-based system suite . . . . . . . . . . . . . . . . 4		4.2. Intent-based system suite . . . . . . . . . . . . . . . . 5
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 5		5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5		7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
	Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 5		Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 6
	Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 6		Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 6
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
	1. Introduction		1. Introduction
	Network slicing is emerging as the future model for service offering		Network slicing is emerging as the future model for service offering
	in telecom operator networks. Conceptually, network slicing provides		in telecom operator networks. Conceptually, network slicing provides
	a customer with an apparent dedicated network built on top of logical		a customer with an apparent dedicated network built on top of logical
	(i.e. virtual) and/or physical functions and resources supported by a		(i.e. virtual) and/or physical functions and resources supported by a
	shared infrastructure, the one from the telecom operator.		shared infrastructure, provided by one or more telecom operators.
	The concept of network slicing has been largely fostered by the		The concept of network slicing has been largely fostered by the
	advent of 5G services which are expected to be deployed on top of		advent of 5G services that are expected to be deployed on top of
	different kind of slices, each built to support specific		different kind of slices, each built to support specific
	characteristics (extreme low latency, high bandwidth, etc).		characteristics (extreme low latency, high bandwidth, etc).
	As part of an end-to-end network slice it is expected to have a		As part of an end-to-end network slice it is expected to have a
	number of transport network slices providing the necessary		number of transport network slices providing the necessary
	connectivity to the rest of components of the end-to-end slice, e.g.,		connectivity to the rest of components of the end-to-end slice, e.g.,
	mobile packet core slice.		mobile packet core slice.
	For a definition of transport slice refer to		For a definition of a transport slice refer to
	[I-D.nsdt-teas-transport-slice-definition]. The following paragraph		[I-D.nsdt-teas-transport-slice-definition]. The following paragraph
	is directly taken from it: "A transport slice is built based on a		is directly taken from it: "A transport slice is built based on a
	request from a higher operations system. The interface to higher		request from a higher operations system. The interface to higher
	operations systems should express the needed connectivity in a		operations systems should express the needed connectivity in a
	technology-agnostic way, and slice customers do not need to recognize		technology-agnostic way, and slice customers do not need to recognize
	concrete configurations based on the technologies (e.g being more		concrete configurations based on the technologies (e.g being more
	declarative than imperative). The request to instantiate a transport		declarative than imperative). The request to instantiate a transport
	slice is represented with some indicators such as SLO, and		slice is represented with some indicators such as SLO, and
	technologies are selected and managed accordingly."		technologies are selected and managed accordingly."
			Intent is a high-level, declarative goal that operates at the level
			of a network and services it provides, not individual devices. It is
			used to define outcomes and high-level operational goals.
	In consequence, it seems very convenient to apply the intent-based		In consequence, it seems very convenient to apply the intent-based
	mechanisms for the provision of transport network slices, providing		mechanisms for the provision of transport network slices, providing
	the adequate level of abstraction towards the transport network		the adequate level of abstraction towards the transport network
	control and management artifacts.		control and management planes.
	This document works on that direction by leveraging on current		This document leverages current industry trends in the definition of
	industry trends in the definition of end-to-end network slices. The		end-to-end network slices. The final objective is to describe
	final objective is to describe intents that can flexibly declare the		intents that can be used to flexibly declare the operational aspects
	operational aspects and goals of a transport network slice, meaning		and goals of a transport network slice, meaning that the customer
	that the customer could declare what kind of transport slice is		could declare what kind of transport slice is needed (the outcome)
	needed and not how to achieve the goals of the transport slice.		and not how to achieve the goals of the transport slice.
	2. Transport slice intent		2. Transport slice intent
	As stated in [I-D.irtf-nmrg-ibn-concepts-definitions], "Intent is a		As stated in [I-D.irtf-nmrg-ibn-concepts-definitions], "Intent is a
	higher-level declarative policy that operates at the level of a		higher-level declarative policy that operates at the level of a
	network and services it provides, not individual devices. It is used		network and services it provides, not individual devices. It is used
	to define outcomes and high-level operational goals, without the need		to define outcomes and high-level operational goals, without the need
	to enumerate specific events, conditions, and actions".		to enumerate specific events, conditions, and actions".
	When applied to transport networks, this implies that an intent for		When applied to transport networks, this implies that an intent for
	transport slices should provide the necessary abstraction with		transport slices should provide the necessary abstraction with
	respect to implementation details, including the final devices (or		respect to implementation details, including the final devices (or
	resources) involved, and be focused on the characteristics and		resources) involved, and be focused on the characteristics and
	performance expectations related to it.		performance expectations related to it.
	With that intent it can be expected that the intent-based system can		With that intent it can be expected that the intent based system can
	fulfill and assure the requested transport network slice, triggering		fulfill and assure the requested transport network slice, triggering
	initial configurations at the time of initial provisioning and		initial configurations at the time of initial provisioning and
	corrective actions during the transport slice lifetime.		corrective actions during the transport slice lifetime.
	3. Foundation of transport slice intents		3. Foundation of transport slice intents
	The industrial interest around 5G is accelerating network deployments		The industrial interest around 5G is accelerating network deployments
	and operational changes.		and operational changes.
	With this respect, the GSMA is developing a universal blueprint that		With this respect, the GSMA has been developing a universal blueprint
	can be used by any vertical customer to order the deployment of a		that can be used by any vertical customer to request the deployment
	network slice instance (NSI) based on a specific set of service		of a network slice instance (NSI) based on a specific set of service
	requirements. Such a blueprint is a network slice descriptor called		requirements. Such a blueprint is a network slice descriptor called
	Generic Slice Template (GST) [GSMA]. The GST contains multiple		Generic Slice Template (GST) [GSMA]. The GST contains multiple
	attributes that can be used to characterize a network slice. A		attributes that can be used to characterize a network slice. A
	particular template filled with values generates a specific Network		particular template filled with values generates a specific Network
	Slice Type(NEST).		Slice Type(NEST).
	Such templates refer to the end-to-end network slice, including the		Such templates refer to the end-to-end network slice, including the
	transport part. Despite some of the values could not have		transport part. Despite the fact that some of the values would not
	applicability for the transport network, others do. An analysis of		have applicability for the transport network, others do. An analysis
	relevant attributes is performed in [I-D.contreras-teas-slice-nbi].		of the relevant attributes is performed in
			[I-D.contreras-teas-slice-nbi].
	According to 3GPP propositions [TS28.541] an upper 3GPP Management		According to 3GPP propositions [TS28.541], an upper 3GPP Management
	System interacts with the transport network for establishing the		System interacts with the transport network for establishing the
	necessary slices at the transport level. Such interaction can be		necessary slices at the transport level. Such interaction can be
	expected to happen using the transport slice intents here described		expected to happen using the transport slice intent, described to an
	to an intent-based system (IBS) in the transport network part. Then,		intent-based system (IBS) in the transport network part. Then,
	according to the intent lifecycle in		according to the intent lifecycle in
	[I-D.irtf-nmrg-ibn-concepts-definitions], the IBS, after recognizing		[I-D.irtf-nmrg-ibn-concepts-definitions], the IBS, after recognizing
	the intent, will proceed to translate it in order to interact with a		the intent, will proceed to translate it in order to interact with a
	transport slice controller by using a NBI as proposed in		transport slice controller by using a NBI as proposed in
	[I-D.contreras-teas-slice-nbi].		[I-D.contreras-teas-slice-nbi].
	4. Mechanisms for translating transport slice intents		4. Mechanisms for translating transport slice intents
	This section describes approaches for implementing mechanisms able to		This section describes approaches for implementing mechanisms to
	translate transport slice intents.		translate transport slice intents.
	4.1. Translation approaches and interaction with the upper systems		4.1. Translation approaches and interaction with the upper systems
	A suite of mechanisms will be required and can be used for the		A suite of mechanisms will be required to allow instantiation of the
	translation of the user's intent into a transport slice. NLP		user's intent into a transport slice. In order to be able to deliver
	(Natural Language Processing) approaches are needed for enabling the		an end2end Intent driven slice - a well defined set of context aware
	expression of requirements in high level terms, and for conducting a		attributes that allow unambiguous instantiation of the intent should
	first analysis towards lower-level network requirements/resources.		be agreed upon. A combination of a structured set of
	The goal would be to identify and classify the answers for as many		attributes communicated between an IBN and an upper layer system with
	fields as possible from the Generic Slice Template (GST), based on		user input would allow an IBN to have intent modeled and reason about
	the free text / speech provided by the user. As it is highly		its completeness/validity. Translation approaches and interaction
	unlikely that the minimum set of fields to properly define a		with the upper systems might benefit from Natural Language Processing
	transport slice (geo-temporal characteristics, performance		(NLP) technics that are needed for enabling high level expression of
	characteristics, SLA properties) will be fulfilled in this first		requirements found missing. The goal would be to identify and
	step, a follow up two-step approach will have to be implemented.		classify the answers for as many fields as possible from the Generic
			Slice Template (GST), based on the free text / speech provided by the
			user. As it is highly unlikely that the minimum set of fields to
			properly define a transport slice (geo-temporal characteristics,
			performance characteristics, SLO and SLA properties) will be
			fulfilled in this first step, a follow up two-step approach might
			need to be implemented.
	o The minimum missing fields from the GST have to be identified and		o The minimum missing fields from the GST have to be identified and
	appropriate questions have to be generated (e.g. based on a pool		appropriate questions have to be generated (e.g. based on a pool
	of available questions corelated with each field, or based on AI		of available questions correlated with each field, or based on AI
	approaches)		approaches).
	o An iterative interrogation phase will be initiated towards the		o An iterative interrogation phase will be initiated towards the
	user using the previously generated questions, until the user		user using the previously generated questions, until the user
	provides all the missing information		provides all the missing information, so the intent can be modeled
			accordingly.
	Interaction with the user and higher-up systems can potentially be		Interaction with the user and higher-up systems can potentially be
	further improved by utilizing Machine learning techniques.		further improved by utilizing Machine Learning techniques.
	4.2. Intent-based system suite		4.2. Intent-based system suite
	A combination of deterministic or stochastic computation approaches		In order to consolidate on the set of devices, technologies and
	will be needed, in order to consolidate on the set of devices,		resources to be used, a combination of deterministic or stochastic
	technologies and resources to be used. Deterministic approaches will		computation approaches will be needed. Deterministic approaches will
	rely on mathematical models and respective algorithms. Stochastic		rely on mathematical models and respective algorithms. Stochastic
	approaches will rely on technologies like machine learning. Their		approaches will rely on technologies like machine learning. Their
	goal will be to learn from experience, so as to optimize future		goal will be to learn from experience, so as to optimize future
	decisions from the viewpoint of speed and reliability. The target of		decisions from the viewpoint of speed and reliability. The target of
	learning will be related to the service behavior and to the		learning will be related to the service behavior and to the
	anticipated network status in the area and time period of the service		anticipated network status in the area and time period of the service
	provision.		provision.
	5. Security Considerations		5. Security Considerations
	To be done.		To be done.
	6. IANA Considerations		6. IANA Considerations
	This draft does not include any IANA considerations		This draft does not include any IANA considerations
	7. References		7. References
	[GSMA] "Generic Network Slice Template, version 2.0", NG.116 ,		[GSMA] "Generic Network Slice Template, version 3.0", NG.116 ,
	October 2019.		May 2020.
	[I-D.contreras-teas-slice-nbi]		[I-D.contreras-teas-slice-nbi]
	Contreras, L., Homma, S., and J. Ordonez-Lucena,		Contreras, L., Homma, S., and J. Ordonez-Lucena,
	"Considerations for defining a Transport Slice NBI",		"Considerations for defining a Transport Slice NBI",
	draft-contreras-teas-slice-nbi-00 (work in progress),		draft-contreras-teas-slice-nbi-01 (work in progress),
	November 2019.		March 2020.
	[I-D.irtf-nmrg-ibn-concepts-definitions]		[I-D.irtf-nmrg-ibn-concepts-definitions]
	Clemm, A., Ciavaglia, L., Granville, L., and J. Tantsura,		Clemm, A., Ciavaglia, L., Granville, L., and J. Tantsura,
	"Intent-Based Networking - Concepts and Definitions",		"Intent-Based Networking - Concepts and Definitions",
	draft-irtf-nmrg-ibn-concepts-definitions-00 (work in		draft-irtf-nmrg-ibn-concepts-definitions-01 (work in
	progress), December 2019.		progress), March 2020.
	[I-D.nsdt-teas-transport-slice-definition]		[I-D.nsdt-teas-transport-slice-definition]
	Rokui, R., Homma, S., and K. Makhijani, "IETF Definition		Rokui, R., Homma, S., Makhijani, K., Contreras, L., and J.
	of Transport Slice", draft-nsdt-teas-transport-slice-		Tantsura, "IETF Definition of Transport Slice", draft-
	definition-00 (work in progress), November 2019.		nsdt-teas-transport-slice-definition-03 (work in
			progress), July 2020.
	[TS28.541]		[TS28.541]
	"TS 28.541 Management and orchestration; 5G Network		"TS 28.541 Management and orchestration; 5G Network
	Resource Model (NRM); Stage 2 and stage 3 (Release 16)		Resource Model (NRM); Stage 2 and stage 3 (Release 16)
	V16.2.0.", 3GPP TS 28.541 V16.2.0 , September 2019.		V16.2.0.", 3GPP TS 28.541 V16.2.0 , September 2019.
	Acknowledgments		Acknowledgments
	This work has been partly funded by the European Commission through		This work has been partly funded by the European Commission through
	the H2020 project 5G-EVE (Grant Agreement no. 815074).		the H2020 project 5G-EVE (Grant Agreement no. 815074).
	skipping to change at line 264 ¶		skipping to change at page 6, line 44 ¶
	Spain		Spain
	Email: luismiguel.contrerasmurillo@telefonica.com		Email: luismiguel.contrerasmurillo@telefonica.com
	URI: http://lmcontreras.com/		URI: http://lmcontreras.com/
	Panagiotis Demestichas		Panagiotis Demestichas
	WINGS ICT Solutions		WINGS ICT Solutions
	Greece		Greece
	Email: pdemest@wings-ict-solutions.eu		Email: pdemest@wings-ict-solutions.eu
			Jeff Tantsura
			Apstra, Inc.
			Email: jefftant.ietf@gmail.com
End of changes. 29 change blocks.
	57 lines changed or deleted		71 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/