%% You should probably cite draft-ietf-mpls-tp-oam-framework instead of this I-D. @techreport{busi-mpls-tp-oam-framework-02, number = {draft-busi-mpls-tp-oam-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-busi-mpls-tp-oam-framework/02/}, author = {Ben Niven-Jenkins and Italo Busi}, title = {{MPLS-TP OAM Framework and Overview}}, pagetotal = 28, year = 2009, month = mar, day = 26, abstract = {Multi-Protocol Label Switching (MPLS) Transport Profile (MPLS-TP) is based on a profile of the MPLS and pseudowire (PW) procedures as specified in the MPLS Traffic Engineering (MPLS-TE), pseudowire (PW) and multi-segment PW (MS-PW) architectures complemented with additional Operations, Administration and Maintenance (OAM) procedures for fault, performance and protection-switching management for packet transport applications that do not rely on the presence of a control plane. This document provides a framework that supports a comprehensive set of OAM procedures that fulfills the MPLS-TP OAM requirements {[}11{]}.}, }