IETF Logo Mail Archive

Re: [Idr] [bess] Comparing using the SD-WAN Overlay SAFI specified by draft-dunbar-idr-bgp-sdwan-overlay-ext with the EVPN approach described by draft-sajassi-bess-secure-evpn-00

"Ali Sajassi (sajassi)" <sajassi@cisco.com> Wed, 31 October 2018 05:04 UTC

Return-Path: <sajassi@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 866DC124D68; Tue, 30 Oct 2018 22:04:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 TdU9K5RAXQ31; Tue, 30 Oct 2018 22:04:17 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6092124C04; Tue, 30 Oct 2018 22:04:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14116; q=dns/txt; s=iport; t=1540962256; x=1542171856; h=from:to:subject:date:message-id:mime-version; bh=+Do7IXGLVFHjILtwjuqzgkYw+LZKzHtCa84ep+T/fWs=; b=iVXLj1SU+gU4GesKW0PGgxuivF+EJTBVZER8V3Yp5cA4Mc9EWW2Petyl Rz3a6iWs2jqeLnpXxENB4mTYka9Ccq+dA/mHZ6jyIaG1NwrFpt89wy1Hm aprCIuHlT9to6Qc+LrV17ssy6unYhQAUq328svaykxExehVkN0qNpsUNo A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A+AAAbN9lb/51dJa1kHAEBAQQBAQcEAQGBUgYBAQsBgQ1IL2Z/KAqDbJQxgWglkVWFS4F6CwEBJYRHGYMNIjUMDQEDAQECAQECbRwMhToBBiNoAQgRAwECJAcCBDAdCgQBEhuDBgGBHWQPqAuBLoQ/QIUqBYtnF4IAgREnDBOCHi6DGwIDAYF9gmQxgiYCjlCGI4lLVAkChmmDIoZ7GIFTiBOGY4x3igoCERSBJh4BNoFVcBVlAYJBgk+ISoU+b4sqgR8BAQ
X-IronPort-AV: E=Sophos;i="5.54,447,1534809600"; d="scan'208,217";a="193570062"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 31 Oct 2018 05:04:15 +0000
Received: from XCH-RTP-005.cisco.com (xch-rtp-005.cisco.com [64.101.220.145]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id w9V54Fr7031562 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 31 Oct 2018 05:04:15 GMT
Received: from xch-rtp-005.cisco.com (64.101.220.145) by XCH-RTP-005.cisco.com (64.101.220.145) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 31 Oct 2018 01:04:14 -0400
Received: from xch-rtp-005.cisco.com ([64.101.220.145]) by XCH-RTP-005.cisco.com ([64.101.220.145]) with mapi id 15.00.1395.000; Wed, 31 Oct 2018 01:04:14 -0400
From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
To: Linda Dunbar <linda.dunbar@huawei.com>, "idr@ietf.org" <idr@ietf.org>, "bess@ietf.org" <bess@ietf.org>
Thread-Topic: [bess] Comparing using the SD-WAN Overlay SAFI specified by draft-dunbar-idr-bgp-sdwan-overlay-ext with the EVPN approach described by draft-sajassi-bess-secure-evpn-00
Thread-Index: AQHUcNcrmdLiJU5oSUqEW64fomgVyA==
Date: Wed, 31 Oct 2018 05:04:14 +0000
Message-ID: <F7356C79-E6D1-4910-9929-0F0270CF1FA8@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.3.181015
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.41.94]
Content-Type: multipart/alternative; boundary="_000_F7356C79E6D1491099290F0270CF1FA8ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 64.101.220.145, xch-rtp-005.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/54bAtfSkkxEtmukh7jl-wKMFR40>
Subject: Re: [Idr] [bess] Comparing using the SD-WAN Overlay SAFI specified by draft-dunbar-idr-bgp-sdwan-overlay-ext with the EVPN approach described by draft-sajassi-bess-secure-evpn-00
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Oct 2018 05:04:19 -0000

Hi Linda,

I haven’t read your draft yet. I am traveling now but will plan to read your draft over next couple of days and respond to your questions.

Cheers,
Ali

From: BESS <bess-bounces@ietf.org> on behalf of Linda Dunbar <linda.dunbar@huawei.com>
Date: Tuesday, October 30, 2018 at 9:19 AM
To: "idr@ietf.org" <idr@ietf.org>, "bess@ietf.org" <bess@ietf.org>
Subject: [bess] Comparing using the SD-WAN Overlay SAFI specified by draft-dunbar-idr-bgp-sdwan-overlay-ext with the EVPN approach described by draft-sajassi-bess-secure-evpn-00

IDR group, BESS group,

https://datatracker.ietf.org/doc/draft-dunbar-idr-bgp-sdwan-overlay-ext/ specifies a new BGP SAFI (=74) 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.

draft-sajassi-bess-secure-evpn-00 describes an EVPN solution for PE nodes to exchange key and policy to create private pair-wise IPsec Security Associations without IKEv2 point-to-point signaling or any other direct peer-to-peer session establishment messages.

I think those two solutions are not conflicting with each other. Actually they are compliment to each other to some degree. For example,

  *   the Re-key mechanism described by draft-sajassi-bess-secure-evpn-00 can be utilized by draft-dunbar-idr-bgp-sdwan-overlay-ext
  *   The SD-WAN Overlay SAFI can be useful to simplify the process on RR to re-distribute the Tunnel End properties to authorized peers.
  *   When SD-WAN edge nodes use private address, or no IP address, NAT properties for the end points distribution described draft-dunbar-idr-bgp-sdwan-overlay-ext is necessary.
  *   The secure channel between SD-WAN edge nodes and RR described by draft-dunbar-idr-bgp-sdwan-overlay-ext is necessary.

Any thoughts?

Thank you very much.

Linda Dunbar

v2.23.0 | Report a Bug | By Email