Skip to main content

IP Prefix Advertisement in E-VPN
draft-rabadan-l2vpn-evpn-prefix-advertisement-01

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
Authors Jorge Rabadan , Jorge Rabadan , Wim Henderickx , Senad Palislamovic , Senad Palislamovic , Florin Balus , Florin Balus , Aldrin Isaac
Last updated 2014-04-24 (Latest revision 2013-10-21)
Replaced by draft-ietf-bess-evpn-prefix-advertisement, RFC 9136
RFC stream (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
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:

Abstract

E-VPN provides a flexible control plane that allows intra-subnet connectivity in an IP/MPLS and/or an NVO-based network. In Data Centers, 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 E-VPN route type for the advertisement of IP Prefixes and explains some use-case examples where this new route- type is used.

Authors

Jorge Rabadan
Jorge Rabadan
Wim Henderickx
Senad Palislamovic
Senad Palislamovic
Florin Balus
Florin Balus
Aldrin Isaac

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