%% You should probably cite rfc6373 instead of this I-D.
@techreport{ietf-ccamp-mpls-tp-cp-framework-06,
    number =    {draft-ietf-ccamp-mpls-tp-cp-framework-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-ietf-ccamp-mpls-tp-cp-framework/06/},
    author =    {Eric Gray and Dr. Nabil N. Bitar and Luyuan Fang and Lou Berger and Loa Andersson},
    title =     {{MPLS Transport Profile (MPLS-TP) Control Plane Framework}},
    pagetotal = 57,
    year =      2011,
    month =     feb,
    day =       10,
    abstract =  {The MPLS Transport Profile (MPLS-TP) supports static provisioning of transport paths via a Network Management System (NMS) and dynamic provisioning of transport paths via a control plane. This document provides the framework for MPLS-TP dynamic provisioning and covers control-plane addressing, routing, path computation, signaling, traffic engineering, and path recovery. MPLS-TP uses GMPLS as the control plane for MPLS-TP Label Switched Paths (LSPs). MPLS-TP also uses the pseudowire (PW) control plane for pseudowires. Management-plane functions are out of scope of this document. This document is a product of a joint Internet Engineering Task Force (IETF) / International Telecommunication Union Telecommunication Standardization Sector (ITU-T) effort to include an MPLS Transport Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge (PWE3) architectures to support the capabilities and functionalities of a packet transport network as defined by the ITU-T. This document is not an Internet Standards Track specification; it is published for informational purposes.},
}