| < draft-ietf-rtgwg-net2cloud-problem-statement-04.txt | draft-ietf-rtgwg-net2cloud-problem-statement-05.txt > | |||
|---|---|---|---|---|
| Network Working Group L. Dunbar | Network Working Group L. Dunbar | |||
| Internet Draft Futurewei | Internet Draft Futurewei | |||
| Intended status: Informational Andy Malis | Intended status: Informational Andy Malis | |||
| Expires: Dec 2019 Independent | Expires: March 2020 Independent | |||
| C. Jacquenet | C. Jacquenet | |||
| Orange | Orange | |||
| M. Toy | M. Toy | |||
| Verizon | Verizon | |||
| September 23, 2019 | November 1, 2019 | |||
| Dynamic Networks to Hybrid Cloud DCs Problem Statement | Dynamic Networks to Hybrid Cloud DCs Problem Statement | |||
| draft-ietf-rtgwg-net2cloud-problem-statement-04 | draft-ietf-rtgwg-net2cloud-problem-statement-05 | |||
| Abstract | Abstract | |||
| This document describes the problems that enterprises face today | This document describes the problems that enterprises face today | |||
| when interconnecting their branch offices with dynamic workloads in | when interconnecting their branch offices with dynamic workloads in | |||
| third party data centers (a.k.a. Cloud DCs). | 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. | ||||
| It examines some of the approaches interconnecting cloud DCs with | It examines some of the approaches interconnecting cloud DCs with | |||
| enterprises' on-premises DCs & branch offices. This document also | enterprises' on-premises DCs & branch offices. This document also | |||
| describes some of the network problems that many enterprises face | describes some of the network problems that many enterprises face | |||
| when they have workloads & applications & data split among different | when they have workloads & applications & data split among different | |||
| data centers, especially for those enterprises with multiple sites | data centers, especially for those enterprises with multiple sites | |||
| that are already interconnected by VPNs (e.g., MPLS L2VPN/L3VPN). | that are already interconnected by VPNs (e.g., MPLS L2VPN/L3VPN). | |||
| Current operational problems are examined to determine whether there | Current operational problems are examined to determine whether there | |||
| is a need to improve existing protocols or whether a new protocol is | is a need to improve existing protocols or whether a new protocol is | |||
| skipping to change at page 2, line 16 ¶ | skipping to change at page 2, line 21 ¶ | |||
| months and may be updated, replaced, or obsoleted by other documents | months and may be updated, replaced, or obsoleted by other documents | |||
| at any time. It is inappropriate to use Internet-Drafts as | at any time. It is inappropriate to use Internet-Drafts as | |||
| reference material or to cite them other than as "work in progress." | reference material or to cite them other than as "work in progress." | |||
| The list of current Internet-Drafts can be accessed at | The list of current Internet-Drafts can be accessed at | |||
| http://www.ietf.org/ietf/1id-abstracts.txt | http://www.ietf.org/ietf/1id-abstracts.txt | |||
| The list of Internet-Draft Shadow Directories can be accessed at | The list of Internet-Draft Shadow Directories can be accessed at | |||
| http://www.ietf.org/shadow.html | http://www.ietf.org/shadow.html | |||
| This Internet-Draft will expire on March 23, 2009. | This Internet-Draft will expire on April 1, 2009. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2019 IETF Trust and the persons identified as the | Copyright (c) 2019 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| skipping to change at page 2, line 40 ¶ | skipping to change at page 2, line 45 ¶ | |||
| Section 4.e of the Trust Legal Provisions and are provided without | Section 4.e of the Trust Legal Provisions and are provided without | |||
| warranty as described in the Simplified BSD License. | warranty as described in the Simplified BSD License. | |||
| Table of Contents | Table of Contents | |||
| 1. Introduction...................................................3 | 1. Introduction...................................................3 | |||
| 1.1. On the evolution of Cloud DC connectivity.................3 | 1.1. On the evolution of Cloud DC connectivity.................3 | |||
| 1.2. The role of SD-WAN techniques in Cloud DC connectivity....4 | 1.2. The role of SD-WAN techniques in Cloud DC connectivity....4 | |||
| 2. Definition of terms............................................4 | 2. Definition of terms............................................4 | |||
| 3. Interconnecting Enterprise Sites with Cloud DCs................5 | 3. Interconnecting Enterprise Sites with Cloud DCs................5 | |||
| 3.1. Multiple connections to workloads in a Cloud DC...........5 | 3.1. Multiple connections to workloads in a Cloud DC...........6 | |||
| 3.2. Interconnect Private and Public Cloud DCs.................7 | 3.2. Interconnect Private and Public Cloud DCs.................7 | |||
| 3.3. Desired Properties for Networks that interconnect Hybrid | 3.3. Desired Properties for Networks that interconnect Hybrid | |||
| Clouds.........................................................8 | Clouds.........................................................8 | |||
| 4. Multiple Clouds Interconnection................................9 | 4. Multiple Clouds Interconnection................................9 | |||
| 4.1. Multi-Cloud Interconnection...............................9 | 4.1. Multi-Cloud Interconnection...............................9 | |||
| 4.2. Desired Properties for Multi-Cloud Interconnection.......11 | 4.2. Desired Properties for Multi-Cloud Interconnection.......11 | |||
| 5. Problems with MPLS-based VPNs extending to Hybrid Cloud DCs...11 | 5. Problems with MPLS-based VPNs extending to Hybrid Cloud DCs...11 | |||
| 6. Problem with using IPsec tunnels to Cloud DCs.................13 | 6. Problem with using IPsec tunnels to Cloud DCs.................13 | |||
| 6.1. Complexity of multi-point any-to-any interconnection.....13 | 6.1. Complexity of multi-point any-to-any interconnection.....13 | |||
| 6.2. Poor performance over long distance......................14 | 6.2. Poor performance over long distance......................14 | |||
| 6.3. Scaling Issues with IPsec Tunnels........................14 | 6.3. Scaling Issues with IPsec Tunnels........................14 | |||
| 7. Problems of Using SD-WAN to connect to Cloud DCs..............15 | 7. Problems of Using SD-WAN to connect to Cloud DCs..............15 | |||
| 7.1. SD-WAN among branch offices vs. interconnect to Cloud DCs15 | 7.1. SD-WAN among branch offices vs. interconnect to Cloud DCs15 | |||
| 8. End-to-End Security Concerns for Data Flows...................18 | 8. End-to-End Security Concerns for Data Flows...................18 | |||
| 9. Requirements for Dynamic Cloud Data Center VPNs...............18 | 9. Requirements for Dynamic Cloud Data Center VPNs...............18 | |||
| 10. Security Considerations......................................19 | 10. Security Considerations......................................19 | |||
| End of changes. 7 change blocks. | ||||
| 7 lines changed or deleted | 11 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||