RFC 2495: Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3895.
Current document in this lineage: RFC 4805 — Definitions of Managed Objects for the DS1, J1, E1, DS2, and E2 Interface Types
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 objects used for managing DS1, E1, DS2 and E2 interfaces. This document is a companion document with Definitions of Managed Objects for the DS0 (RFC 2494), DS3/E3 (RFC 2496), and the work in progress, SONET/SDH Interface Types. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2495
- Published
- January 1999
- Authors
- D. Fowler
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 75
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.
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.
- RFC 2496Definitions of Managed Object for the DS3/E3 Interface TypeObsoleted
January 1999
- RFC 2366Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM NetworksObsoleted
July 1998
- RFC 2667IP Tunnel MIBObsoleted
August 1999
- RFC 2233The Interfaces Group MIB using SMIv2Obsoleted
November 1997
- RFC 2837Definitions of Managed Objects for the Fabric Element in Fibre Channel StandardObsoleted
May 2000
- RFC 2020IEEE 802.12 Interface MIBCurrent
October 1996
- RFC 3197Applicability Statement for DNS MIB ExtensionsCurrent
November 2001
- RFC 1749IEEE 802.5 Station Source Routing MIB using SMIv2Current
December 1994
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?