%% You should probably cite rfc4456 instead of this I-D.
@techreport{ietf-idr-rfc2796bis-02,
    number =    {draft-ietf-idr-rfc2796bis-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-ietf-idr-rfc2796bis/02/},
    author =    {Enke Chen and Tony J. Bates and Ravi Chandra},
    title =     {{BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)}},
    pagetotal = 12,
    year =      2005,
    month =     oct,
    day =       12,
    abstract =  {The Border Gateway Protocol (BGP) is an inter-autonomous system routing protocol designed for TCP/IP internets. Typically, all BGP speakers within a single AS must be fully meshed so that any external routing information must be re-distributed to all other routers within that Autonomous System (AS). This represents a serious scaling problem that has been well documented with several alternatives proposed. This document describes the use and design of a method known as "route reflection" to alleviate the need for "full mesh" Internal BGP (IBGP). This document obsoletes RFC 2796 and RFC 1966. {[}STANDARDS-TRACK{]}},
}