<?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-26">
   <front>
      <title>Status of this Memo</title>
      <author initials="L." surname="Dunbar" fullname="Linda Dunbar">
         <organization>Futurewei</organization>
      </author>
      <author initials="A. G." surname="Malis" fullname="Andrew G. Malis">
         <organization>Malis Consulting</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>
      <author initials="K." surname="Majumdar" fullname="Kausik Majumdar">
         <organization>Microsoft</organization>
      </author>
      <date month="April" day="24" year="2023" />
      <abstract>
	 <t>   This document describes the network-related problems enterprises
   face at the moment of writing this specification when
   interconnecting their branch offices with dynamic workloads in
   third-party data centers (a.k.a. Cloud DCs) and some mitigation
   practices. There can be many problems associated with connecting to
   or among Cloud DCs; the Net2Cloud problem statements are mainly for
   enterprises that already have traditional VPN services and are
   interested in leveraging those networks (instead of altogether
   abandoning them). Other problems are out of the scope of this
   document.
   This document also describes the mitigation practices for getting
   around the identified problems.

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