RFC 2669: DOCSIS Cable Device MIB Cable Device Management Information Base for DOCSIS compliant Cable Modems and Cable Modem Termination Systems
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4639.
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 defines a basic set of managed objects for SNMP-based management of DOCSIS 1.0 compliant Cable Modems and Cable Modem Termination Systems. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2669
- Published
- August 1999
- Authors
- M. St. Johns
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 55
- Also known as
- —
- Obsoleted by:
- RFC 4639
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.
- RFC 2662Definitions of Managed Objects for the ADSL LinesCurrent
August 1999
- RFC 2618RADIUS Authentication Client MIBObsoleted
June 1999
- RFC 2613Remote Network Monitoring MIB Extensions for Switched Networks Version 1.0Current
June 1999
- RFC 2742Definitions of Managed Objects for Extensible SNMP AgentsCurrent
January 2000
- RFC 2515Definitions of Managed Objects for ATM ManagementCurrent
February 1999
- RFC 2514Definitions of Textual Conventions and OBJECT-IDENTITIES for ATM ManagementCurrent
February 1999
- RFC 2513Managed Objects for Controlling the Collection and Storage of Accounting Information for Connection-Oriented NetworksCurrent
February 1999
- RFC 2512Accounting Information for ATM NetworksCurrent
February 1999
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?