<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-rtgwg-net2cloud-problem-statement" target="https://datatracker.ietf.org/doc/html/draft-ietf-rtgwg-net2cloud-problem-statement-00">
   <front>
      <title>Seamless Interconnect Underlay to Cloud Overlay Problem Statement</title>
      <author initials="L." surname="Dunbar" fullname="Linda Dunbar">
         <organization>Huawei</organization>
      </author>
      <author initials="A. G." surname="Malis" fullname="Andrew G. Malis">
         <organization>Huawei</organization>
      </author>
      <author initials="C." surname="Jacquenet" fullname="Christian Jacquenet">
         <organization>Orange</organization>
      </author>
      <author initials="M." surname="Toy" fullname="Mehmet Toy">
         <organization>Verizon</organization>
      </author>
      <date month="February" day="12" year="2019" />
      <abstract>
	 <t>   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&#x27; on-premises DCs &amp; branch offices. This document also
   describes some of the (network) problems that many enterprises face
   when they have workloads &amp; applications &amp; 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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-rtgwg-net2cloud-problem-statement-00" />
   
</reference>
