datatracker.ietf.org
Sign in
Version 5.4.0, 2014-04-22
Report a bug

Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)
RFC 3812

Document type: RFC - Proposed Standard (June 2004)
Document stream: IETF
Last updated: 2013-03-02
Other versions: plain text, pdf, html

IETF State: WG Document
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: RFC 3812 (Proposed Standard)
Responsible AD: Alex Zinin
Send notices to: <swallow@cisco.com>, <loa@pi.se>

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

     Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
                   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 Multiprotocol Label
   Switching (MPLS) based traffic engineering (TE).

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  Terminology. . . . . . . . . . . . . . . . . . . . . . . . . .  2
   3.  The Internet-Standard Management Framework . . . . . . . . . .  3
   4.  Feature List . . . . . . . . . . . . . . . . . . . . . . . . .  3
   5.  Outline. . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
       5.1.  Summary of Traffic Engineering MIB Module. . . . . . . .  4
   6.  Brief Description of MIB Objects . . . . . . . . . . . . . . .  4
       6.1.  mplsTunnelTable. . . . . . . . . . . . . . . . . . . . .  4
       6.2.  mplsTunnelResourceTable. . . . . . . . . . . . . . . . .  5
       6.3.  mplsTunnelHopTable . . . . . . . . . . . . . . . . . . .  5
       6.4.  mplsTunnelARHopTable . . . . . . . . . . . . . . . . . .  5
       6.5.  mplsTunnelCHoptable. . . . . . . . . . . . . . . . . . .  5
       6.6.  mplsTunnelPerfTable. . . . . . . . . . . . . . . . . . .  6
       6.7.  mplsTunnelCRLDPResTable. . . . . . . . . . . . . . . . .  6
   7.  Use of 32-bit and 64-bit Counters. . . . . . . . . . . . . . .  6

Srinivasan, et al.          Standards Track                     [Page 1]
RFC 3812                    MPLS-TE-STD-MIB                    June 2004

   8.  Application of the Interface Group to MPLS Tunnels . . . . . .  6
       8.1.  Support of the MPLS Tunnel Interface by ifTable. . . . .  7
   9.  Example of Tunnel Setup. . . . . . . . . . . . . . . . . . . .  8
   10. The Use of RowPointer. . . . . . . . . . . . . . . . . . . . . 11
   11. MPLS Traffic Engineering MIB Definitions . . . . . . . . . . . 11
   12. Security Considerations. . . . . . . . . . . . . . . . . . . . 63
   13. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . 64
   14. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 64
       14.1. IANA Considerations for MPLS-TE-STD-MIB. . . . . . . . . 65
   15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 65
       15.1. Normative References . . . . . . . . . . . . . . . . . . 65
       15.2. Informative References . . . . . . . . . . . . . . . . . 66
   16. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 67
   17. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 68

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 modeling a
   Multiprotocol Label Switching (MPLS) [RFC3031] based traffic
   engineering.  This MIB module should be used in conjunction with the
   companion document [RFC3813] for MPLS based traffic engineering
   configuration and management.

   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 BCP 14, RFC 2119,
   reference [RFC2119].

2.  Terminology

   This document uses terminology from the MPLS architecture document
   [RFC3031] and MPLS Label Switch Router MIB [RFC3813].  Some
   frequently used terms are described next.

   An explicitly routed LSP (ERLSP) is referred to as an MPLS tunnel.
   It consists of in-segment(s) and/or out-segment(s) at the
   egress/ingress LSRs, each segment being associated with one MPLS

[include full document text]