RFC 7611: BGP ACCEPT_OWN Community Attribute
In plain English — editorial summary, not part of the RFC
Under certain conditions, it is desirable for a Border Gateway Protocol (BGP) route reflector to be able to modify the Route Target (RT) list of a Virtual Private Network (VPN) route that the route reflector distributes, enabling the route reflector to control how a route originated within one VPN Routing and Forwarding table (VRF) is imported into other VRFs. This technique works effectively as long as the VRF that exports the route is not on the same Provider Edge (PE) router as the VRF(s) that imports the route. However, due to the constraints of BGP, it does not work if the two are on the same PE. This document describes a modification to BGP allowing this technique to work when the VRFs are on the same PE and to be used in a standard manner throughout an autonomous system.
Document record
- Document ID
- RFC7611
- Published
- August 2015
- Authors
- J. Uttaro; P. Mohapatra; D. Smith; R. Raszuk; J. Scudder
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6517Mandatory Features in a Layer 3 Multicast BGP/MPLS VPN SolutionCurrent
February 2012
- RFC 7899Multicast VPN State DampingCurrent
June 2016
- RFC 6565OSPFv3 as a Provider Edge to Customer Edge (PE-CE) Routing ProtocolCurrent
June 2012
- RFC 4031Service Requirements for Layer 3 Provider Provisioned Virtual Private Networks (PPVPNs)Current
April 2005
- RFC 7607Codification of AS 0 ProcessingCurrent
August 2015
- RFC 7606Revised Error Handling for BGP UPDATE MessagesCurrent
August 2015
- RFC 7674Clarification of the Flowspec Redirect Extended CommunityObsoleted
October 2015
- RFC 7543Covering Prefixes Outbound Route Filter for BGP-4Current
May 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?