%% You should probably cite draft-keyupate-irs-bgp-usecases-02 instead of this revision.
@techreport{keyupate-irs-bgp-usecases-00,
    number =    {draft-keyupate-irs-bgp-usecases-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-keyupate-irs-bgp-usecases/00/},
    author =    {Keyur Patel and Hannes Gredler and Rex Fernando and Shane Amante},
    title =     {{Use Cases for an Interface to BGP Protocol}},
    pagetotal = 12,
    year =      2012,
    month =     oct,
    day =       15,
    abstract =  {A network routing protocol like BGP is typically configured and results of its operation are analyzed through some form of Command Line Interface (CLI) or NETCONF. These interactions to control BGP and diagnose its operation encompass: configuration of protocol parameters, display of protocol data, setting of certain protocol states and debugging of the protocol. Interface to the Routing System's (IRS) Programatic interfaces, as defined in {[}I-D.ward-irs-framework{]}, provides an alternate way to control the configuration and diagnose the operation of the BGP protocol. IRS may be used for the configuration, manipulation, polling or analyzing protocol data. This document describes a set of use cases for which IRS can be used for BGP protocol. It is indended to provide a base for the solution draft descibring a set of Interfaces to the BGP protocol.},
}