Secure EVPN
draft-sajassi-bess-secure-evpn-04
BESS Working Group A. Sajassi, Ed.
Internet-Draft A. Banerjee
Intended status: Standards Track S. Thoria
Expires: August 26, 2021 Cisco
D. Carrel
Graphiant
B. Weis
Independent
J. Drake
Juniper Networks
February 22, 2021
Secure EVPN
draft-sajassi-bess-secure-evpn-04
Abstract
The applications of EVPN-based solutions ([RFC7432] and [RFC8365])
have become pervasive in Data Center, Service Provider, and
Enterprise segments. It is being used for fabric overlays and inter-
site connectivity in the Data Center market segment, for Layer-2,
Layer-3, and IRB VPN services in the Service Provider market segment,
and for fabric overlay and WAN connectivity in Enterprise networks.
For Data Center and Enterprise applications, there is a need to
provide inter-site and WAN connectivity over public Internet in a
secured manner with same level of privacy, integrity, and
authentication for tenant's traffic as IPsec tunneling using IKEv2.
This document presents a solution where BGP point-to-multipoint
signaling is leveraged for key and policy exchange among PE devices
to create private pair-wise IPsec Security Associations without IKEv2
point-to-point signaling or any other direct peer-to-peer session
establishment messages.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
Sajassi, et al. Expires August 26, 2021 [Page 1]
Internet-Draft Secure EVPN February 2021
This Internet-Draft will expire on August 26, 2021.
Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 5
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1. Tenant's Layer-2 and Layer-3 data and control traffic . . 7
3.2. Tenant's Unicast and Multicast Data Protection . . . . . 7
3.3. P2MP Signaling for SA setup and Maintenance . . . . . . . 7
3.4. Granularity of Security Association Tunnels . . . . . . . 7
3.5. Support for Policy and DH-Group List . . . . . . . . . . 8
4. SA and Key Management . . . . . . . . . . . . . . . . . . . . 8
4.1. Generating Initial IPsec SAs . . . . . . . . . . . . . . 8
4.2. Rekey of IPsec SAs . . . . . . . . . . . . . . . . . . . 10
4.2.1. Single IPSec Device Rekey . . . . . . . . . . . . . . 11
4.2.2. Multiple IPSec Device Rekey . . . . . . . . . . . . . 13
5. IPsec Database Generation . . . . . . . . . . . . . . . . . . 16
5.1. The Security Policy Database (SPD) . . . . . . . . . . . 16
5.2. Security Association Database (SAD) . . . . . . . . . . . 16
5.2.1. Generating Keying Material for IPsec SAs . . . . . . 16
5.2.1.1. g^ir . . . . . . . . . . . . . . . . . . . . . . 16
5.2.1.2. Nonces . . . . . . . . . . . . . . . . . . . . . 17
5.2.1.3. SPIs . . . . . . . . . . . . . . . . . . . . . . 17
Show full document text