[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
Linda Dunbar <linda.dunbar@huawei.com> Tue, 30 October 2018 16:19 UTC
Return-Path: <linda.dunbar@huawei.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 001A512F295; Tue, 30 Oct 2018 09:19:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 g48S3O4WPKxQ; Tue, 30 Oct 2018 09:19:00 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B45AC12D4EA; Tue, 30 Oct 2018 09:18:59 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 74383BB4E8F0B; Tue, 30 Oct 2018 16:18:54 +0000 (GMT)
Received: from SJCEML702-CHM.china.huawei.com (10.208.112.38) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 30 Oct 2018 16:18:55 +0000
Received: from SJCEML521-MBS.china.huawei.com ([169.254.2.103]) by SJCEML702-CHM.china.huawei.com ([169.254.4.237]) with mapi id 14.03.0415.000; Tue, 30 Oct 2018 09:18:52 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "idr@ietf.org" <idr@ietf.org>, "bess@ietf.org" <bess@ietf.org>
Thread-Topic: 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: AdRwaEzosOxE1xU3QRyQAjdOk3ofww==
Date: Tue, 30 Oct 2018 16:18:52 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F66B17F9DE@sjceml521-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.192.11.102]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F66B17F9DEsjceml521mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/Ii2QwCrYssU_PWPtXX6LVZm1fbA>
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
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Oct 2018 16:19:02 -0000
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
- [bess] Comparing using the SD-WAN Overlay SAFI sp… Linda Dunbar
- Re: [bess] Comparing using the SD-WAN Overlay SAF… Ali Sajassi (sajassi)
- Re: [bess] Comparing using the SD-WAN Overlay SAF… Linda Dunbar
- Re: [bess] Comparing using the SD-WAN Overlay SAF… Ali Sajassi (sajassi)
- Re: [bess] Comparing using the SD-WAN Overlay SAF… Ali Sajassi (sajassi)
- Re: [bess] Comparing using the SD-WAN Overlay SAF… Robert Raszuk
- Re: [bess] Comparing using the SD-WAN Overlay SAF… Linda Dunbar
- Re: [bess] [Idr] Comparing using the SD-WAN Overl… Rabadan, Jorge (Nokia - US/Mountain View)
- Re: [bess] Comparing using the SD-WAN Overlay SAF… Robert Raszuk