@techreport{iovanna-rsvp-mpls-flowspec-00,
    number =    {draft-iovanna-rsvp-mpls-flowspec-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-iovanna-rsvp-mpls-flowspec/00/},
    author =    {Paola Iovanna and Roberto Mameli and Giovanna Piantanida and Stefano Salsano},
    title =     {{Definition of the MPLS FlowSpec for RSVP-TE}},
    pagetotal = 12,
    year =      2001,
    month =     oct,
    day =       15,
    abstract =  {The support of QoS Differentiation in MPLS is based on the definition of two types of LSP, respectively E-LSP and L-LSP (see {[}11{]}). Both E-LSP and L-LSP can be established with bandwidth reservation. In this case bandwidth requirements for the LSP must be signaled at LSP establishment time, in order to perform admission control in the LSRs in the path. If RSVP-TE is used as setup protocol, it has to support the signaling of bandwidth requirements for the LSPs. In this document we extend the RSVP-TE capability by defining a new type of Sender\_Tspec (and FlowSpec), explicitly designed to allow signaling of bandwidth requirements for E-LSP and L-LSP set up. This new type, called MPLS Sender\_Tspec (MPLS FlowSpec), can include bandwidth requirements for different classes inside the LSP.},
}