BGP ACCEPT_OWN Community Attribute
draft-ietf-l3vpn-acceptown-community-07
| The information below is for an old version of the document | |||
|---|---|---|---|
| Document | Type | Expired Internet-Draft (l3vpn WG) | |
| Last updated | 2014-04-05 (latest revision 2013-10-02) | ||
| Replaces | draft-pmohapat-l3vpn-acceptown-community | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | WG Document Nov 2013 Nov 2014 | |
| Document shepherd | Thomas Morin | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-l3vpn-acceptown-community-07.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.)