%% You should probably cite draft-ietf-ccamp-mpls-tp-cp-framework instead of this I-D. @techreport{abfb-mpls-tp-control-plane-framework-02, number = {draft-abfb-mpls-tp-control-plane-framework-02}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-abfb-mpls-tp-control-plane-framework/02/}, author = {Loa Andersson and Lou Berger and Luyuan Fang and Dr. Nabil N. Bitar and Attila Takacs and Martin Vigoureux and Elisa Bellagamba}, title = {{MPLS-TP Control Plane Framework}}, pagetotal = 43, year = 2010, month = feb, day = 22, 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 LSPs and provides for compatibility with MPLS. The control plane for Pseudowires (PWs) is also covered by this document. Management plane functions such as manual configuration and the initiation of LSP setup are out of scope of this document.}, }