IP Prefix Advertisement in EVPN

The information below is for an old version of the document
Document Type Expired Internet-Draft (bess WG)
Authors Jorge Rabadan  , Wim Henderickx  , Senad Palislamovic  , Aldrin Isaac 
Last updated 2016-03-17 (latest revision 2015-09-14)
Replaces draft-rabadan-l2vpn-evpn-prefix-advertisement
Stream IETF
Intended RFC status Proposed Standard
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


EVPN provides a flexible control plane that allows intra-subnet connectivity in an IP/MPLS and/or an NVO-based network. In NVO networks, there is also a need for a dynamic and efficient inter- subnet connectivity across Tenant Systems and End Devices that can be physical or virtual and may not support their own routing protocols. This document defines a new EVPN route type for the advertisement of IP Prefixes and explains some use-case examples where this new route- type is used.


Jorge Rabadan (jorge.rabadan@alcatel-lucent.com)
Wim Henderickx (wim.henderickx@alcatel-lucent.com)
Senad Palislamovic (senad.palislamovic@alcatel-lucent.com)
Aldrin Isaac (aisaac71@bloomberg.net)

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