Browse Prior Art Database

BGP ACCEPT_OWN Community Attribute (RFC7611) Disclosure Number: IPCOM000244953D
Original Publication Date: 2015-Aug-01
Included in the Prior Art Database: 2016-Feb-04
Document File: 16 page(s) / 17K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Uttaro: AUTHOR [+5]


In certain scenarios, a BGP speaker may maintain multiple VRFs [RFC4364]. Under certain conditions, it is desirable for a route reflector to be able to modify the RT list of a VPN route that the route reflector distributes, enabling the route reflector to control how a route originated within one VRF is imported into other VRFs. Though it is possible to perform such control directly on the originator, it may be operationally cumbersome in an autonomous system with a large number of border routers having complex BGP policies.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 16% of the total text.

Internet Engineering Task Force (IETF)                         J. Uttaro Request for Comments: 7611                                          AT&T Category: Standards Track                                   P. Mohapatra ISSN: 2070-1721                                         Sproute Networks                                                                 D. Smith                                                            Cisco Systems                                                                R. Raszuk                                                            Mirantis Inc.                                                               J. Scudder                                                         Juniper Networks                                                              August 2015

                    BGP ACCEPT_OWN Community Attribute


   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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at

 Uttaro, et al.               Standards Track       ...