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

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it…

Read RFC 3812 on the RFC Editor

Incoming relationships (13 related RFCs)

Normatively referenced by — RFC 3813: Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)
Normatively referenced by — RFC 6639: Multiprotocol Label Switching Transport Profile (MPLS-TP) MIB-Based Management Overview
Normatively referenced by — RFC 3814: Multiprotocol Label Switching (MPLS) Forwarding Equivalence Class To Next Hop Label Forwarding Entry (FEC-To-NHLFE) Management Information Base (MIB)
Normatively referenced by — RFC 4990: Use of Addresses in Generalized Multiprotocol Label Switching (GMPLS) Networks
Normatively referenced by — RFC 5605: Managed Objects for ATM over Packet Switched Networks (PSNs)
Normatively referenced by — RFC 7453: MPLS Transport Profile (MPLS-TP) Traffic Engineering (TE) Management Information Base (MIB)
Informatively referenced by — RFC 4874: Exclude Routes - Extension to Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)
Informatively referenced by — RFC 5521: Extensions to the Path Computation Element Communication Protocol (PCEP) for Route Exclusions
Informatively referenced by — RFC 3916: Requirements for Pseudo-Wire Emulation Edge-to-Edge (PWE3)
Informatively referenced by — RFC 4687: Operations and Management (OAM) Requirements for Point-to-Multipoint MPLS Networks
Informatively referenced by — RFC 6373: MPLS Transport Profile (MPLS-TP) Control Plane Framework
Informatively referenced by — RFC 7439: Gap Analysis for Operating IPv6-Only MPLS Networks
Informatively referenced by — RFC 6825: Traffic Engineering Database Management Information Base in Support of MPLS-TE/GMPLS