BGP ACCEPT_OWN Well-known Community Attribute

Document Type Replaced Internet-Draft (individual)
Last updated 2010-01-15 (latest revision 2008-06-08)
Replaced by draft-ietf-l3vpn-acceptown-community
Stream (None)
Intended RFC status (None)
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-l3vpn-acceptown-community
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


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.


Pradosh Mohapatra (
Jim Uttaro (
David Smith (
Robert Raszuk (
John Scudder (

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