< draft-dm-net2cloud-gap-analysis-03.txt   draft-dm-net2cloud-gap-analysis-04.txt >
Network Working Group L. Dunbar Network Working Group L. Dunbar
Internet Draft A. Malis Internet Draft A. Malis
Intended status: Informational Huawei Intended status: Informational Huawei
Expires: July 27, 2019 C. Jacquenet Expires: August 6, 2019 C. Jacquenet
Orange Orange
January 27, 2019 February 6, 2019
Gap Analysis of Interconnecting Underlay with Cloud Overlay Gap Analysis of Interconnecting Underlay with Cloud Overlay
draft-dm-net2cloud-gap-analysis-03 draft-dm-net2cloud-gap-analysis-04
Abstract Abstract
This document analyzes the technological gaps when using SD-WAN to This document analyzes the technological gaps when using SD-WAN to
interconnect workloads & apps hosted in various locations, interconnect workloads & apps hosted in various locations,
especially cloud data centers when the network service providers do especially cloud data centers when the network service providers do
not have or have limited physical infrastructure to reach the not have or have limited physical infrastructure to reach the
locations [Net2Cloud-problem]. locations [Net2Cloud-problem].
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. This document may not be modified,
and derivative works of it may not be created, except to publish it
as an RFC and to translate it into languages other than English.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
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."
skipping to change at page 2, line 4 skipping to change at page 1, line 37
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
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 April 27, 2009. This Internet-Draft will expire on July 6, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 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
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
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...................................................2
2. Conventions used in this document..............................3 2. Conventions used in this document..............................3
3. Gap Analysis of C-PEs Registration Protocol....................4 3. Gap Analysis of C-PEs Registration Protocol....................4
4. Gap Analysis in aggregating VPN paths and Internet paths.......5 4. Gap Analysis in aggregating VPN paths and Internet paths.......5
4.1. Gap analysis of Using BGP to cover SD-WAN paths...........7 4.1. Gap analysis of Using BGP to cover SD-WAN paths...........6
4.2. Gaps in preventing attacks from Internet facing ports....10 4.2. Gaps in preventing attacks from Internet facing ports.....9
5. Gap analysis of CPEs not directly connected to VPN PEs........10 5. Gap analysis of CPEs not directly connected to VPN PEs........10
5.1. Gap Analysis of Floating PEs to connect to Remote CPEs...12 5.1. Gap Analysis of Floating PEs to connect to Remote CPEs...11
5.2. NAT Traversal............................................13 5.2. NAT Traversal............................................12
5.3. Complication of using BGP between PEs and remote CPEs via 5.3. Complication of using BGP between PEs and remote CPEs via
Internet......................................................13 Internet......................................................12
5.4. Designated Forwarder to the remote edges.................14 5.4. Designated Forwarder to the remote edges.................13
5.5. Traffic Path Management..................................14 5.5. Traffic Path Management..................................13
6. Manageability Considerations..................................15 6. Manageability Considerations..................................14
7. Security Considerations.......................................15 7. Security Considerations.......................................14
8. IANA Considerations...........................................15 8. IANA Considerations...........................................14
9. References....................................................15 9. References....................................................14
9.1. Normative References.....................................16 9.1. Normative References.....................................15
9.2. Informative References...................................16 9.2. Informative References...................................15
10. Acknowledgments..............................................17 10. Acknowledgments..............................................16
1. Introduction 1. Introduction
[Net2Cloud-Problem] describes the problems that enterprises face [Net2Cloud-Problem] describes the problems that enterprises face
today in transitioning their IT infrastructure to support digital today in transitioning their IT infrastructure to support digital
economy, such as connecting enterprises' branch offices to dynamic economy, such as connecting enterprises' branch offices to dynamic
workloads in different Cloud DCs. workloads in different Cloud DCs.
This document analyzes the technological gaps to interconnect This document analyzes the technological gaps to interconnect
dynamic workloads & apps hosted in various locations and in Cloud dynamic workloads & apps hosted in various locations and in Cloud
 End of changes. 11 change blocks. 
25 lines changed or deleted 21 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/