Multiprotocol Label Switching (MPLS) Label-Controlled Asynchronous Transfer Mode (ATM) and Frame-Relay Management Interface Definition
RFC 4368

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 08

Network Working Group                                          T. Nadeau
Request for Comments: 4368                                      S. Hegde
Category: Standards Track                            Cisco Systems, Inc.
                                                            January 2006

         Multiprotocol Label Switching (MPLS) Label-Controlled
           Asynchronous Transfer Mode (ATM) and Frame-Relay
                    Management Interface Definition

Status of This Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2006).

Abstract

   This memo defines two MIB modules and corresponding MIB Object
   Definitions that describe how label-switching-controlled Frame-Relay
   and Asynchronous Transfer Mode (ATM) interfaces can be managed given
   the interface stacking as defined in the MPLS-LSR-STD-MIB and
   MPLS-TE-STD-MIB.

Table of Contents

   1. Introduction ....................................................2
   2. Terminology .....................................................2
   3. The SNMP Management Framework ...................................3
   4. Interface Stacking of LC-ATM ....................................3
   5. Structure of the MPLS-LC-ATM-STD-MIB Module .....................3
   6. Structure of the MPLS-LC-FR-STD-MIB Module ......................4
   7. MPLS Label-Controlled ATM MIB Definitions .......................5
   8. MPLS Label-Controlled Frame Relay MIB Definitions ..............12
   9. Acknowledgments ................................................18
   10. Security Considerations .......................................18
   11. IANA Considerations ...........................................19
      11.1. IANA Considerations for MPLS-LC-ATM-STD-MIB ..............19
      11.2. IANA Considerations for MPLS-LC-FR-STD-MIB ...............19
   12. References ....................................................20
      12.1. Normative References .....................................20
      12.2. Informative References ...................................21

Nadeau & Hegde              Standards Track                     [Page 1]
RFC 4368                MPLS LC ATM and FR MIBs             January 2006

1.  Introduction

   This memo defines how label-switching-controlled Frame-Relay
   [RFC3034] and ATM [RFC3035] interfaces can be realized given the
   interface stacking as defined in the MPLS-LSR-STD [RFC3813] and
   MPLS-TE-STD [RFC3812] MIBs.  This document also contains a MIB module
   that sparsely extends the MPLS-LSR-STD MIB's mplsInterfaceConfTable
   in such a way as to identify which MPLS-type interfaces have LC-ATM
   or LC-FR capabilities.  Comments should be made directly to the MPLS
   mailing list at mpls@uu.net.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119, reference
   [RFC2119].

2.  Terminology

   This document uses terminology from the document describing the MPLS
   architecture [RFC3031], as well as from RFC 3035 and RFC 3034.
   Specifically, the following terms will be used in this document.

   C-FR  RFC 3034 defines a label-switching-controlled Frame Relay
         (LC-FR) interface.  Packets traversing such an interface carry
         labels in the DLCI field

   C-ATM RFC 3035 defines a label-switching-controlled ATM (LC-ATM)
         interface as an ATM interface controlled by the label switching
         control component.  When a packet traversing such an interface
         is received, it is treated as a labeled packet.  The packet's
         top label is inferred from either the contents of the Virtual
         Channel Identifier (VCI) field or the combined contents of the
         Virtual Path Identifier (VPI) and VCI fields.  Any two LDP
         peers that are connected via an LC-ATM interface will use LDP
         negotiations to determine which of these cases is applicable to
         that interface.  Static configuration of labels is also
         possible.

   When LDP is used to distribute labels for use on label-controlled
   interfaces, label configuration information may be available in the
   MPLS-LDP-ATM-STD-MIB [RFC3815] when LC-ATM interfaces are used, or
   the MPLS-LDP-FRAME-RELAY-STD-MIB [RFC3815] when LC-FR interfaces are
   used.

Nadeau & Hegde              Standards Track                     [Page 2]
RFC 4368                MPLS LC ATM and FR MIBs             January 2006

3.  The SNMP Management Framework

   For a detailed overview of the documents that describe the current