idnits 2.17.1
draft-ietf-ipcdn-docsisevent-mib-06.txt:
Checking boilerplate required by RFC 5378 and the IETF Trust (see
https://trustee.ietf.org/license-info):
----------------------------------------------------------------------------
** It looks like you're using RFC 3978 boilerplate. You should update this
to the boilerplate described in the IETF Trust License Policy document
(see https://trustee.ietf.org/license-info), which is required now.
-- Found old boilerplate from RFC 3978, Section 5.1.a on line 19.
-- Found old boilerplate from RFC 3978, Section 5.5 on line 1908.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1885.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1892.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1898.
** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure
Acknowledgement.
** This document has an original RFC 3978 Section 5.4 Copyright Line,
instead of the newer IETF Trust Copyright according to RFC 4748.
** This document has an original RFC 3978 Section 5.5 Disclaimer, instead
of the newer disclaimer which includes the IETF Trust according to RFC
4748.
** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate
instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission
of drafts without verbatim RFC 3978 boilerplate is not accepted.
The following non-3978 patterns matched text found in the document.
That text should be removed or replaced:
This document is an Internet-Draft and is subject to all provisions of
Section 3 of RFC 3667.
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she
becomes aware will be disclosed, in accordance with Section 6 of
BCP 79.
Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
----------------------------------------------------------------------------
== No 'Intended status' indicated for this document; assuming Proposed
Standard
Checking nits according to https://www.ietf.org/id-info/checklist :
----------------------------------------------------------------------------
No issues found here.
Miscellaneous warnings:
----------------------------------------------------------------------------
== The copyright year in the RFC 3978 Section 5.4 Copyright Line does not
match the current year
== The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but
does not include the phrase in its RFC 2119 key words list.
-- The document seems to lack a disclaimer for pre-RFC5378 work, but may
have content which was first submitted before 10 November 2008. If you
have contacted all the original authors and they are all willing to grant
the BCP78 rights to the IETF Trust, then this is fine, and you can ignore
this comment. If not, you may need to add the pre-RFC5378 disclaimer.
(See the Legal Provisions document at
https://trustee.ietf.org/license-info for more information.)
-- The document date (January 11, 2005) is 7044 days in the past. Is this
intentional?
Checking references for intended status: Proposed Standard
----------------------------------------------------------------------------
(See RFCs 3967 and 4897 for information about using normative references
to lower-maturity documents in RFCs)
** Obsolete normative reference: RFC 2669 (ref. '5') (Obsoleted by RFC 4639)
-- Possible downref: Non-RFC (?) normative reference: ref. '6'
-- Possible downref: Non-RFC (?) normative reference: ref. '8'
-- Possible downref: Non-RFC (?) normative reference: ref. '9'
-- Possible downref: Non-RFC (?) normative reference: ref. '10'
-- Possible downref: Non-RFC (?) normative reference: ref. '11'
-- Possible downref: Non-RFC (?) normative reference: ref. '12'
-- Possible downref: Non-RFC (?) normative reference: ref. '13'
-- Possible downref: Non-RFC (?) normative reference: ref. '14'
-- Possible downref: Non-RFC (?) normative reference: ref. '15'
Summary: 6 errors (**), 0 flaws (~~), 3 warnings (==), 16 comments (--).
Run idnits with the --verbose option for more detailed information about
the items above.
--------------------------------------------------------------------------------
2 IPCDN Working Group A. Ahmad
3 Internet-Draft Protego Networks, Inc.
4 Expires: July 12, 2005 G. Nakanishi
5 Motorola
6 January 11, 2005
8 Event Notification Management Information Base for DOCSIS Compliant
9 Cable Modems and Cable Modem Termination Systems
10 draft-ietf-ipcdn-docsisevent-mib-06
12 Status of this Memo
14 This document is an Internet-Draft and is subject to all provisions
15 of section 3 of RFC 3667. By submitting this Internet-Draft, each
16 author represents that any applicable patent or other IPR claims of
17 which he or she is aware have been or will be disclosed, and any of
18 which he or she become aware will be disclosed, in accordance with
19 RFC 3668.
21 Internet-Drafts are working documents of the Internet Engineering
22 Task Force (IETF), its areas, and its working groups. Note that
23 other groups may also distribute working documents as
24 Internet-Drafts.
26 Internet-Drafts are draft documents valid for a maximum of six months
27 and may be updated, replaced, or obsoleted by other documents at any
28 time. It is inappropriate to use Internet-Drafts as reference
29 material or to cite them other than as "work in progress."
31 The list of current Internet-Drafts can be accessed at
32 http://www.ietf.org/ietf/1id-abstracts.txt.
34 The list of Internet-Draft Shadow Directories can be accessed at
35 http://www.ietf.org/shadow.html.
37 This Internet-Draft will expire on July 12, 2005.
39 Copyright Notice
41 Copyright (C) The Internet Society (2005).
43 Abstract
45 This memo defines a portion of the Management Information Base (MIB)
46 for use with network management protocols in the Internet community.
47 In particular, it defines a basic set of managed objects for SNMP-
48 based event notification management of DOCSIS compliant Cable Modems
49 and Cable Modem Termination Systems. This MIB is defined as an
50 extension to the DOCSIS Cable Device MIB.
52 This memo specifies a MIB module in a manner that is compliant to the
53 SMIv2. The set of objects is consistent with the SNMP framework and
54 existing SNMP standards.
56 This memo is a product of the IPCDN working group within the Internet
57 Engineering Task Force. Comments are solicited and should be
58 addressed to the working group's mailing list at ipcdn@ietf.org
59 and/or the author.
61 Table of Contents
63 1. The Internet-Standard Management Framework . . . . . . . . . 3
64 2. Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . 3
65 2.1 BPI - Baseline Privacy Interface . . . . . . . . . . . . . 3
66 2.2 BPI - Baseline Privacy Plus Interface . . . . . . . . . . 3
67 2.3 CATV . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
68 2.4 CM - Cable Modem . . . . . . . . . . . . . . . . . . . . . 3
69 2.5 CMTS - Cable Modem Termination System . . . . . . . . . . 3
70 2.6 DOCSIS . . . . . . . . . . . . . . . . . . . . . . . . . . 4
71 2.7 Downstream . . . . . . . . . . . . . . . . . . . . . . . . 4
72 2.8 Head-end . . . . . . . . . . . . . . . . . . . . . . . . . 4
73 2.9 MAC Packet . . . . . . . . . . . . . . . . . . . . . . . . 4
74 2.10 RF . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
75 2.11 SID . . . . . . . . . . . . . . . . . . . . . . . . . . 4
76 2.12 TLV . . . . . . . . . . . . . . . . . . . . . . . . . . 4
77 2.13 Upstream . . . . . . . . . . . . . . . . . . . . . . . . 5
78 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 5
79 3.1 Structure of the MIB . . . . . . . . . . . . . . . . . . . 5
80 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . 6
81 5. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 37
82 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 37
83 7. Security Consideration . . . . . . . . . . . . . . . . . . . 37
84 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . 38
85 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 38
86 9.1 Normative References . . . . . . . . . . . . . . . . . . . . 38
87 9.2 Informative References . . . . . . . . . . . . . . . . . . . 40
88 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 40
89 Intellectual Property and Copyright Statements . . . . . . . 41
91 1. The Internet-Standard Management Framework
93 For a detailed overview of the documents that describe the current
94 Internet-Standard Management Framework, please refer to section 7 of
95 RFC 3410 [16].
97 Managed objects are accessed via a virtual information store, termed
98 the Management Information Base or MIB. MIB objects are generally
99 accessed through the Simple Network Management Protocol (SNMP).
100 Objects in the MIB are defined using the mechanisms defined in the
101 Structure of Management Information (SMI). This memo specifies a MIB
102 module that is compliant to the SMIv2, which is described in STD 58,
103 RFC 2578 [2], STD 58, RFC 2579 [3] and STD 58, RFC 2580 [4].
105 2. Glossary
107 The terms in this document are derived either from normal cable
108 system usage, or from the documents associated with the Data Over
109 Cable Service Interface Specification (DOCSIS) process.
111 2.1 BPI - Baseline Privacy Interface
113 A mechanism for providing data privacy over the HFC network in DOCSIS
114 1.0 systems[8].
116 2.2 BPI - Baseline Privacy Plus Interface
118 A mechanism that extend the Baseline Privacy Interface with the
119 addition of CM authentication over the HFC network in DOCSIS1.1/2.0
120 system and beyond [9].
122 2.3 CATV
124 Originally "Community Antenna Television", now used to refer to any
125 cable or hybrid fiber and cable system used to deliver video signals
126 to a community.
128 2.4 CM - Cable Modem
130 A CM acts as a "slave" station in a DOCSIS compliant cable data
131 system.
133 2.5 CMTS - Cable Modem Termination System
135 A generic term covering a cable bridge or cable router in a head-end.
136 A CMTS acts as the master station in a DOCSIS compliant cable data
137 system. It is the only station that transmits downstream, and it
138 controls the scheduling of upstream transmissions by its associated
139 CMs.
141 2.6 DOCSIS
143 DOCSIS stands for "Data-Over-Cable Service Interface Specifications"
144 and refers to the ITU-T J.112 Annex B standard for cable modem
145 systems [10], [13] commonly known as DOCSIS 1.0. The DOCSIS 1.1
146 specification is an extension of DOCSIS 1.0, with new features to
147 support quality of service, fragmentation, and requirements for
148 European cable plants [14].
150 DOCSIS 2.0 [15] builds upon DOCSIS 1.1, and provides all of the
151 features and functionality that DOCSIS 1.1 provides. In addition, it
152 provides some significant enhancements in upstream capacity over
153 DOCSIS 1.1, such as 30.72 Mbps maximum upstream channel capacity,
154 Synchronous-Code Division Multiple Access (CDMA) operation, increased
155 robustness to upstream noise and channel impairments, Enhanced
156 Reed-Solomon error correction and, Trellis Coded Modulation.
158 2.7 Downstream
160 The direction from the CMTS to the CM.
162 2.8 Head-end
164 The origination point in most cable systems of the subscriber video
165 signals. Generally also the location of the CMTS equipment.
167 2.9 MAC Packet
169 A term referring to DOCSIS Protocol Data Unit (PDU).
171 2.10 RF
173 A term referring to Radio Frequency.
175 2.11 SID
177 A term referring to DOCSIS Service ID. The SID identifies a
178 particular upstream bandwidth allocation and class-of-service
179 management for DOCSIS, and identifies a particular bidirectional
180 security association for BPI.
182 2.12 TLV
184 TLV stands for Type/Length/Value. TLV is an encoding method
185 consisting of three fields. The first field indicates the type of
186 element, the second field indicates the length of the element, and
187 the third field contains the element's value.
189 2.13 Upstream
191 The direction from the CM to the CMTS.
193 3. Overview
195 High Speed Internet Service offering in cable industry has become
196 extremely successful. DOCSIS devices are being deployed at a rate of
197 multiple thousands per day. Although operators are enjoying
198 successful deployment, they are also facing a challenge to properly
199 manage deployed devices. Operators are using Simple Network
200 Management Protocol, a set of Management Information Base (MIB)
201 required by DOCSIS, and SNMP Notifications to manage deployed DOCSIS
202 devices. The usage of SNMP Notification for event reporting is
203 becoming more popular as an effective and efficient method for
204 network monitoring.
206 Unfortunately, only a minimal set of SNMP Notifications is currently
207 available. This notification MIB in conjunction with [11] and [12]
208 provide a minimum set of standard DOCSIS Notifications that DOCSIS
209 devices SHOULD support to enable successful management of DOCSIS
210 devices and network.
212 This document defines a set of objects required for the event
213 notification management of DOCSIS compliant Cable Modems (CMs) and
214 Cable Modem Termination Systems (CMTSs). The MIB module is derived
215 from the DOCSIS [11] and [12].
217 The Appendix H of [11] defines all DOCSIS 1.1 required events and the
218 Appendix D of [12] does that for DOCSIS 2.0. The notifications
219 specified in this document are used to notify these events via SNMP.
221 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
222 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
223 document are to be interpreted as described in RFC 2119 [1].
225 3.1 Structure of the MIB
227 This DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB was designed to extend
228 the RFC2669 [5] notification module.
230 Two groups of SNMP notification objects are defined in this document.
231 One group defines notifications for cable modem events, and the other
232 group defines notifications for cable modem termination system
233 events.
235 DOCSIS defines numerous events and each event is assigned to a
236 functional category. This MIB defines a notification object for each
237 functional category. The varbinding list of each notification
238 includes information about the event that occurred on the device.
240 4. Definitions
242 The MIB module defined here IMPORTs from SNMPv2-SMI[2],
243 SNMPv2-CONF[3], DOCS-CABLE-DEVICE-MIB [5], DOCS-IF-MIB [6], and
244 IF-MIB [7].
246 DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB DEFINITIONS ::= BEGIN
248 IMPORTS
249 MODULE-IDENTITY,
250 OBJECT-TYPE,
251 NOTIFICATION-TYPE,
252 mib-2
253 FROM SNMPv2-SMI -- RFC 2578
254 MODULE-COMPLIANCE,
255 OBJECT-GROUP,
256 NOTIFICATION-GROUP
257 FROM SNMPv2-CONF -- RFC 2580
259 docsDevEvLevel,
260 docsDevEvId,
261 docsDevEvText,
262 docsDevSwFilename,
263 docsDevSwServer,
264 docsDevServerDhcp,
265 docsDevServerTime
266 FROM DOCS-CABLE-DEVICE-MIB -- RFC 2669
268 docsIfCmCmtsAddress,
269 docsIfCmtsCmStatusMacAddress,
270 docsIfDocsisBaseCapability,
271 docsIfCmStatusDocsisOperMode,
272 docsIfCmStatusModulationType,
273 docsIfCmtsCmStatusDocsisRegMode,
274 docsIfCmtsCmStatusModulationType
275 FROM DOCS-IF-MIB -- draft-ietf-ipcdn-docs-rfmibv2-10
277 -- RFC ED.: replace 'draft-ietf-ipcdn-docs-rfmibv2-10' with assigned
278 -- RFC number and remove this note.
280 ifPhysAddress
281 FROM IF-MIB; -- RFC 2863
283 docsDevNotifMIB MODULE-IDENTITY
285 LAST-UPDATED "200501110000Z" -- January 11, 2005
286 ORGANIZATION "IETF IP over Cable Data Network
287 Working Group"
288 CONTACT-INFO
289 " Azlina Ahmad
290 Postal: Protego Networks, Inc.
291 1064 Yosemite Drive
292 Milpitas, CA 95035, U.S.A.
293 Phone: 408 262 5220
294 E-mail: azlina@protegonetworks.com
296 Greg Nakanishi
297 Postal: Motorola
298 6450 Sequence Drive
299 San Diego, CA 92121, U.S.A.
300 Phone: 858 404 2366
301 E-mail: gnakanishi@motorola.com
303 IETF IPCDN Working Group
304 General Discussion: ipcdn@ietf.org
305 Subscribe: http://www.ietf.org/mailman/listinfo/ipcdn
306 Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
307 Co-chairs: Richard Woundy,
308 richard_woundy@cable.comcast.com
309 Jean-Francois Mule, jf.mule@cablelabs.com"
311 DESCRIPTION
312 "The Event Notification MIB is an extension of the
313 CABLE DEVICE MIB. It defines various notification
314 objects for both cable modem and cable modem termination
315 systems. Two groups of SNMP notification objects are
316 defined. One group is for notifying cable modem events
317 and one group for notifying cable modem termination
318 system events.
320 DOCSIS defines numerous events and each event is
321 assigned to a functional category. This MIB defines
322 a notification object for each functional category.
323 The varbinding list of each notification includes
324 information about the event that occurred on the
325 device.
327 Copyright (C) The Internet Society (2005). This version
328 of this MIB module is part of RFC yyyy; see the RFC
329 itself for full legal notices."
331 -- RFC Ed.: replace yyyy with actual RFC number & remove this note
333 REVISION "200501110000Z" -- January 11, 2005
334 DESCRIPTION
335 "Initial version, published as RFC yyyy."
337 -- RFC Ed.: replace yyyy with actual RFC number & remove this note
339 ::= { mib-2 xxx }
341 -- Editor's Note (to be removed prior to publication):
342 -- the IANA is requested to assign a value for "xxx" under
343 -- the 'mib-2'subtree and to record the assignment in the
344 -- SMI Numbers registry.
345 -- When the assignment has been made, the RFC Editor is asked to
346 -- replace "xxx" (here and in the MIB module) with the assigned
347 -- value and to remove this note.
349 docsDevNotifControl OBJECT IDENTIFIER ::= { docsDevNotifMIB 1}
350 docsDevCmNotifs OBJECT IDENTIFIER ::= { docsDevNotifMIB 2 0 }
351 docsDevCmtsNotifs OBJECT IDENTIFIER ::= { docsDevNotifMIB 3 0 }
353 docsDevCmNotifControl OBJECT-TYPE
354 SYNTAX BITS {
355 cmInitTLVUnknownNotif( 0),
356 cmDynServReqFailNotif( 1),
357 cmDynServRspFailNotif( 2),
358 cmDynServAckFailNotif( 3),
359 cmBpiInitNotif( 4),
360 cmBPKMNotif( 5),
361 cmDynamicSANotif( 6),
362 cmDHCPFailNotif( 7),
363 cmSwUpgradeInitNotif( 8),
364 cmSwUpgradeFailNotif( 9),
365 cmSwUpgradeSuccessNotif( 10),
366 cmSwUpgradeCVCNotif( 11),
367 cmTODFailNotif( 12),
368 cmDCCReqFailNotif( 13),
369 cmDCCRspFailNotif( 14),
370 cmDCCAckFailNotif( 15)
371 }
372 MAX-ACCESS read-write
374 STATUS current
375 DESCRIPTION
376 "The object is used to enable specific CM notifications.
377 For example, if the first bit is set, then
378 docsDevCmInitTLVUnknownNotif is enabled. If it is not set,
379 the notification is disabled. Note that notifications are
380 also under the control of the MIB modules defined in
381 RFC3413.
383 If the device is rebooted,the value of this object SHOULD
384 revert to the default value.
385 "
386 DEFVAL { {} }
387 ::= { docsDevNotifControl 1 }
389 docsDevCmtsNotifControl OBJECT-TYPE
390 SYNTAX BITS {
391 cmtsInitRegReqFailNotif( 0),
392 cmtsInitRegRspFailNotif( 1),
393 cmtsInitRegAckFailNotif( 2),
394 cmtsDynServReqFailNotif( 3),
395 cmtsDynServRspFailNotif( 4),
396 cmtsDynServAckFailNotif( 5),
397 cmtsBpiInitNotif( 6),
398 cmtsBPKMNotif( 7),
399 cmtsDynamicSANotif( 8),
400 cmtsDCCReqFailNotif( 9),
401 cmtsDCCRspFailNotif( 10),
402 cmtsDCCAckFailNotif( 11)
403 }
404 MAX-ACCESS read-write
405 STATUS current
406 DESCRIPTION
407 "The object is used to enable specific CMTS notifications.
408 For example, if the first bit is set, then
409 docsDevCmtsInitRegRspFailNotif is enabled. If it is not set,
410 the notification is disabled. Note that notifications are
411 also under the control of the MIB modules defined in
412 RFC3413.
414 If the device is rebooted,the value of this object SHOULD
415 revert to the default value.
416 "
417 DEFVAL { {} }
418 ::= { docsDevNotifControl 2 }
420 docsDevCmInitTLVUnknownNotif NOTIFICATION-TYPE
421 OBJECTS {
422 docsDevEvLevel,
423 docsDevEvId,
424 docsDevEvText,
425 ifPhysAddress,
426 docsIfCmCmtsAddress,
427 docsIfDocsisBaseCapability,
428 docsIfCmStatusDocsisOperMode,
429 docsIfCmStatusModulationType
430 }
431 STATUS current
432 DESCRIPTION
433 "Notification to indicate that an unknown TLV was
434 encountered during the TLV parsing process.
436 This notification sends additional information about
437 the event by including the following objects in it's
438 varbinding list.
439 - docsDevEvLevel: the priority level associated with the
440 event.
441 - docsDevEvId: the unique identifier of the event that
442 occurred.
443 - docsDevEvText: a textual description of the event.
444 - ifPhysAddress: the MAC address of the cable
445 interface of this cable modem.
446 - docsIfCmCmtsAddress: the MAC address of the CMTS
447 to which the CM is connected to(if there is a cable
448 card/ interface in the CMTS, then it is actually the
449 MAC address of the cable interface which connected to.
450 - docsIfDocsisBaseCapability: the highest
451 version of the DOCSIS specification(1.0, 1.1, 2.0)
452 that the device is capable of supporting.
453 - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1)
454 that the CM is operating in.
455 - docsIfCmStatusModulationType the upstream modulation
456 methodology used by the CM the CM).
457 "
458 ::= { docsDevCmNotifs 1 }
460 docsDevCmDynServReqFailNotif NOTIFICATION-TYPE
461 OBJECTS {
462 docsDevEvLevel,
463 docsDevEvId,
464 docsDevEvText,
465 ifPhysAddress,
466 docsIfCmCmtsAddress,
467 docsIfDocsisBaseCapability,
468 docsIfCmStatusDocsisOperMode,
469 docsIfCmStatusModulationType
471 }
472 STATUS current
473 DESCRIPTION
475 "A notification to report the failure of a dynamic service
476 request during the dynamic services process.
478 This notification sends additional information about
479 the event by including the following objects in it's
480 varbinding list.
481 - docsDevEvLevel: the priority level associated with the
482 event.
483 - docsDevEvId: the unique identifier of the event that
484 occurred.
485 - docsDevEvText: a textual description of the event.
486 - ifPhysAddress: the MAC address of the cable
487 interface of this cable modem.
488 - docsIfCmCmtsAddress: the MAC address of the CMTS
489 to which the CM is connected to(if there is a cable
490 card/ interface in the CMTS, then it is actually the
491 MAC address of the cable interface which connected to.
492 - docsIfDocsisBaseCapability: the highest
493 version of the DOCSIS specification(1.0, 1.1, 2.0)
494 that the device is capable of supporting.
495 - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1)
496 that the CM is operating in.
497 - docsIfCmStatusModulationType the upstream modulation
498 methodology used by the CM the CM).
499 "
500 ::= { docsDevCmNotifs 2 }
502 docsDevCmDynServRspFailNotif NOTIFICATION-TYPE
503 OBJECTS {
504 docsDevEvLevel,
505 docsDevEvId,
506 docsDevEvText,
507 ifPhysAddress,
508 docsIfCmCmtsAddress,
509 docsIfDocsisBaseCapability,
510 docsIfCmStatusDocsisOperMode,
511 docsIfCmStatusModulationType
512 }
514 STATUS current
516 DESCRIPTION
517 " A notification to report the failure of a dynamic service
518 response during the dynamic services process.
520 This notification sends additional information about
521 the event by including the following objects in it's
522 varbinding list.
523 - docsDevEvLevel: the priority level associated with the
524 event.
525 - docsDevEvId: the unique identifier of the event that
526 occurred.
527 - docsDevEvText: a textual description of the event.
528 - ifPhysAddress: the MAC address of the cable
529 interface of this cable modem.
530 - docsIfCmCmtsAddress: the MAC address of the CMTS
531 to which the CM is connected to(if there is a cable
532 card/ interface in the CMTS, then it is actually the
533 MAC address of the cable interface which connected to.
534 - docsIfDocsisBaseCapability: the highest
535 version of the DOCSIS specification(1.0, 1.1, 2.0)
536 that the device is capable of supporting.
537 - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1)
538 that the CM is operating in.
539 - docsIfCmStatusModulationType the upstream modulation
540 methodology used by the CM the CM).
541 "
542 ::= { docsDevCmNotifs 3}
544 docsDevCmDynServAckFailNotif NOTIFICATION-TYPE
545 OBJECTS {
546 docsDevEvLevel,
547 docsDevEvId,
548 docsDevEvText,
549 ifPhysAddress,
550 docsIfCmCmtsAddress,
551 docsIfDocsisBaseCapability,
552 docsIfCmStatusDocsisOperMode,
553 docsIfCmStatusModulationType
554 }
555 STATUS current
556 DESCRIPTION
557 "A notification to report the failure of a dynamic service
558 acknowledgement during the dynamic services process.
560 This notification sends additional information about
561 the event by including the following objects in it's
562 varbinding list.
563 - docsDevEvLevel: the priority level associated with the
564 event.
565 - docsDevEvId: the unique identifier of the event that
566 occurred.
567 - docsDevEvText: a textual description of the event.
568 - ifPhysAddress: the MAC address of the cable
569 interface of this cable modem.
570 - docsIfCmCmtsAddress: the MAC address of the CMTS
571 to which the CM is connected to(if there is a cable
572 card/ interface in the CMTS, then it is actually the
573 MAC address of the cable interface which connected to.
574 - docsIfDocsisBaseCapability: the highest
575 version of the DOCSIS specification(1.0, 1.1, 2.0)
576 that the device is capable of supporting.
577 - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1)
578 that the CM is operating in.
579 - docsIfCmStatusModulationType the upstream modulation
580 methodology used by the CM the CM).
581 "
582 ::= { docsDevCmNotifs 4}
584 docsDevCmBpiInitNotif NOTIFICATION-TYPE
585 OBJECTS {
586 docsDevEvLevel,
587 docsDevEvId,
588 docsDevEvText,
589 ifPhysAddress,
590 docsIfCmCmtsAddress,
591 docsIfDocsisBaseCapability,
592 docsIfCmStatusDocsisOperMode,
593 docsIfCmStatusModulationType
594 }
595 STATUS current
596 DESCRIPTION
597 "A notification to report the failure of a BPI
598 initialization attempt during the registration process.
600 This notification sends additional information about
601 the event by including the following objects in it's
602 varbinding list.
603 - docsDevEvLevel: the priority level associated with the
604 event.
605 - docsDevEvId: the unique identifier of the event that
606 occurred.
607 - docsDevEvText: a textual description of the event.
608 - ifPhysAddress: the MAC address of the cable
609 interface of this cable modem.
610 - docsIfCmCmtsAddress: the MAC address of the CMTS
611 to which the CM is connected to(if there is a cable
612 card/ interface in the CMTS, then it is actually the
613 MAC address of the cable interface which connected to.
614 - docsIfDocsisBaseCapability: the highest
615 version of the DOCSIS specification(1.0, 1.1, 2.0)
616 that the device is capable of supporting.
617 - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1)
618 that the CM is operating in.
619 - docsIfCmStatusModulationType the upstream modulation
620 methodology used by the CM the CM).
621 "
622 ::= { docsDevCmNotifs 5 }
624 docsDevCmBPKMNotif NOTIFICATION-TYPE
625 OBJECTS {
626 docsDevEvLevel,
627 docsDevEvId,
628 docsDevEvText,
629 ifPhysAddress,
630 docsIfCmCmtsAddress,
631 docsIfDocsisBaseCapability,
632 docsIfCmStatusDocsisOperMode,
633 docsIfCmStatusModulationType
634 }
635 STATUS current
636 DESCRIPTION
637 "A notification to report the failure of a Baseline
638 Privacy Key Management (BPKM) operation.
640 This notification sends additional information about
641 the event by including the following objects in it's
642 varbinding list.
643 - docsDevEvLevel: the priority level associated with the
644 event.
645 - docsDevEvId: the unique identifier of the event that
646 occurred.
647 - docsDevEvText: a textual description of the event.
648 - ifPhysAddress: the MAC address of the cable
649 interface of this cable modem.
650 - docsIfCmCmtsAddress: the MAC address of the CMTS
651 to which the CM is connected to(if there is a cable
652 card/ interface in the CMTS, then it is actually the
653 MAC address of the cable interface which connected to.
654 - docsIfDocsisBaseCapability: the highest
655 version of the DOCSIS specification(1.0, 1.1, 2.0)
656 that the device is capable of supporting.
657 - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1)
658 that the CM is operating in.
659 - docsIfCmStatusModulationType the upstream modulation
660 methodology used by the CM the CM).
661 "
663 ::= { docsDevCmNotifs 6 }
665 docsDevCmDynamicSANotif NOTIFICATION-TYPE
666 OBJECTS {
667 docsDevEvLevel,
668 docsDevEvId,
669 docsDevEvText,
670 ifPhysAddress,
671 docsIfCmCmtsAddress,
672 docsIfDocsisBaseCapability,
673 docsIfCmStatusDocsisOperMode,
674 docsIfCmStatusModulationType
675 }
676 STATUS current
677 DESCRIPTION
678 "A notification to report the failure of a dynamic security
679 association operation.
681 This notification sends additional information about
682 the event by including the following objects in it's
683 varbinding list.
684 - docsDevEvLevel: the priority level associated with the
685 event.
686 - docsDevEvId: the unique identifier of the event that
687 occurred.
688 - docsDevEvText: a textual description of the event.
689 - ifPhysAddress: the MAC address of the cable
690 interface of this cable modem.
691 - docsIfCmCmtsAddress: the MAC address of the CMTS
692 to which the CM is connected to(if there is a cable
693 card/ interface in the CMTS, then it is actually the
694 MAC address of the cable interface which connected to.
695 - docsIfDocsisBaseCapability: the highest
696 version of the DOCSIS specification(1.0, 1.1, 2.0)
697 that the device is capable of supporting.
698 - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1)
699 that the CM is operating in.
700 - docsIfCmStatusModulationType the upstream modulation
701 methodology used by the CM the CM).
702 "
703 ::= { docsDevCmNotifs 7 }
705 docsDevCmDHCPFailNotif NOTIFICATION-TYPE
706 OBJECTS {
707 docsDevEvLevel,
708 docsDevEvId,
709 docsDevEvText,
710 ifPhysAddress,
711 docsIfCmCmtsAddress,
712 docsDevServerDhcp,
713 docsIfDocsisBaseCapability,
714 docsIfCmStatusDocsisOperMode,
715 docsIfCmStatusModulationType
716 }
717 STATUS current
719 DESCRIPTION
720 "A notification to report the failure of a DHCP operation.
722 This notification sends additional information about
723 the event by including the following objects in it's
724 varbinding list.
725 - docsDevEvLevel: the priority level associated with the
726 event.
727 - docsDevEvId: the unique identifier of the event that
728 occurred.
729 - docsDevEvText: a textual description of the event.
730 - ifPhysAddress: the MAC address of the cable
731 interface of this cable modem.
732 - docsIfCmCmtsAddress: the MAC address of the CMTS
733 to which the CM is connected to(if there is a cable
734 card/ interface in the CMTS, then it is actually the
735 MAC address of the cable interface which connected to.
736 - docsDevServerDhcp: the IP address of the DHCP server.
737 - docsIfDocsisBaseCapability: the highest
738 version of the DOCSIS specification(1.0, 1.1, 2.0)
739 that the device is capable of supporting.
740 - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1)
741 that the CM is operating in.
742 - docsIfCmStatusModulationType the upstream modulation
743 methodology used by the CM the CM).
744 "
745 ::= { docsDevCmNotifs 8 }
747 docsDevCmSwUpgradeInitNotif NOTIFICATION-TYPE
748 OBJECTS {
749 docsDevEvLevel,
750 docsDevEvId,
751 docsDevEvText,
752 ifPhysAddress,
753 docsIfCmCmtsAddress,
754 docsDevSwFilename,
755 docsDevSwServer,
756 docsIfDocsisBaseCapability,
757 docsIfCmStatusDocsisOperMode,
758 docsIfCmStatusModulationType
759 }
760 STATUS current
761 DESCRIPTION
762 "A notification to indicate that a software upgrade
763 has been initiated on the device.
765 This notification sends additional information about
766 the event by including the following objects in it's
767 varbinding list.
768 - docsDevEvLevel: the priority level associated with the
769 event.
770 - docsDevEvId: the unique identifier of the event that
771 occurred.
772 - docsDevEvText: a textual description of the event.
773 - ifPhysAddress: the MAC address of the cable
774 interface of this cable modem.
775 - docsIfCmCmtsAddress: the MAC address of the CMTS
776 to which the CM is connected to(if there is a cable
777 card/ interface in the CMTS, then it is actually the
778 MAC address of the cable interface which connected to.
779 - docsIfDocsisBaseCapability: the highest
780 version of the DOCSIS specification(1.0, 1.1, 2.0)
781 that the device is capable of supporting.
782 - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1)
783 that the CM is operating in.
784 - docsIfCmStatusModulationType the upstream modulation
785 methodology used by the CM the CM).
786 "
787 ::= { docsDevCmNotifs 9 }
789 docsDevCmSwUpgradeFailNotif NOTIFICATION-TYPE
790 OBJECTS {
791 docsDevEvLevel,
792 docsDevEvId,
793 docsDevEvText,
794 ifPhysAddress,
795 docsIfCmCmtsAddress,
796 docsDevSwFilename,
797 docsDevSwServer,
798 docsIfDocsisBaseCapability,
799 docsIfCmStatusDocsisOperMode,
800 docsIfCmStatusModulationType
801 }
802 STATUS current
803 DESCRIPTION
804 "A notification to report the failure of a software upgrade
805 attempt.
807 This notification sends additional information about
808 the event by including the following objects in it's
809 varbinding list.
810 - docsDevEvLevel: the priority level associated with the
811 event.
812 - docsDevEvId: the unique identifier of the event that
813 occurred.
814 - docsDevEvText: a textual description of the event.
815 - ifPhysAddress: the MAC address of the cable
816 interface of this cable modem.
817 - docsIfCmCmtsAddress: the MAC address of the CMTS
818 to which the CM is connected to(if there is a cable
819 card/ interface in the CMTS, then it is actually the
820 MAC address of the cable interface which connected to.
821 - docsDevSwFilename: the software image file name
822 - docsDevSwServer: the IP address of the server that
823 the image is retrieved from.
824 - docsIfDocsisBaseCapability: the highest
825 version of the DOCSIS specification(1.0, 1.1, 2.0)
826 that the device is capable of supporting.
827 - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1)
828 that the CM is operating in.
829 - docsIfCmStatusModulationType the upstream modulation
830 methodology used by the CM the CM).
831 "
832 ::= { docsDevCmNotifs 10 }
834 docsDevCmSwUpgradeSuccessNotif NOTIFICATION-TYPE
835 OBJECTS {
836 docsDevEvLevel,
837 docsDevEvId,
838 docsDevEvText,
839 ifPhysAddress,
840 docsIfCmCmtsAddress,
841 docsDevSwFilename,
842 docsDevSwServer,
843 docsIfDocsisBaseCapability,
844 docsIfCmStatusDocsisOperMode,
845 docsIfCmStatusModulationType
847 }
848 STATUS current
849 DESCRIPTION
850 "A notification to report the software upgrade success
851 status.
853 This notification sends additional information about
854 the event by including the following objects in it's
855 varbinding list.
856 - docsDevEvLevel: the priority level associated with the
857 event.
858 - docsDevEvId: the unique identifier of the event that
859 occurred.
860 - docsDevEvText: a textual description of the event.
861 - ifPhysAddress: the MAC address of the cable
862 interface of this cable modem.
863 - docsIfCmCmtsAddress: the MAC address of the CMTS
864 to which the CM is connected to(if there is a cable
865 card/ interface in the CMTS, then it is actually the
866 MAC address of the cable interface which connected to.
867 - docsDevSwFilename: the software image file name
868 - docsDevSwServer: the IP address of the server that
869 the image is retrieved from.
870 - docsIfDocsisBaseCapability: the highest
871 version of the DOCSIS specification(1.0, 1.1, 2.0)
872 that the device is capable of supporting.
873 - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1)
874 that the CM is operating in.
875 - docsIfCmStatusModulationType the upstream modulation
876 methodology used by the CM the CM).
877 "
879 ::= { docsDevCmNotifs 11 }
881 docsDevCmSwUpgradeCVCFailNotif NOTIFICATION-TYPE
882 OBJECTS {
883 docsDevEvLevel,
884 docsDevEvId,
885 docsDevEvText,
886 ifPhysAddress,
887 docsIfCmCmtsAddress,
888 docsIfDocsisBaseCapability,
889 docsIfCmStatusDocsisOperMode,
890 docsIfCmStatusModulationType
891 }
892 STATUS current
893 DESCRIPTION
894 "A notification to report that the verification of the
895 code file has failed during a secure software upgrade
896 attempt.
898 This notification sends additional information about
899 the event by including the following objects in it's
900 varbinding list.
901 - docsDevEvLevel: the priority level associated with the
902 event.
903 - docsDevEvId: the unique identifier of the event that
904 occurred.
905 - docsDevEvText: a textual description of the event.
906 - ifPhysAddress: the MAC address of the cable
907 interface of this cable modem.
908 - docsIfCmCmtsAddress: the MAC address of the CMTS
909 to which the CM is connected to(if there is a cable
910 card/ interface in the CMTS, then it is actually the
911 MAC address of the cable interface which connected to.
912 - docsIfDocsisBaseCapability: the highest
913 version of the DOCSIS specification(1.0, 1.1, 2.0)
914 that the device is capable of supporting.
915 - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1)
916 that the CM is operating in.
917 - docsIfCmStatusModulationType the upstream modulation
918 methodology used by the CM the CM).
919 "
920 ::= { docsDevCmNotifs 12 }
922 docsDevCmTODFailNotif NOTIFICATION-TYPE
923 OBJECTS {
924 docsDevEvLevel,
925 docsDevEvId,
926 docsDevEvText,
927 ifPhysAddress,
928 docsIfCmCmtsAddress,
929 docsDevServerTime,
930 docsIfDocsisBaseCapability,
931 docsIfCmStatusDocsisOperMode,
932 docsIfCmStatusModulationType
933 }
934 STATUS current
935 DESCRIPTION
936 "A notification to report a failure of a time of day
937 operation.
939 This notification sends additional information about
940 the event by including the following objects in it's
941 varbinding list.
943 - docsDevEvLevel: the priority level associated with the
944 event.
945 - docsDevEvId: the unique identifier of the event that
946 occurred.
947 - docsDevEvText: a textual description of the event.
948 - ifPhysAddress: the MAC address of the cable
949 interface of this cable modem.
950 - docsIfCmCmtsAddress: the MAC address of the CMTS
951 to which the CM is connected to(if there is a cable
952 card/ interface in the CMTS, then it is actually the
953 MAC address of the cable interface which connected to.
954 - docsDevServerTime: the IP address of the time server.
955 - docsIfDocsisBaseCapability: the highest
956 version of the DOCSIS specification(1.0, 1.1, 2.0)
957 that the device is capable of supporting.
958 - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1)
959 that the CM is operating in.
960 - docsIfCmStatusModulationType the upstream modulation
961 methodology used by the CM the CM).
962 "
963 ::= { docsDevCmNotifs 13 }
965 docsDevCmDCCReqFailNotif NOTIFICATION-TYPE
966 OBJECTS {
967 docsDevEvLevel,
968 docsDevEvId,
969 docsDevEvText,
970 ifPhysAddress,
971 docsIfCmCmtsAddress,
972 docsIfDocsisBaseCapability,
973 docsIfCmStatusDocsisOperMode,
974 docsIfCmStatusModulationType
975 }
976 STATUS current
977 DESCRIPTION
978 " A notification to report a failure of a dynamic channel
979 change request during the dynamic channel change process
980 on the CM.
982 This notification sends additional information about
983 the event by including the following objects in it's
984 varbinding list.
985 - docsDevEvLevel: the priority level associated with the
986 event.
987 - docsDevEvId: the unique identifier of the event that
988 occurred.
989 - docsDevEvText: a textual description of the event.
991 - ifPhysAddress: the MAC address of the cable
992 interface of this cable modem.
993 - docsIfCmCmtsAddress: the MAC address of the CMTS
994 to which the CM is connected to(if there is a cable
995 card/ interface in the CMTS, then it is actually the
996 MAC address of the cable interface which connected to.
997 - docsIfDocsisBaseCapability: the highest
998 version of the DOCSIS specification(1.0, 1.1, 2.0)
999 that the device is capable of supporting.
1000 - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1)
1001 that the CM is operating in.
1002 - docsIfCmStatusModulationType the upstream modulation
1003 methodology used by the CM the CM).
1004 "
1005 ::= { docsDevCmNotifs 14 }
1007 docsDevCmDCCRspFailNotif NOTIFICATION-TYPE
1008 OBJECTS {
1009 docsDevEvLevel,
1010 docsDevEvId,
1011 docsDevEvText,
1012 ifPhysAddress,
1013 docsIfCmCmtsAddress,
1014 docsIfDocsisBaseCapability,
1015 docsIfCmStatusDocsisOperMode,
1016 docsIfCmStatusModulationType
1017 }
1018 STATUS current
1019 DESCRIPTION
1020 "A notification to report the failure of a dynamic channel
1021 change response during the dynamic channel
1022 change process on the CM.
1024 This notification sends additional information about
1025 the event by including the following objects in it's
1026 varbinding list.
1027 - docsDevEvLevel: the priority level associated with the
1028 event.
1029 - docsDevEvId: the unique identifier of the event that
1030 occurred.
1031 - docsDevEvText: a textual description of the event.
1032 - ifPhysAddress: the MAC address of the cable
1033 interface of this cable modem.
1034 - docsIfCmCmtsAddress: the MAC address of the CMTS
1035 to which the CM is connected to(if there is a cable
1036 card/ interface in the CMTS, then it is actually the
1037 MAC address of the cable interface which connected to.
1038 - docsIfDocsisBaseCapability: the highest
1039 version of the DOCSIS specification(1.0, 1.1, 2.0)
1040 that the device is capable of supporting.
1041 - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1)
1042 that the CM is operating in.
1043 - docsIfCmStatusModulationType the upstream modulation
1044 methodology used by the CM the CM).
1045 "
1046 ::= { docsDevCmNotifs 15 }
1048 docsDevCmDCCAckFailNotif NOTIFICATION-TYPE
1049 OBJECTS {
1050 docsDevEvLevel,
1051 docsDevEvId,
1052 docsDevEvText,
1053 ifPhysAddress,
1054 docsIfCmCmtsAddress,
1055 docsIfDocsisBaseCapability,
1056 docsIfCmStatusDocsisOperMode,
1057 docsIfCmStatusModulationType
1058 }
1059 STATUS current
1060 DESCRIPTION
1061 "A notification to report the failure of a dynamic channel
1062 change acknowledgement during the dynamic channel
1063 change process on the CM.
1065 This notification sends additional information about
1066 the event by including the following objects in it's
1068 varbinding list.
1069 - docsDevEvLevel: the priority level associated with the
1070 event.
1071 - docsDevEvId: the unique identifier of the event that
1072 occurred.
1073 - docsDevEvText: a textual description of the event.
1074 - ifPhysAddress: the MAC address of the cable
1075 interface of this cable modem.
1076 - docsIfCmCmtsAddress: the MAC address of the CMTS
1077 to which the CM is connected to(if there is a cable
1078 card/ interface in the CMTS, then it is actually the
1079 MAC address of the cable interface which connected to.
1080 - docsIfDocsisBaseCapability: the highest
1081 version of the DOCSIS specification(1.0, 1.1, 2.0)
1082 that the device is capable of supporting.
1083 - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1)
1084 that the CM is operating in.
1085 - docsIfCmtsCmStatusModulationType the upstream modulation
1086 methodology used by the CM the CM).
1087 "
1088 ::= { docsDevCmNotifs 16}
1090 docsDevCmtsInitRegReqFailNotif NOTIFICATION-TYPE
1091 OBJECTS {
1092 docsDevEvLevel,
1093 docsDevEvId,
1094 docsDevEvText,
1095 docsIfCmtsCmStatusMacAddress,
1096 ifPhysAddress,
1097 docsIfCmtsCmStatusDocsisRegMode,
1098 docsIfDocsisBaseCapability,
1099 docsIfCmtsCmStatusModulationType
1100 }
1101 STATUS current
1102 DESCRIPTION
1103 "A notification to report the failure of a registration
1104 request from a CM during the CM initialization
1105 process and detected on the CMTS.
1107 This notification sends additional information about
1108 the event by including the following objects in it's
1109 varbinding list.
1110 - docsDevEvLevel: the priority level associated with the
1111 event.
1112 - docsDevEvId: the unique identifier of the event that
1113 occurred.
1114 - docsDevEvText: a textual description of the event.
1115 - docsIfCmtsCmStatusMacAddress: the MAC address of the CM
1116 for which this notification is associated with.
1117 - ifPhysAddress: the MAC address of the CMTS
1118 (if there is a cable card/ interface in the CMTS,
1119 then it is actually the MAC address of the cable
1120 interface which connected to the CM) cable interface
1121 connected to the CM.
1122 - docsIfCmtsCmStatusDocsisRegMode: the QOS level (1.0, 1.1)
1123 that the reporting CM is operating in.
1124 - docsIfDocsisBaseCapability: the highest
1125 version of the DOCSIS specification(1.0, 1.1, 2.0)
1126 that the device is capable of supporting.
1127 - docsIfCmtsCmStatusModulationType the upstream
1128 modulation methodology used by the CM.
1129 "
1130 ::= { docsDevCmtsNotifs 1 }
1132 docsDevCmtsInitRegRspFailNotif NOTIFICATION-TYPE
1133 OBJECTS {
1134 docsDevEvLevel,
1135 docsDevEvId,
1136 docsDevEvText,
1137 docsIfCmtsCmStatusMacAddress,
1138 ifPhysAddress,
1139 docsIfCmtsCmStatusDocsisRegMode,
1140 docsIfDocsisBaseCapability,
1141 docsIfCmtsCmStatusModulationType
1142 }
1143 STATUS current
1144 DESCRIPTION
1145 "A notification to report the failure of a registration
1146 response during the CM initialization
1147 process and detected by the CMTS.
1149 This notification sends additional information about
1150 the event by including the following objects in it's
1151 varbinding list.
1152 - docsDevEvLevel: the priority level associated with the
1153 event.
1154 - docsDevEvId: the unique identifier of the event that
1155 occurred.
1156 - docsDevEvText: a textual description of the event.
1157 - docsIfCmtsCmStatusMacAddress: the MAC address of the CM
1158 for which this notification is associated with.
1159 - ifPhysAddress: the MAC address of the CMTS
1160 (if there is a cable card/ interface in the CMTS,
1161 then it is actually the MAC address of the cable
1162 interface which connected to the CM) cable interface
1163 connected to the CM.
1164 - docsIfCmtsCmStatusDocsisRegMode: the QOS level (1.0, 1.1)
1165 that the reporting CM is operating in.
1166 - docsIfDocsisBaseCapability: the highest
1167 version of the DOCSIS specification(1.0, 1.1, 2.0)
1168 that the device is capable of supporting.
1169 - docsIfCmtsCmStatusModulationType the upstream
1170 modulation methodology used by the CM.
1171 "
1172 ::= { docsDevCmtsNotifs 2 }
1174 docsDevCmtsInitRegAckFailNotif NOTIFICATION-TYPE
1175 OBJECTS {
1176 docsDevEvLevel,
1177 docsDevEvId,
1178 docsDevEvText,
1179 docsIfCmtsCmStatusMacAddress,
1180 ifPhysAddress,
1181 docsIfCmtsCmStatusDocsisRegMode,
1182 docsIfDocsisBaseCapability,
1183 docsIfCmtsCmStatusModulationType
1184 }
1185 STATUS current
1186 DESCRIPTION
1187 "A notification to report the failure of a registration
1188 acknowledgement from the CM during the CM
1189 initialization process and detected by the CMTS.
1191 This notification sends additional information about
1192 the event by including the following objects in it's
1193 varbinding list.
1194 - docsDevEvLevel: the priority level associated with the
1195 event.
1196 - docsDevEvId: the unique identifier of the event that
1197 occurred.
1198 - docsDevEvText: a textual description of the event.
1199 - docsIfCmtsCmStatusMacAddress: the MAC address of the CM
1200 for which this notification is associated with.
1201 - ifPhysAddress: the MAC address of the CMTS
1202 (if there is a cable card/ interface in the CMTS,
1203 then it is actually the MAC address of the cable
1204 interface which connected to the CM) cable interface
1205 connected to the CM.
1206 - docsIfCmtsCmStatusDocsisRegMode: the QOS level (1.0, 1.1)
1207 that the reporting CM is operating in.
1208 - docsIfDocsisBaseCapability: the highest
1209 version of the DOCSIS specification(1.0, 1.1, 2.0)
1210 that the device is capable of supporting.
1211 - docsIfCmtsCmStatusModulationType the upstream
1212 modulation methodology used by the CM.
1213 "
1214 ::= { docsDevCmtsNotifs 3 }
1216 docsDevCmtsDynServReqFailNotif NOTIFICATION-TYPE
1217 OBJECTS {
1218 docsDevEvLevel,
1219 docsDevEvId,
1220 docsDevEvText,
1221 docsIfCmtsCmStatusMacAddress,
1222 ifPhysAddress,
1223 docsIfCmtsCmStatusDocsisRegMode,
1224 docsIfDocsisBaseCapability,
1225 docsIfCmtsCmStatusModulationType
1227 }
1228 STATUS current
1229 DESCRIPTION
1230 "A notification to report the failure of a dynamic service
1231 request during the dynamic services process
1232 and detected by the CMTS.
1234 This notification sends additional information about
1235 the event by including the following objects in it's
1236 varbinding list.
1237 - docsDevEvLevel: the priority level associated with the
1238 event.
1239 - docsDevEvId: the unique identifier of the event that
1240 occurred.
1241 - docsDevEvText: a textual description of the event.
1242 - docsIfCmtsCmStatusMacAddress: the MAC address of the CM
1243 for which this notification is associated with.
1244 - ifPhysAddress: the MAC address of the CMTS
1245 (if there is a cable card/ interface in the CMTS,
1246 then it is actually the MAC address of the cable
1247 interface which connected to the CM) cable interface
1248 connected to the CM.
1249 - docsIfCmtsCmStatusDocsisRegMode: the QOS level (1.0, 1.1)
1250 that the reporting CM is operating in.
1251 - docsIfDocsisBaseCapability: the highest
1252 version of the DOCSIS specification(1.0, 1.1, 2.0)
1253 that the device is capable of supporting.
1254 - docsIfCmtsCmStatusModulationType the upstream
1255 modulation methodology used by the CM.
1256 "
1257 ::= { docsDevCmtsNotifs 4 }
1259 docsDevCmtsDynServRspFailNotif NOTIFICATION-TYPE
1260 OBJECTS {
1261 docsDevEvLevel,
1262 docsDevEvId,
1263 docsDevEvText,
1264 docsIfCmtsCmStatusMacAddress,
1265 ifPhysAddress,
1266 docsIfCmtsCmStatusDocsisRegMode,
1267 docsIfDocsisBaseCapability,
1268 docsIfCmtsCmStatusModulationType
1269 }
1270 STATUS current
1271 DESCRIPTION
1272 "A notification to report the failure of a dynamic service
1273 response during the dynamic services process
1274 and detected by the CMTS.
1276 This notification sends additional information about
1277 the event by including the following objects in it's
1278 varbinding list.
1279 - docsDevEvLevel: the priority level associated with the
1280 event.
1281 - docsDevEvId: the unique identifier of the event that
1282 occurred.
1283 - docsDevEvText: a textual description of the event.
1284 - docsIfCmtsCmStatusMacAddress: the MAC address of the CM
1285 for which this notification is associated with.
1286 - ifPhysAddress: the MAC address of the CMTS
1287 (if there is a cable card/ interface in the CMTS,
1288 then it is actually the MAC address of the cable
1289 interface which connected to the CM) cable interface
1290 connected to the CM.
1291 - docsIfCmtsCmStatusDocsisRegMode: the QOS level (1.0, 1.1)
1292 that the reporting CM is operating in.
1293 - docsIfDocsisBaseCapability: the highest
1294 version of the DOCSIS specification(1.0, 1.1, 2.0)
1295 that the device is capable of supporting.
1296 - docsIfCmtsCmStatusModulationType the upstream
1297 modulation methodology used by the CM.
1298 "
1299 ::= { docsDevCmtsNotifs 5 }
1301 docsDevCmtsDynServAckFailNotif NOTIFICATION-TYPE
1302 OBJECTS {
1303 docsDevEvLevel,
1304 docsDevEvId,
1305 docsDevEvText,
1306 docsIfCmtsCmStatusMacAddress,
1307 ifPhysAddress,
1308 docsIfCmtsCmStatusDocsisRegMode,
1309 docsIfDocsisBaseCapability,
1310 docsIfCmtsCmStatusModulationType
1311 }
1312 STATUS current
1313 DESCRIPTION
1314 "A notification to report the failure of a dynamic service
1315 acknowledgement during the dynamic services
1316 process and detected by the CMTS.
1318 This notification sends additional information about
1319 the event by including the following objects in it's
1320 varbinding list.
1322 - docsDevEvLevel: the priority level associated with the
1323 event.
1324 - docsDevEvId: the unique identifier of the event that
1325 occurred.
1326 - docsDevEvText: a textual description of the event.
1327 - docsIfCmtsCmStatusMacAddress: the MAC address of the CM
1328 for which this notification is associated with.
1329 - ifPhysAddress: the MAC address of the CMTS
1330 (if there is a cable card/ interface in the CMTS,
1331 then it is actually the MAC address of the cable
1332 interface which connected to the CM) cable interface
1333 connected to the CM.
1334 - docsIfCmtsCmStatusDocsisRegMode: the QOS level (1.0, 1.1)
1335 that the reporting CM is operating in.
1336 - docsIfDocsisBaseCapability: the highest
1337 version of the DOCSIS specification(1.0, 1.1, 2.0)
1338 that the device is capable of supporting.
1339 - docsIfCmtsCmStatusModulationType the upstream
1340 modulation methodology used by the CM.
1341 "
1342 ::= { docsDevCmtsNotifs 6 }
1344 docsDevCmtsBpiInitNotif NOTIFICATION-TYPE
1345 OBJECTS {
1346 docsDevEvLevel,
1347 docsDevEvId,
1348 docsDevEvText,
1349 docsIfCmtsCmStatusMacAddress,
1350 ifPhysAddress,
1351 docsIfCmtsCmStatusDocsisRegMode,
1352 docsIfDocsisBaseCapability,
1353 docsIfCmtsCmStatusModulationType
1354 }
1355 STATUS current
1356 DESCRIPTION
1357 "A notification to report the failure of a BPI
1358 initialization attempt during the CM registration process
1359 and detected by the CMTS.
1361 This notification sends additional information about
1362 the event by including the following objects in it's
1363 varbinding list.
1364 - docsDevEvLevel: the priority level associated with the
1365 event.
1366 - docsDevEvId: the unique identifier of the event that
1367 occurred.
1369 - docsDevEvText: a textual description of the event.
1370 - docsIfCmtsCmStatusMacAddress: the MAC address of the CM
1371 for which this notification is associated with.
1372 - ifPhysAddress: the MAC address of the CMTS
1373 (if there is a cable card/ interface in the CMTS,
1374 then it is actually the MAC address of the cable
1375 interface which connected to the CM) cable interface
1376 connected to the CM.
1377 - docsIfCmtsCmStatusDocsisRegMode: the QOS level (1.0, 1.1)
1378 that the reporting CM is operating in.
1379 - docsIfDocsisBaseCapability: the highest
1380 version of the DOCSIS specification(1.0, 1.1, 2.0)
1381 that the device is capable of supporting.
1382 - docsIfCmtsCmStatusModulationType the upstream
1383 modulation methodology used by the CM.
1384 "
1385 ::= { docsDevCmtsNotifs 7 }
1387 docsDevCmtsBPKMNotif NOTIFICATION-TYPE
1388 OBJECTS {
1389 docsDevEvLevel,
1390 docsDevEvId,
1391 docsDevEvText,
1392 docsIfCmtsCmStatusMacAddress,
1393 ifPhysAddress,
1394 docsIfCmtsCmStatusDocsisRegMode,
1395 docsIfDocsisBaseCapability,
1396 docsIfCmtsCmStatusModulationType
1397 }
1398 STATUS current
1399 DESCRIPTION
1400 "A notification to report the failure of a BPKM operation
1401 which is detected by the CMTS.
1403 This notification sends additional information about
1404 the event by including the following objects in it's
1405 varbinding list.
1406 - docsDevEvLevel: the priority level associated with the
1407 event.
1408 - docsDevEvId: the unique identifier of the event that
1409 occurred.
1410 - docsDevEvText: a textual description of the event.
1411 - docsIfCmtsCmStatusMacAddress: the MAC address of the CM
1412 for which this notification is associated with.
1413 - ifPhysAddress: the MAC address of the CMTS
1414 (if there is a cable card/ interface in the CMTS,
1415 then it is actually the MAC address of the cable
1416 interface which connected to the CM) cable interface
1417 connected to the CM.
1418 - docsIfCmtsCmStatusDocsisRegMode: the QOS level (1.0, 1.1)
1419 that the reporting CM is operating in.
1420 - docsIfDocsisBaseCapability: the highest
1421 version of the DOCSIS specification(1.0, 1.1, 2.0)
1422 that the device is capable of supporting.
1423 - docsIfCmtsCmStatusModulationType the upstream
1424 modulation methodology used by the CM.
1425 "
1426 ::= { docsDevCmtsNotifs 8 }
1428 docsDevCmtsDynamicSANotif NOTIFICATION-TYPE
1429 OBJECTS {
1430 docsDevEvLevel,
1431 docsDevEvId,
1432 docsDevEvText,
1433 docsIfCmtsCmStatusMacAddress,
1434 ifPhysAddress,
1435 docsIfCmtsCmStatusDocsisRegMode,
1436 docsIfDocsisBaseCapability,
1437 docsIfCmtsCmStatusModulationType
1438 }
1439 STATUS current
1440 DESCRIPTION
1441 "A notification to report the failure of a dynamic security
1442 association operation which is detected by the CMTS.
1444 This notification sends additional information about
1445 the event by including the following objects in it's
1446 varbinding list.
1448 - docsDevEvLevel: the priority level associated with the
1449 event.
1450 - docsDevEvId: the unique identifier of the event that
1451 occurred.
1452 - docsDevEvText: a textual description of the event.
1453 - docsIfCmtsCmStatusMacAddress: the MAC address of the CM
1454 for which this notification is associated with.
1455 - ifPhysAddress: the MAC address of the CMTS
1456 (if there is a cable card/ interface in the CMTS,
1457 then it is actually the MAC address of the cable
1458 interface which connected to the CM) cable interface
1459 connected to the CM.
1460 - docsIfCmtsCmStatusDocsisRegMode: the QOS level (1.0, 1.1)
1461 that the reporting CM is operating in.
1462 - docsIfDocsisBaseCapability: the highest
1463 version of the DOCSIS specification(1.0, 1.1, 2.0)
1464 that the device is capable of supporting.
1465 - docsIfCmtsCmStatusModulationType the upstream
1466 modulation methodology used by the CM.
1467 "
1468 ::= { docsDevCmtsNotifs 9 }
1470 docsDevCmtsDCCReqFailNotif NOTIFICATION-TYPE
1471 OBJECTS {
1472 docsDevEvLevel,
1473 docsDevEvId,
1474 docsDevEvText,
1475 docsIfCmtsCmStatusMacAddress,
1476 ifPhysAddress,
1477 docsIfCmtsCmStatusDocsisRegMode,
1478 docsIfDocsisBaseCapability,
1479 docsIfCmtsCmStatusModulationType
1480 }
1481 STATUS current
1482 DESCRIPTION
1484 "A notification to report the failure of a dynamic channel
1485 change request during the dynamic channel
1486 change process and is detected by the CMTS.
1488 This notification sends additional information about
1489 the event by including the following objects in it's
1490 varbinding list.
1491 - docsDevEvLevel: the priority level associated with the
1492 event.
1493 - docsDevEvId: the unique identifier of the event that
1494 occurred.
1495 - docsDevEvText: a textual description of the event.
1496 - docsIfCmtsCmStatusMacAddress: the MAC address of the CM
1497 for which this notification is associated with.
1498 - ifPhysAddress: the MAC address of the CMTS
1499 (if there is a cable card/ interface in the CMTS,
1500 then it is actually the MAC address of the cable
1501 interface which connected to the CM) cable interface
1502 connected to the CM.
1503 - docsIfCmtsCmStatusDocsisRegMode: the QOS level (1.0, 1.1)
1504 that the reporting CM is operating in.
1505 - docsIfDocsisBaseCapability: the highest
1506 version of the DOCSIS specification(1.0, 1.1, 2.0)
1507 that the device is capable of supporting.
1508 - docsIfCmtsCmStatusModulationType the upstream
1509 modulation methodology used by the CM.
1510 "
1511 ::= { docsDevCmtsNotifs 10 }
1513 docsDevCmtsDCCRspFailNotif NOTIFICATION-TYPE
1514 OBJECTS {
1515 docsDevEvLevel,
1516 docsDevEvId,
1517 docsDevEvText,
1518 docsIfCmtsCmStatusMacAddress,
1519 ifPhysAddress,
1520 docsIfCmtsCmStatusDocsisRegMode,
1521 docsIfDocsisBaseCapability,
1522 docsIfCmtsCmStatusModulationType
1524 }
1525 STATUS current
1526 DESCRIPTION
1527 "A notification to report the failure of a dynamic channel
1528 change response during the dynamic channel
1529 change process and is detected by the CMTS.
1531 This notification sends additional information about
1532 the event by including the following objects in it's
1533 varbinding list.
1534 - docsDevEvLevel: the priority level associated with the
1535 event.
1536 - docsDevEvId: the unique identifier of the event that
1537 occurred.
1538 - docsDevEvText: a textual description of the event.
1540 - docsIfCmtsCmStatusMacAddress: the MAC address of the CM
1541 for which this notification is associated with.
1542 - ifPhysAddress: the MAC address of the CMTS
1543 (if there is a cable card/ interface in the CMTS,
1544 then it is actually the MAC address of the cable
1545 interface which connected to the CM) cable interface
1546 connected to the CM.
1547 - docsIfCmtsCmStatusDocsisRegMode: the QOS level (1.0, 1.1)
1548 that the reporting CM is operating in.
1549 - docsIfDocsisBaseCapability: the highest
1550 version of the DOCSIS specification(1.0, 1.1, 2.0)
1551 that the device is capable of supporting.
1552 - docsIfCmtsCmStatusModulationType the upstream
1553 modulation methodology used by the CM.
1554 "
1555 ::= { docsDevCmtsNotifs 11 }
1557 docsDevCmtsDCCAckFailNotif NOTIFICATION-TYPE
1558 OBJECTS {
1559 docsDevEvLevel,
1560 docsDevEvId,
1561 docsDevEvText,
1562 docsIfCmtsCmStatusMacAddress,
1563 ifPhysAddress,
1564 docsIfCmtsCmStatusDocsisRegMode,
1565 docsIfDocsisBaseCapability,
1566 docsIfCmtsCmStatusModulationType
1567 }
1568 STATUS current
1569 DESCRIPTION
1570 "A notification to report the failure of a dynamic channel
1571 change acknowledgement during the dynamic channel
1572 change process and is detected by the CMTS.
1574 This notification sends additional information about
1575 the event by including the following objects in it's
1576 varbinding list.
1577 - docsDevEvLevel: the priority level associated with the
1578 event.
1579 - docsDevEvId: the unique identifier of the event that
1580 occurred.
1581 - docsDevEvText: a textual description of the event.
1582 - docsIfCmtsCmStatusMacAddress: the MAC address of the CM
1583 for which this notification is associated with.
1584 - ifPhysAddress: the MAC address of the CMTS
1585 (if there is a cable card/ interface in the CMTS,
1586 then it is actually the MAC address of the cable
1587 interface which connected to the CM) cable interface
1588 connected to the CM.
1589 - docsIfCmtsCmStatusDocsisRegMode: the QOS level (1.0, 1.1)
1590 that the reporting CM is operating in.
1591 - docsIfDocsisBaseCapability: the highest
1592 version of the DOCSIS specification(1.0, 1.1, 2.0)
1593 that the device is capable of supporting.
1594 - docsIfCmtsCmStatusModulationType the upstream
1595 modulation methodology used by the CM.
1596 "
1597 ::= { docsDevCmtsNotifs 12}
1599 --
1600 --Conformance definitions
1601 --
1603 docsDevNotifConformance OBJECT IDENTIFIER
1604 ::= { docsDevNotifMIB 4 }
1606 docsDevNotifGroups OBJECT IDENTIFIER
1607 ::= { docsDevNotifConformance 1 }
1608 docsDevNotifCompliances OBJECT IDENTIFIER
1609 ::= { docsDevNotifConformance 2 }
1610 docsDevCmNotifCompliance MODULE-COMPLIANCE
1611 STATUS current
1612 DESCRIPTION
1613 "The compliance statement for CM Notifications and Control"
1615 MODULE --docsDevNotif
1616 MANDATORY-GROUPS {
1617 docsDevCmNotifControlGroup,
1618 docsDevCmNotificationGroup
1619 }
1621 ::= { docsDevNotifCompliances 1 }
1623 docsDevCmNotifControlGroup OBJECT-GROUP
1624 OBJECTS {
1625 docsDevCmNotifControl
1626 }
1627 STATUS current
1628 DESCRIPTION
1629 "This group represents objects to allow control
1630 over CM Notifications."
1631 ::= { docsDevNotifGroups 1 }
1633 docsDevCmNotificationGroup NOTIFICATION-GROUP
1634 NOTIFICATIONS {
1635 docsDevCmInitTLVUnknownNotif,
1636 docsDevCmDynServReqFailNotif,
1637 docsDevCmDynServRspFailNotif,
1638 docsDevCmDynServAckFailNotif,
1639 docsDevCmBpiInitNotif,
1640 docsDevCmBPKMNotif,
1641 docsDevCmDynamicSANotif,
1642 docsDevCmDHCPFailNotif,
1643 docsDevCmSwUpgradeInitNotif,
1644 docsDevCmSwUpgradeFailNotif,
1645 docsDevCmSwUpgradeSuccessNotif,
1646 docsDevCmSwUpgradeCVCFailNotif,
1647 docsDevCmTODFailNotif,
1648 docsDevCmDCCReqFailNotif,
1649 docsDevCmDCCRspFailNotif,
1650 docsDevCmDCCAckFailNotif
1651 }
1652 STATUS current
1653 DESCRIPTION
1654 "A collection of CM notifications providing device status
1655 and control."
1657 ::= { docsDevNotifGroups 2 }
1659 docsDevCmtsNotifCompliance MODULE-COMPLIANCE
1660 STATUS current
1661 DESCRIPTION
1662 "The compliance statement for DOCSIS CMTS Notification
1663 and Control."
1664 MODULE --docsDevNotif
1665 MANDATORY-GROUPS {
1666 docsDevCmtsNotifControlGroup,
1667 docsDevCmtsNotificationGroup
1668 }
1670 ::= { docsDevNotifCompliances 2 }
1672 docsDevCmtsNotifControlGroup OBJECT-GROUP
1673 OBJECTS {
1674 docsDevCmtsNotifControl
1675 }
1676 STATUS current
1677 DESCRIPTION
1678 "This group represents objects to allow control
1679 over CMTS Notifications."
1680 ::= { docsDevNotifGroups 3 }
1682 docsDevCmtsNotificationGroup NOTIFICATION-GROUP
1683 NOTIFICATIONS {
1684 docsDevCmtsInitRegReqFailNotif,
1685 docsDevCmtsInitRegRspFailNotif,
1686 docsDevCmtsInitRegAckFailNotif ,
1687 docsDevCmtsDynServReqFailNotif,
1688 docsDevCmtsDynServRspFailNotif,
1689 docsDevCmtsDynServAckFailNotif,
1690 docsDevCmtsBpiInitNotif,
1691 docsDevCmtsBPKMNotif,
1692 docsDevCmtsDynamicSANotif,
1693 docsDevCmtsDCCReqFailNotif,
1694 docsDevCmtsDCCRspFailNotif,
1695 docsDevCmtsDCCAckFailNotif
1696 }
1697 STATUS current
1698 DESCRIPTION
1699 "A collection of CMTS notifications providing device
1700 status and control."
1701 ::= { docsDevNotifGroups 4 }
1703 END
1705 5. Contributors
1707 Thanks goes to the following people who have made significant
1708 contributions to this document: Junming Gao, Jean-Francois Mule, Dave
1709 Raftus, Pak Siripunkaw, and Rich Woundy.
1711 6. Acknowledgments
1713 This document was produced by the IPCDN Working Group. Thanks to
1714 Harrie Hazewinkel and Bert Wijnen for their thorough review and
1715 insightful comments on this document. Special thanks to Rich Woundy,
1716 who made several valuable suggestions to improve the notifications.
1718 7. Security Consideration
1720 There are two management objects defined in this MIB module with a
1721 MAX-ACCESS clause of read-write and/or read-create
1722 (docsDevCmNotifControl and docsDevCmtsNotifControl). Such objects
1723 may be considered sensitive or vulnerable in some network
1724 environments. The support for SET operations in a non-secure
1725 environment without proper protection can have a negative effect on
1726 network operations.
1728 Setting docsDevCmNotifControl or docsDevCmtsNotifControl may cause
1729 flooding of notifications, which can disrupt network service.
1730 Besides causing "flooding", changing the objects can also mean that
1731 notifications will not be emitted while one intended that to happen.
1733 This MIB defines a number of notification objects that send detailed
1734 information about the event that caused the generation of the
1735 notification. Information included in the notification message
1736 include: event priority, the event Id, the event message body, the CM
1737 DOCSIS capability, the CM DOCSIS QOS level, the CM DOCSIS upstream
1738 modulation type, the cable interface MAC address of the cable modem
1739 and, the cable card MAC address of the CMTS to which the modem is
1740 connected. The monitoring of these notification messages could be
1741 used to gather information about the state of the network and devices
1742 (CM and CMTS) attached to the network.
1744 SNMP versions prior to SNMPv3 did not include adequate security.
1745 Even if the network itself is secure (for example by using IPSec),
1746 even then, there is no control as to who on the secure network is
1747 allowed to access and GET/SET (read/change/create/delete) the objects
1748 in this MIB module.
1750 It is RECOMMENDED that implementers consider the security features as
1751 provided by the SNMPv3 framework (see [16], section 8),including full
1752 support for the SNMPv3 cryptographic mechanisms (for authentication
1753 and privacy).
1755 Further, deployment of SNMP versions prior to SNMPv3 is NOT
1756 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
1757 enable cryptographic security. It is then a customer/operator
1758 responsibility to ensure that the SNMP entity giving access to an
1759 instance of this MIB module is properly configured to give access to
1760 the objects only to those principals (users) that have legitimate
1761 rights to indeed GET or SET (change/create/delete) them.
1763 8. IANA Considerations
1765 The MIB module defined in this document uses the following IANA-
1766 assigned OBJECT IDENTIFIER values recorded in the SMI Numbers
1767 registry:
1769 Descriptor OBJECT IDENTIFIER value
1770 ---------- -----------------------
1771 docsDevNotifMIB { mib-2 xxx }
1773 -- Editor's Note (to be removed prior to publication): the IANA is
1774 requested to assign a value for "xxx" under the 'mib-2' sub-tree and
1775 to record the assignment in the SMI Numbers registry. When the
1776 assignment has been made, the RFC Editor is asked to replace "xxx"
1777 (here and in the MIB module) with the assigned value and to remove
1778 this note.
1780 9. References
1782 9.1 Normative References
1784 [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
1785 Levels", BCP 14, RFC 2119, March 1997.
1787 [2] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
1788 McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of
1789 Management Information Version 2 (SMIv2)", STD 58, RFC 2578,
1790 April 1999.
1792 [3] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
1793 McCloghrie, K., Rose, M. and S. Waldbusser, "Textual
1794 Conventions for SMIv2", STD 58, RFC 2579, April 1999.
1796 [4] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Conformance
1797 Statements for SMIv2", STD 58, RFC 2580, April 1999.
1799 [5] St. Johns, M., "DOCSIS Cable Device MIB Cable Device Management
1800 Information Base for DOCSIS compliant Cable Modems and Cable
1801 Modem Termination Systems", RFC 2669, August 1999.
1803 [6] Raftus, D., "Radio Frequency (RF) Interface Management
1804 Information Base for DOCSIS 2.0 compliant RF interfaces",
1805 -- RFC ED.: replace this reference of
1806 'draft-ietf-ipcdn-docs-rfmibv2-10' with actual RFC reference
1807 and remove this note.
1809 [7] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB",
1810 RFC 2863, June 2000.
1812 [8] SCTE Data Standards Subcommittee, "Data-Over-Cable Service
1813 Interface Specifications: DOCSIS 1.0 Baseline Privacy Interface
1814 Specification SCTE 22-2", 2002,
1815 .
1817 [9] CableLabs, "Baseline Privacy Plus Interface Specification
1818 SP-BPI+040407", April 2004,
1819 .
1821 [10] SCTE Data Standards Subcommittee, "Data-Over-Cable Service
1822 Interface Specifications: DOCSIS 1.0 Operations Support System
1823 Interface Specification Radio Frequency Interface SCTE 22-3",
1824 2002, .
1826 [11] CableLabs, "Data-Over-Cable Service Interface Specifications:
1827 Operations Support System Interface Specification
1828 SP-OSSIv1.1-I07-030703", July 2003,
1829 .
1831 [12] CableLabs, "Data-Over-Cable Service Interface Specifications:
1832 Operations Support System Interface Specification
1833 SP-OSSIv2.0-I07-041210", December 2004,
1834 .
1836 [13] SCTE Data Standards Subcommittee, "Data-Over-Cable Service
1837 Interface Specifications: DOCSIS 1.0 Radio Frequency Interface
1838 Specification SCTE 22-1", 2002,
1839 .
1841 [14] CableLabs, "Data-Over-Cable Service Interface Specifications:
1842 Radio Frequency Interface Specification SP-RFIv1.1-I10-030730",
1843 July 2003, .
1845 [15] CableLabs, "Data-Over-Cable Service Interface Specifications:
1847 Radio Frequency Interface Specification SP-RFIv2.0-I07-041210",
1848 December 2004, .
1850 9.2 Informative References
1852 [16] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction
1853 and Applicability Statements for Internet-Standard Management
1854 Framework", RFC 3410, December 2002.
1856 Authors' Addresses
1858 Azlina Ahmad
1859 Protego Networks, Inc.
1860 1064 Yosemite Drive
1861 Milpitas, CA 95035
1862 US
1864 Phone: 408 262 5220
1865 EMail: azlina@protegonetworks.com
1867 Greg Nakanishi
1868 Motorola
1869 6450 Sequence Dr.
1870 San Diego, CA 92126
1871 US
1873 Phone: 858 404-2366
1874 EMail: gnakanishi@motorola.com
1876 Intellectual Property Statement
1878 The IETF takes no position regarding the validity or scope of any
1879 Intellectual Property Rights or other rights that might be claimed to
1880 pertain to the implementation or use of the technology described in
1881 this document or the extent to which any license under such rights
1882 might or might not be available; nor does it represent that it has
1883 made any independent effort to identify any such rights. Information
1884 on the procedures with respect to rights in RFC documents can be
1885 found in BCP 78 and BCP 79.
1887 Copies of IPR disclosures made to the IETF Secretariat and any
1888 assurances of licenses to be made available, or the result of an
1889 attempt made to obtain a general license or permission for the use of
1890 such proprietary rights by implementers or users of this
1891 specification can be obtained from the IETF on-line IPR repository at
1892 http://www.ietf.org/ipr.
1894 The IETF invites any interested party to bring to its attention any
1895 copyrights, patents or patent applications, or other proprietary
1896 rights that may cover technology that may be required to implement
1897 this standard. Please address the information to the IETF at
1898 ietf-ipr@ietf.org.
1900 Disclaimer of Validity
1902 This document and the information contained herein are provided on an
1903 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
1904 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
1905 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
1906 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
1907 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
1908 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1910 Copyright Statement
1912 Copyright (C) The Internet Society (2005). This document is subject
1913 to the rights, licenses and restrictions contained in BCP 78, and
1914 except as set forth therein, the authors retain all their rights.
1916 Acknowledgment
1918 Funding for the RFC Editor function is currently provided by the
1919 Internet Society.