ARP/ND Synching And IP Aliasing without IRB
draft-wang-bess-evpn-arp-nd-synch-without-irb-05

Document Type Active Internet-Draft (individual)
Last updated 2020-05-10
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
BESS WG                                                          Y. Wang
Internet-Draft                                                  Z. Zhang
Intended status: Standards Track                         ZTE Corporation
Expires: November 11, 2020                                  May 10, 2020

              ARP/ND Synching And IP Aliasing without IRB
            draft-wang-bess-evpn-arp-nd-synch-without-irb-05

Abstract

   This document proposes an extension to [RFC7432] and
   [I-D.sajassi-bess-evpn-ip-aliasing] to do ARP synchronizing and IP
   aliasing for Layer 3 routes that is needed for EVPN signalled L3VPN
   to build a complete IP ECMP.  The phrase "EVPN signalled L3VPN" means
   that there may be no MAC-VRF or IRB interface in the use case.  When
   there are no MAC-VRF or IRB interface, EVPN signalled L3VPN is also
   called as "pure L3VPN instance" which is a different usecase from
   [I-D.sajassi-bess-evpn-ip-aliasing].

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."

   This Internet-Draft will expire on November 11, 2020.

Copyright Notice

   Copyright (c) 2020 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

Wang & Zhang            Expires November 11, 2020               [Page 1]
Internet-Draft          EVPN ARP/ND Synch no IRB                May 2020

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  ARP/ND Synching and IP Aliasing . . . . . . . . . . . . . . .   4
     2.1.  Constructing MAC/IP Advertisement Route . . . . . . . . .   5
     2.2.  Constructing IP-AD/EVI Route  . . . . . . . . . . . . . .   6
     2.3.  Constructing IP-AD/ES Route . . . . . . . . . . . . . . .   6
   3.  Fast Convergence for Routed Traffic . . . . . . . . . . . . .   7
   4.  Determining Reach-ability to Unicast IP Addresses . . . . . .   7
   5.  Forwarding Unicast Packets  . . . . . . . . . . . . . . . . .   7
   6.  EVPN signalled L3VPN  . . . . . . . . . . . . . . . . . . . .   8
     6.1.  RT-5E Advertisement on Distributed L3 GW  . . . . . . . .   8
     6.2.  Centerlized RT-5G Advertisement for Distributed L3
           Forwarding  . . . . . . . . . . . . . . . . . . . . . . .   8
       6.2.1.  Centerlized CE-BGP  . . . . . . . . . . . . . . . . .   9
       6.2.2.  RT-2E Advertisement from PE1/PE2 to PE3 . . . . . . .  10
       6.2.3.  RT-5G Advertisement from PE3 to PE1/PE2 . . . . . . .  10
       6.2.4.  RT-2E Advertisement between PE1 and PE2 . . . . . . .  11
       6.2.5.  Egress ESI Link Protection between PE1 and PE2  . . .  11
       6.2.6.  Comparing with Distributed RT-5G Advertisement  . . .  11
       6.2.7.  Mass-Withdraw by EAD/ES Route . . . . . . . . . . . .  12
       6.2.8.  On the Failure of PE3 Node  . . . . . . . . . . . . .  12
       6.2.9.  Floating GW-IP between R1 and R2  . . . . . . . . . .  13
     6.3.  RT-5L Advertisement . . . . . . . . . . . . . . . . . . .  13
   7.  Load Balancing of Unicast Packets . . . . . . . . . . . . . .  13
   8.  Special Considerations for Single-Active ESI  . . . . . . . .  14
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   11. Normative References  . . . . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Introduction

   In [I-D.sajassi-bess-evpn-ip-aliasing], an extension to [RFC7432] to
   do aliasing for Layer 3 routes is proposed for symmetric IRB to build
   a complete IP ECMP.  But typically there may be both IRB
   interfaces(to do EVPN IRB per-MAC-VRF basis) and VRF- interfaces in
   the same IP-VRF instance.  It is necessary to apply the EVPN control-
Show full document text