Seamless Interconnect Underlay to Cloud Overlay Problem Statement
draft-dm-net2cloud-problem-statement-07
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2019-02-06 | ||
| Replaces | draft-dm-vpn-ext-to-cloud-dc-problem-statement | ||
| Replaced by | draft-ietf-rtgwg-net2cloud-problem-statement | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-rtgwg-net2cloud-problem-statement | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-dm-net2cloud-problem-statement-07.txt
Abstract
This document describes the problems that enterprises face today when connecting their branch offices to dynamic workloads in third party data centers (a.k.a. Cloud DCs). It examines some of the approaches interconnecting cloud DCs with enterprises' on-premises DCs & branch offices. This document also describes some of the (network) problems that many enterprises face when they have workloads & applications & data split among hybrid 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@huawei.com)
Andrew 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.)