BGP ACCEPT_OWN Well-known Community Attribute
draft-pmohapat-idr-acceptown-community-01

Document Type Expired Internet-Draft (individual)
Last updated 2008-04-25
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (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-pmohapat-idr-acceptown-community-01.txt

Abstract

It may be useful for a BGP speaker in an autonomous system to receive and accept its own advertised route from a route reflector with more fine-grained route control. For example, the route reflector can change certain attributes of a route as desired, and then re- advertise it back to the originator. Though it is possible to perform such policy control directly at the originator, it may be operationally cumbersome in a network with a large number of border routers having complex BGP policies. This draft defines a new and well-known BGP community value, ACCEPT_OWN, that signals a BGP speaker to accept an UPDATE message and process the associated routes even when the ORIGINATOR_ID or the NEXT_HOP matches that of the receiving speaker.

Authors

John Scudder (jgs@juniper.net)
David Smith (dasmith@cisco.com)
Robert Raszuk (raszuk@juniper.net)
Jim Uttaro (uttaro@att.com)
Prodosh Mohapatra (pmohapat@cisco.com)

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