BGP ACCEPT_OWN Community Attribute
draft-ietf-l3vpn-acceptown-community-04

The information below is for an old version of the document
Document Type Expired Internet-Draft (l3vpn WG)
Last updated 2012-04-04 (latest revision 2011-10-02)
Replaces draft-pmohapat-l3vpn-acceptown-community
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream WG state WG Document Nov 2013 Nov 2014
Other - see Comment Log
Document shepherd 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-ietf-l3vpn-acceptown-community-04.txt

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.

Authors

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