%% You should probably cite rfc7625 instead of this I-D.
@techreport{hao-mpls-ip-hard-pipe-01,
    number =    {draft-hao-mpls-ip-hard-pipe-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-hao-mpls-ip-hard-pipe/01/},
    author =    {JiangTao Hao and Praveen Maheshwari and River Huang and Loa Andersson and Mach Chen},
    title =     {{Architecture of MPLS/IP Network with Hardened Pipes}},
    pagetotal = 15,
    year =      2014,
    month =     sep,
    day =       29,
    abstract =  {This document is intended to become an Informational RFC on the independent stream. The document does not specify any new protocol or procedures. It does explain how the MPLS standards implementation, has been deployed and operated to meet the requirements from operators that offer traditional Virtual Leased Line services. This document describes an MPLS/IP network that has an infrastructure that can be separated into two or more strata. For the implementation described in this document the infrastructure has been separated into two strata. One for the 'Hard Pipes', called the 'Hard Pipe Stratum". And one for the normal IP/MPLS traffic - called the 'Normal IP/MPLS stratum'. This document introduces the concept of "Hard Pipes", a Hard Pipe is an MPLS Label Switched Path (LSP) or a Pseudowire (PW) with a bandwidth that is guaranteed and can neither be exceeded nor infringed upon. The Hard Pipe stratum does not use statistical multiplexing, for the LSPs and PWs setup within this stratum the bandwidth are guaranteed end to end.},
}