RFC 4639: Cable Device Management Information Base for Data-Over-Cable Service Interface Specification (DOCSIS) Compliant Cable Modems and Cable Modem Termination Systems
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 Simple Network Management Protocol (SNMP)-based management of Data Over Cable Service Interface Specification (DOCSIS)-compliant Cable Modems and Cable Modem Termination Systems. This memo obsoletes RFC 2669. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4639
- Published
- December 2006
- Authors
- R. Woundy; K. Marez
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 88
- Also known as
- —
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 4682Multimedia Terminal Adapter (MTA) Management Information Base for PacketCable- and IPCablecom-Compliant DevicesUpdated
December 2006
- RFC 4710Real-time Application Quality-of-Service Monitoring (RAQMON) FrameworkCurrent
October 2006
- RFC 4712Transport Mappings for Real-time Application Quality-of-Service Monitoring (RAQMON) Protocol Data Unit (PDU)Updated
October 2006
- RFC 4547Event Notification Management Information Base for Data over Cable Service Interface Specifications (DOCSIS)-Compliant Cable Modems and Cable Modem Termination SystemsUpdated
June 2006
- RFC 4323Data Over Cable System Interface Specification Quality of Service Management Information Base (DOCSIS-QoS MIB)Updated
January 2006
- RFC 5066Ethernet in the First Mile Copper (EFMCu) Interfaces MIBUpdated
November 2007
- RFC 5098Signaling MIB for PacketCable and IPCablecom Multimedia Terminal Adapters (MTAs)Updated
February 2008
- RFC 4133Entity MIB (Version 3)Obsoleted
August 2005
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?