Integrated Routing and Bridging in EVPN
draft-ietf-bess-evpn-inter-subnet-forwarding-13
Document | Type | Active Internet-Draft (bess WG) | |
---|---|---|---|
Authors | Ali Sajassi , Samer Salam , Samir Thoria , John Drake , Jorge Rabadan | ||
Last updated | 2021-02-10 | ||
Replaces | draft-sajassi-l2vpn-evpn-inter-subnet-forwarding | ||
Stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | Proposed Standard | ||
Formats | plain text pdf htmlized (tools) htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Zhaohui Zhang | ||
Shepherd write-up | Show (last changed 2020-07-07) | ||
IESG | IESG state | IESG Evaluation::AD Followup | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Yes | ||
Telechat date |
Has a DISCUSS. Needs 3 more YES or NO OBJECTION positions to pass. |
||
Responsible AD | Martin Vigoureux | ||
Send notices to | "Zhaohui Zhang" <zzhang@juniper.net> | ||
IANA | IANA review state | Version Changed - Review Needed |
BESS WorkGroup A. Sajassi Internet-Draft S. Salam Intended status: Standards Track S. Thoria Expires: August 14, 2021 Cisco Systems J. Drake Juniper J. Rabadan Nokia February 10, 2021 Integrated Routing and Bridging in EVPN draft-ietf-bess-evpn-inter-subnet-forwarding-13 Abstract Ethernet VPN (EVPN) provides an extensible and flexible multi-homing VPN solution over an MPLS/IP network for intra-subnet connectivity among Tenant Systems and End Devices that can be physical or virtual. However, there are scenarios for which there is a need for a dynamic and efficient inter-subnet connectivity among these Tenant Systems and End Devices while maintaining the multi-homing capabilities of EVPN. This document describes an Integrated Routing and Bridging (IRB) solution based on EVPN to address such requirements. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119] and RFC 8174 [RFC8174] when, and only when, they appear in all capitals, as shown here. 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 14, 2021 [Page 1] Internet-Draft Integrated Routing and Bridging in EVPN February 2021 This Internet-Draft will expire on August 14, 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. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 3. EVPN PE Model for IRB Operation . . . . . . . . . . . . . . . 6 4. Symmetric and Asymmetric IRB . . . . . . . . . . . . . . . . 7 4.1. IRB Interface and its MAC and IP addresses . . . . . . . 10 5. Symmetric IRB Procedures . . . . . . . . . . . . . . . . . . 12 5.1. Control Plane - Advertising PE . . . . . . . . . . . . . 12 5.2. Control Plane - Receiving PE . . . . . . . . . . . . . . 13 5.3. Subnet route advertisement . . . . . . . . . . . . . . . 14 5.4. Data Plane - Ingress PE . . . . . . . . . . . . . . . . . 15 5.5. Data Plane - Egress PE . . . . . . . . . . . . . . . . . 15 6. Asymmetric IRB Procedures . . . . . . . . . . . . . . . . . . 16 6.1. Control Plane - Advertising PE . . . . . . . . . . . . . 16 6.2. Control Plane - Receiving PE . . . . . . . . . . . . . . 17 6.3. Data Plane - Ingress PE . . . . . . . . . . . . . . . . . 18 6.4. Data Plane - Egress PE . . . . . . . . . . . . . . . . . 18 7. Mobility Procedure . . . . . . . . . . . . . . . . . . . . . 19 7.1. Initiating a gratutious ARP upon a Move . . . . . . . . . 20 7.2. Sending Data Traffic without an ARP Request . . . . . . . 21 7.3. Silent Host . . . . . . . . . . . . . . . . . . . . . . . 23 8. BGP Encoding . . . . . . . . . . . . . . . . . . . . . . . . 23 8.1. Router's MAC Extended Community . . . . . . . . . . . . . 24 9. Operational Models for Symmetric Inter-Subnet Forwarding . . 24 9.1. IRB forwarding on NVEs for Tenant Systems . . . . . . . . 24Show full document text