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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-07-06
Replaced by draft-ietf-bess-evpn-proxy-arp-nd
Stream (None)
Intended RFC status (None)
Formats pdf 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 Workgroup                                           J. Rabadan, Ed.
Internet Draft                                              S. Sathappan
                                                              K. Nagaraj
Intended status: Informational                             W. Henderickx
                                                              G. Hankins
                                                          Alcatel-Lucent

                                                                 T. King
                                                               D. Melzer
                                                                  DE-CIX

Expires: January 7, 2016                                    July 6, 2015

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

Abstract

   The MAC/IP Advertisement route specified in [RFC7432] can optionally
   carry IPv4 and IPv6 addresses associated with a MAC address. Remote
   PEs can use this information to reply locally (act as proxy) to IPv4
   ARP requests and IPv6 Neighbor Solicitation messages 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 broadcast
   domains, where the amount of ARP/ND flooded traffic causes issues on
   routers and CEs, as explained in [RFC6820]. This document describes
   how the [RFC7432] EVPN proxy-ARP/ND function may be implemented to
   help IXPs and other operators deal with the issues derived from
   Address Resolution in large broadcast domains.

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), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

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

Sathappan-Nagaraj-Rabadan et al.Expires January 7, 2016         [Page 1]
Internet-Draft             EVPN Proxy-ARP/ND                July 6, 2015

   of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on January 7, 2015.

Copyright Notice

   Copyright (c) 2015 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
   (http://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 . . . . . . . . . . . . . . . . . . . . . .  4
     2.2. The IXP Use-Case  . . . . . . . . . . . . . . . . . . . . .  4
   3. Solution Requirements . . . . . . . . . . . . . . . . . . . . .  5
   4. Solution Description  . . . . . . . . . . . . . . . . . . . . .  6
     4.1. Learning Sub-Function . . . . . . . . . . . . . . . . . . .  8
       4.1.1. Proxy-ND and the NA Flags . . . . . . . . . . . . . . . 10
     4.2. Reply Sub-Function  . . . . . . . . . . . . . . . . . . . . 11
     4.3. Maintenance Sub-Function  . . . . . . . . . . . . . . . . . 12
     4.4. Flooding (to Remote PEs) Reduction/Suppression  . . . . . . 13
     4.5. Duplicate IP Detection  . . . . . . . . . . . . . . . . . . 13
   5. Solution Benefits . . . . . . . . . . . . . . . . . . . . . . . 15
   6. Deployment Scenarios  . . . . . . . . . . . . . . . . . . . . . 16
     6.1. All Dynamic Learning  . . . . . . . . . . . . . . . . . . . 16
     6.2. Dynamic Learning with Proxy-ARP/ND  . . . . . . . . . . . . 16
     6.3. Hybrid Dynamic Learning and Static Provisioning with 
          Proxy-ARP/ND  . . . . . . . . . . . . . . . . . . . . . . . 16
     6.4 All Static Provisioning with Proxy-ARP/ND  . . . . . . . . . 17
     6.5 Deployment Scenarios in IXPs . . . . . . . . . . . . . . . . 17
     6.6 Deployment Scenarios in DCs  . . . . . . . . . . . . . . . . 18
Show full document text