< draft-geng-teas-network-slice-mapping-00.txt		draft-geng-teas-network-slice-mapping-01.txt >
	Network Working Group X. Geng		Network Working Group X. Geng
	Internet-Draft J. Dong		Internet-Draft J. Dong
	Intended status: Informational Huawei Technologies		Intended status: Informational Huawei Technologies
	Expires: August 17, 2020 T. Niwa		Expires: October 25, 2020 R. Pang
			China Unicom
			L. Han
			China Mobile
			T. Niwa
	KDDI		KDDI
	J. Jin		J. Jin
	LG U+		LG U+
	February 14, 2020		C. Liu
			China Unicom
			N. Nageshar
			Individual
			April 23, 2020
	5G End-to-end Network Slice Mapping from the view of Transport Network		5G End-to-end Network Slice Mapping from the view of Transport Network
	draft-geng-teas-network-slice-mapping-00		draft-geng-teas-network-slice-mapping-01
	Abstract		Abstract
	Network Slicing is one of the core featrures in 5G. End-to-end		Network Slicing is one of the core featrures in 5G. End-to-end
	network slicing consists of 3 major types of network segments: Access		network slice consists of 3 major types of network segments: Access
	Network (AN), Mobile Core Network (CN) and Transport Network (TN).		Network (AN), Mobile Core Network (CN) and Transport Network (TN).
	This draft describes the procedure of mapping relationship between 5G		This draft describes the procedure of mapping relationship between 5G
	end-to-end network slice into and transport network slice defined in		end-to-end network slice and transport network slice defined in IETF.
	IETF. This draft also intends to expose some gaps in the existing		This draft also intends to expose some gaps in the existing network
	network management plane and data plane to support inter-domain		management plane and data plane to support inter-domain network slice
	network slice mapping. Further work may require cooperation between		mapping. Further work may require cooperation between IETF and 3GPP
	IETF and 3GPP (or other standard organizations). The definition of		(or other standard organizations). The definition of data model,
	data model, signaling protocol extension and new encapsulation is out		signaling protocol extension and new encapsulation are out of the
	of the scope of this draft.		scope of this draft.
	Requirements Language		Requirements Language
	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 RFC 2119 [RFC2119].		document are to be interpreted as described in RFC 2119 [RFC2119].
	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
	skipping to change at page 2, line 4 ¶		skipping to change at page 2, line 11 ¶
	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 August 17, 2020.
			This Internet-Draft will expire on October 25, 2020.
	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
	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 . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Terminologies . . . . . . . . . . . . . . . . . . . . . . . . 3		2. Terminologies . . . . . . . . . . . . . . . . . . . . . . . . 3
	3. Network Slice Mapping Structure . . . . . . . . . . . . . . . 4		3. Network Slice Mapping Structure . . . . . . . . . . . . . . . 4
	3.1. Requirements Profile . . . . . . . . . . . . . . . . . . 5		3.1. Requirements Profile . . . . . . . . . . . . . . . . . . 5
	3.2. Identifiers . . . . . . . . . . . . . . . . . . . . . . . 6		3.2. Identifiers . . . . . . . . . . . . . . . . . . . . . . . 6
	3.3. Relevant functions . . . . . . . . . . . . . . . . . . . 6		3.3. Relevant functions . . . . . . . . . . . . . . . . . . . 6
	4. Network Slice Mapping Procedure . . . . . . . . . . . . . . . 7		4. Network Slice Mapping Procedure . . . . . . . . . . . . . . . 7
	4.1. Network Slice Mapping in Management Plane . . . . . . . . 8		4.1. Network Slice Mapping in Management Plane . . . . . . . . 8
	4.2. Network Slice Mapping in Control Plane . . . . . . . . . 9		4.2. Network Slice Mapping in Control Plane . . . . . . . . . 9
	4.3. Network Slice Mapping in data plane . . . . . . . . . . . 10		4.3. Network Slice Mapping in data plane . . . . . . . . . . . 9
	4.3.1. Data Plane Mapping Considerations . . . . . . . . . . 10		4.3.1. Data Plane Mapping Considerations . . . . . . . . . . 10
	4.3.2. Data Plane Mapping Design . . . . . . . . . . . . . . 10		4.3.2. Data Plane Mapping Design . . . . . . . . . . . . . . 10
	5. Network Slice Mapping Summary . . . . . . . . . . . . . . . . 15		5. Network Slice Mapping Summary . . . . . . . . . . . . . . . . 14
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 15		7. Security Considerations . . . . . . . . . . . . . . . . . . . 15
	8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15		8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15
	9. Normative References . . . . . . . . . . . . . . . . . . . . 15		9. Normative References . . . . . . . . . . . . . . . . . . . . 15
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
	1. Introduction		1. Introduction
	Driven by the new applications of 5G, the concept of network slicing		Driven by the new applications of 5G, the concept of network slicing
	is defined to provide a logical network with specific network		is defined to provide a logical network with specific capabilities
	capabilities and network characteristics. Network slice contains a		and characteristics. Network slice contains a set of network
	set of network functions and the required resources(e.g.		functions and allocated resources(e.g. Computation, storage and
	Computation, storage and network resources).According to [TS28530], a		network resources). According to [TS28530], a 5G end-to-end network
	5G end-to-end network slice consists of three major types network		slice is composed of three major types network segments: Radio Access
	segments: Radio Access Network (RAN), Transport Network (TN) and		Network (RAN), Transport Network (TN) and Mobile Core Network (CN).
	Mobile Core Network (CN). Transport network is supposed to provide		Transport network is supposed to provide the required connectivity
	the required connectivity between AN and CN, which specific		between AN and CN, which specific performance commitment. For each
	performance commitment. For each end-to-end network slice, the		end-to-end network slice, the topology and performance requirement
	topology and performance requirement on transport network can be very		for transport network can be very different, which requires transport
	different, which requires transport network to have the capability of		network to have the capability of supporting multiple different
	supporting multiple different transport network slices.		transport network slices.
	A transport network slice is a virtual (logical) network with a		A transport network slice is a virtual (logical) network with a
	particular network topology and a set of shared or dedicated network		particular network topology and a set of shared or dedicated network
	resources, which are used to provide the network slice consumer with		resources, which are used to provide the network slice consumer with
	the required connectivity, appropriate isolation and specific Service		the required connectivity, appropriate isolation and specific Service
	Level Agreement (SLA). A transport network slice could span multiple		Level Agreement (SLA). A transport network slice could span multiple
	technology (IP, Optical) and multiple administrative domains.		technology (IP, Optical) and multiple administrative domains.
	Depending on the consumer's requirement, a transport network slice		Depending on the consumer's requirement, a transport network slice
	could be isolated from other, often concurrent transport network		could be isolated from other concurrent transport network slices, in
	slices in terms of data plane, control plane and management plane.		terms of data plane, control plane and management plane. Transport
	Transport network slice is being defined and discussed in IETF.		network slice is being defined and discussed in IETF.
			Editor's Note: The work of
	The procedure of end-to-end network slice instance creation, network		The procedure of end-to-end network slice instance creation, network
	slice subnet instance creation and network slice instance termination		slice subnet instance creation and network slice instance termination
	in management plane are defined in [TS28531]. The end-to-end network		in management plane are defined in [TS28531]. The end-to-end network
	slice allocation is defined in ETSI ZSM003. But there is no		slice allocation is defined in ETSI [ZSM003]. But there is no
	specifications about how to map end-to-end network slice in 5G system		specifications about how to map end-to-end network slice in 5G system
	to transport network slice. This draft describes the procedure of		to transport network slice. This draft describes the procedure of
	mapping 5G end-to-end network slice into transport network slice in		mapping 5G end-to-end network slice into transport network slice in
	management plane, control plane and user plane.		management plane, control plane and user plane.
	2. Terminologies		2. Terminologies
	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].		document are to be interpreted as described in [RFC2119].
	skipping to change at page 5, line 34 ¶		skipping to change at page 5, line 34 ¶
	+-------------+ +---------------------+ +-------------+ Plane		+-------------+ +---------------------+ +-------------+ Plane
	| | | | -----------------		| | | | -----------------
	|<----------PDU session (S-NSSAI)---------->| Control		|<----------PDU session (S-NSSAI)---------->| Control
	| | | | Plane		| | | | Plane
	V V V V -----------------		V V V V -----------------
	/\ +-----+ +-----+ +-------+ Data		/\ +-----+ +-----+ +-------+ Data
	/AN\ -----| PE |-----...-----| PE |----| UPF | Plane		/AN\ -----| PE |-----...-----| PE |----| UPF | Plane
	/____\ +-----+ +-----+ +-------+		/____\ +-----+ +-----+ +-------+
	|-->TNSII<--|------>TNSI<-------|-->TNSII<--|		|-->TNSII<--|------>TNSI<-------|-->TNSII<--|
	TNSII: Transport Network Slice Interworking Identifier
	TNSI: Transport Network Slice Identifier
	3.1. Requirements Profile		3.1. Requirements Profile
	In order to satisfy a tenant's request for a network slice with		In order to satisfy a tenant's request for a network slice with
	certain characteristics, creating a new network slice or using		certain characteristics, creating a new network slice or using
	existing network slice instance is constrained by the customer's		existing network slice instance is constrained by the customer's
	requirement and the capability of the network slices.		requirement and the capability of the network slices.
	o Service Profile: represents the properties of network slice		o Service Profile: represents the properties of network slice
	related requirement that should be supported by the network slice		related requirement that should be supported by the network slice
	instance in 5G network. Service profile is defined in [TS28541]		instance in 5G network. Service profile is defined in [TS28541]
	skipping to change at page 6, line 17 ¶		skipping to change at page 6, line 15 ¶
	3.2. Identifiers		3.2. Identifiers
	Network slice related identifiers in management plane, control plane		Network slice related identifiers in management plane, control plane
	and user(data) plane play an important role in end-to-end network		and user(data) plane play an important role in end-to-end network
	slice mapping.		slice mapping.
	o Single Network Slice Selection Assistance Information(S-NSSAI):		o Single Network Slice Selection Assistance Information(S-NSSAI):
	end-to-end network slice identifier in control plane, which is		end-to-end network slice identifier in control plane, which is
	defined in [TS23501];		defined in [TS23501];
	o Network Slice Instance(NSI) Identifier: end-to-end network slice		o Network Slice Instance(NSI) Identifier:end-to-end network slice
	identifier in management plane, which is created in NSMF; NSI is		identifier in management plane, which is created in NSMF; NSI is
	is set of Network Function instances and the required resources		is set of Network Function instances and the required resources
	(e.g. compute, storage and networking resources) which form a		(e.g. compute, storage and networking resources) which form a
	deployed Network Slice, which is defined in [TS23501];		deployed Network Slice, which is defined in [TS23501]; ;
	o Transport Network Slice Instance(TN-NSSI) Identifier: transport		o Transport Network Slice Instance(TN-NSSI) Identifier: transport
	network slice identifier in management plane, which is created in		network slice identifier in management plane, which is created in
	TN NSSMF; TN-NSSI is newly defined in this draft.		TN NSSMF; TN-NSSI is newly defined in this draft.
	o Transport Network Slice Interworking Identifier (TNSII): network		o Transport Network Slice Interworking Identifier (TNSII): network
	slice identifier which is used for mapping end-to-end network		slice identifier which is used for mapping end-to-end network
	slice into transport network slice in user plane. TNSII is newly		slice into transport network slice in user plane. TNSII is newly
	defined in this draft.		defined in this draft.
	skipping to change at page 7, line 4 ¶		skipping to change at page 6, line 49 ¶
	There are a set of slice relevant functions that are necessary for		There are a set of slice relevant functions that are necessary for
	transport network slice management:		transport network slice management:
	o Topology management		o Topology management
	o QoS management		o QoS management
	o Resource management		o Resource management
	o Measurement management		o Measurement management
	o ...		o ...
	Some of these functions are implemented inside the transport network		Some of these functions are implemented inside the transport network
	and independent from the end-to-end network slice, e.g., topology		and independent from the end-to-end network slice, e.g., topology
	management, QoS management, resource management; Some of the		management, QoS management, resource management; Some of the
	functions are related to the end-to-end network slice and should		functions are related to the end-to-end network slice and should
	cooperate with other network elements from other domain, e.g.,		cooperate with other network elements from other domain, e.g.,
	Measurement management.		Measurement management.
	4. Network Slice Mapping Procedure		4. Network Slice Mapping Procedure
	This section provides a general procedure of network slice mapping:		This section provides a general procedure of network slice mapping:
	+--------------------------------+		+--------------------------------+
	| Requirement Matching |		| Requirement Matching |
	+---------------+----------------+		+---------------+----------------+
	|		|
	V		V
	+--------------------------------+		+--------------------------------+
	| NSI<->NSSI Mapping |		| NSI<->TN NSSI Mapping |
	+---------------+----------------+		+---------------+----------------+
	|		|
	V		V
	+--------------------------------+		+--------------------------------+
	| S-NSSAI Selection |		| S-NSSAI Selection |
	+---------------+----------------+		+---------------+----------------+
	|		|
	V		V
	+--------------------------------+		+--------------------------------+
	| S-NSSAI<->TNSII Mapping |		|S-NSSAI<---------->TNSII Mapping|
	+---------------+----------------+		| (NSI<->TN NSSI) |
	|		+---------------+----------------+
	V		|
	+--------------------------------+		V
	| TNSII<->TNSI Mapping |		+--------------------------------+
	+--------------------------------+		| TNSII<->TNSI Mapping |
			+--------------------------------+
	1. NSMF receives the request from CSMF for allocation of the network		1. NSMF receives the request from CSMF for allocation of a network
	slice instance with certain characteristics.		slice instance with certain characteristics.
	2. Based on the service requirement , the Network Slice Management		2. Based on the service requirement , NSMF acquires requirements for
	Function(NSMF) acquires the properties of network slice related		the end-to-end network slice instance , which is defined in Service
	requirement that should be supported by the network slice instance in		Profile([TS28541] section 6.3.3).
	5G network, which is defined in Service Profile([TS28541] section
	6.3.3).
	3. NSMF needs to decide on the constituent NSSIs(including AN NSSI,		3. NSMF derives transport network slice related requirements from
	CN NSSI and TN NSSI) to be created using the information from service		the Service profile, and maintains them in Transport Network Slice
	profile and the endpoint information(AN/CN edge nodes) . So NSMF		Profile, So as to CN Slice Profile and AN Slice Profile, in order to
	derives transport network slice related requirements from the Service		decide on the constituent NSSIs(including AN NSSI, CN NSSI and TN
	profile, and maintains them in Transport Network Slice Profile. So		NSSI) of the NSI, based on the service profile and the endpoint
	as to CN Slice Profile and AN Slice Profile.		information(AN/CN edge nodes).
	4. Transport Network Slice Profile is sent to TN NSSMF to request		4. NSMF sends the Transport Network Slice Profile to TN NSSMF for TN
	allocation of the required TN NSSI(s).		NSSI allocation.
	5. TN NSSMF allocates TN network slicing subnet instance(TN NSSI)		5. TN NSSMF allocates TN NSSI which could satisfy the requirement of
	which could satisfy the requirement between the specified endpoints		Transport Network Slice Profile between the specified endpoints (AN/
	(AN/CN edge nodes) in Transport Network Slice Profile and sends the		CN edge nodes) and sends the TN NSSI Identifier to NSMF.
	TN NSSI Identifier to NSMF.
	6. NSMF acquires the mapping relationship between NSI Identifier and		6. NSMF acquires the mapping relationship between NSI and TN NSSI.
	TN NSSI Identifier.
	7. When a PDU session is set up between AN and CN, S-NSSAI is used		7. NSMF matains the mapping relationship between NSI and S-NSSAI and
	to choose network slice instance for the PDU session.		the mapping relationship between TN NSSI and TNSII, which could be
			used to set up mapping relationship between S-NSSAI and TNSII.
	8. For a user packet in a particular network slice that to be sent		8. When a PDU session is set up between AN and CN, an S-NSSAI is
	to transport network, the AN/CN edge nodes encapsulate the packet		slected for the PDU session.
	using the transport network slice interworking identifier (TNSII)
	according to the S-NSSAI or the NSI. Network Slice could also be
	differentiated by physical interface, if different network slices are
	transported through different interface;
	9. The edge node of transport network parses the TNSII from the		9. AN/CN edge nodes encapsulate the packet using TNSII, according to
	packet and maps the packet to the corresponding transport network		the selected S-NSSAI. Network Slice could also be differentiated by
	slice. It may encapsulate a transport network slice identifier		physical interface, if different network slices are transported
	(TNSI) into the packet. .		through different interface;
	10. The nodes in transport network transit the packet inside the		10. The edge node of transport network parses the TNSII from the
	corresponding transport network slice.		packet and maps the packet to the corresponding transport network
			slice. It may encapsulate packet with TNSI. The nodes in transport
			network transit the packet inside the corresponding transport network
			slice according to TNSI.
	The procedure of end-to-end network slice mapping involves the		The procedure of end-to-end network slice mapping involves the
	mapping in three network planes: management plane, control plane and		mapping in three network planes: management plane, control plane and
	data plane.		data plane.
	4.1. Network Slice Mapping in Management Plane		4.1. Network Slice Mapping in Management Plane
	The transport network management Plane maintains the interface		The transport network management Plane maintains the interface
	between NSMF and TN NSSMF, which 1) guarantees that transport network		between NSMF and TN NSSMF, which 1) guarantees that transport network
	slice could connect the AN and CN with specified characteristics that		slice could connect the AN and CN with specified characteristics that
	skipping to change at page 9, line 40 ¶		skipping to change at page 9, line 35 ¶
	allocation from multiple requests from NSMF (but the detailed		allocation from multiple requests from NSMF (but the detailed
	mechanism should be out of scope in the draft)		mechanism should be out of scope in the draft)
	TN NSSMF sends the selected or newly allocated TN NSSI identifier to		TN NSSMF sends the selected or newly allocated TN NSSI identifier to
	NSMF. The mapping relationship between NSI identifier and TN NSSI		NSMF. The mapping relationship between NSI identifier and TN NSSI
	identifier is maintained in both NSMF and TN NSSMF.		identifier is maintained in both NSMF and TN NSSMF.
	4.2. Network Slice Mapping in Control Plane		4.2. Network Slice Mapping in Control Plane
	There is no explicit interaction between transport network and AN/CN		There is no explicit interaction between transport network and AN/CN
	in the control plane, but the S-NSSAI defined in[TS23501] is treated		in the control plane, but the S-NSSAI defined in [TS23501] is treated
	as the end-to-end network slice identifier in the control plane of AN		as the end-to-end network slice identifier in the control plane of AN
	and CN, which is used in UE registration and PDU session setup. In		and CN, which is used in UE registration and PDU session setup. In
	this draft, we assume that there is mapping relationship between		this draft, we assume that there is mapping relationship between
	S-NSSAI and NSI in the management plane, thus it could be mapped to a		S-NSSAI and NSI in the management plane, thus it could be mapped to a
	transport network slice .		transport network slice .
	Editor's note: The mapping relationship between NSI defined in		Editor's note: The mapping relationship between NSI defined in
	[TS23501] and S-NSSAI defined in [TS23501] is still in discussion.		[TS23501] and S-NSSAI defined in [TS23501] is still in discussion.
	4.3. Network Slice Mapping in data plane		4.3. Network Slice Mapping in data plane
	skipping to change at page 15, line 45 ¶		skipping to change at page 15, line 33 ¶
	Note to RFC Editor: this section may be removed on publication as an		Note to RFC Editor: this section may be removed on publication as an
	RFC.		RFC.
	7. Security Considerations		7. Security Considerations
	TBD		TBD
	8. Acknowledgements		8. Acknowledgements
	The authors would like to thank Shunsuke Homma for reviewing the draft and		The authors would like to thank Shunsuke Homma for reviewing the
	giving valuable comments.		draft and giving valuable comments.
	9. Normative References		9. Normative References
	[GST] "Generic Network Slice Template", 2016,		[GST] "Generic Network Slice Template",
	<https://www.gsma.com/newsroom/all-documents/generic-		<https://www.gsma.com/newsroom/all-documents/generic-
	network-slice-template-v2-0/>.		network-slice-template-v2-0/>.
	[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.
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<https://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
	[TS23501] "3GPP TS23.501", 2016,		[TS23501] "3GPP TS23.501",
	<https://portal.3gpp.org/desktopmodules/Specifications/		<https://portal.3gpp.org/desktopmodules/Specifications/
	SpecificationDetails.aspx?specificationId=3144>.		SpecificationDetails.aspx?specificationId=3144>.
	[TS28530] "3GPP TS28.530", 2016,		[TS28530] "3GPP TS28.530",
	<https://portal.3gpp.org/desktopmodules/Specifications/		<https://portal.3gpp.org/desktopmodules/Specifications/
	SpecificationDetails.aspx?specificationId=3273>.		SpecificationDetails.aspx?specificationId=3273>.
	[TS28531] "3GPP TS28.531", 2016,		[TS28531] "3GPP TS28.531",
	<https://portal.3gpp.org/desktopmodules/Specifications/		<https://portal.3gpp.org/desktopmodules/Specifications/
	SpecificationDetails.aspx?specificationId=3274>.		SpecificationDetails.aspx?specificationId=3274>.
	[TS28541] "3GPP TS 28.541", 2016,		[TS28541] "3GPP TS 28.541",
	<https://portal.3gpp.org/desktopmodules/Specifications/		<https://portal.3gpp.org/desktopmodules/Specifications/
	SpecificationDetails.aspx?specificationId=3400>.		SpecificationDetails.aspx?specificationId=3400>.
	[ZSM003] "End to end management and orchestration of network		[ZSM003] "ETSI ZSM003",
	slicing", 2016,		<https://portal.3gpp.org/desktopmodules/Specifications/
	<https://portal.etsi.org/webapp/WorkProgram/		SpecificationDetails.aspx?specificationId=3144>.
	Report_WorkItem.asp?WKI_ID=54284 >.
	Authors' Addresses		Authors' Addresses
	Xuesong Geng		Xuesong Geng
	Huawei Technologies		Huawei Technologies
	Email: gengxuesong@huawei.com		Email: gengxuesong@huawei.com
	Jie Dong		Jie Dong
	Huawei Technologies		Huawei Technologies
	Email: jie.dong@huawei.com		Email: jie.dong@huawei.com
			Ran Pang
			China Unicom
			Email: pangran@chinaunicom.cn
			Liuyan Han
			China Mobile
			Email: hanliuyan@chinamobile.com
	Tomonobu Niwa		Tomonobu Niwa
	KDDI		KDDI
	Email: to-niwa@kddi.com		Email: to-niwa@kddi.com
	Jaewhan JIN		Jaehwan Jin
	LG U+		LG U+
	Email: daenamu1@lguplus.co.kr		Email: daenamu1@lguplus.co.kr
			Chang Liu
			China Unicom
			Email: liuc131@chinaunicom.cn
			Nikesh Nageshar
			Individual
			Email: nikesh.nageshar@gmail.com
End of changes. 39 change blocks.
	108 lines changed or deleted		123 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/