Propagation of ARP/ND Flags in EVPN
draft-ietf-bess-evpn-na-flags-09
| Document | Type | Active Internet-Draft (bess WG) | |
|---|---|---|---|
| Authors | Jorge Rabadan , Senthil Sathappan , Kiran Nagaraj , Wen Lin | ||
| Last updated | 2020-12-01 | ||
| Replaces | draft-snr-bess-evpn-na-flags | ||
| Stream | 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 | Matthew Bocci | ||
| Shepherd write-up | Show (last changed 2019-07-08) | ||
| IESG | IESG state | IESG Evaluation::AD Followup | |
| Consensus Boilerplate | Yes | ||
| Telechat date |
Has a DISCUSS. Has enough positions to pass once DISCUSS positions are resolved. |
||
| Responsible AD | Martin Vigoureux | ||
| Send notices to | Matthew Bocci <matthew.bocci@nokia.com> | ||
| IANA | IANA review state | Version Changed - Review Needed | |
BESS Workgroup J. Rabadan, Ed.
Internet-Draft S. Sathappan
Intended status: Standards Track K. Nagaraj
Expires: June 4, 2021 Nokia
W. Lin
Juniper
December 1, 2020
Propagation of ARP/ND Flags in EVPN
draft-ietf-bess-evpn-na-flags-09
Abstract
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 or ARP/ND (on IRB interfaces) 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). 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 June 4, 2021.
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
Rabadan, et al. Expires June 4, 2021 [Page 1]
Internet-Draft EVPN Neighbor Advertisement Flags December 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 and Conventions . . . . . . . . . . . . . . . 3
2. The EVPN ARP/ND Extended Community . . . . . . . . . . . . . 3
3. Use of the EVPN ARP/ND Extended Community . . . . . . . . . . 5
3.1. Transmission of the EVPN ARP/ND Extended Community . . . 5
3.2. Reception of the EVPN ARP/ND Extended Community . . . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . 8
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.1. Normative References . . . . . . . . . . . . . . . . . . 9
7.2. Informative References . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
An Ethernet Virtual Private Network (EVPN) MAC/IP Advertisement route
can optionally carry IPv4 or IPv6 addresses associated with a MAC
address. Remote Provider Edge (PE) routers can use this information
to populate their Address Resolution Protocol (ARP) or Neighbor
Discovery (ND) tables on Integrated Routing and Bridging (IRB)
interfaces or their proxy-ARP/ND tables in Broadcast Domains (BD).
PEs can then reply locally (act as an ARP/ND proxy, as per [RFC7432])
to IPv4 ARP requests and IPv6 Neighbor Solicitation messages and
reduce/suppress the flooding produced by the Address Resolution
procedure. However, the information conveyed in the EVPN MAC/IP
Advertisement 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 router or a host, and if that address is an anycast
address, as this information is not carried in the EVPN MAC/IP
Advertisement routes.
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. In particular, the Flags
defined in [RFC4861] can now be conveyed along with a MAC/IP
Show full document text