The IESG has received a request from the BGP Enabled Services WG (bess) to consider the following document: - 'BGP ACCEPT_OWN Community Attribute' <draft-ietf-l3vpn-acceptown-community-08.txt> as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2014-12-08. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract 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. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-l3vpn-acceptown-community/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-l3vpn-acceptown-community/ballot/ No IPR declarations have been submitted directly on this I-D.
