%% You should probably cite draft-ietf-l3vpn-e2e-rsvp-te-reqts instead of this I-D.
@techreport{kumaki-l3vpn-e2e-rsvp-te-reqts-06,
    number =    {draft-kumaki-l3vpn-e2e-rsvp-te-reqts-06},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-kumaki-l3vpn-e2e-rsvp-te-reqts/06/},
    author =    {Kenji Kumaki},
    title =     {{Requirements for supporting Customer RSVP and RSVP-TE Over a BGP/MPLS IP-VPN}},
    pagetotal = 21,
    year =      2008,
    month =     feb,
    day =       20,
    abstract =  {Some service providers want to build a service which guarantees QoS or bandwidth from a local CE to a remote CE through the network. Today, customers expect to run triple play services through BGP/MPLS IP-VPNs. As a result, their requirements for end-to-end QoS of applications are increasing. Depending on the application (e.g., voice, video, bandwidth-guaranteed data pipe, etc.), an end-to-end native RSVP path and/or an end-to-end MPLS TE LSP are required, and they need to meet some constraints. This document describes service provider requirements for supporting customer RSVP and RSVP-TE over a BGP/MPLS VPN},
}