Skip to main content

BGP ACCEPT_OWN Well-known Community Attribute

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Prodosh Mohapatra , Jim Uttaro , David J. Smith , Robert Raszuk , John Scudder
Last updated 2010-01-15 (Latest revision 2008-06-08)
Replaced by draft-ietf-l3vpn-acceptown-community
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-l3vpn-acceptown-community
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:


Under certain conditions it is desirable for a BGP route reflector to be able to modify the Route Target list of a VPN route that is distributed by the route reflector, enabling the route reflector to control how a route originated within one VRF is imported into other VRFs. This technique works effectively as long as the VRF that exports the route is not on the same PE as the VRF(s) that import the route. However, due to the constraints of the BGP protocol, it does not work if the two are on the same PE. This document describes a modification to the BGP protocol allowing this technique to work when the VRFs are on the same PE, allowing the technique to be used in a standard manner throughout an autonomous system.


Prodosh Mohapatra
Jim Uttaro
David J. Smith
Robert Raszuk
John Scudder

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