Operational Aspects of Proxy-ARP/ND in EVPN Networks
draft-ietf-bess-evpn-proxy-arp-nd-09

Document Type Active Internet-Draft (bess WG)
Authors Jorge Rabadan  , Senthil Sathappan  , Kiran Nagaraj  , Greg Hankins  , Thomas King 
Last updated 2020-10-12
Replaces draft-snr-bess-evpn-proxy-arp-nd
Stream IETF
Intended RFC status Informational
Formats plain text pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Matthew Bocci
Shepherd write-up Show (last changed 2019-07-09)
IESG IESG state AD Evaluation::AD Followup
Consensus Boilerplate Yes
Telechat date
Responsible AD Martin Vigoureux
Send notices to Matthew Bocci <matthew.bocci@nokia.com>
BESS Workgroup                                           J. Rabadan, Ed.
Internet-Draft                                              S. Sathappan
Updates: RFC7432 (if approved)                                K. Nagaraj
Intended status: Standards Track                              G. Hankins
Expires: April 12, 2021                                            Nokia
                                                                 T. King
                                                                  DE-CIX
                                                         October 9, 2020

          Operational Aspects of Proxy-ARP/ND in EVPN Networks
                  draft-ietf-bess-evpn-proxy-arp-nd-09

Abstract

   The EVPN MAC/IP Advertisement route can optionally carry IPv4 and
   IPv6 addresses associated with a MAC address.  Remote PEs importing
   those routes in the same Broadcast Domain (BD) can use this
   information to reply locally (act as proxy) to IPv4 ARP requests and
   IPv6 Neighbor Solicitation messages (or 'unicast-forward' them to the
   owner of the MAC) and reduce/suppress the flooding produced by the
   Address Resolution procedure.  This EVPN capability is extremely
   useful in Internet Exchange Points (IXPs) and Data Centers (DCs) with
   large BDs, where the amount of ARP/ND flooded traffic causes issues
   on connected routers and CEs.  This document describes the EVPN
   Proxy-ARP/ND function augmented by the capability of the ARP/ND
   Extended Community, which together help IXPs and other operators to
   deal with the issues derived from Address Resolution in large BDs.

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 April 12, 2021.

Rabadan, et al.          Expires April 12, 2021                 [Page 1]
Internet-Draft              EVPN Proxy-ARP/ND               October 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
   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
     2.1.  The DC Use-Case . . . . . . . . . . . . . . . . . . . . .   5
     2.2.  The IXP Use-Case  . . . . . . . . . . . . . . . . . . . .   5
   3.  Solution Requirements . . . . . . . . . . . . . . . . . . . .   6
   4.  Solution Description  . . . . . . . . . . . . . . . . . . . .   7
     4.1.  Learning Sub-Function . . . . . . . . . . . . . . . . . .   9
       4.1.1.  Proxy-ND and the NA Flags . . . . . . . . . . . . . .  10
     4.2.  Reply Sub-Function  . . . . . . . . . . . . . . . . . . .  11
     4.3.  Unicast-forward Sub-Function  . . . . . . . . . . . . . .  12
     4.4.  Maintenance Sub-Function  . . . . . . . . . . . . . . . .  13
     4.5.  Flooding (to Remote PEs) Reduction/Suppression  . . . . .  14
     4.6.  Duplicate IP Detection  . . . . . . . . . . . . . . . . .  15
   5.  Solution Benefits . . . . . . . . . . . . . . . . . . . . . .  17
   6.  Deployment Scenarios  . . . . . . . . . . . . . . . . . . . .  17
     6.1.  All Dynamic Learning  . . . . . . . . . . . . . . . . . .  17
     6.2.  Dynamic Learning with Proxy-ARP/ND  . . . . . . . . . . .  18
     6.3.  Hybrid Dynamic Learning and Static Provisioning with
           Proxy-ARP/ND  . . . . . . . . . . . . . . . . . . . . . .  18
     6.4.  All Static Provisioning with Proxy-ARP/ND . . . . . . . .  18
     6.5.  Deployment Scenarios in IXPs  . . . . . . . . . . . . . .  19
     6.6.  Deployment Scenarios in DCs . . . . . . . . . . . . . . .  20
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  20
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  21
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  21
Show full document text