RFC 7611

BGP ACCEPT_OWN Community Attribute, August 2015

File formats:
icon for text file icon for PDF icon for HTML
J. Uttaro
P. Mohapatra
D. Smith
R. Raszuk
J. Scudder
bess (rtg)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC7611

Discuss this RFC: Send questions or comments to the mailing list bess@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 7611


Under certain conditions, it is desirable for a Border Gateway Protocol (BGP) route reflector to be able to modify the Route Target (RT) list of a Virtual Private Network (VPN) route that the route reflector distributes, enabling the route reflector to control how a route originated within one VPN Routing and Forwarding table (VRF) is imported into other VRFs. This technique works effectively as long as the VRF that exports the route is not on the same Provider Edge (PE) router as the VRF(s) that imports the route. However, due to the constraints of BGP, it does not work if the two are on the same PE. This document describes a modification to BGP allowing this technique to work when the VRFs are on the same PE and to be used in a standard manner throughout an autonomous system.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.

Advanced Search