BGP Usage for SDWAN Overlay Networks
draft-dunbar-bess-bgp-sdwan-usage-04
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2020-01-31
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
htmlized
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group L. Dunbar
Internet Draft J. Guichard
Intended status: Informational Futurewei
Expires: July 31, 2020 Ali Sajassi
Cisco
J. Drake
Juniper
B. Najem
Bell Canada
Ayan Barnerjee
D. Carrel
Cisco
January 31, 2020
BGP Usage for SDWAN Overlay Networks
draft-dunbar-bess-bgp-sdwan-usage-04
Abstract
The document describes three distinct SDWAN scenarios and discusses
the applicability of BGP for each of those scenarios. The goal of
the document is to make it easier for future SDWAN control plane
protocols discussion.
SDWAN edge nodes are commonly interconnected by multiple underlay
networks which can be owned and managed by different network
providers. A BGP-based control plane is chosen for handling large
number of SDWAN edge nodes with little manual intervention.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
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
Task Force (IETF), its areas, and its working groups. Note that
xxx, et al. Expires July 31, 2020 [Page 1]
Internet-Draft BGP Usage for SDWAN January 31, 2020
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
This Internet-Draft will expire on July 31, 2020.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License.
Table of Contents
1. Introduction...................................................3
2. Conventions used in this document..............................4
3. Use Case Scenario Description and Requirements.................5
3.1. Requirements..............................................6
3.1.1. Client Service Requirement...........................6
3.1.2. Application Flow Based Segmentation..................6
3.1.3. SDWAN Node Provisioning..............................7
3.2. Scenarios #1: Homogeneous WAN.............................9
3.3. Scenario #2: SDWAN WAN ports to VPN's PEs and to Internet10
Dunbar, et al. Expires July 31, 2020 [Page 2]
Internet-Draft BGP Usage for SDWAN January 31, 2020
3.4. Scenario #3: SDWAN WAN ports to MPLS VPN and the Internet13
4. BGP Walk Through..............................................15
4.1. BGP Walk Through for Homogeneous SDWAN...................15
4.2. BGP Walk Through for Application Flow Based Segmentation.17
4.3. Client Service Provisioning Model........................18
4.4. WAN Ports Provisioning Model.............................19
4.5. Why BGP as Control Plane for SDWAN?......................19
5. SDWAN Traffic Forwarding Walk Through.........................20
Show full document text