%% You should probably cite draft-ietf-idr-bgp-ls-bgp-only-fabric instead of this I-D.
@techreport{ketant-idr-bgp-ls-bgp-only-fabric-05,
    number =    {draft-ketant-idr-bgp-ls-bgp-only-fabric-05},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ketant-idr-bgp-ls-bgp-only-fabric/05/},
    author =    {Ketan Talaulikar and Clarence Filsfils and Krishnaswamy Ananthamurthy and Shawn Zandi and Gaurav Dawra and Muhammad Durrani},
    title =     {{BGP Link-State Extensions for BGP-only Fabric}},
    pagetotal = 25,
    year =      2020,
    month =     sep,
    day =       8,
    abstract =  {BGP is used as the only routing protocol in some networks today. In such networks, it is useful to get a detailed view of the nodes and underlying links in the topology along with their attributes similar to one available when using link state routing protocols. Such a view of a BGP-only fabric enables use cases like traffic engineering and forwarding of services along paths other than the BGP best path selection. This document defines extensions to the BGP Link-state address-family (BGP-LS) and the procedures for advertisement of the topology in a BGP-only network. It also describes a specific use-case for traffic engineering based on Segment Routing.},
}