Subject: [Idr] Seeking feedback to requesting a SD-WAN SAFI for advertising SD-WAN edge node’s capabilities: draft-dunbar-idr-bgp-sdwan-overlay-ext-00.txt

From: Linda Dunbar <[email-masked]>
Date: Wed, 24 Oct 2018 02:43:39 +0000

We are seeking feedback for requesting a new SD-WAN SAFI in order to advertise a SD-WAN edge node’s capabilities in establishing SD-WAN overlay tunnels with other SD-WAN nodes through third party untrusted networks. Details on why and what are described in our new draft: https://www.ietf.org/internet-drafts/draft-dunbar-idr-bgp-sdwan-overlay-ext-00.txt

We understand the complication of having a new SAFI.
But, the mechanisms described by [draft-ietf-idr-tunnel-encaps-10] cannot be effectively used for SD-WAN overlay network because a SD-WAN Tunnel needs to be established before data arrival. There is no Routes to be associated with the SD-WAN Tunnel.
There is a suggestion on using a “Fake Route” for a SD-WAN node to use [draft-ietf-idr-tunnel-encaps] to advertise its SD-WAN tunnel end-points properties. However, using “Fake Route” can create deployment complexity for large SD-WAN networks with many tunnels. For example, for a SD-WAN network with hundreds of nodes, with each node having many ports & many end-points to establish SD-WAN tunnels to their corresponding peers, the node would need many “fake addresses”. For large SD-WAN networks (such as has more than 10000 nodes), each node might need 10’s thousands of “fake addresses”, which is very difficult to manage and needs lots of configuration to get the nodes provisioned.

In addition, hosts/applications attached to SD-WAN edge nodes can belong to different tenants, requiring SD-WAN nodes to establish different tunnels to different SD-WAN nodes. As shown in the figure below, C1 node alone has to establish following SD-WAN tunnels:
•       two SD-WAN tunnels to C2: one for Tenant 1, another one for Tenant 2,
•       One SD-WAN tunnel to C3 for Tenant 1, and
•       two SD-WAN tunnels to C4: one for Tenant 1, another one for Tenant 2,

                                                     +----------+
                                            +--------+ Tenant 2 |
                                            |        +----------+
         +--------+                         |          +--------+
         | Tenant +--+                      |     +----| Tenant |
         | 1      |  |                      |     |    | 1      |
         +--------+  |    ................. |     |    +--------+
                     |  +-+-+           +-+-+     |
                     +--|C1 |---+   +---|C2 |-----+        +---------+
                        +-+-+   |   |   +---+        /-----+ Tenant 1|
                        / .    +-----+      .       /      +---------+
                       /  . +--| RR  |--+   .      /     +---------+
                      /   . |  +-----+   \  .     /------+ Tenant 3|
                     |    . |  Overlay    \ .    /       +---------+
                     |    . |  untrusted   +--+--+    +--------+
         +--------+  |    . |   Networks   | C4  |    | Tenant |
         | Tenant +--+    . |              |     |----| 2      |
         | 2      |       ..  \ +---+       +--+--+    +--------+
         +--------+       .....+C3 +..........+
                               +---+
                                 |
                                 |
                       =====================
                         |               |
                     +--------+      +--------+
                     | Tenant |      | Tenant |
                     | 2      |      | 3      |
                     +--------+      +--------+

Thank you very much.

Linda Dunbar

-----Original Message-----
From: [email-masked] [mailto:[email-masked]]
Sent: Sunday, October 21, 2018 8:41 AM
To: Linda Dunbar <[email-masked]>; Haoweiguo <[email-masked]>; Wanghaibo (Rainsword) <[email-masked]>; Linda Dunbar <[email-masked]>; Haoweiguo <[email-masked]>
Subject: New Version Notification for draft-dunbar-idr-bgp-sdwan-overlay-ext-00.txt

A new version of I-D, draft-dunbar-idr-bgp-sdwan-overlay-ext-00.txt
has been successfully submitted by Linda Dunbar and posted to the IETF repository.

Name:           draft-dunbar-idr-bgp-sdwan-overlay-ext
Revision:       00
Title:          BGP Extension for SDWAN Overlay Networks
Document date:  2018-10-19
Group:          Individual Submission
Pages:          16
URL:            https://www.ietf.org/internet-drafts/draft-dunbar-idr-bgp-sdwan-overlay-ext-00.txt
Status:         https://datatracker.ietf.org/doc/draft-dunbar-idr-bgp-sdwan-overlay-ext/
Htmlized:       https://tools.ietf.org/html/draft-dunbar-idr-bgp-sdwan-overlay-ext-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-dunbar-idr-bgp-sdwan-overlay-ext

Abstract:
   The document defines a new BGP SAFI with a new NLRI in order to
   advertise a SD-WAN edge node's capabilities in establishing SD-WAN
   overlay tunnels with other SD-WAN nodes through third party
   networks. The goal is for SD-WAN network to scale, enabling SD-WAN
   overlay tunnels among large number of SD-WAN nodes to be established
   with few provisioning needed.

   A "SD-WAN" tunnel refers to a point-to-point IPsec overlay path
   between two end-points that can aggregate multiple different types
   of underlay networks. An "end-point" is referring to a port on a SD-
   WAN node throughout this document.

   This document specifies new sub-TLVs for the SD-WAN Tunnel
   Encapsulation Attribute.

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat