%% You should probably cite draft-ietf-idr-long-lived-gr instead of this I-D.
@techreport{uttaro-idr-bgp-persistence-01,
    number =    {draft-uttaro-idr-bgp-persistence-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-uttaro-idr-bgp-persistence/01/},
    author =    {Jim Uttaro and Adam Simpson and Rob Shakir and Clarence Filsfils and Prodosh Mohapatra and Bruno Decraene and John Scudder and Yakov Rekhter},
    title =     {{BGP Persistence}},
    pagetotal = 24,
    year =      2012,
    month =     mar,
    day =       12,
    abstract =  {For certain AFI/SAFI combinations it is desirable that a BGP speaker be able to retain routing state learned over a session that has terminated. By maintaining routing state forwarding may be preserved. This technique works effectively as long as the AFI/SAFI is primarily used to realize services that do not depend on exchanging BGP routing state with peers or customers. There may be exceptions based upon the amount and frequency of route exchange that allow for this technique. Generally the BGP protocol tightly couples the viability of a session and the routing state that is learned over it. This is driven by the history of the protocol and it's application in the internet space as a vehicle to exchange routing state between administrative authorities. This document addresses new services whose requirements for persistence diverge from the Internet routing point of view.},
}