@techreport{pmohapat-idr-acceptown-community-01,
    number =    {draft-pmohapat-idr-acceptown-community-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-pmohapat-idr-acceptown-community/01/},
    author =    {John Scudder and David J. Smith and Robert Raszuk and Jim Uttaro and Prodosh Mohapatra},
    title =     {{BGP ACCEPT\_OWN Well-known Community Attribute}},
    pagetotal = 8,
    year =      2008,
    month =     apr,
    day =       25,
    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.},
}