Skip to main content

IP Prefix Advertisement in EVPN
draft-rabadan-l2vpn-evpn-prefix-advertisement-03

Document Type Replaced Internet-Draft (bess WG)
Expired & archived
Authors Jorge Rabadan , Jorge Rabadan , Wim Henderickx , Senad Palislamovic , Senad Palislamovic , Florin Balus , Florin Balus , Aldrin Isaac
Last updated 2015-10-14 (Latest revision 2014-10-17)
Replaced by draft-ietf-bess-evpn-prefix-advertisement
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state Adopted by a WG
Document shepherd Martin Vigoureux
IESG IESG state Replaced by draft-ietf-bess-evpn-prefix-advertisement
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:

Abstract

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.

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.)