draft-ietf-teas-ietf-network-slice-definition-00.txt		draft-ietf-teas-ietf-network-slice-definition-01.txt
	teas R. Rokui		teas R. Rokui
	Internet-Draft Nokia		Internet-Draft Nokia
	Intended status: Informational S. Homma		Intended status: Informational S. Homma
	Expires: July 25, 2021 NTT		Expires: August 26, 2021 NTT
	K. Makhijani		K. Makhijani
	Futurewei		Futurewei
	LM. Contreras		LM. Contreras
	Telefonica		Telefonica
	J. Tantsura		J. Tantsura
	Apstra, Inc.		Juniper Networks
	January 21, 2021		February 22, 2021
	Definition of IETF Network Slices		Definition of IETF Network Slices
	draft-ietf-teas-ietf-network-slice-definition-00		draft-ietf-teas-ietf-network-slice-definition-01
	Abstract		Abstract
	This document provides a definition of the term "IETF Network Slice"		This document provides a definition of the term "IETF Network Slice"
	for use within the IETF and specifically as a reference for other		for use within the IETF and specifically as a reference for other
	IETF documents that describe or use aspects of network slices.		IETF documents that describe or use aspects of network slices.
	The document also describes the characteristics of an IETF network		The document also describes the characteristics of an IETF network
	slice, related terms and their meanings, and explains how IETF		slice, related terms and their meanings, and explains how IETF
	network slices can be used in combination with end-to-end network		network slices can be used in combination with end-to-end network
	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 July 25, 2021.		This Internet-Draft will expire on August 26, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2021 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		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 3, line 4 ¶		skipping to change at page 3, line 4 ¶
	12. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 15		12. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 15
	13. Informative References . . . . . . . . . . . . . . . . . . . 15		13. Informative References . . . . . . . . . . . . . . . . . . . 15
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
	1. Introduction		1. Introduction
	A number of use cases benefit from network connections that along		A number of use cases benefit from network connections that along
	with the connectivity provide assurance of meeting a specific set of		with the connectivity provide assurance of meeting a specific set of
	objectives wrt network resources use. In this document, as detailed		objectives wrt network resources use. In this document, as detailed
	in the subsequent sections, we refer to this connectivity and		in the subsequent sections, we refer to this connectivity and
	resource commitment as an IETF network slice. Services that might		resource commitment as an IETF Network Slice. Services that might
	benefit from the network slices include but not limited to:		benefit from the network slices include but not limited to:
	o 5G services (e.g. eMBB, URLLC, mMTC)(See [TS.23.501-3GPP])		o 5G services (e.g. eMBB, URLLC, mMTC)(See [TS.23.501-3GPP])
	o Network wholesale services		o Network wholesale services
	o Network infrastructure sharing among operators		o Network infrastructure sharing among operators
	o NFV connectivity and Data Center Interconnect		o NFV connectivity and Data Center Interconnect
	skipping to change at page 3, line 28 ¶		skipping to change at page 3, line 28 ¶
	connectivity coupled with a set of specific commitments of network		connectivity coupled with a set of specific commitments of network
	resources between a number of endpoints over a shared network		resources between a number of endpoints over a shared network
	infrastructure. Since the term network slice is rather generic, the		infrastructure. Since the term network slice is rather generic, the
	qualifying term 'IETF' is used in this document to limit the scope of		qualifying term 'IETF' is used in this document to limit the scope of
	network slice to network technologies described and standardized by		network slice to network technologies described and standardized by
	the IETF.		the IETF.
	IETF network slices are created and managed within the scope of one		IETF network slices are created and managed within the scope of one
	or more network technologies (e.g., IP, MPLS, optical). They are		or more network technologies (e.g., IP, MPLS, optical). They are
	intended to enable a diverse set of applications that have different		intended to enable a diverse set of applications that have different
	requirements to coexist on the same network infrastructure. A		requirements to coexist on the shared network infrastructure. A
	request for an IETF network slice is technology-agnostic so as to		request for an IETF network slice is technology-agnostic so as to
	allow a consumer to describe their network connectivity objectives in		allow a consumer to describe their network connectivity objectives in
	a common format, independent of the underlying technologies used.		a common format, independent of the underlying technologies used.
	2. Terms and Abbreviations		2. Terms and Abbreviations
	The terms and abbreviations used in this document are listed below.		The terms and abbreviations used in this document are listed below.
	o NS: Network Slice		o NS: Network Slice
	skipping to change at page 7, line 45 ¶		skipping to change at page 7, line 45 ¶
	Since it carries traffic for multiple flows between the two		Since it carries traffic for multiple flows between the two
	endpoints, the objectives should also say if they are for the entire		endpoints, the objectives should also say if they are for the entire
	connection, group of flows or on per flow basis. Maximal occupancy		connection, group of flows or on per flow basis. Maximal occupancy
	should specify the scale of the flows (i.e. maximum number of flows		should specify the scale of the flows (i.e. maximum number of flows
	to be admitted) and optionally a maximum number of countable resource		to be admitted) and optionally a maximum number of countable resource
	units, e.g IP or MAC addresses a slice might consume.		units, e.g IP or MAC addresses a slice might consume.
	4.2. IETF Network Slice Endpoints		4.2. IETF Network Slice Endpoints
	As noted in Section 3, an IETF network slice describes connectivity		As noted in Section 3, an IETF network slice describes connectivity
	between endpoints across the underlying network. This connectivity		between multiple endpoints across the underlying network. These
	may be be point-to-point, point-to-multipoint (P2MP), multipoint-to-		connectivity types are: point-to-point, point-to-multipoint,
	point, or multipoint-to-multipoint.		multipoint-to-point multipoint-to-point, or multipoint-to-multipoint.
			Figure 1 shows an IETF network slice along with its NSEs.
	The characteristics of IETF network slice endpoints (NSEs) are as		The characteristics of IETF network slice endpoints (NSEs) are as
	follows.		follows:
	o They are conceptual points of connection of a consumer network,		o The IETF network slice endpoints (NSEs) are conceptual points of
	network function, device, or application to the IETF network		connection to IETF network slice. As such, they serve as the IETF
	slice. This might include routers, switches, firewalls, WAN,		network slice ingress/egress points.
	4G/5G RAN nodes, 4G/5G Core nodes, application acceleration, Deep
	Packet Inspection (DPI), server load balancers, NAT44 [RFC3022],
	NAT64 [RFC6146], HTTP header enrichment functions, and TCP
	optimizers.
	o They are identified in a request provided by the consumer of an		o Each endpoint could map to a device, application or a network
	IETF network slice when the IETF network slice is requested.		function. A non-exhaustive list of devices, applications or
			network functions might include but not limited to: routers,
			switches, firewalls, WAN, 4G/5G RAN nodes, 4G/5G Core nodes,
			application acceleration, Deep Packet Inspection (DPI), server
			load balancers, NAT44 [RFC3022], NAT64 [RFC6146], HTTP header
			enrichment functions, and TCP optimizers.
	o An NSE is identified a unique identifier and/or a unique name and		o An NSE should be identified by a unique ID in the context of an
	other data. A non-exhaustive list of other data includes IPv4 or		IETF network slice consumer.
	IPv6 address, VLAN tag, port number, connectivity type (P2P, P2MP,
	MP2MP).
	Note that the NSE is different from access points (AP) defined in		o In addition to an identifier, each NSE should contain a subset of
	[RFC8453] as an AP is a logical identifier to identify the shared		attributes such as IPv4/IPv6 addresses, encapsulation type (i.e.,
	link between the consumer and the operator where as NSE is an		VLAN tag, MPLS Label etc.), interface/port numbers, node ID etc.
	identifier of an endpoint. Also NSE is different from TE Link
	Termination Point (LTP) defined in [I-D.ietf-teas-yang-te-topo] as it
	is a conceptual point of connection of a TE node to one of the TE
	links on a TE node.
	The NSE is similar to the Termination Point (TP) defined in [RFC8345]		o A combination of NSE unique ID and NSE attributes defines an NSE
	and can contain more attributes. NSE could be modeled by augmenting		in the context of the IETF network slice controller.
	the TP model.
	There is another type of the endpoints called "IETF Network Slice		o During the realization of the IETF network slice, in addition to
	Realization Endpoints (NSREs)". These endpoints are allocated and		SLOs, all or subset of IETF NSE attributes will be utilized by
	assigned by the network controller during the realization of an IETF		IETF network slice controller (NSC) to find the optimal
	network slice and are technology-specific, i.e. they depend on the		realization in the IETF network.
	network technology used during the IETF network slice realization.
	The identification of NSREs forms part of the realization of the IETF
	network slice and is implementation and deployment specific.
	Figure 1 shows an example of an IETF network slice and its		o Similarly to IETF network slices, the IETF network slice endpoints
	realization between multiple NSEs and NSREs.		are logical entities that are mapped to services/tunnels/paths
			endpoints in IETF network slice during its initialization and
			realization.
	(-------------------)		Note that there are various IETF TE terms such as access points (AP)
	( IETF scoped Network )		defined in [RFC8453], Termination Point (TP) defined in [RFC8345],
	DAN1 ( ) DAN2		and Link Termination Point (LTP) defined in [RFC8795] which are
	-------- NSRE1 -------- -------- NSRE2 --------		tightly coupled with TE network type and various realization
	| o |-------o| A | | B |o--------| o |		techniques. At the time of realization of the IETF network slice,
	| NSE1| -------- -------- | NSE2 |		the NSE could be mapped to one or more of these based on the network
	-------- | ( ) | --------		slice realization technique in use.
	| | ( ) | |
	| | (-------------------) | |
	| | | |
	| | <=============================> | |
	| IETF Network Slice realization |
	| between NSRE1 and NSRE2 |
	| |
	| <===================================================> |
	IETF Network Slice between NSE1 and NSE2 with SLO1
	Legend:		|----------------------------------|
	DAN: Device, application and/or network function		NSE1 | | NSE2
			O.....| |.....O
			. | | .
			. | | .
			. | | .
			| |
			NSEm | | NSEn
			O.....| |.....O
			| |
			|----------------------------------|
	Figure 1: An IETF Network Slice between NSEs and its realization		<------------ IETF Network Slice -------------->
	between NSREs		between endpoints NSE1 to NSEn
			Legend:
			NSE: IETF Network Slice Endpoint
			O: Represents IETF Network Slice Endpoints
			Figure 1: An IETF Network Slice Endpoints (NSE)
	4.2.1. IETF Network Slice Connectivity Types		4.2.1. IETF Network Slice Connectivity Types
	The IETF Network Slice connection types can be point to point (P2P),		The IETF Network Slice connection types can be point to point (P2P),
	point to multipoint (P2MP), multi-point to point (MP2P), or multi-		point to multipoint (P2MP), multi-point to point (MP2P), or multi-
	point to multi-point (MP2MP). They will requested by the higher		point to multi-point (MP2MP). They will requested by the higher
	level operation system.		level operation system.
	4.3. IETF Network Slice Composition		4.3. IETF Network Slice Composition
	Operationally, an IETF network slice maybe decomposed in two or more		Operationally, an IETF network slice may be decomposed in two or more
	IETF network slices as specified below. Decomposed network slices		IETF network slices as specified below. Decomposed network slices
	are then independently realized and managed.		are then independently realized and managed.
	o Hierarchical (i.e., recursive) composition: An IETF network slice		o Hierarchical (i.e., recursive) composition: An IETF network slice
	can be further sliced into other network slices. Recursive		can be further sliced into other network slices. Recursive
	composition allows an IETF network slice at one layer to be used		composition allows an IETF network slice at one layer to be used
	by the other layers. This type of multi-layer vertical IETF		by the other layers. This type of multi-layer vertical IETF
	network slice associates resources at different layers.		network slice associates resources at different layers.
	o Sequential composition: Different IETF network slices can be		o Sequential composition: Different IETF network slices can be
	skipping to change at page 10, line 13 ¶		skipping to change at page 10, line 13 ¶
	support different dataplanes that need to be stitched together.		support different dataplanes that need to be stitched together.
	5. IETF Network Slice Structure		5. IETF Network Slice Structure
	Editor's note: This content of this section merged with Relationship		Editor's note: This content of this section merged with Relationship
	with E2E slice discussion.		with E2E slice discussion.
	An IETF network slice is a set of connections among various endpoints		An IETF network slice is a set of connections among various endpoints
	to form a logical network that meets the SLOs agreed upon.		to form a logical network that meets the SLOs agreed upon.
	____________________________		|------------------------------------------------|
	[EP11]------/ /--[EP21]		NSE1 O....| |.....O NSE2
	/ /		. | | .
	[EP12]----/ IETF Network Slice /----[EP22]		. | IETF Network Slice | .
	: / (SLOs e.g. /		. | (SLOs e.g. B/W > x bps, Delay < y ms) | .
	: / B/W > x bps, Delay < y ms)/		NSEm O....| |.....O NSEn
	[EP1m]-/___________________________/-------[EP2n]		|------------------------------------------------|
	== == == == == == == == == == == == == == == == == ==		== == == == == == == == == == == == == == == == == == == == == == == == ==
	.--. .--.		.--. .--.
	[EP11] ( )- . ( )- . [EP21]		[EP1] ( )- . ( )- . [EP2]
	.' ' SLO .' '		. .' IETF ' SLO .' IETF ' .
	[EP12] ( Network-1 ) ... ( Network-p ) [EP22]		. ( Network-1 ) ... ( Network-p ) .
	: `-----------' `-----------' :		`-----------' `-----------'
	[EP1m] [EP2n]		[EPm] [EPn]
	Legend		Legendy
	SLOs in terms of attributes, e.g. BW, delay.		NSE: IETF Network Slice Endpoints
	EP: Endpoint		EP: Serivce/tunnels/path Endpoints used to realize the
	B/W: Bandwidth		IETF Network Slice
	Figure 2: IETF Network slice		Figure 2: IETF Network slice
	Figure 2 illustrates a case where an IETF network slice provides		Figure 2 illustrates a case where an IETF network slice provides
	connectivity between a set of endpoints pairs with specific		connectivity between a set of IEFT network slice endpoints (NSE)
	characteristics for each SLO (e.g. guaranteed minimum bandwidth of x		pairs with specific SLOs (e.g. guaranteed minimum bandwidth of x bps
	bps and guaranteed delay of no more than y ms). The endpoints may be		and guaranteed delay of no more than y ms). The IETF network slice
	distributed in the underlay networks, and an IETF network slice can		endpoints are mapped to the underlay IETF networks endpoints (EP).
	be deployed across multiple network domains. Also, the endpoints on		Also, the IETF network slice endpoints on the same IETF network slice
	the same IETF network slice may belong to the same or different		may belong to the same or different address spaces.
	address spaces.
	IETF Network slice structure fits into a broader concept of end-to-		IETF Network slice structure fits into a broader concept of end-to-
	end network slices. A network operator may be responsible for		end network slices. A network operator may be responsible for
	delivering services over a number of technologies (such as radio		delivering services over a number of technologies (such as radio
	networks) and for providing specific and fine-grained services (such		networks) and for providing specific and fine-grained services (such
	as CCTV feed or High definition realtime traffic data). That		as CCTV feed or High definition realtime traffic data). That
	operator may need to combine slices of various networks to produce an		operator may need to combine slices of various networks to produce an
	end-to-end network service. Each of these networks may include		end-to-end network service. Each of these networks may include
	multiple physical or virtual nodes and may also provide network		multiple physical or virtual nodes and may also provide network
	functions beyond simply carrying of technology-specific protocol data		functions beyond simply carrying of technology-specific protocol data
	skipping to change at page 12, line 9 ¶		skipping to change at page 12, line 9 ¶
	that offers network resources to NSC to realize a particular		that offers network resources to NSC to realize a particular
	network slice. These may be existing network controllers		network slice. These may be existing network controllers
	associated with one or more specific technologies that may be		associated with one or more specific technologies that may be
	adapted to the function of realizing IETF network slices in a		adapted to the function of realizing IETF network slices in a
	network.		network.
	7. IETF Network Slice Controller Interfaces		7. IETF Network Slice Controller Interfaces
	The interworking and interoperability among the different		The interworking and interoperability among the different
	stakeholders to provide common means of provisioning, operating and		stakeholders to provide common means of provisioning, operating and
	monitoring the IETF Network slices is enabled by the following		monitoring the IETF network slices is enabled by the following
	communication interfaces (see Figure 3).		communication interfaces (see Figure 3).
	NSC Northbound Interface (NBI): The NSC Northbound Interface is an		NSC Northbound Interface (NBI): The NSC Northbound Interface is an
	interface between a consumer's higher level operation system		interface between a consumer's higher level operation system
	(e.g., a network slice orchestrator) and the NSC. It is a		(e.g., a network slice orchestrator) and the NSC. It is a
	technology agnostic interface. The consumer can use this		technology agnostic interface. The consumer can use this
	interface to communicate the requested characteristics and other		interface to communicate the requested characteristics and other
	requirements (i.e., the SLOs) for the IETF network slice, and the		requirements (i.e., the SLOs) for the IETF network slice, and the
	NSC can use the interface to report the operational state of an		NSC can use the interface to report the operational state of an
	IETF network slice to the consumer.		IETF network slice to the consumer.
	skipping to change at page 17, line 38 ¶		skipping to change at page 17, line 38 ¶
	Email: kiranm@futurewei.com		Email: kiranm@futurewei.com
	Luis M. Contreras		Luis M. Contreras
	Telefonica		Telefonica
	Spain		Spain
	Email: luismiguel.contrerasmurillo@telefonica.com		Email: luismiguel.contrerasmurillo@telefonica.com
	Jeff Tantsura		Jeff Tantsura
	Apstra, Inc.		Juniper Networks
	Email: jefftant.ietf@gmail.com		Email: jefftant.ietf@gmail.com
End of changes. 26 change blocks.
	90 lines changed or deleted		90 lines changed or added
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/