Multiprotocol Label Switching (MPLS) Forwarding Equivalence Class To Next Hop Label Forwarding Entry (FEC-To-NHLFE) Management Information Base (MIB)
RFC 3814

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

• Versions
• 09

Network Working Group                                          T. Nadeau
Request for Comments: 3814                           Cisco Systems, Inc.
Category: Standards Track                                  C. Srinivasan
                                                          Bloomberg L.P.
                                                          A. Viswanathan
                                                  Force10 Networks, Inc.
                                                               June 2004

      Multiprotocol Label Switching (MPLS) Forwarding Equivalence
        Class To Next Hop Label Forwarding Entry (FEC-To-NHLFE)
                   Management Information Base (MIB)

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 (2004).

Abstract

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it describes managed objects for defining,
   configuring, and monitoring Forwarding Equivalence Class (FEC) to
   Next Hop Label Forwarding Entry (NHLFE) mappings and corresponding
   actions for use with Multiprotocol Label Switching (MPLS).

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  Terminology. . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Conventions Used In This Document. . . . . . . . . . . . . . .  3
   4.  The Internet-Standard Management Framework . . . . . . . . . .  3
   5.  Outline. . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
       5.1.  mplsFTNTable . . . . . . . . . . . . . . . . . . . . . .  4
             5.1.1.  Advantages of Address Ranges Over CIDR Prefixes.  4
       5.2.  mplsFTNMapTable. . . . . . . . . . . . . . . . . . . . .  5
             5.2.1.  Indexing Requirements. . . . . . . . . . . . . .  5
             5.2.2.  How the Current Indexing Works . . . . . . . . .  5
       5.3.  mplsFTNPerfTable . . . . . . . . . . . . . . . . . . . .  7
   6.  Avoiding Retrieval-Modification Interactions . . . . . . . . .  7

Nadeau, et al.              Standards Track                     [Page 1]
RFC 3814                      MPLS FTN MIB                     June 2004

   7.  Example Illustrating MIB Module Components . . . . . . . . . .  8
       7.1.  Sample FTN Rules . . . . . . . . . . . . . . . . . . . .  8
       7.2.  Creating FTN Entries and Applying them to Interfaces . .  9
       7.3.  Mapping an FTN Entry to Multiple Interfaces. . . . . . . 10
       7.4.  Inserting an Entry Into Existing List. . . . . . . . . . 11
       7.5.  Pictorial Tabular Relationship . . . . . . . . . . . . . 13
       7.6.  Deleting an Entry. . . . . . . . . . . . . . . . . . . . 14
   8.  The Use of RowPointer. . . . . . . . . . . . . . . . . . . . . 16
   9.  MPLS-FTN-STD-MIB Definitions . . . . . . . . . . . . . . . . . 16
   10. Security Considerations. . . . . . . . . . . . . . . . . . . . 38
   11. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 39
       11.1. IANA Considerations for MPLS-FTN-STD-MIB . . . . . . . . 39
   12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 39
       12.1. Normative References . . . . . . . . . . . . . . . . . . 39
       12.2. Informative References . . . . . . . . . . . . . . . . . 40
   13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 41
   14. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 41
   15. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 42

1.  Introduction

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it describes managed objects for specifying Forwarding
   Equivalence Class (FEC) to Next Hop Label Forwarding Entry (NHLFE)
   mappings and corresponding actions for Multiprotocol Label Switching
   (MPLS).

   At the ingress of an MPLS network, packets entering the MPLS domain
   are assigned to an FEC.  Those packets belonging to an FEC are
   associated with an NHLFE (i.e., MPLS label) via the FEC-to-NHLFE
   (FTN) mapping [RFC3031].  This relationship defines how ingress LSRs
   will impose MPLS labels onto incoming packets.  It also defines how
   egress LSRs will decapsulate the MPLS shim header from MPLS packets.

   Conceptually, some of the FTN table functionality could be
   implemented using the Forwarding Information Base (FIB) to map all
   packets destined for a prefix to an LSP.  However, this mapping is
   coarse in nature.

   Similar functionality is already being used in other contexts such as