EVPN Path Attribute Propagation
draft-rs-bess-evpn-attr-prop-00

Document Type Expired Internet-Draft (individual)
Last updated 2017-09-14 (latest revision 2017-03-13)
Replaces draft-rabadan-simpson-bess-evpn-attr-prop
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
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
https://www.ietf.org/archive/id/draft-rs-bess-evpn-attr-prop-00.txt

Abstract

EVPN is being actively used to provide tenant inter-subnet-forwarding in DC networks, as described in [IP-PREFIX] and [INTER-SUBNET]. When those tenant networks are interconnected to vpn-ipv4/vpn-ipv6 or ipv4/ipv6 BGP networks, there is a need for the EVPN BGP Path Attributes to be seamlessly propagated so that the receiver PE or NVE can consider the original EVPN Attributes in its path calculations. This document analyses the use-cases, requirements and rules based on which the BGP Path Attributes should be propagated between EVPN and other BGP families.

Authors

Jorge Rabadan (jorge.rabadan@nokia.com)
Adam Simpson (adam.1.simpson@nokia.com)
Jim Uttaro (ju1738@att.com)

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