metasystema.org
UpdatedPROPOSED STANDARDLegacy stream

RFC 3970: A Traffic Engineering (TE) MIB

Still current, but amended. Parts of this document are changed or extended by RFC 9141. Read both.

In plain English — editorial summary, not part of the RFC

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 Traffic Engineered (TE) Tunnels; for example, Multi-Protocol Label Switched Paths. [STANDARDS-TRACK]

Document record

Document ID
RFC3970
Published
January 2005
Authors
K. Kompella
Status
PROPOSED STANDARD
Stream
Legacy
Area
—
Pages
44
Also known as
—
Updated by:
RFC 9141

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/3970-a-traffic-engineering-te-mib