RFC 9161: Operational Aspects of Proxy ARP/ND in Ethernet Virtual Private Networks
In plain English — editorial summary, not part of the RFC
This document describes the Ethernet Virtual Private Network (EVPN) Proxy ARP/ND function augmented by the capability of the ARP/ND Extended Community. From that perspective, this document updates the EVPN specification to provide more comprehensive documentation of the operation of the Proxy ARP/ND function. The EVPN Proxy ARP/ND function and the ARP/ND Extended Community help operators of Internet Exchange Points, Data Centers, and other networks deal with IPv4 and IPv6 address resolution issues associated with large Broadcast Domains by reducing and even suppressing the flooding produced by address resolution in the EVPN network.
Document record
- Document ID
- RFC9161
- Published
- January 2022
- Authors
- J. Rabadan; S. Sathappan; K. Nagaraj; G. Hankins; T. King
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 22
- Also known as
- —
- Updates:
- RFC 7432
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9166A YANG Data Model for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) SnoopingCurrent
February 2022
- RFC 9168Path Computation Element Communication Protocol (PCEP) Extension for Flow SpecificationUpdated
January 2022
- RFC 9145Integrity Protection for the Network Service Header (NSH) and Encryption of Sensitive Context HeadersCurrent
December 2021
- RFC 9184BGP Extended Community Registries UpdateCurrent
January 2022
- RFC 9186Fast Failover in Protocol Independent Multicast - Sparse Mode (PIM-SM) Using Bidirectional Forwarding Detection (BFD) for Multipoint NetworksCurrent
January 2022
- RFC 9136IP Prefix Advertisement in Ethernet VPN (EVPN)Current
October 2021
- RFC 9135Integrated Routing and Bridging in Ethernet VPN (EVPN)Current
October 2021
- RFC 9130YANG Data Model for the IS-IS ProtocolCurrent
October 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?