Skip to main content

Propagation of IPv6 Neighbor Advertisement Flags in EVPN

Document Type Replaced Internet-Draft (bess WG)
Authors Jorge Rabadan , Senthil Sathappan , Kiran Nagaraj
Last updated 2017-09-30 (Latest revision 2017-07-03)
Replaced by RFC 9047
Stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Expired & archived
Stream WG state Adopted by a WG
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-bess-evpn-na-flags
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


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. However, if the Neighbor information is learnt via EVPN, the PE would not know if a 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. This document proposes an OPTIONAL advertisement of the Flags defined in [RFC4861] along with the EVPN MAC/IP Advertisement routes, so that an EVPN PE implementing a proxy-ND function can reply to Neighbor Solicitations with the correct Flag information in Neighbor Advertisements.


Jorge Rabadan
Senthil Sathappan
Kiran Nagaraj

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)