smilint output for ./PKTC-MTA-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| severe | 16 |
| warning | 9 |
| Message Types |
|---|
| Type | Count |
|---|
| group-unref (warning) | 1 |
| index-exceeds-too-large (warning) | 2 |
| inetaddress-inetaddresstype (warning) | 5 |
| lexical (severe) | 16 |
| sequence-order (warning) | 1 |
Messages:
PKTC-MTA-MIB
1: -- extracted from draft-ietf-ipcdn-pktc-mtamib-00.txt
2: -- at Thu Oct 31 06:10:53 2002
3:
4: PKTC-MTA-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY,
8: OBJECT-TYPE,
9: Integer32,
10: Counter32,
11: NOTIFICATION-TYPE,
12: mib-2
13: FROM SNMPv2-SMI
14: TruthValue,
15: RowStatus,
16: TEXTUAL-CONVENTION
17: FROM SNMPv2-TC
18: OBJECT-GROUP,
19: MODULE-COMPLIANCE,
20: NOTIFICATION-GROUP
21: FROM SNMPv2-CONF
22: InetAddressType, InetAddress
23: FROM INET-ADDRESS-MIB
24: sysDescr
25: FROM SNMPv2-MIB
26: SnmpAdminString
27: FROM SNMP-FRAMEWORK-MIB
28: docsDevSwCurrentVers
29: FROM DOCS-CABLE-DEVICE-MIB; -- version 8
30: pktcMtaMib MODULE-IDENTITY
31: LAST-UPDATED "200210250000Z" -- October 25, 2002
32: ORGANIZATION " PacketCable OSS Group "
33: CONTACT-INFO
34: "Matt Osman
35: Postal: Cable Television Laboratories, Inc.
36: 400 Centennial Parkway Louisville,
37: Colorado 80027-1266
38: U.S.A.
39: Phone: +1 303-661-9100
40: Fax: +1 303-661-9199
41: E-mail: m.osman@cablelabs.com
42:
43: Eugene Nechamkin
44: Postal: Broadcom Corporation,
45: 200-13711 International Place,
46: Richmond, BC, V6V 2Z8
47: Canada
48: Phone: +1 604 233 8500
49: Fax: +1 604 233 8501
50: E-mail: enechamkin@broadcom.com
51:
52: IETF IPCDN Working Group
53: General Discussion: ipcdn@ietf.org
54: Subscribe:
55: http://www.ietf.org/mailman/listinfo/ipcdn
56: Archive:
57: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
58:
59: Co-chairs:
60: Richard Woundy, rwoundy@cisco.com
61: Jean-Francois Mule, jf.mule@cablelabs.com"
62: DESCRIPTION
63: "This is the MIB module for PacketCable 1.x
64: compliant Multimedia Terminal Adapter Devices in
65: Telephony-Over-Cable Systems"
66: REVISION "200210250000Z"
67: DESCRIPTION
68: "Initial Introduction of the draft of the document."
69: ::= { mib-2 99991 } -- to be assigned by IANA
70:
71: -- Textual Conventions
72:
73: X509Certificate ::= TEXTUAL-CONVENTION
74: STATUS current
75: DESCRIPTION
76: "An X509 digital certificate encoded as an ASN.1
77: DER object."
78: SYNTAX OCTET STRING (SIZE (0..4096))
79:
80: --
81: ================================================================
81: severe -
lexically unexpected character, skipping to end of line
82: --
83: -- The MTA MIB only supports a single provisioning server.
84: --
85: --
86: ================================================================
86: severe -
lexically unexpected character, skipping to end of line
87:
88: pktcMtaMibObjects OBJECT IDENTIFIER ::= { pktcMtaMib 1 }
89: pktcMtaDevBase OBJECT IDENTIFIER ::= { pktcMtaMibObjects 1 }
90: pktcMtaDevServer OBJECT IDENTIFIER ::= { pktcMtaMibObjects 2 }
91: pktcMtaDevSecurity OBJECT IDENTIFIER ::= { pktcMtaMibObjects 3 }
92:
93: --
94: -- The following group describes the base objects in the MTA
95: --
96: pktcMtaDevResetNow OBJECT-TYPE
97: SYNTAX TruthValue
98: MAX-ACCESS read-write
99: STATUS current
100: DESCRIPTION
101: "Setting this object to true(1) causes the device
102: to reset. Reading this object always returns
103: false(2). When pktcMtaDevResetNow is set to true,
104: the following actions occur:
105: 1. All connections (if present) are flushed locally.
106: 2. All current actions such as ringing immediately
107: terminate.
108: 3. Requests for notifications such as notification
109: based on digit map recognition are flushed.
110: 4. All endpoints are disabled.
111: 5. The provisioning flow is started at step MTA-1."
112:
113: ::= { pktcMtaDevBase 1 }
114:
115: pktcMtaDevSerialNumber OBJECT-TYPE
116: SYNTAX SnmpAdminString (SIZE (1..128))
117: MAX-ACCESS read-only
118: STATUS current
119: DESCRIPTION
120: "The manufacturer's serial number for this MTA."
121: ::= { pktcMtaDevBase 2 }
122:
123: pktcMtaDevMacAddress OBJECT-TYPE
124: SYNTAX OCTET STRING
125: MAX-ACCESS read-only
126: STATUS current
127: DESCRIPTION
128: "The telephony MAC address for this device."
129: ::= { pktcMtaDevBase 3 }
130:
131: pktcMtaDevFQDN OBJECT-TYPE
132: SYNTAX SnmpAdminString
133: MAX-ACCESS read-only
134: STATUS current
135: DESCRIPTION
136: "The Fully Qualified Domain Name for this MTA."
137: ::= { pktcMtaDevBase 4 }
138:
139: pktcMtaDevEndPntCount OBJECT-TYPE
140: SYNTAX Integer32 (1..255)
141: MAX-ACCESS read-only
142: STATUS current
143: DESCRIPTION
144: "The physical end points for this MTA."
145: ::= { pktcMtaDevBase 5 }
146:
147: pktcMtaDevEnabled OBJECT-TYPE
148: SYNTAX TruthValue
149: MAX-ACCESS read-write
150: STATUS current
151: DESCRIPTION
152: "The MTA Admin Status of this device, where True(1)
153: means the voice feature is enabled and false(2)
154: indicates that it is disabled."
155: ::= { pktcMtaDevBase 6 }
156:
157: pktcMtaDevTypeIdentifier OBJECT-TYPE
158: SYNTAX SnmpAdminString
159: MAX-ACCESS read-only
160: STATUS current
161: DESCRIPTION
162: "This is a copy of the device type identifier used in
163: the DHCP option 60 exchanged between the MTA and the
164: DHCP server."
165: ::= { pktcMtaDevBase 7 }
166:
167: pktcMtaDevProvisioningState OBJECT-TYPE
168: SYNTAX INTEGER
169: {
170: pass(1),
171: inProgress(2),
172: failConfigFileError(3),
173: passWithWarning(4),
174: passWithIncompleteParsing(5),
175: failureInternalError(6),
176: failOtherReason(7)
177: }
178: MAX-ACCESS read-only
179: STATUS current
180: DESCRIPTION
181: "This parameter indicates the completion state of
182: the MTA Device provisioning process. This parameter
183: is sent as part of the final INFORM (step 25 of the
184: MTA provisioning process) refer to the MTA Device
185: provisioning spec for explanation on how an MTA
186: chooses a particular state to report."
187: ::= { pktcMtaDevBase 8 }
188:
189: pktcMtaDevHttpAccess OBJECT-TYPE
190: SYNTAX TruthValue
191: MAX-ACCESS read-only
192: STATUS current
193: DESCRIPTION
194: "This indicates whether HTTP file access is
195: supported for MTA configuration file transfer."
196: ::= { pktcMtaDevBase 9 }
197:
198: pktcMtaDevProvisioningTimer OBJECT-TYPE
199: SYNTAX Integer32 (0..30)
200: UNITS "minutes"
201: MAX-ACCESS read-write
202: STATUS current
203: DESCRIPTION
204: "This object enables setting the duration of the
205: provisioning timeout timer. The timer covers the
206: provisioning sequence from step MTA-1 to step MTA-23.
207: The value is in minutes and setting the timer to 0
208: disables this timer."
209: DEFVAL {10}
210: ::= {pktcMtaDevBase 10}
211:
212: pktcMtaDevProvisioningCounter OBJECT-TYPE
213: SYNTAX Counter32
214: MAX-ACCESS read-only
215: STATUS current
216: DESCRIPTION
217: "This object is the count of the number of times the
218: provisioning cycle has looped through step MTA-1
219: since the last reboot."
220: ::= {pktcMtaDevBase 11}
221:
222: pktcMtaDevErrorOidsTable OBJECT-TYPE
223: SYNTAX SEQUENCE OF PktcMtaDevErrorOidsEntry
224: MAX-ACCESS not-accessible
225: STATUS current
226: DESCRIPTION
227: "If pktcMtaDevProvisioningSate reported with anything
228: other than a pass(1) then this table is populated
229: with the necessary information, each pertaining to
230: observations of the configuration file. Even if
231: different parameters share the same error (ex., All
232: Realm Names are invalid), all recognized errors
233: must be reported as different instances."
234: ::= {pktcMtaDevBase 12}
235:
236: pktcMtaDevErrorOidsEntry OBJECT-TYPE
237: SYNTAX PktcMtaDevErrorOidsEntry
238: MAX-ACCESS not-accessible
239: STATUS current
240: DESCRIPTION
241: "This contains the necessary information an MTA must
242: attempt to provide in case the configuration file
243: is not parsed and/or accepted in its entirety."
244: INDEX { pktcMtaDevErrorOidIndex }
245: ::= {pktcMtaDevErrorOidsTable 1}
246:
247: PktcMtaDevErrorOidsEntry ::= SEQUENCE {
248: pktcMtaDevErrorOidIndex Integer32,
249: pktcMtaDevErrorOid SnmpAdminString,
250: pktcMtaDevErrorValueGiven SnmpAdminString,
251: pktcMtaDevErrorReason SnmpAdminString
252: }
253: pktcMtaDevErrorOidIndex OBJECT-TYPE
254: SYNTAX Integer32 (1..1024)
255: MAX-ACCESS not-accessible
256: STATUS current
257: DESCRIPTION
258: "This is the index to pktcMtaDevErrorOidsEntry. This
259: is an integer value and will start from the value
260: of 1 and be incremented for each error encountered
261: in the configuration file. These indices need not
262: necessarily reflect the order of error occurrences
263: in the configuration file."
264: ::= {pktcMtaDevErrorOidsEntry 1}
265:
266: pktcMtaDevErrorOid OBJECT-TYPE
267: SYNTAX SnmpAdminString
268: MAX-ACCESS read-only
269: STATUS current
270: DESCRIPTION
271: "This is the OID associated with the particular
272: error. If the error was not due to an identifiable
273: OID, then this can be populated with impartial
274: identifiers, in hexadecimal or numeric format."
275: ::= {pktcMtaDevErrorOidsEntry 2}
276:
277: pktcMtaDevErrorValueGiven OBJECT-TYPE
278: SYNTAX SnmpAdminString
279: MAX-ACCESS read-only
280: STATUS current
281: DESCRIPTION
282: "If the error was due to the value associated with
283: the corresponding pktcMtaDevErrorOid, then this
284: contains the value of the OID as interpreted
285: by the MTA in the configuration file provided. If
286: the error was not due to the value of an OID this
287: must be set to an empty string. This is provided
288: to eliminate errors due to
289: misrepresentation/misinterpretation of data."
290: ::= {pktcMtaDevErrorOidsEntry 3}
291:
292: pktcMtaDevErrorReason OBJECT-TYPE
293: SYNTAX SnmpAdminString
294: MAX-ACCESS read-only
295: STATUS current
296: DESCRIPTION
297: "This indicates the reason for the error, as per the
298: MTA's interpretation, in human readable form. EX.:
299: 'VALUE NOT IN RANGE', 'VALUE DOES NOT MATCH TYPE',
300: 'UNSUPPORTED VALUE', 'LAST 4 BITS MUST BE SET TO
301: ZERO', 'OUT OF MEMORY - CANNOT STORE', ..etc.
302: This may also contain vendor specific errors for
303: vendor specific OIDs and any proprietary error
304: codes/messages which can help diagnose errors
305: better, in a manner the vendor deems fit."
306: ::= {pktcMtaDevErrorOidsEntry 4}
307:
308: --
309: -- The following group describes server access and parameters
310: -- used for initial provisioning and bootstrapping.
311: --
312: pktcMtaDevServerDns1 OBJECT-TYPE
312: warning -
warning: `InetAddress' object should have an accompanied preceding `InetAdressType' object
313: SYNTAX InetAddress
314: MAX-ACCESS read-write
315: STATUS current
316: DESCRIPTION
317: "The IP address of the primary DNS server to be used
318: by the MTA to resolve the FQDNs and IP addresses."
319: ::= { pktcMtaDevServer 1 }
320:
321: pktcMtaDevServerDns2 OBJECT-TYPE
321: warning -
warning: `InetAddress' object should have an accompanied preceding `InetAdressType' object
322: SYNTAX InetAddress
323: MAX-ACCESS read-write
324: STATUS current
325: DESCRIPTION
326: "The IP address of the Secondary DNS server to be
327: used by the MTA to resolve the FQDNs and IP
328: addresses. Contains 0.0.0.0 if there is no
329: Secondary DNS server specified for the MTA under
330: consideration."
331: ::= { pktcMtaDevServer 2 }
332:
333: pktcMtaDevConfigFile OBJECT-TYPE
334: SYNTAX SnmpAdminString
335: MAX-ACCESS read-write
336: STATUS current
337: DESCRIPTION
338: "The URL of the TFTP/HTTP file for downloading
339: provisioning and configuration parameters to this
340: device. Returns NULL if the server address is
341: unknown. Supports both TFTP and HTTP."
342: ::= { pktcMtaDevServer 3 }
343:
344: pktcMtaDevSnmpEntity OBJECT-TYPE
345: SYNTAX SnmpAdminString
346: MAX-ACCESS read-write
347: STATUS current
348: DESCRIPTION
349:
350: "The FQDN of the SNMP V3 entity of the Provisioning
351: Server to which the MTA has to communicate in
352: order to receive the access method, location and
353: the name of the Configuration file during MTA
354: provisioning. This would also be the entity which
355: caters to the End-point provisioning needs of the
356: MTA and is the destination for all provisioning
357: informs. It may be also used for post-provisioning
358: SNMP operations."
359: ::= { pktcMtaDevServer 4 }
360:
361: pktcMtaDevProvConfigHash OBJECT-TYPE
362: SYNTAX OCTET STRING (SIZE(16|20))
363: MAX-ACCESS read-write
364: STATUS current
365: DESCRIPTION
366: "Hash of the contents of the config file,
367: calculated and sent to the MTA prior to sending
368: the config file. If the authenthenication
369: algorithm is MD5, the length is 128 bits, If the
370: authentication algorithm is SHA-1, the length is
371: 160 bits."
372: ::= { pktcMtaDevServer 5 }
373:
374: pktcMtaDevProvConfigKey OBJECT-TYPE
375: SYNTAX OCTET STRING (SIZE(0|8))
376: MAX-ACCESS read-write
377: STATUS current
378: DESCRIPTION
379: "Key used to encrypt/decrypt the config file, sent
380: to the MTA prior to sending the config file. If
381: the privacy algorithm is null, the length is 0. If
382: the privacy algorithm is DES, the length is 64
383: bits."
384: ::= { pktcMtaDevServer 6 }
385:
386: pktcMtaDevProvSolicitedKeyTimeout OBJECT-TYPE
387: SYNTAX Integer32 (15..600)
388: UNITS "seconds"
389: MAX-ACCESS read-write
390: STATUS current
391: DESCRIPTION
392: "This timeout applies only when the Provisioning
393: Server initiated key management (with a Wake Up
394: message) for SNMPv3. It is the period during
395: which the MTA will save a nonce (inside the
396: sequence number field) from the sent out AP
397: Request and wait for the matching AP Reply from
398: the Provisioning Server."
399: DEFVAL { 120 }
400: ::= { pktcMtaDevServer 7 }
401:
402: --
403: =================================================================
403: severe -
lexically unexpected character, skipping to end of line
404: --
405: -- Unsolicited Key Updates are based on an exponential backoff
406: -- mechanism with two timers for AS replies. The fast timers
407: -- has a maximum timer
408: -- (pktcMtaDevProvUnsolicitedKeyMaxTimeout seconds) and a
409: -- nominal timer (pktcMtaDevProvUnsolicitedKeyNomTimeout
410: -- seconds) from which the backoff timer determinations
411: -- are made.
412: --
413: --
414: =================================================================
414: severe -
lexically unexpected character, skipping to end of line
415: --
416: =================================================================
416: severe -
lexically unexpected character, skipping to end of line
417: --
418: -- Timeouts for unsolicited key management updates are only
419: -- pertinent before the first SNMP message is sent between the
420: -- MTA and the CMS and before the configuration file is
421: -- loaded. No SNMP communications can
422: -- exist under PacketCable without the security association
423: -- existing. The following object is provided only for
424: -- diagnosistic purposes and are only useful if the MTA can be
425: -- brought up without any security.
426: --
427: --
428: =================================================================
428: severe -
lexically unexpected character, skipping to end of line
429:
430: pktcMtaDevProvUnsolicitedKeyMaxTimeout OBJECT-TYPE
431: SYNTAX Integer32 (15..600)
432: UNITS "seconds"
433: MAX-ACCESS read-only
434: STATUS current
435: DESCRIPTION
436: "This timeout applies to MTA initiated AP-REQ/REP key
437: management exchange with Provisioning Server. The
438: maximum timeout is the value which may not be
439: exceeded in the exponential backoff algorithm."
440: REFERENCE
441: "PacketCable Security Specification [18]"
442: DEFVAL {600}
443: ::= { pktcMtaDevServer 8 }
444:
445: pktcMtaDevProvUnsolicitedKeyNomTimeout OBJECT-TYPE
446: SYNTAX Integer32 (15..600)
447: UNITS "seconds"
448: MAX-ACCESS read-only
449: STATUS current
450: DESCRIPTION
451: "This timeout applies only when the MTA initiated
452: AP-REQ/REP key management. Typically this is the
453: average roundtrip time between the MTA and the
454: Provisioning server."
455: REFERENCE
456: "PacketCable Security Specification [18]"
457: DEFVAL {30}
458: ::= { pktcMtaDevServer 9 }
459:
460: pktcMtaDevProvUnsolicitedKeyMaxRetries OBJECT-TYPE
461: SYNTAX Integer32 (1..32)
462: MAX-ACCESS read-only
463: STATUS current
464: DESCRIPTION
465: "This retries number applies to MTA initiated
466: AP-REQ/REP key management exchange with
467: Provisioning Server. This is the maximum number of
468: retries before the MTA gives up attempting to
469: establish an SNMPv3 security association with
470: Provisioning Server."
471: REFERENCE
472: "PacketCable Security Specification [18]"
473: DEFVAL {8}
474: ::= { pktcMtaDevServer 10 }
475:
476: pktcMtaDevProvKerbRealmName OBJECT-TYPE
477: SYNTAX SnmpAdminString (SIZE(1..255))
478: MAX-ACCESS read-only
479: STATUS current
480: DESCRIPTION
481: "The name of the associated Provisioning Kerberos
482: Realm acquired during MTA4 ( DHCP Ack ). This is
483: used as an index into the pktcMtaDevRealmTable.
484: When used as an index, the upper case ASCII
485: representation of the associated Kerberos Realm
486: name MUST be used by both the Manager(SNMPv3
487: Entity) and the MTA."
488: ::= { pktcMtaDevServer 11 }
489:
490: pktcMtaDevProvState OBJECT-TYPE
491: SYNTAX INTEGER {
492: operational (1),
493: disabled (2),
494: other (3),
495: unknown (4),
496: waitingToStart (10),
497: waitingForDhcpOffer (12),
498: waitingForDhcpAckResponse (14),
499: waitingForProvRealmKdcNameResponse (16),
500: waitingForProvRealmKdcAddrResponse (18),
501: waitingForAsReply (20),
502: waitingForTgsReply (22),
503: waitingForApReply (24),
504: waitingForSnmpGetRequest (26),
505: waitingForSnmpSetInfo (28),
506: waitingForTftpAddrResponse (30),
507: waitingForConfigFile (32),
508: waitingForTelRealmKdcNameResponse (34),
509: waitingForTelRealmKdcAddrResponse (36),
510: waitingForPkinitAsReply (38),
511: waitingForCmsKerbTickTgsReply (40),
512: waitingForCmsKerbTickApReply (42)
513: }
514: MAX-ACCESS read-only
515: STATUS current
516: DESCRIPTION
517: "If operational(1), the device has completed
518: loading and processing of initialization
519: parameters.
520: If disabled(2) then the device was
521: administratively disabled, possibly by being
522: refused network access in the configuration file.
523: If waitingToStart(10) then the MTA is has not
524: received a signal to start initialization.
525: If waitingForDhcpOffer(12) then a DHCP Discover
526: has been transmitted and no offer has yet been
527: received.
528: If waitingForDhcpAckResponse(14) then a
529: DHCP Request has been transmitted and no response
530: has yet been received.
531: If waitingProvRealmKdcNameResponse(16) then a DNS
532: Srv request has been transmitted and no reply
533: has yet been received.
534: If waitingForProvRealmKdcAddrResponse(18) then a
535: DNS request has been transmitted and no reply has
536: yet been received.
537: If waitingForAsReply(20) then an AS request has
538: been and no MSO KDC AS Kerberos ticket reply has
539: yet been received.
540: If waitingForTgsReply(22) then a TGS request has
541: been transmitted and no TGS ticket reply has yet
542: been received.
543: If waitingForApReply(24) then an AP request has
544: been transmitted and no SNMPv3 key info reply has
545: yet been received.
546: If waitingForSnmpGetRequest(26) then an INFORM
547: message has been transmitted and the device is
548: waiting on optional/iterative GET requests.
549: If waitingForSnmpSetInfo(28) then the device is
550: waiting on config file download access
551: information.
552: If waitingForTftpAddrResponse(30) then a DNS
553: request has been transmitted and no reply has yet
554: been received.
555: If waitingForConfigFile(32) then a TFTP request has
556: been transmitted and no reply has yet been
557: received or a download is in progress.
558: If waitingForTelRealmKdcNameResponse(34) then a DNS
559: Srv request has been transmitted and no name reply
560: has yet been received.
561: If waitingForTelRealmKdcAddrResponse(36) then a DNS
562: request has been transmitted and no address reply
563: has yet been received.
564: If waitingForPkinitAsReply(38) then an AS request
565: has been transmitted and no ticket reply has yet
566: been received.
567:
568: If waitingForCmsKerbTickTgsReply(40) then a TGS
569: request has been transmitted and no ticket reply
570: has yet been received.
571: If waitingForCmsKerbTickApReply(42) then a AP
572: request has been transmitted and no Ipsec
573: parameters reply has yet been received."
574: REFERENCE
575: "PacketCable Provisioning Specification
576: PacketCable Security Specification [18]"
577: ::= { pktcMtaDevServer 12 }
578:
579: pktcMtaDevServerDhcp1 OBJECT-TYPE
579: warning -
warning: `InetAddress' object should have an accompanied preceding `InetAdressType' object
580: SYNTAX InetAddress
581: MAX-ACCESS read-only
582: STATUS current
583: DESCRIPTION
584: "The IP address of the primary DHCP server which
585: would cater to the MTA during its provisioning.
586: Contains 255.255.255.255 if there was no preference
587: given with respect to the DHCP servers for MTA
588: provisioning."
589: ::= { pktcMtaDevServer 13 }
590:
591: pktcMtaDevServerDhcp2 OBJECT-TYPE
591: warning -
warning: `InetAddress' object should have an accompanied preceding `InetAdressType' object
592: SYNTAX InetAddress
593: MAX-ACCESS read-only
594: STATUS current
595: DESCRIPTION
596: "The IP address of the Secondary DHCP server which
597: could cater to the MTA during its provisioning.
598: Contains 0.0.0.0 if there is no specific secondary
599: DHCP server to be considered during MTA
600: provisioning."
601: ::= { pktcMtaDevServer 14 }
602:
603: pktcMtaDevTimeServer OBJECT-TYPE
603: warning -
warning: `InetAddress' object should have an accompanied preceding `InetAdressType' object
604: SYNTAX InetAddress
605: MAX-ACCESS read-write
606: STATUS current
607: DESCRIPTION
608: "This holds the IP address of the Time Server used
609: for Time Synchronization and must be populated in
610: the case of SMTA. Contains 0.0.0.0 if the Time
611: Protocol is not used for time synchronization."
612: ::= { pktcMtaDevServer 15}
613:
614: pktcMtaDevServerDns1AddressType OBJECT-TYPE
615: SYNTAX InetAddressType
616: MAX-ACCESS read-write
617: STATUS current
618: DESCRIPTION
619: "The type of Internet address of the primary DNS
620: server to be used by the MTA to resolve the FQDNs
621: and IP addresses. An Internet address of DNS-type
622: must not be used."
623: ::= { pktcMtaDevServer 16 }
624:
625: pktcMtaDevServerDns2AddressType OBJECT-TYPE
626: SYNTAX InetAddressType
627: MAX-ACCESS read-write
628: STATUS current
629: DESCRIPTION
630: "The type of Internet address of the Secondary DNS
631: server to be used by the MTA to resolve the FQDNs
632: and IP addresses. An Internet address of DNS-type
633: must not be used."
634: ::= { pktcMtaDevServer 17 }
635:
636: pktcMtaDevServerDhcp1AddressType OBJECT-TYPE
637: SYNTAX InetAddressType
638: MAX-ACCESS read-only
639: STATUS current
640: DESCRIPTION
641: "The type of Internet address of the primary DHCP
642: server which would cater to the MTA during its
643: provisioning."
644: ::= { pktcMtaDevServer 18 }
645:
646: pktcMtaDevServerDhcp2AddressType OBJECT-TYPE
647: SYNTAX InetAddressType
648: MAX-ACCESS read-only
649: STATUS current
650: DESCRIPTION
651: "The type of Internet address of the secondary DHCP
652: server which would cater to the MTA during its
653: provisioning."
654: ::= { pktcMtaDevServer 19 }
655:
656: pktcMtaDevTimeServerAddressType OBJECT-TYPE
657: SYNTAX InetAddressType
658: MAX-ACCESS read-write
659: STATUS current
660: DESCRIPTION
661: "The type of Internet address of the Time Server
662: used to obtain the time."
663: ::= { pktcMtaDevServer 20}
664:
665: --
666: -- The following group describes the security objects in the MTA.
667: --
668:
669: pktcMtaDevManufacturerCertificate OBJECT-TYPE
670: SYNTAX X509Certificate
671: MAX-ACCESS read-only
672: STATUS current
673: DESCRIPTION
674: "ASN.1 DER encoding of the MTA Manufacturer's X.509
675: public-key certificate, called MTA Manufacturer
676: Certificate. It is issued to each MTA manufacturer
677: and is installed into each MTA either in the
678: factory or with a code download. The provisioning
679: server cannot update this certificate."
680: ::= {pktcMtaDevSecurity 1}
681:
682: pktcMtaDevCertificate OBJECT-TYPE
683: SYNTAX X509Certificate
684: MAX-ACCESS read-only
685: STATUS current
686: DESCRIPTION
687: "ASN.1 DER encoding of the MTA's X.509 public-key
688: certificate issued by the manufacturer and
689: installed into the embedded-MTA in the factory.
690: This certificate, called MTA Device Certificate,
691: contains the MTA's MAC address. It cannot be
692: updated by the provisioning server."
693: ::= { pktcMtaDevSecurity 2 }
694:
695: pktcMtaDevCorrelationId OBJECT-TYPE
696: SYNTAX Integer32
697: MAX-ACCESS read-only
698: STATUS current
699: DESCRIPTION
700: "Random value generated by the MTA for use in
701: registration authorization. It is for use only in
702: the MTA initialization messages and for MTA
703: configuration file download."
704: ::= { pktcMtaDevSecurity 3 }
705:
706: pktcMtaDevTelephonyRootCertificate OBJECT-TYPE
707: SYNTAX X509Certificate
708: MAX-ACCESS read-only
709: STATUS current
710: DESCRIPTION
711: "ASN.1 DER encoding of the IP Telephony Root X.509
712: public-key certificate stored in the MTA non-
713: volatile memory and updateable with a code download.
714: This certificate is used to validate the initial AS
715: Reply from the KDC received during the MTA
716: initialization."
717: ::= { pktcMtaDevSecurity 4 }
718:
719: --
720: ===================================================================
720: severe -
lexically unexpected character, skipping to end of line
721: --
722: -- Procedures for setting up security associations:
723: --
724: -- A security association may be setup either via
725: -- configuration or via NCS signaling.
726: --
727: -- I. Security association setup via configuration.
728: --
729: -- The realm must be configured first. Associated with
730: -- the realm is a KDC. The realm table
731: -- (pktcMtaDevRealmTable) indicates information about
732: -- realm (e.g., name, organization name) and
733: -- parameters associated with KDC communications (e.g.,
734: -- grace periods, AS request/AS reply adaptive backoff
735: -- parameters).
736: --
737: -- Once the realm is established, one or more servers may
738: -- be defined in the realm. For PacketCable 1.0, these are
739: -- Call Management Servers (CMSs). Associated with each CMS
740: -- entry in the pktcMtaDevCmsTable is an explicit reference
741: -- to a Realm via the realm index
742: -- (pktcMtaDevCmsKerbRealmName), the FQDN of the CMS, and
743: -- parameters associated with IPSec key management with the
744: -- CMS (e.g., clock skew, AP request/AP reply adaptive
745: -- backoff parameters).
746: --
747: --
748: --
749: -- II. Security association setup via NCS signaling.
750: --
751: -- Note: The following process is done automatically by
752: -- the MTA. The NCS is not involved in creating signaled
753: -- entries.
754: -- The current CMS signaling association being used by an
755: -- endpoint is marked as active in CMS MAP table. If NCS
756: -- signaling requests a change of signaling association to
757: -- a different FQDN, the MTA checks the current CMS MAP
758: -- table entries for the affected endpoint. If the entry
759: -- exists in the CMS MAP table, the current CMS MAP table
760: -- entry is marked inactive and the newly chosen CMS MAP
761: -- table entry is marked active.
762: --
763: -- If the entry does not exist in the CMS MAP table, the
764: -- CMS table is checked to determine whether or not it
765: -- contains the CMS specified by CMS signaling (possibly
766: -- a redirection). If the desired CMS entry is defined,
767: -- then a corresponding entry is created and an entry in
768: -- the CMS MAP table is created. If the MTA does not
769: -- have current associations with that CMS, it will now
770: -- perform key management to establish required security
771: -- associations. Once the desired CMS entry is
772: -- established, the current CMS MAP table entry is marked
773: -- inactive and the newly created CMS MAP table entry is
774: -- marked active. Otherwise the current CMS MAP table
775: -- entry remains active and the newly created CMS MAP
776: -- table entry is marked in active.
777: --
778: -- If the entry does not exist in the CMS MAP table and
779: -- the CMS entry does not exist in the CMS table, a new
780: -- CMS table entry should be created. This CMS entry
781: -- should use the same realm as used by this endpoint. The
782: -- default values for the clock skew and AP request/AP
783: -- reply adaptive backoff parameters should be used. The
784: -- MTA will now perform key management to establish
785: -- required security associations. Once the desired CMS
786: -- entry is established, the current CMS MAP table entry
787: -- is marked inactive and the newly created CMS MAP table
788: -- entry is marked active. Otherwise the current CMS MAP
789: -- table entry remains active and the newly created CMS
790: -- MAP table entry is marked inactive.
791: --
792: -- III. When the MTA receives wake-up or re-key messages from a
793: -- CMS, it performs key management based on the
794: -- corresponding entry in the CMS table. If the matching
795: -- CMS entry does not exist, it must ignore the wake-up or
796: -- re-key messages.
797: --
798: --
799: ==================================================================
799: severe -
lexically unexpected character, skipping to end of line
800: --
801: ==================================================================
801: severe -
lexically unexpected character, skipping to end of line
802: --
803: -- pktcMtaDevRealmTable
804: --
805: -- The pktcMtaDevRealmTable shows the KDC realms. The table is
806: -- indexed withpktcMtaDevRealmName. The Realm Table is used in
807: -- conjunction with any server which needs a security
808: -- association with an MTA. The server table (today the CMS)
809: -- has a security association. Each server-MTA security
810: -- association is associated with a single Realm. This allows
811: -- for multiple realms, each with its own security
812: -- association.
813: --
814: --
815: ==================================================================
815: severe -
lexically unexpected character, skipping to end of line
816:
817: pktcMtaDevRealmTable OBJECT-TYPE
818: SYNTAX SEQUENCE OF PktcMtaDevRealmEntry
819: MAX-ACCESS not-accessible
820: STATUS current
821: DESCRIPTION
822: "Contains per Kerberos realm security parameters."
823: ::= { pktcMtaDevSecurity 5 }
824:
825: pktcMtaDevRealmEntry OBJECT-TYPE
825: warning -
warning: index of row `pktcMtaDevRealmEntry' can exceed OID size limit by 139 subidentifier(s)
826: SYNTAX PktcMtaDevRealmEntry
827: MAX-ACCESS not-accessible
828: STATUS current
829: DESCRIPTION
830: "List of security parameters for a single Kerberos
831: realm."
832: INDEX { IMPLIED pktcMtaDevRealmName }
833: ::= { pktcMtaDevRealmTable 1 }
834:
835: PktcMtaDevRealmEntry ::= SEQUENCE {
836: pktcMtaDevRealmName SnmpAdminString,
837: pktcMtaDevRealmPkinitGracePeriod Integer32,
838: pktcMtaDevRealmTgsGracePeriod Integer32,
839: pktcMtaDevRealmOrgName OCTET STRING,
840: pktcMtaDevRealmUnsolicitedKeyMaxTimeout Integer32,
841: pktcMtaDevRealmUnsolicitedKeyNomTimeout Integer32,
842: pktcMtaDevRealmUnsolicitedKeyMaxRetries Integer32,
843: pktcMtaDevRealmStatus RowStatus
844: }
845:
846: pktcMtaDevRealmName OBJECT-TYPE
847: SYNTAX SnmpAdminString (SIZE(1..255))
848: MAX-ACCESS not-accessible
849: STATUS current
850: DESCRIPTION
851: "The corresponding Kerberos Realm name. This is used
852: as an index into pktcMtaDevRealmTable. When used as
853: an index, the upper case ASCII representation of
854: Realm Name MUST be used by both the Manager(SNMPv3
855: Entity) and the MTA."
856: ::= { pktcMtaDevRealmEntry 1 }
857:
858:
859: pktcMtaDevRealmPkinitGracePeriod OBJECT-TYPE
860: SYNTAX Integer32 (15..600)
861: UNITS "minutes"
862: MAX-ACCESS read-create
863: STATUS current
864: DESCRIPTION
865: "For the purposes of the key management with an
866: Application Server (CMS or Provisioning Server), the
867: MTA MUST obtain a new Kerberos ticket (with a PKINIT
868: exchange) this many minutes before the old ticket
869: expires. The minimum allowable value is 15 mins. The
870: default is 30 mins. This parameter MAY also be used
871: with other Kerberized applications."
872: DEFVAL { 30 }
873: ::= { pktcMtaDevRealmEntry 2 }
874:
875: pktcMtaDevRealmTgsGracePeriod OBJECT-TYPE
876: SYNTAX Integer32 (1..600)
877: UNITS "minutes"
878: MAX-ACCESS read-create
879: STATUS current
880: DESCRIPTION
881: "When the MTA implementation uses TGS Request/TGS
882: Reply Kerbersos messages for the purpose of the
883: key management with an Application Server (CMS or
884: Provisioning Server), the MTA MUST obtain a new
885: service ticket for the Application Server (with a
886: TGS Request) this many minutes before the old
887: ticket expires. The minimum allowable value is 1
888: min. The default is 10 mins. This parameter MAY
889: also be used with other Kerberized applications."
890: DEFVAL { 10 }
891: ::= { pktcMtaDevRealmEntry 3 }
892:
893: pktcMtaDevRealmOrgName OBJECT-TYPE
894: SYNTAX OCTET STRING (SIZE (1..64))
895: MAX-ACCESS read-create
896: STATUS current
897: DESCRIPTION
898: "The value of the X.500 organization name attribute
899: in the subject name of the Service provider
900: certificate."
901: ::= { pktcMtaDevRealmEntry 4 }
902:
903: --
904: ==================================================================
904: severe -
lexically unexpected character, skipping to end of line
905: --
906: -- Unsolicited Key Updates are based on an exponential backoff
907: -- mechanism with two timers for AS replies. The backoff
908: -- timers has a maximum value of
909: -- pktcMtaDevRealmUnsolicitedKeyMaxTimeout seconds and a
910: -- nominal timer has a
911: -- pktcMtaDevRealmUnsolicitedKeyNomTimeout seconds from which
912: -- the backoff timer determinations are made. After
913: -- pktcMatDevRealmUnsolicitedMaxRetries have occurred no more
914: -- attempts are made.
915: --
916: --
917: ===================================================================
917: severe -
lexically unexpected character, skipping to end of line
918:
919: pktcMtaDevRealmUnsolicitedKeyMaxTimeout OBJECT-TYPE
920: SYNTAX Integer32 (1..600)
921: UNITS "seconds"
922: MAX-ACCESS read-create
923: STATUS current
924: DESCRIPTION
925: "This timeout applies only when the MTA initiated
926: key management.
927: The maximum timeout is the value which may not be
928: exceeded in the exponential backoff algorithm."
929: REFERENCE
930: "PacketCable Security Specification [18]"
931: DEFVAL { 30 }
932: ::= { pktcMtaDevRealmEntry 5 }
933:
934: pktcMtaDevRealmUnsolicitedKeyNomTimeout OBJECT-TYPE
935: SYNTAX Integer32 (100..600000)
936: UNITS "milliseconds"
937: MAX-ACCESS read-create
938: STATUS current
939: DESCRIPTION
940: "This timeout applies only when the MTA initiated
941: key management.
942: This value should account for the average roundtrip
943: time between the MTA and the KDC as well as for the
944: processing delay on the KDC."
945: REFERENCE
946: "PacketCable Security Specification [18]"
947: DEFVAL { 10000 }
948: ::= { pktcMtaDevRealmEntry 6 }
949:
950: pktcMtaDevRealmUnsolicitedKeyMaxRetries OBJECT-TYPE
951: SYNTAX Integer32 (0..1024)
952: MAX-ACCESS read-create
953: STATUS current
954: DESCRIPTION
955: "This is the maximum number of retries before the
956: MTA gives up attempting to establish a security
957: association."
958: REFERENCE
959: "PacketCable Security Specification [18]"
960: DEFVAL { 5 }
961: ::= { pktcMtaDevRealmEntry 7 }
962:
963: pktcMtaDevRealmStatus OBJECT-TYPE
964: SYNTAX RowStatus
965: MAX-ACCESS read-create
966: STATUS current
967: DESCRIPTION
968: "This object contains the Row Status associated with
969: the pktcMtaDevRealmTable."
970: ::= { pktcMtaDevRealmEntry 8 }
971:
972: --
973: ==================================================================
973: severe -
lexically unexpected character, skipping to end of line
974: --
975: -- pktcMtaDevCmsTable
976: --
977: -- The pktcMtaDevCmsTable shows the IPSec key management policy
978: -- relating to a particular CMS. The table is indexed with
979: -- pktcMtaDevCmsFQDN.
980: --
981: --
982: ===================================================================
982: severe -
lexically unexpected character, skipping to end of line
983:
984: pktcMtaDevCmsTable OBJECT-TYPE
985: SYNTAX SEQUENCE OF PktcMtaDevCmsEntry
986: MAX-ACCESS not-accessible
987: STATUS current
988: DESCRIPTION
989: "Contains per CMS key management policy."
990: ::= { pktcMtaDevSecurity 6 }
991:
992: pktcMtaDevCmsEntry OBJECT-TYPE
992: warning -
warning: index of row `pktcMtaDevCmsEntry' can exceed OID size limit by 139 subidentifier(s)
993: SYNTAX PktcMtaDevCmsEntry
994: MAX-ACCESS not-accessible
995: STATUS current
996: DESCRIPTION
997: "List of key management parameters for a single
998: MTA-CMS interface."
999: INDEX { IMPLIED pktcMtaDevCmsFqdn }
1000: ::= { pktcMtaDevCmsTable 1 }
1001:
1002: PktcMtaDevCmsEntry ::= SEQUENCE {
1002: warning -
warning: SEQUENCE element #3 `pktcMtaDevCmsSolicitedKeyTimeout' does not match order of columnar objects under `pktcMtaDevCmsEntry'
1003: pktcMtaDevCmsFqdn SnmpAdminString,
1004: pktcMtaDevCmsKerbRealmName SnmpAdminString,
1005: pktcMtaDevCmsSolicitedKeyTimeout Integer32,
1006: pktcMtaDevCmsMaxClockSkew Integer32,
1007: pktcMtaDevCmsUnsolicitedKeyMaxTimeout Integer32,
1008: pktcMtaDevCmsUnsolicitedKeyNomTimeout Integer32,
1009: pktcMtaDevCmsUnsolicitedKeyMaxRetries Integer32,
1010: pktcMtaDevCmsStatus RowStatus,
1011: pktcMtaDevCmsIpsecCtrl TruthValue
1012: }
1013:
1014: pktcMtaDevCmsFqdn OBJECT-TYPE
1015: SYNTAX SnmpAdminString (SIZE(1..255))
1016: MAX-ACCESS not-accessible
1017: STATUS current
1018: DESCRIPTION
1019: "The fully qualified domain name of the CMS.
1020: This is the index into the pktcMtaDevCmsTable.
1021: When used as an index, the upper case ASCII
1022: representation of the associated CMS FQDN
1023: MUST be used by both the Manager(SNMPv3 Entity)
1024: and the MTA."
1025: ::= { pktcMtaDevCmsEntry 1 }
1026:
1027: pktcMtaDevCmsKerbRealmName OBJECT-TYPE
1028: SYNTAX SnmpAdminString (SIZE(1..255))
1029: MAX-ACCESS read-create
1030: STATUS current
1031: DESCRIPTION
1032: "The Kerberos Realm Name of the associated CMS.
1033: This is the index into the pktcMtaDevRealmTable.
1034: When used as an index, the upper case ASCII
1035: representation of the associated CMS FQDN MUST be
1036: used by both the Manager (SNMPv3 Entity) and the
1037: MTA."
1038: ::= { pktcMtaDevCmsEntry 2 }
1039:
1040: pktcMtaDevCmsMaxClockSkew OBJECT-TYPE
1041: SYNTAX Integer32 (1..1800)
1042: UNITS "seconds"
1043: MAX-ACCESS read-create
1044: STATUS current
1045: DESCRIPTION
1046: "This is the maximum allowable clock skew between
1047: the MTA and CMS."
1048: DEFVAL { 300 }
1049: ::= { pktcMtaDevCmsEntry 3 }
1050:
1051: pktcMtaDevCmsSolicitedKeyTimeout OBJECT-TYPE
1052: SYNTAX Integer32 (100..30000)
1053: UNITS "milliseconds"
1054: MAX-ACCESS read-create
1055: STATUS current
1056: DESCRIPTION
1057: "This timeout applies only when the CMS initiated
1058: key management (with a Wake Up or Rekey message). It
1059: is the period during which the MTA will save a nonce
1060: (inside the sequence number field) from the sent out
1061: AP Request and wait for the matching AP Reply from
1062: the CMS."
1063: REFERENCE
1064: "PacketCable Security Specification [18]"
1065: DEFVAL { 1000 }
1066: ::= { pktcMtaDevCmsEntry 4 }
1067:
1068: --
1069: ===================================================================
1069: severe -
lexically unexpected character, skipping to end of line
1070: --
1071: -- Unsolicited Key Updates are based on an exponential backoff
1072: -- mechanism with two timers for AP replies. The backoff timers
1073: -- has a maximum value of pktcMtaDevCmsUnsolicitedKeyMaxTimeout
1074: -- seconds and a nominal timer has a
1075: -- pktcMtaDevCmsUnsolicitedKeyNomTimeout seconds from which the
1076: -- backoff timer determinations are made. After
1077: -- pktcMatDevCmsUnsolicitedMaxRetries have occurred no more
1078: -- attempts are made.
1079: --
1080: --
1081: ==================================================================
1081: severe -
lexically unexpected character, skipping to end of line
1082:
1083: pktcMtaDevCmsUnsolicitedKeyMaxTimeout OBJECT-TYPE
1084: SYNTAX Integer32 (1..600)
1085: UNITS "seconds"
1086: MAX-ACCESS read-create
1087: STATUS current
1088: DESCRIPTION
1089: "This timeout applies only when the MTA initiated
1090: key management. The maximum timeout is the value
1091: which may not be exceeded in the exponential
1092: backoff algorithm."
1093: REFERENCE
1094: "PacketCable Security Specification [18]"
1095: DEFVAL { 8 }
1096: ::= { pktcMtaDevCmsEntry 5 }
1097:
1098: pktcMtaDevCmsUnsolicitedKeyNomTimeout OBJECT-TYPE
1099: SYNTAX Integer32 (100..30000)
1100: UNITS "milliseconds"
1101: MAX-ACCESS read-create
1102: STATUS current
1103: DESCRIPTION
1104: "This timeout applies only when the MTA initiated
1105: key management. Typically this is the average
1106: roundtrip time between the MTA and the CMS."
1107: REFERENCE
1108: "PacketCable Security Specification [18]"
1109: DEFVAL { 500 }
1110: ::= { pktcMtaDevCmsEntry 6 }
1111:
1112: pktcMtaDevCmsUnsolicitedKeyMaxRetries OBJECT-TYPE
1113: SYNTAX Integer32 (0..1024)
1114: MAX-ACCESS read-create
1115: STATUS current
1116: DESCRIPTION
1117: "This is the maximum number of retries before the
1118: MTA gives up attempting to establish a security
1119: association."
1120: REFERENCE
1121: "PacketCable Security Specification [18]"
1122: DEFVAL { 5 }
1123: ::= { pktcMtaDevCmsEntry 7 }
1124:
1125: pktcMtaDevCmsStatus OBJECT-TYPE
1126: SYNTAX RowStatus
1127: MAX-ACCESS read-create
1128: STATUS current
1129: DESCRIPTION
1130: "This object contains the Row Status associated with
1131: the pktcMtaDevCmsTable."
1132: ::= { pktcMtaDevCmsEntry 8 }
1133:
1134: pktcMtaDevCmsIpsecCtrl OBJECT-TYPE
1135: SYNTAX TruthValue
1136: MAX-ACCESS read-only
1137: STATUS current
1138: DESCRIPTION
1139: "This value of 'true(1)' indicates that IPSec and
1140: IPSec key Management MUST be used to communicate
1141: with the CMS. The value of 'fales(2)' indicates
1142: that IPSec Signaling Security is disabled for both
1143: IPSec Key Management and IPSec protocol (for the
1144: specific CMS)."
1145: DEFVAL { true }
1146: ::= { pktcMtaDevCmsEntry 9 }
1147:
1148: --
1149: -- notification group is for future extension.
1150: --
1151:
1152: pktcMtaNotification OBJECT IDENTIFIER ::= { pktcMtaMib 2 }
1153: pktcMtaNotificationPrefix OBJECT IDENTIFIER ::= {
1154: pktcMtaNotification 0 }
1155: pktcMtaConformance OBJECT IDENTIFIER ::= { pktcMtaMib 3 }
1156: pktcMtaCompliances OBJECT IDENTIFIER ::= { pktcMtaConformance 1 }
1157: pktcMtaGroups OBJECT IDENTIFIER ::= { pktcMtaConformance 2 }
1158:
1159: --
1160: -- Notification Group
1161: --
1162:
1163: pktcMtaDevProvisioningEnrollment NOTIFICATION-TYPE
1164: OBJECTS {
1165: sysDescr,
1166: docsDevSwCurrentVers,
1167: pktcMtaDevTypeIdentifier,
1168: pktcMtaDevMacAddress,
1169: pktcMtaDevCorrelationId
1170: }
1171:
1172: STATUS current
1173: DESCRIPTION
1174: "This inform is issued to initiate the PacketCable
1175: process provisioning."
1176: REFERENCE "Inform as defined in [20]"
1177: ::= { pktcMtaNotificationPrefix 1 }
1178:
1179: pktcMtaDevProvisioningStatus NOTIFICATION-TYPE
1180: OBJECTS {
1181: pktcMtaDevMacAddress,
1182: pktcMtaDevCorrelationId,
1183: pktcMtaDevProvisioningState
1184: }
1185: STATUS current
1186: DESCRIPTION
1187: "This inform is issued to confirm completion of
1188: the PacketCable provisioning process, and indicate
1189: the completion state."
1190: REFERENCE
1191: "Inform as defined in [20]"
1192: ::= { pktcMtaNotificationPrefix 2 }
1193:
1194: -- compliance statements
1195:
1196: pktcMtaBasicCompliance MODULE-COMPLIANCE
1197: STATUS current
1198: DESCRIPTION
1199: "The compliance statement for devices that implement
1200: MTA feature."
1201:
1202: MODULE --pktcMtaMib
1203:
1204: -- unconditionally mandatory groups
1205: MANDATORY-GROUPS {
1206: pktcMtaGroup
1207: }
1208: ::= { pktcMtaCompliances 1 }
1209:
1210: pktcMtaGroup OBJECT-GROUP
1211: OBJECTS {
1212: pktcMtaDevResetNow,
1213: pktcMtaDevSerialNumber,
1214: pktcMtaDevMacAddress,
1215: pktcMtaDevFQDN,
1216: pktcMtaDevEndPntCount,
1217: pktcMtaDevEnabled,
1218: pktcMtaDevErrorOid,
1219: pktcMtaDevErrorValueGiven,
1220: pktcMtaDevErrorReason,
1221: pktcMtaDevTypeIdentifier,
1222: pktcMtaDevProvisioningState,
1223: pktcMtaDevHttpAccess,
1224: pktcMtaDevCertificate,
1225: pktcMtaDevCorrelationId,
1226: pktcMtaDevManufacturerCertificate,
1227: pktcMtaDevServerDhcp1,
1228: pktcMtaDevServerDhcp2,
1229: pktcMtaDevServerDhcp1AddressType,
1230: pktcMtaDevServerDhcp2AddressType,
1231: pktcMtaDevServerDns1,
1232: pktcMtaDevServerDns2,
1233: pktcMtaDevServerDns1AddressType,
1234: pktcMtaDevServerDns2AddressType,
1235: pktcMtaDevTimeServer,
1236: pktcMtaDevTimeServerAddressType,
1237: pktcMtaDevConfigFile,
1238: pktcMtaDevSnmpEntity,
1239: pktcMtaDevRealmPkinitGracePeriod,
1240: pktcMtaDevRealmTgsGracePeriod,
1241: pktcMtaDevRealmOrgName,
1242: pktcMtaDevRealmUnsolicitedKeyMaxTimeout,
1243: pktcMtaDevRealmUnsolicitedKeyNomTimeout,
1244: pktcMtaDevRealmUnsolicitedKeyMaxRetries,
1245: pktcMtaDevRealmStatus,
1246: pktcMtaDevCmsKerbRealmName,
1247: pktcMtaDevCmsUnsolicitedKeyMaxTimeout,
1248: pktcMtaDevCmsUnsolicitedKeyNomTimeout,
1249: pktcMtaDevCmsUnsolicitedKeyMaxRetries,
1250: pktcMtaDevCmsSolicitedKeyTimeout,
1251: pktcMtaDevCmsMaxClockSkew,
1252: pktcMtaDevCmsStatus,
1253: pktcMtaDevCmsIpsecCtrl,
1254: pktcMtaDevProvUnsolicitedKeyMaxTimeout,
1255: pktcMtaDevProvUnsolicitedKeyNomTimeout,
1256: pktcMtaDevProvUnsolicitedKeyMaxRetries,
1257: pktcMtaDevProvKerbRealmName,
1258: pktcMtaDevProvSolicitedKeyTimeout,
1259: pktcMtaDevProvConfigHash,
1260: pktcMtaDevProvConfigKey,
1261: pktcMtaDevProvState,
1262: pktcMtaDevProvisioningTimer,
1263: pktcMtaDevProvisioningCounter,
1264: pktcMtaDevTelephonyRootCertificate
1265: }
1266: STATUS current
1267: DESCRIPTION
1268: "Group of objects for PacketCable MTA MIB."
1269: ::= { pktcMtaGroups 1 }
1270:
1271: pktcMtaNotificationGroup NOTIFICATION-GROUP
1271: warning -
warning: current group `pktcMtaNotificationGroup' is not referenced in this module
1272: NOTIFICATIONS { pktcMtaDevProvisioningStatus,
1273: pktcMtaDevProvisioningEnrollment }
1274: STATUS current
1275: DESCRIPTION
1276: "These notifications deal with change in status of
1277: MTA Device."
1278: ::= { pktcMtaGroups 2 }
1279:
1280: END
1281:
1282: -- Copyright(C) The Internet Society (2001). All Rights Reserved. This
1283: -- document and translations of it may be copied and furnished to
1284: -- others, and derivative works that comment on or otherwise explain it
1285: -- or assist in its implementation may be prepared, copied, published
1286: -- and distributed, in whole or in part, without restriction of any
1287: -- kind, provided that the above copyright notice and this paragraph
1288: -- are included on all such copies and derivative works. However, this
1289: -- document itself may not be modified in any way, such as by removing
1290: -- the copyright notice or references to the Internet Society or other
1291: -- Internet organizations, except as needed for the purpose of
1292: -- developing Internet standards in which case the procedures for
1293: -- copyrights defined in the Internet Standards process must be
1294: -- followed, or as required to translate it into languages other than
1295: -- English.
1296: --
1297: -- The limited permissions granted above are perpetual and will not be
1298: -- revoked by the Internet Society or its successors or assigns.
1299: --
1300: -- This document and the information contained herein is provided on an
1301: -- "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
1302: -- TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
1303: -- BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
1304: -- HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
1305: -- MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1306: --
1307: