Management Event Management Information Base (MIB) for PacketCable- and IPCablecom-Compliant Devices
RFC 5428
Network Working Group S. Channabasappa
Request for Comments: 5428 CableLabs
Category: Standards Track W. De Ketelaere
tComLabs
E. Nechamkin
Broadcom Corp.
April 2009
Management Event Management Information Base (MIB)
for PacketCable- and IPCablecom-Compliant Devices
Status of This Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Abstract
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 events that
can be generated by PacketCable- and IPCablecom-compliant Multimedia
Terminal Adapter devices.
Channabasappa, et al. Standards Track [Page 1]
RFC 5428 PacketCable/IPCablecom Event MTA MIB April 2009
Table of Contents
1. The Internet-Standard Management Framework ......................2
2. Introduction ....................................................2
3. Terminology .....................................................3
3.1. PacketCable ................................................3
3.2. IPCablecom .................................................3
3.3. MTA ........................................................4
3.4. Endpoint ...................................................4
3.5. MSO ........................................................4
3.6. UDP ........................................................4
4. Overview ........................................................4
4.1. Structure of the MIB .......................................5
4.2. pktcEventControl ...........................................6
4.3. pktcEventThrottle ..........................................6
4.4. pktcEventStatus ............................................7
4.5. pktcEvent ..................................................7
4.6. pktcEventLog ...............................................7
4.7. pktcEventNotifications .....................................7
5. Relationship to Other MIB Modules ...............................7
5.1. MIB Modules Required for IMPORTS ...........................7
6. Definitions .....................................................8
7. IANA Considerations ............................................32
8. Security Considerations ........................................32
9. Acknowledgments ................................................34
10. Normative References ..........................................35
11. Informative References ........................................36
1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580].
2. Introduction
A Multimedia Terminal Adapter (MTA) is used to deliver broadband
Internet, data, and/or voice access jointly with telephony service to
a subscriber's or customer's premises using a cable network
Channabasappa, et al. Standards Track [Page 2]
RFC 5428 PacketCable/IPCablecom Event MTA MIB April 2009
infrastructure. An MTA is normally installed at the subscriber's or
Show full document text