@misc{rfc5824,
    series =    {Request for Comments},
    number =    5824,
    howpublished =  {RFC 5824},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC5824},
    url =       {https://www.rfc-editor.org/info/rfc5824},
    author =    {Kenji Kumaki and Raymond Zhang and Yuji Kamite},
    title =     {{Requirements for Supporting Customer Resource ReSerVation Protocol (RSVP) and RSVP Traffic Engineering (RSVP-TE) over a BGP/MPLS IP-VPN}},
    pagetotal = 27,
    year =      2010,
    month =     apr,
    abstract =  {Today, customers expect to run triple-play services through BGP/MPLS IP-VPNs. Some service providers will deploy services that request Quality of Service (QoS) guarantees from a local Customer Edge (CE) to a remote CE across the network. As a result, the application (e.g., voice, video, bandwidth-guaranteed data pipe, etc.) requirements for an end-to-end QoS and reserving an adequate bandwidth continue to increase. Service providers can use both an MPLS and an MPLS Traffic Engineering (MPLS-TE) Label Switched Path (LSP) to meet their service objectives. This document describes service-provider requirements for supporting a customer Resource ReSerVation Protocol (RSVP) and RSVP-TE over a BGP/MPLS IP-VPN. This document is not an Internet Standards Track specification; it is published for informational purposes.},
}