< draft-fang-actn-multidomain-dci-00.txt		draft-fang-actn-multidomain-dci-01.txt >
	Network Working Group Luyuan Fang		Network Working Group Luyuan Fang
	Internet Draft Microsoft		Internet Draft Microsoft
	Intended status: Informational		Intended status: Informational
			Expires: March 29, 2015 September 29, 2014
	June 5, 2014		ACTN Use Case for Multi-domain Data Center Interconnect
	ACTN Use-case for Multi-domain Data Center Interconnect
	draft-fang-actn-multidomain-dci-00.txt		draft-fang-actn-multidomain-dci-01.txt
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with		This Internet-Draft is submitted to IETF in full conformance with
	the provisions of BCP 78 and BCP 79.		the 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), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	skipping to change at page 1, line 33 ¶		skipping to change at page 1, line 32 ¶
	months and may be updated, replaced, or obsoleted by other documents		months and may be updated, replaced, or obsoleted by other documents
	at any time. It is inappropriate to use Internet-Drafts as		at any time. It is inappropriate to use Internet-Drafts as
	reference material or to cite them other than as "work in progress."		reference material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt		http://www.ietf.org/ietf/1id-abstracts.txt
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on December 5, 2014.		This Internet-Draft will expire on March 29, 2015.
	Copyright Notice		Copyright Notice
	Copyright (c) 2014 IETF Trust and the persons identified as the		Copyright (c) 2014 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
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://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		carefully, as they describe your rights and restrictions with
	respect to this document.		respect to this document.
	Abstract		Abstract
	This document discusses a use-case for data center operators that		This document discusses a use case for data center operators that
	need to interface multi-domain transport networks to offer their		need to interface multi-domain transport networks to offer their
	global data center applications and services. As data center		global data center applications and services. As data center
	operators face multi-domain and diverse transport technology,		operators face multi-domain and diverse transport technology,
	interoperability based on standard-based abstraction is required for		interoperability based on standard-based abstraction is required to
	dynamic and flexible applications and services.		support dynamic and flexible applications and services.
	Table of Contents		Table of Contents
	1. Introduction..................................................2		1. Introduction..................................................2
	2. Multi-domain Data Center Interconnection Applications..........3		2. Multi-domain Data Center Interconnection Applications..........3
	2.1. VM Migration..............................................3		2.1. VM Migration..............................................3
	2.2. Global Load Balancing.....................................4		2.2. Global Load Balancing.....................................4
	2.3. Disaster Recovery.........................................4		2.3. Disaster Recovery.........................................4
	2.4. On-demand Virtual Connection/Circuit Services.............5		2.4. On-demand Virtual Connection/Circuit Services.............5
	3. Issues and Challenges for Multi-domain Data Center		3. Issues and Challenges for Multi-domain Data Center
	Interconnection Operations........................................5		Interconnection Operations........................................5
	4. Requirements...................................................7		4. Control Hierarchy..............................................7
	5. References.....................................................9		5. Requirements...................................................9
	6. Contributors...................................................9		6. References....................................................10
	Authors' Addresses................................................9		7. Contributors..................................................11
	Intellectual Property Statement...................................9		Authors' Addresses...............................................11
	Disclaimer of Validity...........................................10		Intellectual Property Statement..................................11
			Disclaimer of Validity...........................................11
	1. Introduction		1. Introduction
	This document discusses a use-case for data center operators that		This document discusses a use case for data center operators that
	need to interface multi-domain transport networks to offer their		need to interface multi-domain transport networks to offer their
	global data center applications and services. As data center		global data center applications and services. As data center
	providers face multi-domain and diverse transport technology,		providers face multi-domain and diverse transport technology,
	interoperability based on standard-based abstraction is required for		interoperability based on standard-based abstraction is required to
	dynamic and flexible applications and services.		support dynamic and flexible applications and services.
	This use-case is a part of the overarching work, called Abstraction		This use case is a part of the overarching work, called Abstraction
	and Control of Transport Networks (ACTN). The goal of ACTN is to		and Control of Transport Networks (ACTN). The goal of ACTN is to
	facilitate virtual network operation by:		facilitate virtual network operation by:
	. The creation of a virtualized environment allowing operators to		. The creation of a virtualized environment allowing operators to
	view the abstraction of the underlying multi-admin, multi-		view the abstraction of the underlying multi-admin, multi-
	vendor, multi-technology networks and		vendor, multi-technology networks and
	. The operation and control/management of these multiple networks		. The operation and control/management of these multiple networks
	as a single virtualized network.		as a single virtualized network.
	skipping to change at page 7, line 40 ¶		skipping to change at page 7, line 40 ¶
	5. These transport network domains may be diverse in terms of local		5. These transport network domains may be diverse in terms of local
	policy, transport technology and its capability and vendor		policy, transport technology and its capability and vendor
	equipment. Due to this diversity, new service introduction,		equipment. Due to this diversity, new service introduction,
	requiring connections that traverse multiple domains, need		requiring connections that traverse multiple domains, need
	significant planning, and several manual operations to interface		significant planning, and several manual operations to interface
	different vendor equipment and technology. New applications		different vendor equipment and technology. New applications
	requiring dynamic and elastic services and real-time mobility may		requiring dynamic and elastic services and real-time mobility may
	be hampered by these manual operational factors.		be hampered by these manual operational factors.
	4. Requirements		4. Control Hierarchy
			This section provides a control hierarchy for multi-domain DC
			operations.
			Figure 2 shows a control hierarchy for multi-domain Data Center
			Interconnection operation.
			+----------------+
			| Global DCI |
			| Operation |
			| Control |
			| |
			| |
			+--------+-------+
			|
			|
			|
			|
			+--------+-------+
			| |
			| |
			| E2E |
			| Network Control|
			| |
			+----+---+---+---+
			| | |
			| | |
			+---------------+ | +----------------+
			| | |
			| | |
			+------+-----+ +-----+------+ +------+-----+
			| Control for| | Control for| | Control for|
			| Transport | | Transport | | Transport |
			| Network A | | Network B | | network C |
			| | | | | |
			+------------+ +------------+ +------------+
			+---+ ------ ------ ------ +---+
			|DC1|--//// \\\\ //// \\\\ //// \\\\---+DC4|
			+---+ | | | | | | +---+
			| TN A +---+ TN B +--+ TN C |
			/ | | | | |
			/ \\\\ //// / \\\\ //// \\\\ ////
			+---+/ ------ / ------ \ ------ \
			|DC2| / \ \\+---+
			+---+ / \ \DC6|
			+/--+ \ +---+ +---+
			|DC3| \|DC4|
			+---+ +---+
			There are a number of important considerations to support a global
			multi-domain data center interconnection operation.
			1. Need a hierarchical operation/control.
			2. Build on top of existing network control technologies/domains
			to be able to E2E network control to help global DCI
			operation/control.
			3. Need standard-based abstraction/APIs and protocols between E2E
			network control and global DCI operation control and between
			E2E network control and domain transport network controls.
			5. Requirements
	This section provides high-level requirements to fulfill multi-		This section provides high-level requirements to fulfill multi-
	domain data center interconnection to support various applications		domain data center interconnection to support various applications
	discussed in the previous sections.		discussed in the previous sections.
	1. The interfaces between the Data Center Operation and each		1. The interfaces between the Data Center Operation and each
	transport network domain SHOULD support standards-based		transport network domain SHOULD support standards-based
	abstraction with a common information/data model.		abstraction with a common information/data model.
	2. The Data Center Operation should be able to create a single		2. The Data Center Operation should be able to create a single
	skipping to change at page 8, line 30 ¶		skipping to change at page 10, line 4 ¶
	Center Operation to each transport domain to establish an		Center Operation to each transport domain to establish an
	end-to-end virtual connections/circuits.		end-to-end virtual connections/circuits.
	i. The type of the connection: P2P, P2MP, etc.		i. The type of the connection: P2P, P2MP, etc.
	ii. Concurrency of the request (this indicates if the		ii. Concurrency of the request (this indicates if the
	connections must be simultaneously available or not in		connections must be simultaneously available or not in
	case of multiple connection requests).		case of multiple connection requests).
	iii. The duration of the connections		iii. The duration of the connections
	iv. SLA/QoS parameters: minimum guaranteed bandwidth,		iv. SLA/QoS parameters: minimum guaranteed bandwidth,
	latency range, etc.		latency range, etc.
	v. Protection/Reroute Options (e.g., SRLG requirement,		v. Protection/Reroute Options (e.g., SRLG requirement,
	etc.)		etc.)
	vi. Policy Constraints (e.g., peering preferences, etc.)		vi. Policy Constraints (e.g., peering preferences, etc.)
	d. Network Virtual Connections/Circuits Modification Request		d. Network Virtual Connections/Circuits Modification Request
	from the Data Center Operation to each transport domain to		from the Data Center Operation to each transport domain to
	change QoS/SLA, protection schemes of the existing		change QoS/SLA, protection schemes of the existing
	connections/circuits.		connections/circuits.
	e. Network Abnormality Report (Push Model) from each transport		e. Network Abnormality Report (Push Model) from each transport
	domain to the Data Center Operation indicating the service		domain to the Data Center Operation indicating the service
	impacting network conditions or the potential degradation		impacting network conditions or the potential degradation
	indications of the existing virtual connections/circuits.		indications of the existing virtual connections/circuits.
	5. References		6. References
	[ACTN-Frame] D. Ceccarelli, L. Fang, Y. Lee and D. Lopez, "Framework		[ACTN-Frame] D. Ceccarelli, L. Fang, Y. Lee and D. Lopez, "Framework
	for Abstraction and Control of Transport Networks," draft-		for Abstraction and Control of Transport Networks," draft-
	ceccarelli-actn-framework, work in progress.		ceccarelli-actn-framework, work in progress.
	[ACTN-PS] Y. Lee, D. King, M. Boucadair, R. Jing and L. Murillo,		[ACTN-PS] Y. Lee, D. King, M. Boucadair, R. Jing and L. Murillo,
	"Problem Statement for the Abstraction and Control of		"Problem Statement for the Abstraction and Control of
	Transport Networks," draft-leeking-actn-problem-statement,		Transport Networks," draft-leeking-actn-problem-statement,
	work in progress.		work in progress.
	6. Contributors		7. Authors' Addresses
	Authors' Addresses
	Luyuan Fang		Luyuan Fang
	Microsoft		Microsoft
	Email : lufang@microsoft.com		Email : lufang@microsoft.com
	Intellectual Property Statement		Intellectual Property Statement
	The IETF Trust takes no position regarding the validity or scope of		The IETF Trust takes no position regarding the validity or scope of
	any Intellectual Property Rights or other rights that might be		any Intellectual Property Rights or other rights that might be
	claimed to pertain to the implementation or use of the technology		claimed to pertain to the implementation or use of the technology
End of changes. 14 change blocks.
	24 lines changed or deleted		84 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/