Re: [bess] comments and suggestions to draft-rosen-bess-secure-l3vpn-01

Linda Dunbar <> Fri, 06 July 2018 19:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 45DCA130EF3 for <>; Fri, 6 Jul 2018 12:33:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.209
X-Spam-Status: No, score=-2.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DC_PNG_UNO_LARGO=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id THKzVtDelZuH for <>; Fri, 6 Jul 2018 12:32:59 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 739B3130E07 for <>; Fri, 6 Jul 2018 12:32:58 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTP id E2B1EE5752DBC for <>; Fri, 6 Jul 2018 20:32:53 +0100 (IST)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.382.0; Fri, 6 Jul 2018 20:32:54 +0100
Received: from ([]) by ([]) with mapi id 14.03.0382.000; Fri, 6 Jul 2018 12:32:47 -0700
From: Linda Dunbar <>
To: Ron Bonica <>, Eric Rosen <>, "" <>
Thread-Topic: comments and suggestions to draft-rosen-bess-secure-l3vpn-01
Thread-Index: AdQUd6UGClvRk5FQRUGF9YyejctT/AA3qsZwAAIU+0A=
Date: Fri, 06 Jul 2018 19:32:47 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
x-originating-ip: []
Content-Type: multipart/related; boundary="_004_4A95BA014132FF49AE685FAB4B9F17F66B07EB23sjceml521mbschi_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [bess] comments and suggestions to draft-rosen-bess-secure-l3vpn-01
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 06 Jul 2018 19:33:03 -0000


This is referring to a Managed Overlay WAN services with many CPEs (large scale SD-WAN) and where

-        there are many CPEs at each location and multiple WAN ports on each CPE

-        SD-WAN Controller needs to detour a path between Site -A-&  Site-B via another site (e.g. Site-C) for reasons like Performance, Regulatory,  or others. Instead of designating to specific CPE of the site-C.

It is preferable to partition CPEs to clusters, as shown in the figure below:


Do I explain well? If not, can we talk face to face in Montreal?

Thanks, Linda Dunbar

From: Ron Bonica []
Sent: Friday, July 06, 2018 1:25 PM
To: Linda Dunbar <>; Eric Rosen <>;
Subject: RE: comments and suggestions to draft-rosen-bess-secure-l3vpn-01

Hi Linda,

I'm not sure that I understand what you mean when you say, "aggregate CPE-based VPN routes with internet routes that interconnect the CPEs". Could you elaborate?


From: Linda Dunbar <<>>
Sent: Thursday, July 5, 2018 11:53 AM
To: Eric Rosen <<>>; Ron Bonica <<>>;<>
Subject: comments and suggestions to draft-rosen-bess-secure-l3vpn-01

Eric and Ron,

We think that the method described in your draft is useful for CPE based EVPN, especially for SD-WAN between CPEs.
But, it misses some aspects to aggregate CPE-based VPN routes with internet routes that interconnect the CPEs.

Question to you: Would you like to expand your draft to cover the scenario of aggregating CPE-based VPN routes with internet routes that interconnect the CPEs?

If yes, we think the following areas are needed:

*        For RR communication with CPE, this draft only mentioned IPSEC. Are there any reasons that TLS/DTLS are not added?

*        The draft assumes that C-PE "register" with the RR. But it doesn't say how. Should "NHRP" (modified version) be considered?

*        It assumes that C-PE and RR are connected by IPsec tunnel. With zero touch provisioning, we need an automatic way to synchronize the IPSec SA between C-PE and RR. The draft assumes:

p  A C-PE must also be provisioned with whatever additional information is needed in order to set up an IPsec SA with each of the red RRs

*        IPsec requires periodic refreshment of the keys. How to synchronize the refreshment among multiple nodes?

*        IPsec usually only send configuration parameters to two end points and let the two end points to negotiate the KEY. Now we assume that RR is responsible for creating the KEY for all end points. When one end point is confiscated, all other connections are impacted.

If you are open to expand your draft to cover SD-WAN, we can help providing the sections to address the bullets mentioned above.

We have a draft analyzing the technological gaps when using SD-WAN to interconnect workloads & apps hosted in various locations:<>
Appreciate your comments and suggestions to our gap analysis.

Thanks, Linda Dunbar