"The use of the OAM Acronym in MPLS-TP"

At first glance the acronym "OAM" seems to be well known and well understood. Looking at the acronym a bit more closely reveals a set of recurring problems that are revisited time and again. The goal of this document is to find an understanding of the OAM acronym that is useful for the MPLS Transport Profile (MPLS-TP) effort. 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 PWE3 architectures to support the capabilities and functionalities of a packet transport network. This Informational Internet-Draft is aimed at achieving IETF Consensus before publication as an RFC and will be subject to an IETF Last Call. [RFC Editor, please remove this note before publication as an RFC and insert the correct Streams Boilerplate to indicate that the published RFC has IETF Consensus.]