Propagation of ARP/ND Flags in EVPN
draft-ietf-bess-evpn-na-flags-04

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04

BESS Workgroup                                           J. Rabadan, Ed.
Internet Draft                                              S. Sathappan
                                                              K. Nagaraj
Intended status: Standards Track                                   Nokia

                                                                  W. Lin
                                                                 Juniper

Expires: January 4, 2020                                    July 3, 2019

                  Propagation of ARP/ND Flags in EVPN
                    draft-ietf-bess-evpn-na-flags-04

Abstract

   An EVPN MAC/IP Advertisement route can optionally carry an IPv4 or
   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. The information
   conveyed in the MAC/IP route may not be enough for the remote PE to
   reply to local ARP or ND requests. For example, if a PE learns an
   IPv6->MAC ND entry via EVPN, the PE would not know if that particular
   IPv6->MAC pair belongs to a host, a router or a host with an anycast
   address, as this information is not carried in the MAC/IP route
   advertisements. Similarly, other information relevant to the IP->MAC
   ARP/ND entries may be needed. This document defines an extended
   community that is advertised along with an EVPN MAC/IP Advertisement
   route and carries information relevant to the ARP/ND resolution, so
   that an EVPN PE implementing a proxy-ARP/ND function can reply to ARP
   Requests or Neighbor Solicitations with the correct information.

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
 

Rabadan et al.          Expires January 4, 2020                 [Page 1]
Internet-Draft     EVPN Neighbor Advertisement Flags        July 3, 2019

   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 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 4, 2020.

Copyright Notice

   Copyright (c) 2019 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. Introduction  . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1 Terminology and Conventions  . . . . . . . . . . . . . . . .  3
   2. The EVPN ARP/ND Extended Community  . . . . . . . . . . . . . .  4
   3. Use of the EVPN ARP/ND Extended Community . . . . . . . . . . .  5
   4. Security Considerations . . . . . . . . . . . . . . . . . . . .  6
   5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . .  7
   6. References  . . . . . . . . . . . . . . . . . . . . . . . . . .  7
     6.1. Normative References  . . . . . . . . . . . . . . . . . . .  7
     6.2. Informative References  . . . . . . . . . . . . . . . . . .  8
   7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . .  8
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  8

 

Rabadan et al.          Expires January 4, 2020                 [Page 2]
Internet-Draft     EVPN Neighbor Advertisement Flags        July 3, 2019

1. Introduction

   An EVPN MAC/IP Advertisement route can optionally carry an IPv4 or
   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. The information
   conveyed in the MAC/IP route may not be enough for the remote PE to