Requirements for Operations, Administration, and Maintenance (OAM) in MPLS Transport Networks
RFC 5860

Internet Engineering Task Force (IETF)                 M. Vigoureux, Ed.
Request for Comments: 5860                                Alcatel-Lucent
Category: Standards Track                                   D. Ward, Ed.
ISSN: 2070-1721                                         Juniper Networks
                                                           M. Betts, Ed.
                                             M. C. Betts Consulting Ltd.
                                                                May 2010

   Requirements for Operations, Administration, and Maintenance (OAM)
                       in MPLS Transport Networks

Abstract

   This document lists architectural and functional requirements for the
   Operations, Administration, and Maintenance of MPLS Transport
   Profile.  These requirements apply to pseudowires, Label Switched
   Paths, and Sections.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc5860.

Copyright Notice

   Copyright (c) 2010 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Vigoureux, et al.            Standards Track                    [Page 1]
RFC 5860              OAM Requirements for MPLS-TP              May 2010

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Scope of This Document . . . . . . . . . . . . . . . . . .  3
     1.2.  Requirements Language and Terminology  . . . . . . . . . .  4
   2.  OAM Requirements . . . . . . . . . . . . . . . . . . . . . . .  5
     2.1.  Architectural Requirements . . . . . . . . . . . . . . . .  6
       2.1.1.  Scope of OAM . . . . . . . . . . . . . . . . . . . . .  6
       2.1.2.  Independence . . . . . . . . . . . . . . . . . . . . .  6
       2.1.3.  Data Plane . . . . . . . . . . . . . . . . . . . . . .  7
       2.1.4.  OAM and IP Capabilities  . . . . . . . . . . . . . . .  7
       2.1.5.  Interoperability and Interworking  . . . . . . . . . .  8
       2.1.6.  Configuration  . . . . . . . . . . . . . . . . . . . .  8
     2.2.  Functional Requirements  . . . . . . . . . . . . . . . . .  9
       2.2.1.  General Requirements . . . . . . . . . . . . . . . . .  9
       2.2.2.  Continuity Checks  . . . . . . . . . . . . . . . . . . 10
       2.2.3.  Connectivity Verifications . . . . . . . . . . . . . . 10
       2.2.4.  Route Tracing  . . . . . . . . . . . . . . . . . . . . 11
       2.2.5.  Diagnostic Tests . . . . . . . . . . . . . . . . . . . 11
       2.2.6.  Lock Instruct  . . . . . . . . . . . . . . . . . . . . 11
       2.2.7.  Lock Reporting . . . . . . . . . . . . . . . . . . . . 12
       2.2.8.  Alarm Reporting  . . . . . . . . . . . . . . . . . . . 12
       2.2.9.  Remote Defect Indication . . . . . . . . . . . . . . . 13
       2.2.10. Client Failure Indication  . . . . . . . . . . . . . . 13
       2.2.11. Packet Loss Measurement  . . . . . . . . . . . . . . . 13
       2.2.12. Packet Delay Measurement . . . . . . . . . . . . . . . 14
   3.  Congestion Considerations  . . . . . . . . . . . . . . . . . . 15
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . . 15
   5.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
   6.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
     6.1.  Normative References . . . . . . . . . . . . . . . . . . . 16
     6.2.  Informative References . . . . . . . . . . . . . . . . . . 16

Vigoureux, et al.            Standards Track                    [Page 2]
RFC 5860              OAM Requirements for MPLS-TP              May 2010

1.  Introduction

   In the context of MPLS Transport Profile (MPLS-TP, see [9] and [1]),
   the rationales for Operations, Administration, and Maintenance (OAM)