%% You should probably cite draft-gao-mpls-teas-rsvpte-state-update-06 instead of this revision.
@techreport{gao-mpls-teas-rsvpte-state-update-03,
    number =    {draft-gao-mpls-teas-rsvpte-state-update-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-gao-mpls-teas-rsvpte-state-update/03/},
    author =    {Jun Gao and Jinyou Dai},
    title =     {{State-updating mechanism in RSVP-TE for MPLS network}},
    pagetotal = 8,
    year =      2021,
    month =     may,
    day =       3,
    abstract =  {RSVP-TE has the following advantages: source routing capability, and the ability to reserve resources hop by hop along the LSP path. RSVP takes a "soft state" approach to manage the reservation state in routers and hosts. The use of 'Refresh messages' to cover many possible failures has resulted in a number of operational problems. One problem relates to scaling, another relates to the reliability and latency of RSVP Signaling. This document describes a number of mechanisms that can be used to reduce processing overhead requirements of refresh messages. These extension present no backwards compatibility issues.},
}