RFC 3083: Baseline Privacy Interface Management Information Base for 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 SNMP-based (Simple Network Management Protocol) management of the Baseline Privacy Interface (BPI), which provides data privacy for DOCSIS 1.0 (Data-Over- Cable Service Interface Specifications) compliant Cable Modems and Cable Modem Termination Systems. This MIB is defined as an extension to the DOCSIS Radio Frequency Interface MIB, RFC 2670. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3083
- Published
- March 2001
- Authors
- R. Woundy
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 45
- 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.
- RFC 3144Remote Monitoring MIB Extensions for Interface Parameters MonitoringCurrent
August 2001
- RFC 3014Notification Log MIBCurrent
November 2000
- RFC 3165Definitions of Managed Objects for the Delegation of Management ScriptsCurrent
August 2001
- RFC 2982Distributed Management Expression MIBCurrent
October 2000
- RFC 2981Event MIBCurrent
October 2000
- RFC 2940Definitions of Managed Objects for Common Open Policy Service (COPS) Protocol ClientsCurrent
October 2000
- RFC 3231Definitions of Managed Objects for Scheduling Management OperationsCurrent
January 2002
- RFC 2925Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup OperationsObsoleted
September 2000
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?