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

[Linda Dunbar <[e-mail]>]

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: https://datatracker.ietf.org/doc/draft-dm-net2cloud-gap-analysis/
Appreciate your comments and suggestions to our gap analysis.


Thanks, Linda Dunbar