Browse Prior Art Database

Assignment of the 'OAM Alert Label' for Multiprotocol Label Switching Architecture (MPLS) Operation and Maintenance (OAM) Functions (RFC3429)

IP.com Disclosure Number: IPCOM000010306D
Original Publication Date: 2002-Nov-01
Included in the Prior Art Database: 2002-Nov-20
Document File: 7 page(s) / 11K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

H. Ohta: AUTHOR

Abstract

This document describes the assignment of one of the reserved label values defined in RFC 3032 (MPLS label stack encoding) to the 'Operation and Maintenance (OAM) Alert Label' that is used by user- plane Multiprotocol Label Switching Architecture (MPLS) OAM functions for identification of MPLS OAM packets.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 26% of the total text.

Network Working Group                                            H. Ohta

Request for Comments: 3429                                           NTT

Category: Informational                                    November 2002

                Assignment of the 'OAM Alert Label' for

           Multiprotocol Label Switching Architecture (MPLS)

              Operation and Maintenance (OAM) Functions

Status of this Memo

   This memo provides information for the Internet community.  It does

   not specify an Internet standard of any kind.  Distribution of this

   memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2002).  All Rights Reserved.

Abstract

   This document describes the assignment of one of the reserved label

   values defined in RFC 3032 (MPLS label stack encoding) to the

   'Operation and Maintenance (OAM) Alert Label' that is used by user-

   plane Multiprotocol Label Switching Architecture (MPLS) OAM functions

   for identification of MPLS OAM packets.

1. Introduction

   This document describes the assignment of one of the reserved label

   values defined in RFC 3032 (MPLS label stack encoding [2]) to the

   'OAM Alert Label' that is used by user-plane MPLS OAM functions for

   identification of MPLS OAM packets as described in the ITU-T

   Recommendation Y.1711 [1] (on MPLS OAM functions).

2. OAM functions

   MPLS OAM (Operation and Maintenance) functions provide necessary

   tools for network operators to operate and maintain the networks.

   MPLS OAM functionality is required at the MPLS layer, and more

   specifically at each MPLS level, independent of OAM functionality

   provided by the lower layers (SONET/SDH, etc.).  The objectives of

   the OAM functions include the following:

   -  Defect and failure detection: Defect/failures affecting the

      transport of user information are detected by continuous or

      periodic checking.  As a result, maintenance event information or

      appropriate alarms will be produced.

Ohta                         Informational                      [Page 1]

RFC 3429           OAM Alert Label for OAM Functions       November 2002

   -  Reporting the defect/failure information: Defect information is

      given to other management entities (e.g., Operation Support

      System) in order to provide the appropriate indications to the

      maintenance staff for maintaining the Quality of Service (QoS)

      level offered to customers.

   -  Defect/failure localization: Determination by internal or external

      test systems of a failed entity is performed if defect information

      is insufficient.

   -  Performance monitoring: Performance (packet losses, transfer

      delay, bit errors, etc.) of the user in...