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, J1, E1, DS2, and E2 interfaces. This document is a companion to the documents that define managed objects for the DS0, DS3/E3, and Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface Types. This document obsoletes RFC 3895. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4805
- Published
- March 2007
- Authors
- O. Nicklass
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 94
- Also known as
- —
- Obsoletes:
- RFC 3895
Topics
Standards lineage
This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.
- RFC 1232 (1991)
- RFC 1406 (1993)
- RFC 2495 (1999)
- RFC 3895 (2004)
- RFC 4805 (2007)
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4801Definitions of Textual Conventions for Generalized Multiprotocol Label Switching (GMPLS) ManagementCurrent
February 2007
- RFC 4712Transport Mappings for Real-time Application Quality-of-Service Monitoring (RAQMON) Protocol Data Unit (PDU)Updated
October 2006
- RFC 4706Definitions of Managed Objects for Asymmetric Digital Subscriber Line 2 (ADSL2)Current
November 2006
- RFC 4939Definitions of Managed Objects for iSNS (Internet Storage Name Service)Current
July 2007
- RFC 4560Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup OperationsCurrent
June 2006
- RFC 4545Definitions of Managed Objects for IP Storage User Identity AuthorizationCurrent
May 2006
- RFC 5066Ethernet in the First Mile Copper (EFMCu) Interfaces MIBUpdated
November 2007
- RFC 4455Definition of Managed Objects for Small Computer System Interface (SCSI) EntitiesCurrent
April 2006
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?