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

Jeff Tantsura <jefftant.ietf@gmail.com> Tue, 10 July 2018 14:11 UTC

Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DE40130FB7; Tue, 10 Jul 2018 07:11:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.008
X-Spam-Level:
X-Spam-Status: No, score=-0.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FciZa-iZyYDw; Tue, 10 Jul 2018 07:11:05 -0700 (PDT)
Received: from mail-pl0-x244.google.com (mail-pl0-x244.google.com [IPv6:2607:f8b0:400e:c01::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45B84130FB1; Tue, 10 Jul 2018 07:11:05 -0700 (PDT)
Received: by mail-pl0-x244.google.com with SMTP id k1-v6so7679137plt.2; Tue, 10 Jul 2018 07:11:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version; bh=FYttjXAcPeQPOoRhRmjlx0XRkUiZOremkwZsLbpug14=; b=Mg7nvpNjm2kUHfj4Le+OGu41I0wfAuYWofQbRs+mmgrDfxIGDEM+zo6HH+nA2mCwFc Tyuf2pvasGyi6MGcmhjr5d8rgdUaumv/pbwT+FFyO4s2yXL6+1CqGuqTsjRuzu1WRJwZ 8eTX63kTM9jtYCcdy7Hlh9xif0zOtWH/14N26hHQKH1LjUf8pDX58qAa7Mk0ZCy3lbci tSSF9orWt0G9/3qGMVhbee9rhz+zNP7tMAZGHfJ+Alxw+IOkCsmptwZhpNOqrKilD0if kHiJNbb5y1UwPOq2qHFCv3638E3BjCMqSd6QLm8M0uENTuHAUI1LtcclVvOW5Rdojpr2 jQNA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version; bh=FYttjXAcPeQPOoRhRmjlx0XRkUiZOremkwZsLbpug14=; b=GJwBhY9qrkfwbmAkYL5quCak5zr2a/bKZ+otIelJPf/mw4ShdFI1oghx0TXyCDN6Hq 1yUdXP4rx3/LZVpRLJwJhLvXYsnPFUH1/8ys3qdoBMxAWu9Q4jwI7jnJXTDgChSOurgb QTrQ4nFmSJYbMY4IiGj9WYaJBFuKqHan33608mxYitWny+BcTcW4MoSxMxIhAD3kOlVi LLo09VES5iMdM0fCXoyhEIRE2wGcbUANTHzQHpiRXB3f2HfZ59uOtGvB2fmYh14BZCA1 gSf6Gitut0Yn9e8Ck0Z89/9OG56GCfyQRbsTqVLboqEYqhZqE/oegWIk3xEZR8nQbwO+ f+DA==
X-Gm-Message-State: APt69E0RG5fUmyb9OHW5AaJUtrKjs70uiOOrah5L7T+Z7TNO6sq9qmnM ID7u82b1t+sF4+KJw3SayNg=
X-Google-Smtp-Source: AAOMgpePuEKK/ktZ1QyE6TA51/qyUhH1oz3rt5k9dPFFCq1eggp+rGwWKKzNdOFiVlCmQuh9JmAjnw==
X-Received: by 2002:a17:902:5a4f:: with SMTP id f15-v6mr24906760plm.253.1531231864820; Tue, 10 Jul 2018 07:11:04 -0700 (PDT)
Received: from [192.168.1.16] ([2601:647:5801:7388:8d21:3de3:5d6d:fe02]) by smtp.gmail.com with ESMTPSA id q87-v6sm31549209pfa.180.2018.07.10.07.11.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Jul 2018 07:11:03 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/10.e.1.180613
Date: Tue, 10 Jul 2018 07:11:02 -0700
Subject: Re: [bess] comments and suggestions to draft-rosen-bess-secure-l3vpn-01
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: "UTTARO, JAMES" <ju1738@att.com>, Ron Bonica <rbonica@juniper.net>
CC: "bess@ietf.org" <bess@ietf.org>, RTGWG <rtgwg@ietf.org>, Eric Rosen <erosen@juniper.net>, Robert Raszuk <robert@raszuk.net>, Linda Dunbar <linda.dunbar@huawei.com>
Message-ID: <866880B0-0893-4E17-AF35-7CBB17845567@gmail.com>
Thread-Topic: [bess] comments and suggestions to draft-rosen-bess-secure-l3vpn-01
References: <4A95BA014132FF49AE685FAB4B9F17F66B07E161@sjceml521-mbs.china.huawei.com> <DM2PR05MB4485047CBE1ABF17FBE7083AE470@DM2PR05MB448.namprd05.prod.outlook.com> <4A95BA014132FF49AE685FAB4B9F17F66B07EB23@sjceml521-mbs.china.huawei.com> <CA+b+ERnwvYF4JdoiHhPPBYds-Tm9EPyZm6vPLdscjNtKhqTY4A@mail.gmail.com> <49131D01-708D-4A17-9521-F0DEA6891FC9@gmail.com> <4A95BA014132FF49AE685FAB4B9F17F66B07EDB4@sjceml521-mbs.china.huawei.com> <DM2PR05MB448D2B060B09D4275A9BC6AAE470@DM2PR05MB448.namprd05.prod.outlook.com> <14EDAB4B-1023-4084-93CC-C1C6AA36C081@gmail.com> <B17A6910EEDD1F45980687268941550F3676A366@MISOUT7MSGUSRCD.ITServices.sbc.com>
In-Reply-To: <B17A6910EEDD1F45980687268941550F3676A366@MISOUT7MSGUSRCD.ITServices.sbc.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3614051463_753509626"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/ubybFE3X-kNyrgEbObIr-K1JqXw>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2018 14:11:14 -0000

Hi Jim,

 

This is a general statement applicable to overall SD-WAN effort.

 

Cheers,

Jeff

 

From: "UTTARO, JAMES" <ju1738@att.com>
Date: Tuesday, July 10, 2018 at 05:22
To: Jeff Tantsura <jefftant.ietf@gmail.com>om>, Ron Bonica <rbonica@juniper.net>
Cc: "bess@ietf.org" <bess@ietf.org>rg>, RTGWG <rtgwg@ietf.org>rg>, Eric Rosen <erosen@juniper.net>et>, Robert Raszuk <robert@raszuk.net>et>, Linda Dunbar <linda.dunbar@huawei.com>
Subject: RE: [bess] comments and suggestions to draft-rosen-bess-secure-l3vpn-01

 

Jeff,

 

                Comments In-Line..

 

Thanks,

                Jim Uttaro

 

From: BESS [mailto:bess-bounces@ietf.org] On Behalf Of Jeff Tantsura
Sent: Friday, July 06, 2018 8:16 PM
To: Ron Bonica <rbonica@juniper.net>
Cc: bess@ietf.org; RTGWG <rtgwg@ietf.org>rg>; Eric Rosen <erosen@juniper.net>et>; Robert Raszuk <robert@raszuk.net>et>; Linda Dunbar <linda.dunbar@huawei.com>
Subject: Re: [bess] comments and suggestions to draft-rosen-bess-secure-l3vpn-01

 

There are also many companies using EVPN as the control plane.

It is important to find a “golden middle” where on one side we achieve interoperability but on another don’t hinder the innovation in that, fast growing space.

[Jim U>] Is this specific to inter-operability with secure-l3vpn-01 or intended as a general statement in re interoperability with the 2547 ?

Data planes are a jungle and would not be standardized any time soon.

However - an abstraction on top would be very useful.

 

Regards,

Jeff


On Jul 6, 2018, at 14:23, Ron Bonica <rbonica@juniper.net> wrote:

+1

 

Let’s follow up on this discussion in Montreal.

 

From: Linda Dunbar <linda.dunbar@huawei.com> 
Sent: Friday, July 6, 2018 4:33 PM
To: Jeff Tantsura <jefftant.ietf@gmail.com>om>; Robert Raszuk <robert@raszuk.net>
Cc: Ron Bonica <rbonica@juniper.net>et>; RTGWG <rtgwg@ietf.org>rg>; Eric Rosen <erosen@juniper.net>et>; bess@ietf.org
Subject: RE: [bess] comments and suggestions to draft-rosen-bess-secure-l3vpn-01

 

Jess, 

 

Great Action! There are much more than the Data modeling. 

A lot to be done in Control Plane. Many SD-WAN deployment (ours included) use NHRP/DMVPN/DSPVN to manage routes via internet. But NHRP being developed decades ago (for ATM) just doesn’t scale to support Managed Overlay network of 100s or 1000s CPEs. 

 

Linda

 

From: BESS [mailto:bess-bounces@ietf.org] On Behalf Of Jeff Tantsura
Sent: Friday, July 06, 2018 3:20 PM
To: Robert Raszuk <robert@raszuk.net>
Cc: Ron Bonica <rbonica@juniper.net>et>; RTGWG <rtgwg@ietf.org>rg>; Eric Rosen <erosen@juniper.net>et>; bess@ietf.org; Linda Dunbar <linda.dunbar@huawei.com>
Subject: Re: [bess] comments and suggestions to draft-rosen-bess-secure-l3vpn-01

 

Robert/Linda,

 

RTGWG chairs have been thinking of starting SD-WAN discussion in RTGWG.

Service data modeling(data modeling in general)is an obvious candidate (at ONUG we started, there’s some early effort, but IETF help is needed).

Control plane interworking is another interesting topic.

Please bring your ideas, I’m still working on agenda

 

Regards,

Jeff


On Jul 6, 2018, at 13:12, Robert Raszuk <robert@raszuk.net> wrote:

Hi Linda,

 

What you are expressing is very clear and in fact happens today on any good SD-WAN controller. 

 

But in the context of this discussion are you bringing it here to suggest that draft-rosen-bess-secure-l3vpn should have such functionality build in ? 

 

Personally I don't think it really belongs in this draft as perfect sweet spot for it still IMHO resides on a SD-WAN controller. Pushing all that logic into BGP may be a bit excessive ...

 

Many thx,

R.

 

 

On Fri, Jul 6, 2018 at 9:32 PM, Linda Dunbar <linda.dunbar@huawei..com> wrote:

Ron, 

 

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 [mailto:rbonica@juniper.net] 
Sent: Friday, July 06, 2018 1:25 PM
To: Linda Dunbar <linda.dunbar@huawei.com>om>; Eric Rosen <erosen@juniper.net>et>; bess@ietf.org
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?

 

                                                            Ron

 

 

From: Linda Dunbar <linda.dunbar@huawei.com> 
Sent: Thursday, July 5, 2018 11:53 AM
To: Eric Rosen <erosen@juniper.net>et>; Ron Bonica <rbonica@juniper.net>et>; bess@ietf.org
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: https://datatracker.ietf.org/doc/draft-dm-net2cloud-gap-analysis/

Appreciate your comments and suggestions to our gap analysis. 

 

 

Thanks, Linda Dunbar

 


_______________________________________________
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

 

_______________________________________________
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess