Skip to main content

Seamless Interconnect Underlay to Cloud Overlay Problem Statement

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Linda Dunbar , Andrew G. Malis , Christian Jacquenet , Mehmet Toy
Last updated 2019-02-06
Replaces draft-dm-vpn-ext-to-cloud-dc-problem-statement
Replaced by draft-ietf-rtgwg-net2cloud-problem-statement
RFC stream (None)
Intended RFC status (None)
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 (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


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.


Linda Dunbar
Andrew G. Malis
Christian Jacquenet
Mehmet Toy

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