metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 3201: Definitions of Managed Objects for Circuit to Interface Translation

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 an extension of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the insertion of interesting Circuit Interfaces into the ifTable. This is important for circuits that must be used within other MIB modules which require an ifEntry. It allows for integrated monitoring of circuits as well as routing to circuits using unaltered, pre-existing MIB modules. [STANDARDS-TRACK]

Document record

Document ID
RFC3201
Published
January 2002
Authors
R. Steinberger; O. Nicklass
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
23
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/3201-definitions-of-managed-objects-for-circuit-to-interface-translation