Dynamic Networks to Hybrid Cloud DCs Problem Statement
draft-ietf-rtgwg-net2cloud-problem-statement-11

Document Type Expired Internet-Draft (rtgwg WG)
Authors Linda Dunbar  , Andy Malis  , Christian Jacquenet  , Mehmet Toy 
Last updated 2021-01-27 (latest revision 2020-07-26)
Replaces draft-dm-net2cloud-problem-statement
Stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-rtgwg-net2cloud-problem-statement-11.txt

Abstract

This document describes the problems that enterprises face today when interconnecting their branch offices with dynamic workloads in third party data centers (a.k.a. Cloud DCs). There can be many problems associated with network connecting to or among Clouds, many of which probably are out of the IETF scope. The objective of this document is to identify some of the problems that need additional work in IETF Routing area. Other problems are out of the scope of this document. This document focuses on the network problems that many enterprises face when they have workloads & applications & data split among different data centers, especially for those enterprises with multiple sites that are already interconnected by VPNs (e.g., MPLS L2VPN/L3VPN). Current operational problems are examined to determine whether there is a need to improve existing protocols or whether a new protocol is necessary to solve them.

Authors

Linda Dunbar (linda.dunbar@futurewei.com)
Andy Malis (agmalis@gmail.com)
Christian Jacquenet (christian.jacquenet@orange.com)
Mehmet Toy (mehmet.toy@verizon.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)