@techreport{scudder-idr-ebgp-rr-02,
    number =    {draft-scudder-idr-ebgp-rr-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-scudder-idr-ebgp-rr/02/},
    author =    {John Scudder},
    title =     {{Considerations for Route Reflection and EBGP}},
    pagetotal = 4,
    year =      2012,
    month =     oct,
    day =       18,
    abstract =  {Although originally conceived of as a purely IBGP device, in some cases a route reflector may function as an EBGP speaker in addition to its role as envisioned in RFC 4456. When it does so, just like any other EBGP speaker it must advertise its routes to its IBGP peers. This document updates RFC 4456 by explaining what behavior is required of a route reflector that also functions as an EBGP speaker. It also clarifies the use of the ORIGINATOR\_ID and CLUSTER\_LIST attributes in this environment.},
}